How to Audit Your Website for AEO: A Free 2026 Checklist

An AEO audit checks whether AI answer engines — ChatGPT, Perplexity, Claude, and Google AI Overviews — can crawl your site, understand it, and quote it in their answers. It reviews four things: AI-crawler access, machine-readable structure (schema and llms.txt), answer-ready content, and entity signals. This guide gives you a free 10-point checklist to run that audit yourself today.

What is an AEO audit?

AEO stands for Answer Engine Optimization — the practice of getting your content cited inside AI-generated answers instead of (or alongside) the classic blue links. An AEO audit is the diagnostic step: a structured pass over your site to find the reasons an AI engine isn't picking you up.

It's close to a technical SEO audit, but the bar is different. Traditional SEO asks "can Google rank this page?" AEO asks a harder question: "can an LLM read this page, extract a clean answer, trust the source, and quote it?" A page can rank fine on Google and still be invisible to AI engines — usually because the answer is buried, the HTML is empty until JavaScript runs, or the crawler is blocked at the door.

If you want the full framework behind the checklist below, start with our complete Answer Engine Optimization guide. This post is the hands-on audit.

Why does AEO need its own audit?

Three reasons a normal SEO audit misses AEO problems:

1. AI crawlers are separate bots. GPTBot, ClaudeBot, and PerplexityBot are not Googlebot. A robots.txt that welcomes Google can silently block all three. Your SEO tool won't flag this because, to it, the site is perfectly crawlable.
2. AI engines read for extractable answers, not keywords. A page stuffed with the right terms can still fail if there's no clean, self-contained answer an LLM can lift in two sentences.
3. New machine-readable signals exist that SEO tools ignore. llms.txt and answer-shaped FAQ schema are AEO-native. Most SEO audits don't look for them at all.

So you need a checklist built for how answer engines actually behave. Here it is.

The 10-point AEO audit checklist

Work through these in order. The first three are pass/fail gates — if you fail them, nothing else matters because the engine never sees your content. The rest are quality signals that decide whether you get quoted once the engine can read you.

• 1. AI crawlers are allowed in robots.txt. Open yoursite.com/robots.txt and confirm there's no Disallow: / aimed at GPTBot, ClaudeBot, PerplexityBot, Google-Extended, or CCBot. Many CMS and hosting defaults block AI bots by category, so check explicitly rather than assuming. If you need to rebuild the file cleanly, our robots.txt generator has first-class AI-crawler controls. For the directive-by-directive reference, read our robots.txt for AI crawlers guide.

• 2. Pages ship server-rendered HTML. View the raw page source (right-click → View Source, or curl the URL) and check that your actual answer text is present before any JavaScript runs. If the source is a near-empty shell that only fills in inside a browser, AI crawlers that don't execute JS will see nothing. This is the single most common reason a good-looking site earns zero citations.

• 3. An llms.txt file is present. Check for yoursite.com/llms.txt — a plain-text map of your most important pages, written for AI consumption. It's an emerging standard, not yet universal, but it's cheap to add and it tells engines exactly which URLs are your canonical references. See our llms.txt guide for copy-paste templates.

• 4. Key pages open with a direct-answer paragraph. Every important page should answer its main question in the first 40–80 words, in plain prose, before any preamble. AI engines extract these opening paragraphs as quotable chunks. If your answer sits 800 words down the page, it gets skipped. (The intro to this post is an example of the shape you want.)

• 5. Headings are phrased as real questions. Use ## How do I..., ## What is..., ## Why does... for your H2s, matching how people actually phrase prompts. Question-format headings map directly onto the questions users type into ChatGPT and Perplexity, which makes each section a self-contained answer the engine can lift.

• 6. FAQPage schema is present and matches the visible page. Pages with a FAQ section should ship valid FAQPage JSON-LD — and the schema must mirror the on-page Q&A, not invent new ones. Empty or mismatched schema can hurt you. Validate your markup with our free schema markup tester, and follow our FAQ schema implementation guide for the exact JSON-LD.

• 7. Content has high factual density. Count the named entities, specific dates, concrete numbers, and sourced claims on the page. Answer engines prefer content that reads like a reference, not a brochure. "Many businesses use chatbots" is wallpaper; a specific, attributable claim is citable. Replace vague qualifiers — "many", "most", "leading" — with concrete, sourced facts wherever you honestly can.

• 8. Entity and Organization signals are in place. Ship Organization schema with sameAs links to your LinkedIn, X, Crunchbase, and G2 profiles so engines can confirm you're a real, consistent entity. Consistent naming across the web (your "entity footprint") helps an LLM trust and disambiguate your brand.

• 9. Freshness dates are visible. Add a visible "Last reviewed" or "Last updated" date to every long-form page, and actually refresh the content behind it. AI engines — Perplexity especially — lean toward recent sources. A stale-looking page gets deprioritized even when it's authoritative.

