Someone searches for how long a service takes. Before any result appears, a box answers the question in forty words & credits one site. A large proportion of searchers read it & stop. The site ranked first, below the box, gets a fraction of the traffic it used to. The site cited inside the box gets attention it never had.
That is the whole argument for answer engine optimisation. The most valuable position in search is increasingly not the first result. It is the answer above the results, & it is won by structure as much as by authority.
The formats you are competing for
Several distinct surfaces sit above the organic results, & they reward different content shapes.
- Paragraph snippets. A short direct answer, typically forty to sixty words. Triggered by what, why & definitional queries. The most common format by a wide margin.
- List snippets. Ordered lists for processes & steps, unordered lists for sets of items. Triggered by how-to & best-of queries.
- Table snippets. Comparative or numeric data. Triggered by comparison & specification queries.
- People also ask. Expandable related questions, each pulling an answer from a page. Many separate opportunities per query.
- AI overviews. Synthesised answers drawing on several sources with citations. The newest & the one changing fastest.
You cannot win a snippet you are not already competitive for. Snippets are almost always drawn from pages already ranking on the first page.
Choose the right queries to target
Not every query deserves this effort, & some are actively bad targets.
Prioritise queries where you already rank between positions two & ten, because the snippet is usually pulled from that range & you are a realistic candidate. Prioritise question-shaped queries, since they trigger answer formats far more often than commercial ones.
Be selective about queries where a snippet would satisfy the searcher completely. Winning the snippet for a purely definitional query may produce a citation & no visit. That is not always a loss, since brand exposure has value, but it should be a deliberate choice rather than an accident. The queries worth winning are the ones where a short answer creates a follow-up question your page also answers.
Format the answer so it can be lifted
This is mechanical & it works. The pattern is consistent across formats.
Use a heading that states the question in the words people search. Immediately beneath it, place a single self-contained paragraph of roughly forty to sixty words that answers the question completely. No preamble, no "it depends", no cross-references. Then expand below with the nuance, the exceptions & the detail.
For list formats, use a heading phrased as the process, then an actual ordered or unordered list with concise items. Do not put a long paragraph between the heading & the list. For tables, use real table markup with clear header cells & keep the table small enough to display.
The discipline is to write the extractable answer first, then the article around it. Most writers do the reverse & bury the answer in the middle of a paragraph where it cannot be lifted cleanly.
People also ask is a content plan
The related questions box is a free, continuously updated list of what people want to know about your topic, with an answer slot attached to each one.
Work it systematically. Search your main topic, expand every related question, record them, then expand the new ones that appear. In fifteen minutes you can assemble thirty genuine questions. Add a question-led section to your existing page for each one that fits, & create new pages for the ones that do not.
Each question you answer in the extractable format is a separate opportunity, & these compound. A page answering twelve related questions well tends to appear across many of them.
AI overviews change the calculation
Synthesised answers behave differently from snippets. They draw on multiple sources, they cite several, & they are more likely to appear on complex or multi-part queries.
Three practical implications. First, being cited among several sources is now a realistic goal even where winning a single snippet is not. Second, comprehensiveness matters more, because a synthesised answer draws from pages that cover the subject fully rather than pages that answer one narrow question. Third, clarity of individual statements matters enormously, since the system is assembling an answer from fragments.
The structural work is largely the same as for snippets. The difference is that you should also ensure the page covers the surrounding questions, because that is what makes it a useful source for a synthesised answer.
Dealing honestly with fewer clicks
It is worth stating plainly: for informational queries, click volumes are falling & will continue to. Optimising for answer surfaces will not reverse that.
The sensible response is to change what you measure & where you invest. Impressions & citation frequency become meaningful metrics alongside clicks. Brand search volume becomes a proxy for whether the exposure is working. & the commercial weight of your content programme should shift towards queries where a short answer cannot satisfy the searcher: pricing, process, comparison, suitability, local specifics. Those queries still produce visits because the decision requires more than a sentence.
That shift is precisely why we pair answer optimisation with content marketing focused on decision-stage material rather than definitional articles.
Structured data & supporting signals
FAQPage markup makes question & answer pairs explicit & is worth implementing on pages that genuinely contain them. HowTo markup applies to real step-by-step processes. Both must reflect visible page content.
Beyond markup, the ordinary signals still apply. Pages need to be crawlable, fast, & authoritative enough to rank in the first place. Answer optimisation is a formatting layer applied to content that has already earned a position.
A working routine
- Export queries where you rank between two & ten & filter for question shapes.
- Check which of those currently show an answer surface & what format it uses.
- Add or rewrite a question-led heading & a forty to sixty word answer on the relevant page.
- Harvest related questions & add sections for each.
- Recheck after four to six weeks & record wins & losses.
Snippets are volatile, so expect to lose some & regain them. Treat it as ongoing maintenance rather than a project. To run it as a programme, see our answer engine optimisation service, or send us a query list.