What is AEO? Answer Engine Optimization, explained

Where an AEO placement actually shows up

AEO isn't one feature — it's a handful of different surfaces, each pulling from the same kind of well-structured content:

• Featured snippets — the boxed answer shown above the regular results for a query.
• People Also Ask — the expandable Q&A accordion that appears mid-results.
• Voice assistant answers — Google Assistant, Siri and Alexa resolving a spoken query to a single spoken response.
• Google AI Overviews and AI Mode — the generated summary at the top of results, which cites a small set of sources.

Google just changed the FAQ schema playbook

On May 7, 2026, Google quietly added a note to the top of its FAQPage structured-data documentation: FAQ rich results are no longer supported in Search. There was no blog post or explanation — trade press (Search Engine Land, Search Engine Journal, Search Engine Roundtable) picked it up from the documentation change itself. The rollback is staged: the rich result stopped appearing May 7, 2026; the FAQ search-appearance filter, rich-result report and Rich Results Test support are being dropped in June 2026; and Search Console API support for the FAQ report goes away in August 2026.

It's a smaller shock than the headline makes it sound. Google had already restricted FAQ rich results to well-known government and health sites back in August 2023 — for nearly three years, most stores' FAQ dropdowns were already invisible in regular search results. May 2026 mostly made that restriction permanent and removed the reporting layer around it.

What this means practically: keep FAQPage schema on your pages. It's free, it's still valid markup, and Google itself says unused or no-longer-displayed structured data doesn't hurt a page — it's still one of the clearest structural signals available to AI engines outside Google's own results page. What to stop expecting is the visual dropdown bonus in a regular Google search result. And per Google's own guidance, People Also Ask has always leaned more on a page's visible Q&A content than on the schema markup around it, so a genuine, well-written FAQ section keeps earning its place with or without the rich result.

“Google didn't remove FAQ content's value — it removed one visual reward for having it. The schema, and the actual Q&A writing underneath it, still do the same job for every AI engine that isn't Google's own results page.”

What actually earns an AEO placement

None of these are exotic — they're the same structural habits that earn SEO rankings and GEO citations, applied specifically to the shape of an answer engine's query:

• Answer the question directly in the first sentence, in the same words a searcher would use — snippets and voice answers are usually a single lifted sentence, not a paragraph the engine has to summarize down.
• Match the content format to the query type: a definition question wants a 40-60 word paragraph, a "how to" wants a numbered list, a comparison wants a table — Google's snippet format tracks the query shape closely.
• Use the question itself as the heading, so the engine can map "what is X" directly onto the section that answers it.
• Keep the direct answer self-contained, separate from caveats or disclaimers — snippets get pulled from the cleanest sentence on the page, not the most nuanced one.
• Build topical depth around the query instead of publishing a single isolated answer — a page inside a cluster of related, structured content earns more trust from the retrieval step than a one-off.

Where Speakable schema fits (and where it doesn't)

Speakable is Google's structured-data type for marking sections of a page as suitable for text-to-speech playback. Google still labels it beta, and eligibility is narrow: production use is limited to English-language content, for users with Google Home devices in the US, and Google has historically tied broader access to news publishers specifically. For most ecommerce and service-business sites, Speakable isn't a lever worth building around yet — worth knowing it exists, not worth prioritizing over the fundamentals above.

Measuring AEO: what you can and can't see anymore

Search Console never had a clean, standalone "featured snippet" report, and now that the FAQ rich-result report is being phased out through August 2026, FAQ visibility disappears from Search Console entirely. What still works: the Performance report shows impressions and position per query, including position-1 results that often carry the snippet, though it doesn't label snippet ownership explicitly. A third-party rank tracker with SERP-feature tracking is the more reliable way to confirm you actually hold a snippet or PAA slot. For AI Overviews and voice answers, there's still no first-party citation report from Google — the practical signal is referral traffic from AI surfaces plus manual spot-checks, the same gap that exists for ChatGPT and Perplexity citations.

The bigger context: zero-click search is now the majority outcome. SparkToro's 2026 tracking puts the share of Google searches ending without a click at roughly two-thirds. Most of the traffic AEO wins never shows up as a "visit" in analytics at all — winning the answer is often the entire outcome, not a step toward a click.

A practical AEO checklist

1. Pull your existing FAQ and how-to content and confirm it still answers the question in the first sentence — don't assume schema alone is doing the work.
2. Keep FAQPage (and Article/Product where relevant) schema in place; it's still valid and still useful to AI answer engines even though Google Search's own dropdown is gone.
3. Match content format to query type: a short paragraph for definitions, a numbered list for how-to, a table for comparisons.
4. Use the literal question as a heading wherever it maps to real search intent, so both engines and a scanning reader land on the answer immediately.
5. Track snippet and PAA ownership with a SERP-feature-aware rank tracker, since Search Console's FAQ-specific reporting is being retired.
6. Treat AEO as one layer of the same content system that earns SEO rankings and GEO citations — not a separate content plan.

None of this is a reason to abandon FAQ content — quite the opposite. Google removing one visual reward doesn't touch the two things that actually earned that placement in the first place: a page that answers clearly, and a domain worth trusting enough to quote.