Layer 2 · Answerability
Answer engine optimization (AEO)
SEO optimizes a page to rank. AEO optimizes a passage to be extracted. That one change in unit rewrites how you structure everything.
Answer engine optimization is the practice of structuring content so a single passage can be lifted out and used as a complete answer.
The core move: put a self-contained 40–60 word answer immediately under a question-shaped heading, then support and expand it — instead of building toward a conclusion the reader has to assemble from the whole page.
01The inverted pyramid, enforced
Journalism solved this a century ago and marketing forgot it. Answer first, context second, nuance third. The difference now is that the machine reading your page may only ever see the first block, because that's the chunk that matched.
Before
“Before we can discuss schema markup, it's important to understand the history of structured data on the web. In 2011, the major search engines came together…”
After
“Schema markup is structured data added to a page's HTML that tells machines what the content means rather than how it looks. It uses the schema.org vocabulary, usually in JSON-LD format, and is the most reliable way to state facts about an entity in a form software can parse without guessing.”
The second version is quotable. The first version is a warm-up.
02Chunk-safe writing
Retrieval systems split documents into passages. You don't control where the splits land, so write as though every section might be read in isolation.
Survives extraction
- Repeats the subject noun instead of using “it” or “this”
- Names the year explicitly rather than saying “currently”
- Defines an acronym on first use in each major section
- Keeps a claim and its source in the same paragraph
- Puts the answer above any table that supports it
Breaks on extraction
- “As we saw above…” / “in the previous section…”
- Numbered references to earlier list items
- Pronouns whose antecedent is three headings back
- Answers that only make sense after a long setup
- Key facts that live only in an image or chart
03Question-shaped headings
Real user questions are phrased as questions, and headings that mirror them create an obvious match between query and passage. This does not mean every heading becomes a question — that reads badly — but the ones covering a genuine user question should.
| Generic heading | Question-shaped heading |
|---|---|
| Pricing | How much does X cost per user per month? |
| Integrations | Which tools does X integrate with natively? |
| Getting started | How long does it take to set X up? |
| Comparison | What's the difference between X and Y? |
| Requirements | What do I need before I can use X? |
04One page, one job
Because assistants fan a question out into narrow sub-queries, narrow pages win more often than broad ones. A single page trying to serve “what is it”, “how much does it cost” and “how does it compare” will be beaten on each sub-query by a page dedicated to it.
Split when a section could stand as its own page with its own H1 and its own answer block. Consolidate when two pages answer the same question with different words — that's cannibalisation, and it splits your signals across two mediocre candidates instead of one strong one.
05Formats that get extracted disproportionately
- Definition blocks. “X is a Y that does Z.” The single most reliably quoted sentence pattern on the web.
- Comparison tables. Machine-parseable, quotable row by row, and hard to paraphrase away from the source.
- Numbered procedures. Ordered lists with one action per step map cleanly onto
“how do I…” queries and onto
HowTomarkup. - Direct answers to yes/no questions. Start with “Yes” or “No”, then qualify. Most content never actually says the word.
- Short FAQ pairs. One question, one complete answer, no cross-references.
The read-aloud testTake any section of your page, read it aloud to someone who hasn't seen the rest, and ask whether they got a complete answer. If they ask a clarifying question, an engine would have needed the same clarification — and it can't ask.
Passages extractable? Now make them worth choosing: generative engine optimization.
Questions engines askFrequently asked questions
What's the ideal length for an answer block?
Roughly 40–60 words, or two to three sentences. Long enough to be complete and specific, short enough to be quoted without editing. The test is not word count though — it's whether the passage still makes sense with everything around it deleted. If it contains ‘as noted above’ or an unexplained pronoun, it fails regardless of length.
Should I add an FAQ section to every page?
Add one where you have genuine questions with genuine answers, which is most informational pages. Don't manufacture questions to fill a schema block — padded FAQs read as thin to both readers and engines. Note also that Google restricted FAQ rich results in search, but the markup still helps machines parse question-answer pairs, which is why it remains worth adding.
Does content chunking actually matter?
It matters, though it's worth knowing that Google's 2026 generative-AI guidance (developers.google.com) listed manual chunking among tactics it considers unnecessary. The resolution is that you shouldn't engineer artificial chunk boundaries for a specific system — but you should write sections that stand alone, because that's good writing and it happens to survive any chunking strategy.