How to Structure a Page So AI Can Quote It

What a quotable section actually looks like

Two different questions get sold as one. Whether answer engines matter for a small site is a budget question, and I worked through it separately in what AEO is and whether a small site needs it. This post is the narrower one: given that you are writing a page anyway, what on the page decides which part of it gets reused.

Almost everything written about this skips the mechanism and goes straight to a formatting checklist. The checklist is not useless. It is just downstream of one fact about how selection works, and once you have that fact, most of the checklist either explains itself or falls away.

Pages get ranked, passages get picked

Confusion here starts with a Google announcement from a few years back. The original wording said Google was now able to index not just webpages but individual passages from those pages, which sounded like passages had become their own units. Google then walked that back. As Search Engine Land reported at the time, the clarification was that “this change doesn't mean we're indexing individual passages independently of pages” and that “We're still indexing pages and considering info about entire pages for ranking”, with passages used as an additional ranking signal.

That distinction has a practical edge. You cannot format a buried section into its own independent unit. The page competes as a page. What the passage-level machinery changes is which part of a page that already ranks gets pulled into view, and how far down that part is allowed to sit without being ignored.

Selection is easiest to watch in the featured snippet, because Google documents that one. Asked how a site can mark a page as a featured snippet, the documentation answers “You can't”, and says Google systems determine whether a page would make a good featured snippet and promote it. There is no markup, no attribute, no field. The text is the only lever you hold.

Snippet construction works the same way. The snippet documentation says snippets are “automatically created from page content” and are “primarily created from the page content itself”, with the meta description used only when it happens to describe the page better. Neither page mentions structured data as a source at all.

The chunking advice Google tells you to skip

Most advice in this space says to rewrite every page into self-contained blocks of roughly eighty to a hundred and fifty words, one idea each, a heading above every one. Vendors call it chunking and sell it as the thing that makes content retrievable.

Google's own guide to optimizing for generative AI features puts that in its mythbusting section. The line is short enough to quote in full: “There's no requirement to break your content into tiny pieces for AI to better understand it.” The same section says you do not need to create new markup to appear in Google Search. You can read it on Search Central.

Half of the chunking pitch is still correct, and it is worth separating out. Self-containment is real and it is the part that matters. A section that only makes sense after the three sections above it is a section that cannot be reused. The wrong half is the word count target. Writing to a chunk size produces the clipped, uniform rhythm that makes a page read as machine-assembled, which is its own problem and the subject of writing AI copy that does not sound like AI.

What Google does say about organization is modest and framed around readers: people generally appreciate web pages organized by paragraphs and sections, with headings that give a clear structure to navigate. That is the whole instruction. It describes a decently edited article, not a database of cards.

Write sections that survive being pulled out

Here is the detail that turned this from an abstraction into an editing rule for me. Google's featured snippet documentation says that clicking a featured snippet takes the user directly to the section of the page that appeared in the snippet, and that the scroll happens automatically with no annotation needed from the site.

So the quoted section is a landing point, not a waypoint. Someone arrives there having read nothing above it. If the first sentence of that section says “This is the part most people get wrong”, the visitor has no idea what this refers to, and the assistant quoting it has the same problem.

Three edits fix almost every instance. Replace opening pronouns with the actual noun, so “It takes about an hour” becomes “Pointing a Namecheap domain at Netlify takes about an hour”. Delete backward references: as mentioned above, as we saw earlier, building on the previous section. Delete forward promises too, because a section that ends by pointing at a section the reader cannot see is incomplete on its own.

That test takes five minutes per page. Read only the first two sentences under each heading, in isolation, and ask whether a stranger could act on them. Any section that fails gets its subject put back into its opening line.

Put the answer above the explanation

Heading, then answer, then reasoning. Most drafts arrive in the other order, because explaining your way toward a conclusion is how thinking feels from the inside. It reads as withholding, and it buries the one sentence worth reusing under four paragraphs of setup.

Two concrete habits. Phrase the heading as the question a person would actually type, not as a topic label, so “How much does a domain cost per year” rather than “Domain pricing”. Then answer it in the first forty words underneath, specifically, with the number or the verdict in the sentence rather than a promise that the number is coming.

Be honest about what is documented here and what is judgment. The forty-word figure is mine, not Google's. Google explicitly declines to publish a length: the featured snippet page says it “does not provide an exact minimum length required to appear as a featured snippet” because the minimum varies with the information, the language and the platform. Treat any specific word count you read on this subject, including mine, as a working habit rather than a threshold.

One real constraint sits under all of this: the reused unit is short. Whatever gets lifted out is a sentence or two, so a page whose best sentence arrives in paragraph nine is competing against itself.

Lists and tables, for the right reason

You will read that lists and tables get quoted more often. I went looking for the source. Google's snippet documentation and its featured snippet documentation do not mention headings, lists or tables at all, in any capacity. Anyone citing Google for a list-and-table rule is citing something that is not in the text.

They are still worth using, for a reason that has nothing to do with format preferences. Five values in a table are one unit that answers one question. The same five values distributed across a paragraph require the reader, or the model, to collect them and reassemble them in the right order, which is work that can go wrong.

The rule I use: three or more parallel items of the same kind become a list or a table. Two stay in prose. Anything that is not parallel stays in prose regardless, because a bulleted list of unrelated sentences is just a paragraph with the connective tissue removed.

