AEO Entity-Consistency Audit

---
name: aeo-entity-consistency-audit
description: Weekly audit of your brand descriptions, facts and profiles, with a ranked fix list and an owner-only DM for changes needing a login or decision.
---

# AEO Entity-Consistency Audit

Compare your own pages and public profiles against the canonical brand description, category and company facts. Marketing and engineering teams get exact replacement text for conflicting fields, with login-dependent fixes sent privately to the configured owner. Part of the [Answer Engine Optimization (AEO) skillset](https://type.com/library/skills/answer-engine-optimization).

## When it runs

- Recommended schedule: Thursdays at 9am in `timezone`.
- Post one report to `report_channel` every run. Send at most one DM to `owner`, only when a fix needs that owner's login or a decision.
- With no conflicts, post a short no-action result; omit all-clear lists from the channel.

## Inputs

| Input | What it is | Example |
| --- | --- | --- |
| `brand_name`, `brand_exclusions` | Canonical spelling and look-alike names that must not count | Example, Example Writer |
| `site_url`, `docs_url`, `llms_txt_urls` | Your marketing site, docs and AI-readable summaries | https://example.com, https://docs.example.com, https://example.com/llms.txt |
| `own_surfaces` | Pricing, about/company, security/trust, integrations and top 10 marketing page URLs | https://example.com/pricing |
| `public_profiles` | GitHub org, X bio, LinkedIn company page, YouTube About tab and review profiles | https://github.com/example |
| `brand_mark_url`, `legal_entity` | Current logo or brand mark and legal entity used for searches | https://example.com/icon.png, Example Inc. |
| `master_doc`, `listings_list`, `mcp_tracker` | Positioning/Entity audit doc, listings list and MCP directory tracker | Workspace doc links |
| `content_repo` | Optional read-only repository access to locate affected files | example/website |
| `report_channel`, `owner`, `timezone` | Report channel, sole DM recipient and scheduling timezone | #aeo, @owner, America/Los_Angeles |

## Before you start

- You need web search, plain fetch and a browser-capable read-only fetch, a report-channel connection supporting owner DMs, and scoped shared-doc writes. Repository access is optional and read-only.
- Read the positioning section in the AEO master doc. Establish it with the owner if no approved positioning exists; do not invent canonical facts.
- Reuse the AEO master doc, listings list and MCP directory tracker in your workspace. If absent on first run, create the missing docs and the sections this skill uses, and tell the owner where they are. An empty tracker is not evidence that no profiles exist.
- This audit does not need an AI-answer tracker connection.

## Steps

### 1. Read the canonical sources

Read the current homepage hero, the homepage Organization and SoftwareApplication JSON-LD, and the AEO master doc's positioning section first. If these disagree with one another, make that finding #1.

Write the brand exactly as `brand_name`. Look-alike names in `brand_exclusions` must not count as your brand.

### 2. Fetch your surfaces

Fetch your homepage, pricing, about or company page, security or trust page, integrations page, docs landing page, `llms_txt_urls`, homepage JSON-LD, and OG title, OG description and meta description on the top 10 marketing pages.

Check the GitHub org profile, X bio, LinkedIn company page and YouTube About tab supplied in `public_profiles`.

### 3. Fetch third-party profiles

Check your G2 profile; Capterra or GetApp if present; Crunchbase; Product Hunt; Wellfound; every MCP directory listing recorded in the MCP directory tracker; and every row marked Live in the listings list.

Run 3 web searches: "<brand_name> AI", "<brand_name> <legal_entity>", and "what is <brand_name>". Check the top 10 results for descriptions.

Use browser-capable fetch only when plain fetch is blocked, and never sign in. G2, Crunchbase and Wellfound may return 403 to plain fetches; use the read-only browser fallback for them. Record inaccessible surfaces as unchecked rather than inventing their descriptions.

### 4. Compare every field

Compare the complete field list:

- Company and product name as written, including capitalization, bare-name variants and excluded look-alikes.
- One-sentence description.
- Category: what kind of product it is.
- Who it is for.
- Pricing and plan names.
- Founder names.
- Legal entity.
- Founding year.
- HQ.
- Logo, against `brand_mark_url` or the current brand mark.
- Website URL, against `site_url`.
- Whether the listing points to a dead or redirected page.

Compare to the previous Entity audit to count new conflicts and fixes since last week. Never treat inaccessible surfaces as fixed.

### 5. Update the owned section and report

Create `## Entity audit` in the AEO master doc if missing. Replace only that section's contents each week with the full conflict table and all-clear list. Table columns: surface | field | theirs | canonical | owner | status.

Post the report below, with at most 3 actions. If read-only access to `content_repo` finds a relevant file path, include it for engineering. For owner-operated profiles, provide a verified deep link to the edit screen when available; do not log in or edit anything.

Send at most one private DM, to `owner` only, when a fix needs that owner's login or decision. Otherwise send no DM. Confirm the channel post succeeded before finishing.

## What it posts

Maximum 12 channel lines, with Do next before the headline and evidence:

```text
Do next
1. Eng: change <field> on <own page> from "<theirs>" to "<canonical>" — <file path if found> — <link>
2. <owner>: edit <profile> <field> to "<canonical>" — <deep link to edit screen>
AEO entity audit — <Mon D> · <n> surfaces · <n> conflicts (<n> new) · <n> fixed since last week
Why
• <surface> · <field> · "<theirs>" vs "<canonical>"
• Bare-name variants: <n> · <example 1> · <example 2>
Details → <master doc Entity audit section link>
```

Why has at most 5 one-line bullets for remaining conflicts, including one line for the bare-name count and 2 examples. Omit all-clear lists from the channel.

With no conflicts, use no more than 3 lines: "Do next: nothing this week.", the headline, and the fixed-since-last-week line if relevant.

DM, maximum 4 lines:

```text
<profile> · <field> is "<theirs>"; needs your login or decision.
Edit → <verified edit-screen link>
Paste: <exact canonical text>
Report → <channel message link>
```

## Output rules

- Lead with the action. Every action is one line: owner (<owner>, Eng or agent) + verb + exact surface and field + exact replacement text + link.
- Numbers and quotes, not adjectives. No preamble, "I checked", restating the task or caveats unless they change the action.
- Detail lives in the master doc section, linked once at the end as "Details →".
- Hard caps: channel 12 lines; DM 4 lines. One idea per line.

## Safety

- Read-only on every third party: never submit forms, send email or outreach, sign up, comment, vote or post on Reddit, X, LinkedIn or any social or community site. Draft text for human review only.
- Never change the AI-answer tracker's prompts, monitors, personas, models or schedules.
- Only write posts to `report_channel`, DMs to the configured `owner` only when this skill calls for one, and scoped edits to the named shared docs and sections this skill owns.
- Never @-mention anyone in the channel. Never put credentials, tokens or passwords in posts, docs or DMs.
- Never open PRs, edit the site or change third-party profiles.

## Example configuration

How type.com configures this skill (example):

- Exact brand: type.com; excluded look-alike: type.ai, a separate AI writing editor. The audit counts bare-name and capitalization variants rather than silently treating them as canonical.
- Own surfaces include https://type.com, /pricing, /integrations, docs.type.com, https://type.com/llms.txt and https://github.com/type-dot-com. Legal entity: Savvy Learn, Inc. Logo: https://type.com/icon-512.png.
- Public profiles include @typedotcom, the LinkedIn company page, YouTube About tab, G2, Crunchbase, Product Hunt and MCP directories. Plans include type.com Basic and type.com Pro.
- Report channel: #b-aeo. Owner: Sam. Thursdays at 9am, America/Los_Angeles.
- On Oct 16, 2026 the homepage described type.com three different ways. The Oct 22 dry run found 11 conflicts across 19 surfaces, including older positioning in public profiles. These are historical example findings, not canonical text for your company.