The AEO Audit Checklist I Run Before Touching a Client Domain

An AEO audit checklist is the sequence I run before recommending visibility work on a client domain: baseline what AI already says, inspect entities and machine-readable facts, score citeable content, map citation gaps, and only then propose a roadmap. Skipping straight to “write more blogs” is how budgets burn.

This spoke is the field checklist behind Spurlock Studios visibility audits. The strategic home is the Answer Engine Optimization playbook.

AI visibility audit steps (overview)

1. Scope prompts and competitors
2. Baseline AI answers and accuracy
3. Entity and profile consistency
4. On-site truth layer (llms.txt, schema, canonical pages)
5. Content citeability and cluster coverage
6. Off-site corroboration and citation gaps
7. Technical fetchability
8. Measurement readiness
9. Prioritized roadmap

Below is the detailed checklist. Mark each item pass / fail / n/a with notes.

1. Scope

• Business model and ICP written in one paragraph
• Priority markets / languages listed
• Competitor set (3–6) frozen for the audit
• Prompt panel drafted (25–40) across recommendation, comparison, how-to, brand, local
• Success definition agreed (e.g., citation rate on recommendation prompts)

2. Baseline answers

• Run panel in ChatGPT (buyer-relevant mode)
• Run panel in Perplexity
• Sample Google AI Overviews on priority queries
• Log citation rate, mention rate, SOV, accuracy issues
• Screenshot or archive critical failures

Method notes: Measuring AI Search Visibility.

3. Entity and brand facts

• Fact sheet extracted (name, founded, HQ, offers)
• Conflicts across site vs LinkedIn vs directories listed
• Name collision check completed
• Person entities (founders) consistency spot-checked
• sameAs candidates inventoried

Deep dive: Entity Architecture, Knowledge Panels & Model Memory.

4. On-site truth layer

• /llms.txt exists, fetches cleanly, reads as briefing not sitemap (spec)
• Organization / LocalBusiness JSON-LD valid and aligned (schema)
• Article / FAQ markup honest where present
• About page answers who/what/for whom in first screen
• Primary offer / pricing posture pages extractable
• Old product names redirected or explained

5. Content citeability

• Definition page exists for core category terms
• Comparison or criteria page exists if buyers compare
• How-to / method pages use steps and tables
• Cluster map drafted (pillar + spokes) (clusters)
• Top pages pass “60-word quote” test
• Surfer or equivalent used only as coverage aid — not as pass/fail religion
• Thin / contradictory posts flagged for merge or removal

6. Corroboration and gaps

• URL leaderboard from AI citations built (citation gaps)
• Directory / roundup presence reviewed
• High-value PR targets listed (digital PR)
• Partner / customer case studies on external domains noted
• Toxic or wrong mentions queued for cleanup (hallucinations)

Semrush (or similar) supports competitor and SERP discovery around this step.

7. Local (if applicable)

• NAP matrix across top listings
• GBP categories/services match site
• LocalBusiness schema matches GBP
• Service-area pages quality-reviewed
• Local prompts included in baseline

See Local Business AEO.

8. Technical fetchability

• Key pages 200, indexable, not blocked to relevant crawlers
• Canonical tags sane
• Performance acceptable on primary templates (not a Lighthouse vanity hunt — just not broken)
• Sitemap includes answer pages
• No accidental noindex on About/offer URLs

9. Measurement readiness

• Logging template owned by a named person
• Analytics can show AI referrers where possible
• Monthly reporting stub agreed
• KPI definitions written (citation rate, SOV, accuracy)

10. Roadmap output (what the audit must produce)

• Top 5 risks (accuracy, collisions, legal)
• Top 5 opportunities ranked by revenue × winnability
• 30 / 60 / 90 day plan
• Explicit non-goals (what you will not do yet)
• Tooling notes (what Semrush/Surfer/manual panel will cover)

How long a real audit takes

For a focused SMB or single-product B2B brand: a few intensive days of operator time once access is granted. For multi-location or multi-product orgs: longer on entity and local matrices. Distrust anyone who “finishes AEO” in an afternoon without a prompt panel.

Evidence pack to request from the client

Before kickoff, ask for:

• Analytics access (or exports)
• GBP access or screenshots
• CMS / repo access for schema and llms.txt
• Brand guidelines / press kit
• Top 20 landing pages by revenue or leads
• Known competitors
• Any prior SEO audits (to avoid rework)
• List of product renames in the last 3 years

Missing access is the main cause of shallow audits.

Scoring model (simple)

For each major section (entities, truth layer, content, corroboration, measurement), score 0–5. Average into a headline index for executives, but always show section scores. A shiny content library with broken entities should not look “green.”

Document the rubric in the appendix so the next quarterly audit is comparable.

Sample findings language

Prefer receipts:

Brand query in Perplexity (2026-03-01) stated founding year 2014; About and schema state 2017; Crunchbase states 2014. Recommend reconciling to 2017 across Crunchbase and three directory pages listed in Appendix B.