One thing people miss. A table needs a sentence above it naming what it compares and in what units. Pulled out of the page, a grid of numbers with column headers like Basic and Pro means nothing. The lead-in sentence is what makes the table self-contained.

The settings that quietly make a page unquotable

Four mechanical things override everything above, and all four are easy to leave switched on by accident in a theme or a plugin.

A low max-snippet value. Google's documented method for getting out of featured snippets is to set that rule to lower lengths, and the documentation says that “the shorter your max-snippet rule setting, the less likely the page will appear as a featured snippet”. A site-wide value in a template is an opt-out nobody chose. Check your page source for it.

A nosnippet rule anywhere on the page. Per the same documentation, if both nosnippet and data-nosnippet appear, nosnippet takes priority and snippets are not shown for the page at all. One inherited tag removes the whole page from consideration.

Content behind an interaction. The snippet documentation advises making sure content is immediately visible to a human and not hidden behind an expandable section or a tabbed interface. That is the argument against the collapsible FAQ accordion, which is exactly where most sites put their clearest answers.

Eligibility itself. Google's page on AI features states that to be shown as a supporting link, a page must be indexed and eligible to be shown in Search with a snippet, and that there are no additional technical requirements. Structure is downstream of being indexed. On JavaScript, Google says it can process content inside JavaScript as long as it is not blocked, though an answer that exists in the HTML is still the safer bet than one assembled after a click.

Specific content gets quoted, comprehensive content gets ignored

Structure decides which part of a page is reusable. It does not make a page worth reusing. Google's generative AI guide draws that line with an example pair I keep thinking about: it calls “7 Tips for First-Time Homebuyers” commodity content, and contrasts it with “Why We Waived the Inspection & Saved Money: A Look Inside the Sewer Line”.

The instruction next to it is blunt: do not just recycle what others on the internet have already said, or what could easily be produced by a generative AI model. An assistant choosing between a thousand interchangeable versions of the same seven tips has no reason to name any of them.

In practice the passages that get quoted are the ones carrying something only you can supply. A real number from your own work. A procedure with actual values in it, your DNS records, your actual settings. A date. A named tool and what went wrong with it. Generic advice is unquotable not because of its structure but because attribution adds nothing to it.

That same guide warns against volume for its own sake, noting that a high quantity of pages does not make a site higher quality or more relevant, and that spinning out near-identical pages for query variations to manipulate results runs into Google's scaled content abuse policy. Ten pages with something first-hand in them beat eighty assembled ones. Earning the mention is a separate problem from formatting for it, and I covered that side in getting your site mentioned by ChatGPT and Claude.

The pass I run on one page

About an hour for a page of this length, less once you have done a few. Work on a copy if the page matters.

First, read the page source and search it for nosnippet and max-snippet. If either is there and you did not put it there, that is the whole job for today.

Second, rewrite every heading as the question it answers, in the words a person would use. If two headings answer the same question, merge the sections.

Third, go heading by heading and move the answer to the top of each section. The explanation follows it. This is usually a cut-and-paste job rather than new writing.

Fourth, read the first two sentences of each section with the rest of the page covered. Put the missing subject back into any that do not stand alone, and delete every backward reference.

Fifth, convert any run of three or more parallel items into a list or a table, and give each table a lead-in sentence naming what it compares.

Sixth, open any accordion or tab widget and ask whether the answer inside it needs to be hidden. Usually it does not, and the page reads better with it open anyway. The basic SEO checks for a new site still apply underneath all of this, since none of it helps a page that is not indexed.

---

What I like about this list is that none of it is speculative. Every item either comes out of documentation that names the behaviour, or is an editing habit that makes the page better for a person reading it at two in the afternoon on a phone. Nothing here is a bet on a ranking factor that may not exist.

What it will not do is manufacture a reason to quote you. A perfectly structured page about a subject you have no direct experience of is a well-organised page nobody needs. Structure decides which forty words of yours are reachable. Having forty words worth reaching is the other job, and it is the harder one.

Common questions

How long should a section be if I want AI to quote it?

There is no documented length. Google's featured snippet documentation explicitly says it does not provide an exact minimum length, because the minimum varies with the information, the language and the platform. Its generative AI guide also states there is no requirement to break content into tiny pieces. A practical habit rather than a rule: answer the heading's question within the first forty words of the section, then explain at whatever length the subject needs.

Can I mark a passage as the answer I want quoted?

No. Google's documentation answers the question of how to mark a page as a featured snippet with two words: you can't. Its systems decide whether a page would make a good snippet and promote it, and there is no markup, attribute or submission field for nominating a passage. The text itself is the only input you control, which is why the wording and the placement of the answer carry all the weight.

Does a collapsible FAQ accordion hurt my chances of being quoted?

It can. Google's snippet documentation advises making sure content is immediately visible to a human rather than hidden behind an expandable section or a tabbed interface. Most sites put their clearest, most directly quotable answers inside exactly that kind of widget. If the answers are short, leave them visible on the page and keep the accordion for genuinely secondary material.

Is it better to restructure old posts or write new ones?

Restructure first, on the pages that already get some traffic. A page that is indexed and ranking for something is a page where better answer placement can change what gets shown, and the edit takes under an hour. Google's own guide notes that a high quantity of pages does not make a site higher quality, so adding new thin pages is the weaker move. Write new pages when you have something first-hand to put in them.