Writing Content That AI Can Actually Quote

Most advice about writing for AI answers starts with the writing. It should start with eligibility, because eligibility is binary and a surprising number of sites have switched it off without noticing.

Google's requirement is short: a page must be indexed, and it must be snippet-eligible. The same controls that limit a normal search snippet limit what an AI feature can use — and those controls are often set years earlier, for reasons nobody remembers.

The gate, in Google's words

From Google's AI features documentation:

"There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary."

and, on eligibility:

"a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements."

That is the whole technical entry condition. It also means the market for AI-specific files and markup is selling against the documentation, which we went through in the llms.txt guide.

The way sites exclude themselves by accident

Google names the controls that limit what appears:

"use nosnippet, data-nosnippet, max-snippet, or noindex controls"

Each of those is legitimate and each one is a way to remove yourself without meaning to:

• max-snippet set to a small number years ago, to stop competitors scraping summaries or to nudge click-through. It now caps what any AI feature can take.
• data-nosnippet wrapped around a block that later became the main content, usually after a template refactor.
• nosnippet applied site-wide by a plugin or a header rule that nobody has audited since.
• noindex on a template that also covers pages you want found — the classic version is a staging rule that shipped.

None of these produce an error. Nothing in Search Console says "you removed yourself". The page ranks, the traffic looks normal, and the AI feature quietly uses somebody else.

Check this before writing anything. View source on three important pages and search for nosnippet, max-snippet and data-nosnippet. It takes two minutes and it is the only item on this list that can be a complete blocker.

The control that is not the one people think

Google-Extended gets used as an AI Overviews control and is not one. Google describes it as the way to limit "AI training and grounding in some of Google's other systems" — other systems, not Search.

So blocking Google-Extended does not remove you from AI Overviews, and allowing it does not get you in. It is a decision about training. Making it while believing you made a visibility decision is a common and expensive confusion, and it sits next to the wider allow-or-block question.

What makes a passage quotable

With eligibility settled, the writing question is narrow and answerable: does the passage survive being lifted out of the page?

That gives four concrete tests.

The claim is in the first sentence. A section that opens with "here is the part that matters" or "this is where most guides get it wrong" hands an extractor nothing — the claim is in the next paragraph, and a model quoting the opening quotes a signpost. We had to rewrite ten of our own section openings for exactly this reason.

The specifics are inside the passage. If the number is in this paragraph and its source is two paragraphs up, the quoted version is an unsourced number. Keep the figure, the unit, the date and the attribution close enough that they travel together.

It is true without the heading. Headings are frequently dropped. A paragraph that begins "This is cheaper" is meaningless once "Managed hosting" is gone.

It commits. Hedged text is unquotable because there is nothing to quote. "It depends" is often the honest answer, and the quotable version of it names what it depends on.

What does not help

• Special markup for AI. Google says structured data "isn't required for generative AI search" and there is "no special schema.org markup you need to add." Implement schema where a rich result depends on it, as covered in our schema guide, and not as a lever here.
• Word count. A longer page is not a more quotable page. A page with one extractable answer beats a page with three thousand words of context around a buried one.
• Repeating the question as a heading and then not answering it. Common, and worse than not having the heading.
• Restating the same claim in five phrasings. It does not increase the chance of being quoted; it makes the page harder to read.

Where we say no

We do not add AI-specific files or markup for clients, and we say why in one sentence rather than quoting for it.

We do not rewrite a site for quotability before checking eligibility. A perfectly written page with max-snippet:20 in its head is invisible to the thing you are writing for, and the rewrite would have looked like it failed.

And we do not promise citations. Nobody can, and the honest measurement — impressions in the generative AI report, sessions in GA4's AI Assistant channel, and nothing in between — is set out in how to measure AI search traffic.

The order to do it in

1. Check nosnippet, max-snippet and data-nosnippet on your important pages. Fix any that were set for a reason nobody remembers.
2. Confirm indexing for the pages you care about, using URL Inspection rather than assumption.
3. Rewrite section openings so the first sentence carries the claim.
4. Pull each figure's source into the same paragraph as the figure.
5. Read three sections with the headings covered. Anything that stops making sense needs its context moved inside.
6. Measure impressions, not promises, and label them as impressions.

If you want this checked rather than assumed — starting with whether your site has quietly opted itself out — send us the domain, or see how we scope the work on the GEO service page.