What is answer engine optimisation, and how is it different from SEO?

Answer engine optimisation is the work of making a page quotable inside an answer, rather than ranked beside one. Classic SEO competes for a position in a list of links. AEO competes to be the passage an assistant lifts when it writes the answer itself.

The distinction matters because the two are measured differently. A ranking is a position. Being quoted is a yes or no about one passage on one page.

Is AEO a different discipline from SEO?

No. It is a different emphasis on overlapping mechanics, and the overlap is larger than most of the commentary suggests. Google Search Central documents the entry requirement plainly: "To be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements."

Read that carefully, because it settles an argument. There is no separate AEO index to get into. If a page is not indexable and snippet-eligible, no amount of answer-shaped writing will help it. Ordinary technical hygiene is the prerequisite, not the alternative.

What AEO adds is the shape of the content once the page is reachable. A ranked link only has to be about the topic. A quoted passage has to answer the question on its own, without the rest of the page around it.

What actually changes in the writing?

Three things, in order of how much they matter.

• The answer comes first. Put the direct answer in the first sentence or two under the

heading, then explain. An assistant retrieving a passage takes what is there, not what arrives four paragraphs later.

• The heading is the question. Match the words a reader would actually type. The

question-and-answer shape is well understood: Google Search Central describes such pages as containing "data in a question and answer format, which is one question followed by its answers."

• Each answer stands alone. Avoid "as mentioned above". A passage that depends on

earlier context loses its meaning the moment it is extracted.

None of that requires writing for a machine. It requires writing the way a good reference page has always been written, and being disciplined about it.

Does this mean writing for algorithms?

It should not, and the guidance is explicit about the difference. Google Search Central puts it as: "People-first content means content that's created primarily for people, and not to manipulate search engine rankings."

That line is a useful test to apply to your own drafts. If a change makes the page easier for a person to get an answer from, it is almost certainly the same change an answer engine rewards. If a change only makes sense as a signal, it is the other kind.

What should you measure?

Measure capability, not outcomes, because the outcomes are not observable to you. No assistant publishes which pages it quoted. What you can measure directly:

• Whether your text is present without JavaScript running.
• Whether each AI crawler receives a 200 rather than a 403.
• Whether your headings match real questions.
• Whether each answer is self-contained.

Those four are checkable in minutes and they are the ones under your control.

What this does not tell you

It does not tell you that doing this will get you quoted. Nobody can promise that, and anyone who does is selling something they cannot measure. What these steps do is remove the reasons you would be skipped: unreadable content, a blocked crawler, an answer buried in the middle of a page. Removing an obstacle is not the same as causing a result, and the honest version of this work says so.