AI engines never load your full page into a model.
Retrieval systems chunk documents into passages, embed each passage
separately, and pull back only the few that match a query. Your page is
not the unit of retrieval. Your paragraphs are.
This has a blunt consequence most SEO advice skips: a brilliant
explanation in section four competes as an independent fragment against
every other fragment on the internet, stripped of the title, the headings
above it, and everything that gave it meaning.
Google's own docs set the gate. Search Central states that to appear in AI
features, "a page must be indexed and eligible to be shown in Google
Search with a snippet." Snippet eligibility is passage eligibility, and
your opening is the highest probability passage you own.
The three failures that kill retrieval
Orphaned pronouns, DOM order, and preamble. None of them show up in a
standard SEO audit, because rank trackers and crawl reports cannot detect
any of them.
The second one is a genuine bug and almost nobody checks for it.
1. Orphaned pronouns
Cheapest fix on the list, largest effect.
Open a section with a pronoun and the passage is dead on arrival:
They pull from structured data, so make sure your markup is valid.
Retrieved alone, that sentence is unusable. Who is "they"? A reranker
scoring it against a query about AI Overviews has nothing to match on.
Rewrite it so the passage carries its own subject:
AI Overviews pull from structured data, so make sure your markup is valid.
Same length. Same information for a human reading top to bottom. Totally
different behaviour under retrieval.
Apply this to the first sentence of every section you own. It feels
repetitive when you read the page start to finish. Retrieval systems never
read your page start to finish.
2. DOM order
Extraction reads HTML source order. Not your CSS. Not your visual layout.
Not what your design system renders on screen.
If a breadcrumb, cookie notice, share bar or "related posts" widget sits
before your article in the DOM, it occupies your opening passage even when
it renders in a sidebar or a sticky footer.
<!-- Costs you the opening passage -->
<article>
<nav class="breadcrumb">Home > Blog > AEO</nav>
<aside class="share-bar">Share this post</aside>
<p>Answer-first content places the answer first...</p>
</article>
<!-- Keeps it -->
<article>
<p>Answer-first content places the answer first...</p>
<aside class="share-bar">Share this post</aside>
</article>
The second version renders identically with about four lines of CSS. It
just stops handing your highest value chunk to a breadcrumb.
To check your own pages, render them in Screaming Frog and read the
extracted text in source order. The gap between what you designed and what
a parser sees is usually wider than people expect. In one audit the first
90 words of every article were a cookie banner, a language switcher and a
"trending now" carousel. The article started at word 91.
3. Preamble
A 300 word history of search before the answer does not delay the answer.
It replaces it.
The opening passage gets embedded either way. If yours is a warm-up, your
page gets embedded as a page about warm-ups, and it gets retrieved for
queries about warm-ups, which nobody searches for.
Where does 200 come from
Honest answer: no search engine publishes its chunk size, and anyone
quoting an exact figure from Google is guessing.
200 is a working constraint, not a documented threshold. Retrieval
pipelines commonly chunk into a few hundred tokens with a small overlap,
which lands somewhere around 150 to 250 English words. Keep your answer
inside that window and it occupies one clean passage. Spill past it and
the answer splits across a chunk boundary, arriving as two half-answers
that each score worse than one whole one.
Treat it as a budget you spend, not a target you fill. If the answer takes
60 words, stop at 60.
The rewrite sequence
For an existing post, in this order:
- Write the question the way a person actually types it. Not the keyword. The question. "Why is my page not cited by ChatGPT" beats "chatgpt citation optimization".
- Find the sentence that already answers it. It is usually buried somewhere in the middle. Move it to the top.
- Name the subject. No "this means", no "they pull from". Start with the noun.
- Attach one piece of evidence. A number, a named system, a documented claim. The GEO researchers tested exactly this and reported gains up to 40 percent.
- Delete the introduction you were going to write. We stopped writing them entirely. Context belongs after the answer, where it costs nothing.
Test it in three minutes
Rankings and citations diverge, so stop inferring one from the other. A
page can hold position three and never appear in a single AI answer.
Check 1: the covered title test. Read your first 200 words with the Check 2: paste the opening alone into a chat interface and ask what the Check 3: impressions against clicks in Google Search Console, filteredThree checks, fastest first
title hidden. If you cannot tell what the page is about, no retrieval
system can either.
page is about. This is the fastest diagnostic I have found. About twenty
seconds per page, and brutally honest.
to query clusters where AI Overviews appear. Rising impressions with flat
clicks means you are being summarised without attribution.
What this does not fix
Structure decides whether a passage can be retrieved. Authority decides
whether it gets chosen once retrieved.
Both matter. Teams that fix only the structure wonder why nothing moved,
and teams that only chase links wonder why their best page never gets
quoted. Answer-first writing is a multiplier on work you have already
done. It is not a substitute for having something worth citing.
I write about this at Loop2Tech, a technology
studio in Karachi, Pakistan.
The full version, with the comparison table and the research links, is at
loop2tech.com/blog/answer-first-content-ai-engines.
If you run this test on your own top ten pages, I would genuinely like to
know what you find. The results are usually worse than people expect, and
mine were too.
Top comments (1)
this explains why my long-form guides aren't ranking as well as the short a-b summaries lol. damn, the chunking really changes how we should structure content.