• 10. Internal linking ties related pages together. Link your related pages to each other with descriptive anchor text (not "click here"). Internal links help crawlers discover your full content cluster and signal which pages are central. A tight topic cluster — like the AEO posts linked throughout this article — reinforces topical authority for the whole set.

Score yourself: count how many of the ten you pass. Eight or more and you're in good shape. Five to seven means clear, fixable gaps. Four or fewer means AI engines are probably struggling to see you at all — start at the top of the list.

How do I run an AEO audit automatically?

The manual checklist is the most thorough way to learn why a page passes or fails, but you can get a fast machine-graded baseline first, then dig in by hand:

• Run the AEO Score tool on your most important URLs. It scores structured data, answer-ready content, and metadata for cite-ability across Perplexity, ChatGPT, and Google AI Overviews — a quick read on checklist items 4 through 9.
• Run the LLM-Friendly Website Score to grade crawler access, content accessibility, and HTML hygiene — that's items 1, 2, and 3, the pass/fail gates.
• Validate your structured data with the schema markup tester for items 6 and 8.

A practical order: run the two scorers for a baseline, fix the red flags they surface, then walk the full 10-point checklist by hand on your top 5 pages. Re-score after you ship the fixes.

Which pages should I audit first?

You don't need to audit every page on day one. Prioritize:

1. Your highest-intent commercial pages — pricing, product, comparison pages. These are where a citation turns into a customer.
2. Pages that already rank top-10 on Google. For Google AI Overviews, top-10 organic ranking is roughly the entry ticket, so these pages are closest to earning an AI citation. See our Google AI Overviews guide for how that surface picks sources.
3. Long-form guides that answer real questions. These are natural citation bait for Perplexity and ChatGPT.

Audit those first, ship the fixes, then expand outward. Trying to fix the whole site at once is how AEO projects stall.

How often should I re-audit?

Treat AEO as ongoing, not a one-time cleanup:

• Quarterly full audit of your priority pages against the 10-point checklist.
• Monthly content refresh — update dates, add new facts, fix anything that's gone stale.
• Ongoing citation tracking — keep a list of 20–50 queries your customers would actually ask and check weekly whether AI engines cite you. The metric to watch is citation rate over time, not a single position.

The engines change their behavior and so does your content, so a number that was green in January can drift by April. The teams winning AI visibility in 2026 treat it as a discipline, not a project.

FAQ

What is the difference between an AEO audit and an SEO audit?

An SEO audit checks whether search engines can crawl, index, and rank your pages for keywords. An AEO audit checks whether AI answer engines can read your content, extract a clean answer, trust your site as a source, and quote it. They overlap on crawlability and content quality, but AEO adds AI-specific checks: AI-crawler access in robots.txt, llms.txt, answer-shaped formatting, and entity signals. For how to split your effort between the two, see our guide on AEO vs SEO and where to invest.

Is there a free AEO checker I can use?

Yes. Our AEO Score tool grades any URL's cite-ability across Perplexity, ChatGPT, and Google AI Overviews, and the LLM-Friendly Website Score checks crawler access and HTML hygiene. Both are free and run on any public URL. Use them for a fast baseline, then walk the manual 10-point checklist above for the full picture.

How do I check if AI crawlers can access my site?

Open yoursite.com/robots.txt in a browser and look for any Disallow rules targeting GPTBot, ClaudeBot, PerplexityBot, Google-Extended, or CCBot. If those user-agents are blocked, AI engines can't read you. The LLM-Friendly Website Score checks this automatically, and our robots.txt for AI crawlers guide explains every directive.

Does schema markup actually matter for AEO?

Yes. Valid FAQPage, Article, and Organization schema helps AI engines confirm what your content means and that your brand is a real entity. The catch is that the schema must match what's visible on the page — empty or invented FAQ schema can backfire. Validate yours with the schema markup tester and follow the FAQ schema implementation guide.

Why isn't my site being cited by ChatGPT or Perplexity?

The usual suspects, in order: AI crawlers are blocked in robots.txt; the page ships empty HTML that only fills in with JavaScript; the answer is buried far down the page instead of stated up top; or the content is too promotional and light on facts. Work the 10-point checklist from the top — the first three items are pass/fail gates that block everything downstream. For Perplexity specifically, see our how to rank in Perplexity playbook.

How long does it take to see results after fixing AEO issues?

It depends on the fix and your domain's existing authority. Crawler-access and rendering fixes can show up within weeks once engines re-crawl. Content and entity improvements compound more slowly. Track citation rate over a 4–8 week window rather than expecting an overnight jump, and re-run the AEO Score tool after each round of fixes.

Run your audit today

AEO isn't mysterious — it's a checklist. Can the bots reach you, can they read you, can they trust you, and can they quote you? The 10 points above answer all four. Start with the two free scorers for a baseline, fix the gates first, then walk the full list on your top pages.

If you want the strategy behind the tactics, read the complete AEO guide. And if you're building a chatbot or content site and want it AI-readable from day one, InsiteChat ships server-rendered pages and clean structured data out of the box — the same fundamentals this audit checks for.

---

Last reviewed: June 2026.