On-page mechanics
Answer-first writing: structuring sections so they can be quoted
Snippets, AI Overviews and assistants all quote passages, not pages. Answer-first structure is the difference between a section that can be lifted and one that cannot.
7 min read
Every extraction system — featured snippets, AI Overviews, assistant answers, on-site search — works the same way at the last step: it finds a passage, decides whether it stands alone, and lifts it. A passage that only makes sense after three paragraphs of preamble fails that test, however good the preamble is.
Answer-first writing is the fix, and it is a structural change rather than a stylistic one. The section still contains the nuance, the caveats and the examples. They just stop being the entry point.
This article covers where the answer belongs, what shape each snippet type expects, how to write a definition or a step list that survives being lifted out of context, and the failure patterns that stop otherwise good sections from being quoted.
The rule: heading, answer, then everything else
Phrase the H2 as the question, answer it in the first one or two sentences beneath, and only then expand. The answer must be self-contained: no "as mentioned above", no pronoun pointing at the previous section, no clause that depends on a sentence the extractor will not carry with it.
This is also the structure a skimming reader wants. Someone scanning the heading list stops at the section that matches their question and reads the first sentence. If that sentence is a wind-up, they leave.
- Answer length: roughly 40-60 words. Long enough to be complete, short enough to be lifted whole.
- Repeat the subject in the answer instead of using a pronoun — the extracted passage has no antecedent.
- Put the qualifier in the answer, not after it. "It is a hint, not a directive" belongs in the quoted block.
- Never open a section with "In this section we will look at". It uses the most valuable line on nothing.
| Text | |
|---|---|
| Buried answer | There has been a lot of debate about this over the years, and opinions differ depending on who you ask. Some practitioners argue one way, others another. Ultimately, most agree that a canonical tag tells search engines which URL is the preferred version of duplicate pages. |
| Answer first | A canonical tag tells search engines which URL is the preferred version when the same content is reachable at several addresses. It is a hint, not a directive — Google can choose a different canonical if the signals disagree. The debate below is about when those signals disagree. |
Match the format to the snippet type
Google draws the snippet format from the query and takes the content from whatever page supplies that format cleanly. You cannot choose the type, but you can be the page that offers the right shape.
| Query shape | Format expected | How to structure it |
|---|---|---|
| What is X / definition | Paragraph | One 40-60 word definition immediately under the heading, subject repeated up front |
| How to X / steps | Numbered list | A real <ol>, one action per item, imperative verb first, no step spanning three sentences |
| Best / types of / examples | Bulleted list | A real <ul> with parallel items, each self-describing without the intro |
| X vs Y / comparison | Table | A <table> with a header row, attribute names in the first column, no merged cells |
| How much / when / how long | Paragraph with the figure | Lead with the number and its unit, then the conditions that change it |
| Follow-up questions | FAQ block | Question as the heading, answer in the first sentence, one topic per pair |
Writing the answer block
Definitions
Start with the term, use a linking verb, give the category, then the distinguishing property: "Keyword density is the share of total words a term accounts for on a page. It is a diagnostic read-out, not a target."
Avoid opening with a hedge. "There is no single agreed definition, but generally speaking" turns a quotable sentence into an unquotable one, and readers hear it as uncertainty.
Step lists
One action per step, imperative first word, and each step must make sense to someone who has not read the intro. If a step needs three sentences of explanation, split the explanation out below the list or make it two steps.
Keep the list to a single level. Nested sub-steps rarely survive extraction and usually indicate the procedure needs splitting.
Comparisons
A comparison table works when the rows are attributes and the columns are the things compared — never the other way round when there are more than three attributes. Give every row a value in every column; empty cells make the table unquotable.
Add a one-sentence verdict directly above or below the table. That sentence is what an assistant will quote when the table is too wide to reproduce.
Numbers and figures
Lead with the figure and its unit, then attribute it, then explain the variance: "Roughly 1,500 words is the median length of the top ten results for this query, ranging from 600 to 4,000." A figure without its condition gets quoted without its condition.
Why this matters more for AI answers than for snippets
A featured snippet at least links back and shows a single source. Generative answers synthesise several passages, and the ones that make it in are the ones that can be understood in isolation and verified quickly. Structure is doing double duty: it decides whether your passage is a candidate at all, and how faithfully it survives being summarised.
Two consequences follow. First, self-contained beats elegant — a section that repeats its subject rather than referring back is more likely to be used correctly. Second, attribution beats assertion: a claim with a date, a figure, or a named source is easier for a system to keep intact than a general statement of good practice.
- Name the subject in the first sentence of every section, even when it feels repetitive in a full read.
- Keep each section to one question. Two answers under one heading means neither is cleanly extractable.
- Put the caveat inside the answer, not two paragraphs down, so a summary cannot drop it.
- Use an FAQ block for genuine follow-up questions only. Padding it with restated body content produces near-duplicate passages that compete with each other.
Failure patterns
| Pattern | Why the passage is skipped | Fix |
|---|---|---|
| Preamble before the answer | The first sentences are not an answer to anything | Move the answer up; the preamble is usually deletable |
| Pronoun opening | "It works by..." has no antecedent once lifted | Repeat the subject noun |
| Answer split across paragraphs | No single block contains a complete answer | Consolidate into one 40-60 word block |
| Fake lists and fake tables | The markup is a paragraph or a set of divs | Use <ol>, <ul>, <table> |
| Heading that is not a question | No query to match the passage against | Rephrase the H2 as the question the section answers |
| Two topics under one heading | Ambiguous passage boundary | Split into two sections |
| Answer hidden behind an accordion | Content loaded on interaction may not be in the rendered HTML | Render it in the HTML and collapse with CSS |
Checking a page for answer placement
Generated drafts in wordiqo apply this by default: sections lead with the answer, lists and tables ship as real markup, and an FAQ block is produced from genuine follow-up questions rather than restated body copy. If you are checking text you already have, the free optimizer reports the structural side — heading counts, list presence and where the primary term appears in the opening.
- Read only the headings and the first sentence under each — That sequence should stand alone as a coherent summary of the page. Anywhere it does not, the answer is buried.
- Cover the rest of the section — Hide everything except the answer block. If a reader with no context could act on it, it is quotable.
- Check the markup, not the rendering — Confirm lists are <ol>/<ul> and tables are <table> in the rendered DOM, not styled paragraphs.
- Look for the questions you did not answer — The People Also Ask box for your primary query is the cheapest source of missing sections — each one is a heading plus a 50-word answer.
Questions people ask
How long should a featured-snippet answer be?
- Around 40-60 words. Shorter tends to omit a necessary condition; longer usually gets truncated mid-thought. The constraint is that the block must be complete on its own, not that it hits an exact count.
Can you optimise for a specific snippet type?
- Not directly — Google picks the format from the query. What you control is whether your page supplies that format cleanly: a real list for step queries, a real table for comparisons, a tight paragraph for definitions.
Does answer-first writing make articles worse to read?
- No, if the nuance stays. You are moving the conclusion to the front and keeping the reasoning below it, which is how reference material has always worked. It reads worse only when the answer replaces the depth instead of introducing it.
Do FAQ blocks still help now that FAQ rich results were retired?
- The rich result is largely gone, but the block still serves readers and still gives extraction systems clean question-answer pairs. Keep genuine FAQs; do not add them purely for markup.
Should the answer repeat the exact query wording?
- It should contain the subject in natural language. Matching the query phrasing helps when it is how people actually speak, but bending a sentence to fit an exact string makes the passage read like boilerplate, which works against selection.
References
- Google Search Central — Featured snippets and your website — How featured snippets are selected and what you can and cannot control.
- Google Search Central — AI features and your website — Google's guidance on how content is used in AI Overviews and AI Mode.
- Google Search Central — Creating helpful, reliable, people-first content — The self-assessment questions behind "does this answer the question".
- MDN — The description list element — Real markup for term/definition pairs instead of styled paragraphs.
Keep reading
- Knowing which question the answer has to serve — The four intent types and the SERP evidence that identifies each one.
- The on-page checklist item for answer placement — Where this check sits among the other twenty on-page pass conditions.
- The heading tree that makes a passage boundary clear — H2/H3 rules — extraction needs the structure as much as the wording.
- Answer-first sections by default — How generated and rewritten sections lead with the answer and ship real list and table markup.