Three ways a free AEO audit works, and which predicts citations

• Intermediate
• High impact
• 12 min read
• AEO fundamentals
• Free audit
• AI citations
• ChatGPT
• Perplexity
• Google AI Overviews

Quick Answer

A free AEO audit is a diagnostic check of whether AI engines such as ChatGPT, Perplexity, and Google AI Overviews can find, retrieve, and cite your content. Three distinct methods exist. Only one of them predicts citations.

The market has produced tools built on three different approaches: rule-based static scoring, live-crawl DOM analysis, and manual brand-visibility testing. Each method refers to a fundamentally different layer of your site's AI readiness. Most buyers never ask which one they're running. A score is a score, until it isn't.

What distinguishes a live-crawl audit from the other two is this: it fetches the rendered DOM the same way GPTBot and ClaudeBot do. It sees the page after JavaScript has run. The others read what the source says, or query what AI engines have learned to say about you. Neither looks at the page as AI crawlers see it at retrieval time. That gap is where most AEO diagnoses fail.

What is a free AEO audit and what does it check?

A free AEO audit is a structured check of whether AI engines can find, fetch, parse, and cite your content. Three distinct methods exist, and only one predicts citations reliably.

An analysis of 18 practitioner sources shows that most people running free AEO tools do not realize the tool they chose determines whether the results mean anything at all. The market has fragmented fast. Web-design studios, solo developers, and enterprise platforms have all shipped free audits in the past twelve months, each working from a different checklist, none sharing a common benchmark. No industry standard exists to compare scores across tools. A score of 81 on one tool and 62 on another may be measuring entirely different things.

Here is what separates them. Call it the methodology test: before reading any free audit result, ask one question. Does this tool fetch the rendered page as an AI crawler sees it, or does it score the static HTML source? That single question sorts the three types.

Rule-based audits read the static HTML source. They check robots.txt permissions for GPTBot, ClaudeBot, and PerplexityBot; schema types like FAQ, HowTo, Article, and Organization; heading hierarchy; author signals; content depth. Fast and free. But they score the HTML a crawler may never see. A page that looks well-formed in source can be empty to an AI engine once JavaScript has run.

Live-crawl audits fetch the rendered DOM. They see what GPTBot and ClaudeBot actually retrieve. This is the only method that catches rendering gaps, the places where content exists in your source but disappears before any AI engine can read it or chunk it.

Manual reviews run a fixed set of prompts across ChatGPT, Gemini, Perplexity, Claude, and Copilot. They log whether your brand appears, what AI engines say about it, and whether the description is accurate and current. They surface brand representation gaps. They cannot detect crawlability failures at all.

According to Rankability's 2026 analysis, pages cited across eight or more distinct queries reach a 43.3% top-10 AI citation rate, versus 15.5% for pages cited on just one query. The takeaway is blunt: what determines citations is not the score any audit assigns. It is whether the rendered page is actually reachable by an AI crawler. That is what the methodology test isolates.

How does a rule-based free AEO audit work?

A rule-based free AEO audit scores your page against a fixed checklist of technical signals, reading the HTML source without ever rendering the page as an AI crawler would.

The checklist varies by tool, but the logic is the same across all of them. The audit fetches your source HTML. It looks for GPTBot, ClaudeBot, and PerplexityBot entries in robots.txt. It checks whether you have JSON-LD schema types present, typically FAQ, HowTo, Article, and Organization. It examines heading hierarchy, paragraph length, presence of author bylines and publication dates, and whether your content has enough depth to be chunked by an AI retrieval system. Some tools also check e-commerce signals, image alt text, and internal linking patterns. The result is a score and a list of prioritized fixes.

This method has real uses. It surfaces structural problems fast. It catches the obvious failures: no schema at all, AI crawlers blocked in robots.txt, thin content on key pages. According to Rankability's 2026 agency tool review, the most useful audit output is not the score itself but whether the audit connects each flag to a concrete action inside a real content workflow. The takeaway is that a rule-based score is a starting point, not a verdict.

The problem is what these tools cannot see. Most sites built after 2020 use JavaScript frameworks that render content in the browser. The HTML source the rule-based tool reads may look structurally sound while the rendered DOM, the actual page GPTBot retrieves and chunks, is nearly empty. Rule-based tools score what the source says. Live-crawl tools score what AI engines see. Those are often different pages.

A second limitation is brand representation. Rule-based tools do not query AI models at all. They cannot tell you whether ChatGPT describes your company accurately, whether your product is being misrepresented by an AI-generated answer, or whether a competitor is appearing in your place when someone asks a buying question. That gap is real. According to Rankability's review, brand visibility tools like HubSpot's free AEO Grader address it: the Grader reveals how ChatGPT, Perplexity, and Gemini characterize your brand, based on what those models have learned. In practice, a brand-visibility check and a crawlability check answer different questions entirely.

The temptation is to run one free tool, see a score, and treat it as a comprehensive picture. It is not. What you see depends entirely on which layer the tool audits.

What does a brand-visibility free AEO audit reveal?

A brand-visibility audit queries AI models directly to show how ChatGPT, Perplexity, and Gemini describe your company, not what your HTML source says.

This is the third category, and it works on entirely different logic from rule-based tools. It does not read your site at all. Instead, it submits prompts to live AI models and captures the responses. It records whether your brand appears, what the AI says about you, whether the description is accurate, and whether competitors are named in your place. The auditor becomes the user.