Avoid:

Your AEO is weak and needs a complete transformation across everything.

What we deliberately skip in v1 audits

• Full backlink detox (unless spam is extreme)
• Entire blog rewrite
• International hreflang programs
• Paid media audits

Call these non-goals so stakeholders do not expect infinity.

After-audit workshop agenda (90 minutes)

1. Baseline KPI screenshots (15)
2. Top risks (15)
3. 30-day truth-layer plan (20)
4. Cluster proposal (20)
5. Resourcing and decision (20)

Leave with yes/no on the 30-day plan. Audits that end in “interesting” without a decision waste the fee.

DIY vs Spurlock Studios

DIY works when you have an SEO lead who will run the panel weekly. Hire an audit when you need an external prioritization hammer, multi-stakeholder alignment, or you suspect identity conflicts you cannot see. The checklist above is the same skeleton either way.

Timeboxing each section

Suggested hours for a single-brand audit when the operator already knows AEO: scope and panel design 2 to 3 hours; baseline runs and logging 3 to 5; entities and profiles 2 to 3; truth layer 2 to 3; content citeability 3 to 4; gaps and PR targets 2 to 3; local and technical as needed 1 to 3; roadmap writeup 2 to 3. Total often lands around 2 to 4 working days elapsed. Multi-location multiplies local hours.

Deliverable outline

Include an executive summary, KPI baseline tables, critical accuracy issues, section scores with checklist appendix, opportunity backlog ranked, a 30/60/90 plan, resource ask, and an appendix with a raw prompt log sample. Keep the full raw log available but not in the main PDF. Executives need decisions; operators need receipts.

Re-audit triggers

Rebrand or rename, major market expansion, merger or acquisition, product line sunset, sudden AI misrepresentation incident, and quarterly reviews if you are actively investing in visibility. Between re-audits, the weekly panel is the heartbeat.

Using this checklist with Spurlock Studios

If you engage us, we run a version of this list, customize the prompt panel to your ICP, and hand back a roadmap tied to the visibility offer. You can also run it internally and hire us only for execution. Either path beats guessing. Bring the filled checklist to visibility conversations so kickoff starts from evidence.

Implementation notes: turning the checklist into tickets

Each failed checkbox should become a ticket with type labels matching the playbook layers: entity, truth-layer, content, corroboration, measurement, technical, local. Estimate effort in half-days. Sort by severity × revenue influence. Resist the urge to open forty tickets on day one — open the ten that unblock the rest (usually fact conflicts, missing About clarity, and measurement).

Attach checklist line IDs in tickets (truth-llms-01) so re-audits can mark lines resolved with evidence URLs. That is how audits become operating systems instead of PDFs.

Edge case: auditing marketplaces and docs subdomains

If docs.live on a subdomain or offers live on a marketplace, include them in the truth-layer and content sections. Many audits stop at www and miss the URL AI actually cites. Add fetch checks and schema checks for those hosts explicitly in the technical section.

Practical week-one kit

Copy this checklist into your tracker. Request the evidence pack. Build the prompt panel. Run baselines before changing anything — otherwise you will never know what worked. Score each section 0 to 5. Present the roadmap with non-goals. Decide whether the next 30 days are self-serve or a Spurlock Studios visibility engagement. Audits that end without a decision are diaries, not audits.

Repeat the kit after major launches. The cost of re-baselining is tiny compared with a quarter of unmeasured content. Keep owners named in the sheet. When someone goes on leave, transfer the ritual explicitly — AEO dies in the handoff gaps. If you need a second pair of eyes, the visibility lane exists for that reason: /visibility and the visibility audit path turn these kits into a managed baseline with a 30/60/90 plan. Either way, ship the ritual before you buy another dashboard logo.

FAQ

What is an AEO audit checklist?

A structured list of checks — prompts, entities, schema, content, corroboration, tech, measurement — used to baseline AI visibility before investing in fixes.

What are the AI visibility audit steps?

Scope → baseline answers → entities → truth layer → content → gaps/PR → local/tech → measurement → roadmap. Details above.

Do we need Semrush and Surfer to audit?

They speed SERP/competitive and on-page coverage review. The non-negotiable core is the multi-product prompt panel plus human review of facts and schema.

Can we self-run this checklist?

Yes for a first pass. Independent audits help when you are blind to your own contradictions or need a prioritized roadmap for stakeholders.

How does this connect to the playbook?

The checklist operationalizes the playbook layers. Use the playbook for strategy depth on each fail.

What happens after the audit?

Ship the 30-day truth-layer fixes first, then cluster content, then corroboration — measuring as you go. Or engage Spurlock Studios to execute.

Closing

Do not touch tactics until you can see citations, conflicts, and gaps on one page. That is the audit.

Run this list yourself, or have us run it as a visibility audit. Lane overview: /visibility. System map: AEO playbook.