AEO Audit: What It Covers and How to Run One (2026)

The 40-second answer

An AEO audit checks whether AI answer engines can reach, extract, and cite your pages. It covers four areas: crawler access, content structure, schema markup, and current citation visibility. You can run one manually or pull an automated report — SEO AEO Specialist audits all four in one pass for €9 and returns a prioritized fix list.

If you're investing in AEO without an audit, you're guessing. The most common reason pages aren't cited isn't weak content — it's a technical blocker nobody checked. An audit finds it. This page covers exactly what an AEO audit inspects and how to run one, manually or with a tool.

What an AEO audit covers

A complete audit spans four layers. Skip any one and you'll miss the issue that's actually costing you citations.

1. Crawler access

Can answer engines fetch your content at all? This is where most citation losses hide.

• robots.txt rules — are retrieval bots (OAI-SearchBot, PerplexityBot, Claude-SearchBot, ChatGPT-User) allowed? A Q1 2026 audit found 41% of B2B sites block at least one major AI bot, each costing 18-34% of citations on that engine.

• JavaScript rendering — does content appear server-side, or only after client rendering many crawlers skip?

• llms.txt — is there a root-level index pointing engines to your best content?

2. Content structure

Can engines extract clean, citable passages?

• Answer-first capsules (40-60 words) at the top of key pages

• Question-shaped headings that match user prompts

• Self-contained sections that make sense in isolation

• Sequential H2 > H3 > H4 hierarchy — worth a 2.8x citation lift over unstructured pages

• Tables, lists, and citable stats rather than dense prose

3. Schema markup

Can engines parse your pages reliably?

• FAQPage schema on Q&A sections (41% citation rate versus 15% unmarked)

• Valid JSON-LD — the format all major engines rely on

• Appropriate Article, HowTo, Product, and Organization types

4. Citation visibility

Are you actually being cited right now?

• Presence across ChatGPT, Perplexity, and Google AI Mode for your core queries

• Share of voice versus competitors

• A baseline to measure fixes against

How to run an AEO audit

Option A: Manual audit

Doable for a handful of pages, tedious at scale.

1. Check access. Open robots.txt, confirm retrieval bots aren't disallowed. Fetch key pages with JavaScript disabled to see what crawlers see.

2. Grade structure. For each priority page, confirm a 40-60 word answer up top, question headings, standalone sections, and a clean heading hierarchy.

3. Validate schema. Run pages through a JSON-LD validator; confirm FAQPage and other relevant types are present and valid.

4. Test citations. Query ChatGPT, Perplexity, and Google AI Mode for your core terms. Record whether you appear and against whom.

5. Prioritize. Rank issues by impact — access first, then structure, then schema, then authority.

Option B: Automated audit

A tool crawls the way an engine would and returns the prioritized list in one pass — faster, more consistent, and it won't miss a blocked bot on page 40. This is what SEO AEO Specialist does: it inspects access, structure, and schema across your pages and hands back a ranked fix list. A full report is €9, and there's a free tier at €0 for 50 pages/month if you want to try it before paying.

Manual vs automated: which to choose

Reading your audit results

An audit is only useful if you act on it in order:

1. Fix access blockers first. Binary and fast — unblocking a retrieval bot can recover a big share of lost citations.

2. Fix structure next. Add answer capsules and question headings to priority pages.

3. Add schema. FAQPage and JSON-LD where relevant.

4. Re-baseline. Re-test citations after fixes to confirm movement, then set a recurring cadence.

How often to re-audit

Freshness decays and engines change. Re-audit priority pages quarterly, and after any major site or CMS change. Because 83% of AI citations for commercial queries come from pages updated within 12 months, a stale page that passed six months ago may already be slipping.

FAQ