Audit AEO.

Can AI actually read your website?

Most sites cannot be read properly. When ChatGPT, Perplexity or Google AI Overviews compose an answer, they only cite pages they can extract structured, self-contained information from — a criterion classic SEO never measured.

This audit reads your page the way an answer engine would, then returns a score out of 100, your three strengths, and the three technical issues currently preventing you from being cited.

One page analysed · results in under 30 seconds · no sign-up

02Context

Why AEO now decides your visibility

An AI does not read your page, it slices it

Answer engines split your content into fragments, then keep only those that answer a question on their own. A paragraph beginning with “as mentioned above” becomes unusable the moment it is isolated, however well written it is.

Without structured data, the AI has to guess

A JSON-LD block explicitly declares what your page is: an article, a product, a procedure, an FAQ. Without it, the model infers that context from the text alone — and an uncertain inference turns into a citation that never comes.

Ranking first on Google guarantees nothing anymore

Ranking rewards a whole page; citation rewards a passage. A page can therefore dominate search results and stay entirely absent from generative answers, for lack of usable structure.

03Method

Exactly what the audit measures

Six weighted criteria applied to your page's real source code. The counts are taken from the HTML; only the interpretation is left to the model.

  1. 25 %

    01Schema.org structured data

    Presence, validity and relevance of JSON-LD blocks. The most decisive signal: it tells the AI exactly what the page is.

  2. 20 %

    02Semantic HTML structure

    A single descriptive <h1>, a logical h2/h3 hierarchy, and a <main> or <article> container isolating content from navigation.

  3. 20 %

    03Extractable format

    Headings phrased as real questions, a direct answer in the following two sentences, lists and tables rather than walls of text.

  4. 15 %

    04Factual density

    Figures, dates, proper nouns, explicit definitions. An AI cites what is verifiable and ignores vague marketing.

  5. 10 %

    05Passage self-sufficiency

    Each section must remain understandable out of context, because answer engines split the page into independent fragments.

  6. 10 %

    06Entity clarity and E-E-A-T

    Who publishes, with what authority, last updated when, citing which sources.

04Frequently asked questions

Frequently asked questions about AEO

What is AEO (Answer Engine Optimization)?

AEO is the practice of making a page citable by answer engines such as ChatGPT, Perplexity, Claude or Google AI Overviews. Where SEO aims to earn a click from a list of links, AEO aims to be the source an AI quotes in its answer. The levers differ: Schema.org structured data, semantic HTML hierarchy and the self-sufficiency of each passage matter more than backlinks.

How does AEO concretely differ from SEO?

SEO optimises for ranking, AEO for extraction. A search engine ranks whole pages; an answer engine splits your page into fragments and keeps only those that answer a question on their own. A page can therefore rank first on Google and be entirely absent from ChatGPT's answers if its content is not structured into self-contained units.

Why does my site never appear in ChatGPT's answers?

In most cases three causes compound: no JSON-LD structured data, content injected via JavaScript that crawlers cannot see, and decorative headings matching no real question. The audit identifies which of these is blocking your page first.

What is JSON-LD and why does it matter so much?

JSON-LD is a block of Schema.org structured data placed in the page's code that explicitly declares what the page is: an article, a product, an FAQ, a procedure. Without it, an AI must guess what your page is about from the text alone, which sharply reduces the odds of being cited. It is the highest-weighted criterion in this audit.

How long does the audit take and what do I need to provide?

The audit takes between 10 and 30 seconds and only needs the URL of the page to analyse. No installation, no access to your server, no code to insert: the tool reads the page exactly as an answer engine's crawler would.

Does the audit cover my whole site or a single page?

The main audit covers a single URL, because answer engines evaluate and cite individual pages, never whole sites. A multi-page audit is available separately: it reads your sitemap.xml and scores up to ten pages to produce an average.

Will the score be the same if I run the audit again?

Yes, provided the page has not changed. Forty of the hundred points are computed mechanically from the source code — JSON-LD presence and validity, heading hierarchy, crawler access, metadata — and depend on no model at all. The remaining sixty assess editorial quality and are produced at low temperature to stay stable.

Why is my JavaScript-rendered content a problem?

AI crawlers do not execute JavaScript, unlike Googlebot. Any content injected after load is invisible to them. The audit fetches your page twice — the raw HTML served by your server, then the DOM after execution in a real browser — and measures the gap. On a single-page application without server rendering, that gap often reaches 90%.