Writing a page that answers
A page that answers starts by answering: a direct answer of a few lines under the heading, before any list and any image. That is the passage a snippet picks up. No special format is required to appear in AI-assisted displays, and the documentation says so explicitly.
Why start by answering?
Because the person arriving on the page asked a question, and did not come to read an introduction. That is the only justification needed, and it comes before any consideration of search engines: a text that makes its answer wait loses its reader before giving it.
The same gesture happens to serve elsewhere. A snippet displayed in a results page has to stand alone, outside the context of the page.
Snippets are mainly built from the content of the page itself.
officialSource : Google Search Central, “Control your snippets in search results”
A paragraph that answers in a few lines, understandable without its surroundings, is therefore a natural candidate. This is not a trick: it is the consequence of having written clearly.
What does an AI-assisted display actually ask for?
This is where the consulting market has drifted furthest from the documentation. Two sentences are enough to put things back in place.
There is no additional requirement to appear in AI-assisted overviews or mode, and no special optimisation is needed.
officialSource : Google Search Central, “AI features and your website”
No machine-readable file, no AI-dedicated text file and no particular schema.org markup has to be created to appear in those displays.
officialSource : Google Search Central, “AI features and your website”
No additional requirement, no dedicated markup, no special file. Any “answer engine optimisation” service selling a format, a mandatory structure or a file to drop in is therefore selling something the engine’s own vendor declares unnecessary.
What is required, on the other hand, is required without ambiguity:
To be offered as a supporting link in those displays, a page must be indexed and eligible to be shown in search.
officialSource : Google Search Central, “AI features and your website”
In other words, the entry condition is the groundwork: a page crawled, indexed, eligible. A page that is not indexed will be quoted by nothing, however good its answer — which points back to the guide on pages that are not indexed, and not to a writing technique.
Putting a self-contained direct answer under the heading
hypothesis
- Effort
- low
- Time to effect
- weeks
- Risk
- none
- Durability
- structural

How do you write a direct answer that stands on its own?
Four constraints, and they can all be checked on rereading with no tool at all.
It answers, it does not announce. “This article explains how indexing works” is not an answer, it is a promise of one. The difference is tested by deleting the sentence: if nothing is lost, it was bringing nothing.
It is understandable out of context. No “as we saw above”, no “the latter”, no reference to a heading. The passage has to be readable by someone who has not seen the page.
It fits in a few lines. Enough to answer, few enough to be picked up. On this site the bound adopted is forty to sixty words — a working convention, not a measured value, and it is checked when the site is built.
It is true without being empty. That is the hardest constraint. An answer cautious to the point of saying nothing — “it depends on many factors” — satisfies the form and misses the point. When the honest answer is uncertain, saying so precisely is better: what is documented, what is observed, what remains unknown.
What is the rest of the page for, then?
For deserving the answer. A page limited to its opening paragraph would have nothing to offer someone for whom the answer is not enough — that is, most of the people who click. The body is there to show where the claim comes from, to handle the cases where it does not apply, and to say what remains uncertain.
The test the documentation itself proposes is the best one available:
Among the self-assessment questions offered to publishers is this one: will someone reading your content leave feeling they have had a satisfying experience?
officialSource : Google Search Central, “Creating helpful, reliable, people-first content”
Should you limit what can be picked up?
The question arises seriously for sites whose reading is the product. The means exist and are documented.
The snippet controls — including the no-snippet directive and the length limit — apply to AI-assisted displays as well.
officialSource : Google Search Central, “AI features and your website”
The trade-off is therefore not technical but economic, and it is blunt: the same controls reduce pickup in AI-assisted displays and in classic snippets. You cannot restrict one and keep the other intact. This site has chosen to restrict nothing, because being quoted is its most realistic acquisition channel; a site living off subscriptions could choose the opposite, and that would be just as defensible.
What does not work, or no longer works
To appear in AI Overviews, structure your content as marked-up questions and answers, publish an llms.txt file and add the AI-dedicated schema.
One last reflex is worth dropping: writing the direct answer last, after the body. The order of drafting does not matter, but the order of publication does, and an answer added at the end almost always reads like a summary of the text rather than an answer to the question. The reader had asked a question.
Sources
- AI features and your website — Google Search Centralaccessed on
- Control your snippets in search results — Google Search Centralaccessed on
- Creating helpful, reliable, people-first content — Google Search Centralaccessed on
- Page indexing report — Google Search Consoleaccessed on
Block revalidated on
Frequently asked questions
- Do you need a special format to be quoted by an answer engine?
- No, and the documentation is explicit: no additional requirement, no special optimisation, no dedicated markup. What is left to do is the basics — a page that is indexed, eligible to be shown, and that genuinely answers the question it claims to handle.
- Where should the direct answer go on the page?
- Immediately under the main heading, before any list, any box and any image. A reader in a hurry should get their answer without scrolling, and a snippet built from the page's content then finds a self-contained passage, understandable outside its context.
- Is a file dedicated to AI crawlers necessary?
- The documentation explicitly says no machine-readable file of that kind has to be created for those displays. Publishing one is not harmful in itself and may serve other uses, but presenting it as a condition of appearing is false.
- How do you stop a passage being picked up in a snippet?
- Through the documented snippet controls, which limit the length picked up or forbid it entirely, section by section within a page if needed. Those same controls apply to AI-assisted displays: restricting them restricts both at once, with no way to separate them.