According to HubSpot's free AEO Grader, the six things a brand-visibility audit tracks are: Brand Visibility, Prompt Performance, Competitor Visibility, Share of Voice, Sentiment, and Citation Analysis. The free Grader provides a one-time snapshot of where you stand across ChatGPT, Perplexity, and Gemini. The paid monitoring product extends that into ongoing tracking at $900 per month. In practice, the free version answers one question clearly: does the AI know who you are and does it describe you correctly today?

What it cannot answer is equally clear. It cannot tell you whether GPTBot can render your pages. It cannot detect a JavaScript framework stripping your content before crawl. It cannot tell you which of your articles are being chunked and embedded into AI retrieval indexes, or which ones are invisible because the rendered DOM is empty.

The contrast here is sharp. According to macronimous's free AEO audit tool, a checklist-style rule-based audit runs 18 distinct checks: GPTBot and ClaudeBot entries in robots.txt, JSON-LD schema types, Core Web Vitals, E-E-A-T signals, heading hierarchy, content depth, and more. Eighteen checks. None of them tell you what the AI model has learned to say about you. Both tools identify real problems. Neither surfaces the other tool's blind spot.

What I have seen working with content teams is that most sites running a single free audit do not realize which layer they checked. They ran a brand check and assumed their crawlability was fine. Or they ran a rule-based check and assumed their AI reputation was clean. The methodology test is not a formality. It changes what the score means.

What questions should you ask any AEO company before trusting their free audit?

Before using any free AEO audit result, ask one question first: does this tool fetch the rendered DOM, or does it score the static HTML source?

This is where the tension in the market lives. The three methods produce scores that look identical to a buyer who does not know to ask. A rule-based tool reports 74 out of 100. A live-crawl tool reports 74 out of 100. A brand-visibility checker shows a passing score. All three numbers land in the same inbox and carry the same apparent authority. The methodology that generated each score is not on the cover sheet.

According to Seal Global's "8 Questions to Ask Search Optimization Consultants," one of the most important evaluative questions is what methodology the consultant uses to measure AI search visibility, and whether that methodology distinguishes between crawlability, content structure, and brand representation in AI-generated answers. In practice, most consultants presenting free audits have not been asked this question. The free audit becomes a credibility prop rather than a diagnostic instrument.

The fragmentation runs deeper than tools. One builder released a Webflow-based free AEO audit checker targeting a visual design audience. Another developer released a separate tool with different checks for a SaaS audience. Neither is compatible with the other. A buyer comparing results from two different free tools is not doing a comparison at all. They are looking at two different operational definitions of AEO fitness.

There is a second friction point. A free audit is a snapshot. AI engine behavior changes between crawl cycles. A page that was citeable in March may be de-indexed in May if a framework update empties the rendered DOM. A brand-visibility check that showed clean sentiment in Q1 may show misrepresentation in Q3 if competitors have published heavily in the interim. The takeaway is that any audit result decays. What matters is whether the methodology underneath it can actually detect the change.

The methodology question does not have a diplomatic answer. Only a live-crawl approach catches rendering failures. That is not a preference. It is a structural fact about how AI crawlers retrieve content.

Which type of free AEO audit actually predicts citations?

Of the three methods, only a live-crawl audit predicts whether your page will actually be retrieved and cited by AI engines. The other two reveal real problems but different ones.

The Reddit r/aeo community's practical guidance on running an AEO audit is instructive here. Practitioners who have done this repeatedly recommend running all three layers, but in a specific order: crawlability first, content structure second, brand representation third. The crawl is the foundation. If the rendered DOM is empty, the structural checks are measuring a page that AI engines never see. No schema type, no author signal, no heading hierarchy matters if GPTBot retrieves nothing.

The decision framework is simple once you understand the layers. Run a live-crawl audit to answer: can AI engines see my pages? Run a rule-based audit to answer: are my pages structured for AI extraction once they can be seen? Run a brand-visibility check to answer: what are AI engines saying about me in conversations where buyers are evaluating options?

These are three different diagnostics. They do not overlap. A site can pass a rule-based check with a high score, be invisible to AI crawlers due to a JavaScript rendering failure, and simultaneously be misrepresented in AI-generated answers by competitor content. All three problems exist independently. All three require a different tool to detect.

What the evidence makes clear is that citation prediction requires the crawl layer. A rule-based score of 90 on a page that renders empty after JavaScript runs predicts nothing about citations. A clean brand-visibility result does not mean your pages are being indexed. The live-crawl is the only method that checks the actual state of the page at retrieval time.

In practice, for most sites doing AEO for the first time, the live-crawl finding is the one that changes the work plan. Rule-based issues are fixable with content edits. Brand-visibility gaps are fixable with publishing. But a rendering failure means AI engines are not seeing your content at all, and no amount of structural optimization or brand publishing resolves that until the render gap is closed. Start with the crawl. The other audits follow from there.

The free audit market is expanding fast. More platforms are entering the space with brand-visibility checkers and rule-based scorers, most of them effective sales funnels to paid monitoring products. The choice of which one to run first has always mattered. It matters more now, because the options are multiplying and their scores look interchangeable on the surface.

My read of the available evidence is this: no free audit predicts citations by itself. What predicts citations is whether the rendered page is reachable by an AI crawler. That is a crawl-layer question. Run it first. Run the others after you have confirmed the foundation is sound.

The three methods are not competitors. They answer different questions about different layers. The mistake is not running any of them. The mistake is running one and thinking you have run all three.