Answer Engine Optimisation
Answer engine optimisation, or AEO, is passage-level work. Each block of text is structured so that it answers one question completely and can be lifted out intact, without the surrounding page, by an assistant or a featured snippet.
Writing a passage that can be quoted whole
An answer engine does not return your page. It returns a passage from it, sometimes attributed and sometimes not. Whether that is possible depends on whether a complete answer exists in one place on the page, or whether understanding it requires reading three paragraphs above and one below.
That is the whole discipline. A page can rank well and never be quoted, because its argument is distributed across the article in a way that reads well to a person working through it and yields nothing extractable to a machine sampling it.
AEO is often mistaken for adding FAQ schema. Schema describes structure that exists; it does not create it. OMAV restructures the prose first and then describes it accurately, and tests the result by attempting the extraction.
What AEO covers
Six workstreams, ordered from question inventory to verification.
Question inventory
The questions buyers actually ask, drawn from search data, support tickets, sales call notes and the objections that recur — not from keyword tools alone, which miss the phrasing people use in conversation.
Answer mapping
Each question assigned to exactly one page and one passage, so that no two pages compete to be the answer and no question is answered nowhere.
Passage restructuring
Prose rewritten so a complete answer sits in one block: the claim stated first, the qualification attached, and no dependency on a paragraph three screens above.
Heading hierarchy
Headings written as the questions they answer rather than as topic labels, so the structure of the page matches the structure of the enquiry.
Structured data
FAQPage, HowTo and Article markup that matches the visible text exactly, implemented after the restructuring rather than in place of it.
Extraction testing
Each target passage tested by attempting to lift it: does it stand alone, is it correct out of context, and would a reader understand it without the page around it?
How an AEO engagement runs
Inventory questions
Real questions collected from search data, support and sales, then deduplicated and prioritised by commercial value.
Map answers
Each question assigned to one page and one passage, with cannibalisation resolved by consolidation rather than by another new page.
Restructure
Passages rewritten to stand alone, headings rewritten as questions, and the page reordered so the answer precedes the elaboration.
Describe
Structured data implemented and validated against the visible text, so the markup is a description rather than a claim.
Test extraction
Each passage lifted and read in isolation, and revised wherever it fails to make sense or overstates without its qualification.
AEO next to the disciplines beside it
How AEO differs from SEO and GEO in unit of work and measurement.
| Dimension | SEO | AEO | GEO |
|---|---|---|---|
| Unit of work | The page | The passage | The entity and the source |
| Goal | Rank and earn the click | Be the extracted answer | Be retrieved and cited |
| Primary lever | Relevance and authority | Structure and clarity | Authority and consistency |
| Measured by | Position, clicks, conversions | Snippet and answer capture | Share of answers and citations |
| Time to effect | 2 to 6 months | Weeks to 2 months | 3 to 9 months |
| Fails when | The site cannot be crawled | The answer needs context | Facts disagree across sources |
What AEO cannot do
AEO cannot make a weak answer authoritative. Structuring a superficial claim so that it extracts cleanly produces a superficial claim that extracts cleanly. Where the underlying knowledge is thin, the honest work is to acquire it — usually by talking to whoever actually does the job — before restructuring anything.
Nor does it suit every page. Applied indiscriminately it produces robotic question-and-answer padding that damages pages which were working as arguments. We select the pages where extraction is the goal and leave the others as prose, which is why extraction testing is the check rather than question count.
- A page can rank well and never be quoted. That gap is what AEO addresses.
- Schema describes structure; it does not create it. Restructure first.
- Each question belongs to exactly one page and one passage.
- Test by lifting the passage out and reading it cold.
Questions buyers ask about this
Is AEO just adding FAQ schema?
No. Schema describes structure that already exists on the page. If the prose does not contain a complete self-contained answer, marking it up as one is a mismatch between the markup and the visible text, which is a liability rather than an advantage. The work is restructuring the prose; the markup describes the result.
Will this make our pages worse for human readers?
Done properly it improves them. Self-contained sections with honest headings are easier to skim and easier to return to. Done badly it produces padded question-and-answer blocks that damage pages which worked as arguments, which is why we select target pages deliberately and test extraction rather than counting questions.
How do you know a passage will be extracted?
We cannot know, because retrieval is decided by systems we do not control. What we can verify is whether the passage is extractable: lift it out, read it without the page around it, and check that it is complete, correct and not misleading in isolation. Passages that fail that test would not be usable even if retrieved.
Where do the questions come from?
Search query data, your support tickets, notes from sales conversations, and the objections that recur in your market. Support tickets are the most underused source, because they contain the exact phrasing customers use, which is usually not the phrasing in a keyword tool.
How long before AEO shows results?
Faster than SEO or GEO — weeks to about two months — because the change is on-page and does not depend on accumulating authority. It does depend on AIO being in place first: a passage on a page a crawler cannot read is not a candidate for anything.
Marked up as FAQPage structured data, matching the visible text exactly.
Still not sure this is the right service?
Answer four questions and we will tell you which one fits — or that none of them do.
Tell us what you are trying to fix.
A short conversation about the objective, the constraints and the timing. If we are not the right fit, we will say so.