Answer engine optimization (AEO): what it is and how to do it

Answer engine optimization grew up with the short answers search engines show above their results. Google’s featured snippets are the clearest case: a box that reverses the usual result and shows the descriptive snippet first, and that can also appear inside the group of related questions known as People Also Ask^[1]. The same kind of passage now also stands behind the supporting links of AI Overviews and AI Mode^[2], and behind the sources that assistants such as Copilot and ChatGPT cite.

AEO is part of SEO, not a separate discipline. Google says so in its guide to generative AI search: from Google Search’s perspective, optimizing for generative AI search is optimizing for the search experience, and so still SEO^[3].

What AEO cannot do is choose for the engine. Google is plain about featured snippets: you cannot mark a page as one; its systems decide whether a page would make a good featured snippet for a search and, if so, elevate it^[1]. AEO is one part of the wider work set out in the practical guide to generative engine optimization; how it differs from classic SEO in practice is in GEO vs SEO.

An answer can reach a reader in several places, and each has its own rules. The controls are the vendor’s; the page is yours.

One surface has gone. Google stopped showing the FAQ rich result in Search from 7 May 2026 and removed its documentation in June^[6]. FAQ markup no longer earns that result, which changes what it is worth; the section on structured data below comes back to it.

An answer block is a heading that asks the question and the passage that answers it. Most of the work is in the first two sentences.

1. 1Write the heading as the question, in the words a customer uses. A vague heading such as “Learn more” tells neither a reader nor a machine where an idea starts; Microsoft’s guidance uses the same example^[4].
2. 2Answer in the first one or two sentences, completely enough to stand alone if lifted out. Microsoft describes answers that can be lifted the same way: concise, one or two sentences, self-contained^[4].
3. 3Put the specifics in that answer: the size, the price, the time, the name. A word such as “quiet” or “fast” gives an engine nothing to quote; a measured fact does.
4. 4Follow with the detail, the conditions and the exceptions, in a list or a table where the answer is a set of steps or a comparison.
5. 5Answer each question once, on the page where it belongs. Two pages answering the same question compete for it, a form of keyword cannibalization.
6. 6Keep the answer in the HTML, visible without a click. Microsoft warns that answers hidden in tabs or expanding menus may be skipped, and that key facts should not live only in images or PDFs^[4].

Write sections that each make sense on their own, on pages written for people. Whether to go further and cut pages into small pieces for machines is answered, with Google’s and Microsoft’s views side by side, in the second step of the practical guide: no.

The first sentence answers; the shape of what follows depends on the kind of question. A definition, a set of steps and a comparison are read differently, and lifted differently.

Microsoft names numbered steps and comparison tables as especially effective for how-to questions and feature comparisons, and warns against using bullets for every line^[4]. Use a list or a table where the answer is a list or a table, and a sentence everywhere else.

Research points the same way. The paper that named GEO found that edits which add statistics, quotations and citations of credible sources raised a page’s visibility in generated answers the most, and that keyword stuffing did not^[7]. What it measured, and the limits of its tests, are set out in the research section of the practical guide.

Featured snippets are the oldest answer surface, and the only one with controls written for it. Google gives two ways to limit them^[1]:

• nosnippet removes every snippet of a page, featured and regular. Text marked with data-nosnippet is left out of both, and when a page carries both rules, nosnippet wins.
• A lower max-snippet makes a featured snippet less likely while keeping regular snippets, because a featured snippet appears only when enough text can be shown. Google gives no exact minimum, which varies with the information, the language and the platform, and a low setting is no guarantee.

Opting out is rarely the aim. The more useful fact is what happens on a click: it takes the reader straight to the section of the page the snippet came from, scrolling there with no markup from the site^[1]. The answer block is the landing point too, so what follows the answer has to carry the reader on, to the detail, the price or the next step.

Google builds snippets primarily from the content of the page, and uses the meta description only when it describes the page better^[8]. The answer under its heading, not the meta description, is the text to get right.

Structured data labels what a page already says. In schema.org, FAQPage marks a page that presents one or more frequently asked questions^[9], and a Question can carry an acceptedAnswer, the answer accepted as the best one^[10]. Labels like these help a machine read the page; they do not make it the answer.

Google says structured data is not required for its generative AI features and that no special schema.org markup is needed, while advising you to keep using it for rich results^[3]. With the FAQ rich result gone, FAQ markup earns no result in Google Search. Keep it where a page truly shows questions and answers and the markup matches the visible text, as Google asks of all structured data^[2]. Do not add it to pages that show none.

The best questions are the ones customers already ask. Start with the emails, calls and chats your team answers every week, then check what people type into Google.

Search Console shows the second part. In the Performance report, a query filter set to Custom (regex) takes the RE2 syntax and is not case-sensitive by default^[11], so one expression lists the queries phrased as questions:

^(how|what|why|when|where|which|who|can|does|do|is|are|should)\b

Sort the result by impressions and read the questions against your pages. A question with many impressions and few clicks is a candidate for an answer block on the page that already ranks for it. A question no page answers is a candidate for a new section, which is not always a new page.

AEO is measured where the answers appear. For Google, compare the clicks and impressions of the pages you changed with the period before; for AI answers, track a fixed set of questions and record whether each answer uses your page. How to track AI Overviews and the metrics worth reporting cover both.

No edit guarantees a result. Google notes that a page meeting every requirement and best practice is still not guaranteed to be crawled, indexed or served^[2].

Two pieces of groundwork come before any of this. An answer a crawler may not fetch cannot be quoted, so check which AI crawlers your robots.txt allows. And a special file such as llms.txt does not replace answers on the page, as the guide to llms.txt explains.