AEO Audit Checklist for 2026 With 40 Checks

An AEO audit checklist, also called an AI visibility audit, tells you whether AI assistants mention your brand, cite your pages, and describe you accurately. It is not a rebranded SEO audit. Different retrieval, different checks.

Traditional search ranks documents and hands you a list. Answer engines pull passages, stitch them together, and credit a handful of sources. Which means a page can sit at position 3 in Google and never once surface in an AI answer.

This is the AEO audit checklist we run: 40 checks across five parts, plus how it differs from the SEO audit you already have. Every check has a pass condition, so you finish with a score rather than an impression.

What does an AI visibility audit measure?

Three things: whether you appear, whether you get credited, and whether machines can reach you at all. Most audits that go wrong stop at the first.

How do presence, citation, and access differ?

Presence means your brand name shows up in the answer text. Citation means the engine links your page as the source. Not the same thing, and the gap between them is the most useful number you will get out of this.

Access sits underneath both. If a crawler cannot fetch your page, or fetches it and finds an empty shell where the body copy should be, then nothing above it matters and the rest of the audit is measuring noise. Start here whenever presence reads near zero.

Why does the order matter?

Fixing content before fixing access wastes the quarter. A blocked crawler makes every content improvement invisible. So access gets checked early, dull as that part is.

What do you need before you start?

A spreadsheet, a browser, and roughly six hours. No paid tool for a first pass. It does get tedious past about 30 prompts, which is the real reason tracking software exists.

You also need a prompt set built from questions real buyers ask, not keywords you wish you ranked for. Get this wrong and nothing downstream is worth reading.

Pick 20 to 30, spread across three types: category questions with no brand named, comparison questions naming two or more vendors, and branded questions about you specifically.

Part 1: Presence (checks 1 to 10)

Run every prompt on every engine that matters to your market, then record what came back. Per prompt, per engine, presence is binary. No partial credit.

The checks

How do you read the result?

Run each prompt in a fresh session with no history. Personalization and memory will quietly hand you a friendlier answer than a stranger gets (and yes, that is the most common way a self-run audit flatters itself).

Record the raw answer text, not a yes or no. You will want the exact wording later, when you get to accuracy and sentiment.

Part 2: Citation and source share (checks 11 to 18)

Citation is where the audit stops being vanity. Record every source URL the engine credited, not just whether you made the list.

The checks

What do most audits fail to count?

Count who wins the slots you lose. If the same five domains take every citation in your category, that list is your content plan. It tells you which format the engines already trust for that question.

The slot count swings more than most teams expect. In our own July 2026 scan of one audit-related prompt, Perplexity returned 13 cited sources, Claude 11, and Gemini 11. ChatGPT returned none, because it answered without searching at all.

Convert the raw counts into share of voice if you want a single number that compares cleanly against a rival.

Part 3: Technical access for AI crawlers (checks 19 to 28)

This part is boring, and it is where most sites fail. Fetch your own robots.txt and read it line by line before assuming anything. Current agent names sit with OpenAI and Google.

The checks

Which two failures should you check twice?

Check 24 catches the most damage. One wildcard rule, added years ago to hide a staging path, can block an entire content directory from every answer engine at once.

Check 25 is the other. Disable JavaScript, reload your most important page, and watch what survives. If the body copy vanishes, retrieval sees exactly the emptiness you just saw.

Part 4: Content structure (checks 29 to 35)

Answer engines lift passages, not pages. So the audit checks whether your pages contain liftable passages at all.

The checks

What does good look like?

A passage passes when it can be pasted into an answer with no surrounding context and still make sense. That is the whole test.

Checks 33 and 34 are the quiet failures: structured data that no longer matches what the page actually says. Google's structured data policies call that a violation, not a technicality.

Part 5: Entity and off-site signals (checks 36 to 40)

Engines decide what your brand is from the whole web, not from your site alone. These five cover the part you do not own.

What do most audits get wrong?

Five failures account for most bad audits, and four of them happen before a single page is read.

• Testing while logged in. Personalization names your brand from memory, not retrieval, so the score flatters you.
• Merging presence and citation. One combined number hides the only diagnostic worth having.
• Changing the prompt set between runs. An improving score and an easier question list look identical.
• Auditing content before access. Fixes on a page no crawler can fetch change nothing.
• Scoring without competitors. A percentage with no benchmark cannot be called good or bad.

The last one is the most common. Our keyword research puts the cost per click on "ai visibility audit" at $62.08. That tells you how commercially motivated the surrounding advice is, and how little of it carries a benchmark.

How does an AEO audit differ from an SEO audit?

An SEO audit checks whether your pages can rank; an AEO audit checks whether your passages get retrieved, quoted and credited inside an AI answer. Roughly two thirds of the work overlaps, and the third that differs is where most sites fail right now.

They are not competing methods. Google documents that its AI features run on the same core ranking systems as organic search, so a site that fails a standard technical audit usually fails this checklist too, for the same reason.

What does the SEO audit still catch?

Several failure modes still show up only in a traditional audit. Duplicate content and canonical conflicts, redirect chains, crawl budget waste on faceted URLs, Core Web Vitals regressions and internal link architecture all remain SEO findings that no prompt set surfaces.

Indexation is the clearest example. A page missing from Google's index can still be fetched and cited by an answer engine, so the two audits can disagree about the same URL and both be right.

What order should you run them in?

Run one audit with two output sections rather than two engagements, in four stages:

• Technical access, covering both crawler families in one pass (Part 3)
• Indexation and page health, the standard technical layer
• The prompt set, run across every engine that matters to you (Parts 1 and 2)
• Passage structure and entity checks, on whichever pages the prompt set flagged (Parts 4 and 5)

Sequenced this way, the prompt set tells you which pages deserve the effort. Run it before access is confirmed and you produce content fixes for pages nothing can reach.

Are AEO, GEO and AI SEO audits the same thing?

AEO audit, GEO audit, AI SEO audit and AI visibility audit are used interchangeably by most providers. Where a real distinction is drawn, AEO covers direct answers on every answer surface, while GEO means generative engines synthesising and citing you.

For buying purposes, ignore the label and read the method: which engines are tested, how many prompts, and whether crawler access beyond Googlebot is checked.

How do you score the result?

Give one point per passing check and divide by 40. The absolute number matters less than the split across the five parts. Each part has a different fix and a different timeline.

Access problems (Part 3) fix in a day and show up in weeks. Entity problems (Part 5) take quarters. Score badly in Part 3 and well everywhere else and you have the best possible outcome, because the cheapest fix is the one blocking you.

Re-run the same 40 checks on the same prompt set every 8 to 12 weeks. One audit is a snapshot. Snapshots cannot tell you whether anything you changed actually worked.

That second run is also the one teams quietly stop doing, which is the honest reason this turns into a tooling decision rather than a discipline one. Freeze the prompt set and put the re-scan on a calendar, so it happens regardless of who remembers and the before and after stay comparable.