Google Kills FAQ Rich Results: What It Means for AEO in 2026

If you’ve been doing SEO for a while, you probably remember when FAQ rich results felt like free money. For years, dropping in a little FAQPage schema was the easiest way to buy extra space on Google’s results page without paying for it. It was almost comical: add a few lines of code and your listing suddenly sprouted expandable questions that shoved competitors down the fold.

Now it’s official. As of May 7, 2026, FAQ rich results no longer appear in Google Search. And Google isn’t stopping at the UI change: FAQ search appearance reporting in Search Console and Rich Results Test support are scheduled to be removed in June 2026, and Search Console API support for FAQ rich results is slated to be removed in August 2026.

This isn’t a reason to panic. It’s a reason to stop treating FAQ schema as a CTR trick and start treating it like what it always should’ve been: a way to publish clear, useful Q&A content, then measure performance with the reporting that’s actually sticking around.

Quick checklist (so you don’t overthink it)

• Screenshot or export your historical FAQ rich results reporting before June 2026.
• Compare CTR on the pages that used to show FAQ dropdowns (28 days before vs. 28 days after May 7, 2026 works well).
• Keep FAQPage schema only when the questions and answers are real and visible on the page.
• Update QA: stop using Rich Results Test as a "will we get the dropdown" gate once June 2026 hits.
• Shift measurement toward page performance and AI citation visibility (AEO), not SERP pixels.

What Exactly Changed in May 2026?

The simplest way to say it: the SERP feature is gone. Google no longer shows the expandable FAQ dropdowns in search results, even if your pages still have valid FAQ schema (FAQPage schema) and even if it used to trigger the enhancement.

A few clarifications that matter in real life:

• FAQ rich results are no longer shown in Google Search.
• FAQ schema itself is not "banned". You can still use structured data where it accurately describes the page.
• What disappeared is the visible SERP treatment, not your ability to publish Q&A content.
• Google is retiring the surrounding ecosystem, reporting in Search Console and support in the Rich Results Test, plus Search Console API support later in 2026.
• If your FAQPage markup existed mainly to win extra pixels and boost CTR, that play is dead.

Why Google Made the Change (And Why It Was Overdue)

Google’s "cleaner" explanation isn’t wrong, but it’s not exactly the full postmortem either. Everyone who watched the SERPs knew FAQ schema was getting abused. Product pages were packed with irrelevant questions purely to win dropdown real estate. The incentives were backwards, and users paid for it. Marketers didn’t just stretch the format, they broke it.

The deeper motivation is about control and what Google is preparing users to expect. Search is being remodeled into an answer engine. With AI Overviews (formerly SGE), Google increasingly wants to deliver an answer first, not a menu of links. FAQ rich results were an early, clunky bridge: they expanded the snippet, but they still nudged people toward your page for context. The new model is Google ingesting your content and returning a synthesized response under Google’s own UI. Removing FAQ rich results clears the space and helps normalize the idea that the SERP itself is where the answer lives.

What SEOs Should Check in Search Console

If you’ve ever tried to explain a traffic drop to a stakeholder with nothing but vibes and a screenshot, you already know why this matters. The reporting is going away, so grab what you can while you can, then shift your monitoring to page-level performance.

• Export historical FAQ rich result data before the reporting disappears. If you’ve got an internal dashboard pulling Search Console API data, archive the relevant extracts now so you can still answer "what changed" later.
• Compare affected pages’ CTR before and after May 7, 2026. Pick a clean window (for example, 28 days before vs. 28 days after) and keep it consistent across page groups.
• Identify pages that relied on FAQ dropdown visibility. In practice, these are often high-impression, mid-position pages where the dropdowns were doing a lot of persuasion work.
• Monitor organic CTR, impressions, and clicks at page level in Search Console. Don’t over-focus on query-level noise when the UI treatment is what changed.
• Don’t panic if the FAQ enhancement or search appearance reporting disappears from Search Console. That disappearance is the planned retirement, not a new penalty.

Should You Keep or Remove FAQ Schema?

This comes up constantly, usually right after someone notices their FAQ rich results are gone and assumes something is "broken." The decision is less about Google features now and more about whether the markup reflects real, visible content that helps users.

Google has previously said there’s no reason to proactively remove structured data that no longer triggers a visible feature, and it doesn’t create problems for Search. SearchPilot tested this in late 2024 and found that removing the schema didn’t produce a statistically significant change in organic traffic.

So don’t burn developer cycles on a cleanup project that won’t move the needle. But do stop shipping junk FAQ schema out of habit. I’ve seen teams keep a templated FAQ block on thousands of pages because "it used to work," even after it stopped doing anything visible. That’s how you end up maintaining code nobody benefits from.

One nuance worth keeping: FAQPage markup may still help machines understand the relationship between questions and answers, even if it no longer triggers a Google rich result. That’s a very different claim than "it helps you get picked by AI." It’s just making your intent unambiguous.

Update Your Testing and Reporting Workflows

Teams that used the Rich Results Test as a quick QA step for FAQ validation need a new habit in June 2026, because that support is being removed. Same story for reporting pipelines that pull FAQ rich result dimensions through the Search Console API, that support is expected to be removed in August 2026.

Practical fix: update your checklists so FAQPage schema validation is treated as general structured data QA (schema validity, content matches what’s visible, no spammy Q&A), not a "will we get the dropdown" gate. And if you’ve got automated reports, swap out FAQ-specific widgets for page-level CTR and query clusters that reflect actual business pages.

From SEO to AEO: The New Playbook

Answer Engine Optimization (AEO) is the practice of shaping content so AI systems can understand it, trust it, and cite it as the direct answer to a query. The goal shifts from "rank #1" to "be the source." Traditional SEO still matters as the base layer, but AEO is the next layer on top of it: the work that keeps your brand present when the interface stops being ten blue links and starts being a single synthesized response.

This is also where all that legacy FAQ content can stop being dead weight. Instead of serving as SERP ornamentation, it becomes raw material you can turn into something durable. Here’s how to adjust:

• Reframe for Direct Answers: Write like you expect your best sentence to be quoted. Aim for short, unambiguous answers that stand on their own, then back them up with context. Keyword density matters less here than accuracy and "extractability." If an AI model pulled two lines from your page, would the result still read like a complete answer? That’s the bar.
• Embrace Entity-Based Content: AI models organize information around entities (people, places, products, concepts) and the relationships between them. Your content should make those entities explicit. Use structured data beyond FAQPage (including Organization, Product, and Article) to help Google build a clearer picture of who you are and what you’re credible on. This is central to how AI mode changes SEO.
• Focus on Authority, Not Just Keywords: Google didn’t keep FAQ rich results around for government and health sites by accident. It kept them where it expects higher trust. An AEO strategy has to start with real expertise and verifiable accuracy. This goes past E-E-A-T as a slogan and into the work of publishing content an AI system can safely rely on. This is a core reason why organic marketing is beyond SEO.
• Monitor Mentions, Not Just Ranks: In an AEO world, "how are we ranking?" is only part of the picture. The more telling question is whether your brand shows up as a cited source inside AI Overviews. That means tracking visibility inside AI-generated answers, which is exactly what Answer Engine Monitoring platforms like Vizup are built to do.

What This Means for Your Content Strategy in 2026

FAQ rich results didn’t vanish in isolation. Paired with Google’s recent core updates, the move reads like a loud signal that the old playbook is losing its leverage. Churning out "more content" isn’t a plan anymore. The work now is publishing content that’s tighter, better structured, and easier for machines to interpret and trust.

Start with an audit of the FAQ content you already have. Was it written to help real people, or was it written to win a SERP feature? Keep what’s genuinely useful and put it where it belongs: on core product and service pages, answering objections and clarifying edge cases. Leave FAQ schema in place where it fits, but treat it as structured content hygiene, not a bid for extra pixels in the results.

For net-new content, work backward from the question. What, exactly, should the answer be? Can you state it plainly enough that a machine won’t misread it? Which entities show up in the explanation, and how do you define them with structured data? Our AI Search Visibility Optimization: 2026 Playbook goes into deep detail on these tactics.

Losing FAQ rich results stings if you built workflows around them, and the June and August 2026 reporting retirements make it feel even more final. But it also removes a lot of low-value noise from the SERP. The upside is a forced return to fundamentals: publish authoritative, genuinely helpful material, then measure what users actually do. The twist is that the first "reader" is often an AI system deciding what to quote. Brands that adapt to that reality stand to gain something more valuable than an expanded snippet: they get to be the cited source when the answer is delivered upfront.

Your FAQ Schema Questions Answered

What were FAQ rich results?

FAQ rich results were a Google Search feature that displayed a page’s questions and answers directly in the SERP as expandable dropdowns. Google reduced visibility for most sites in 2023, and as of May 7, 2026, FAQ rich results no longer appear in Google Search.

Should I remove FAQPage schema from my website now?

Not automatically. Keep FAQPage schema if the Q&A content is real, visible on the page, and helpful. Remove or clean it up if it was added only to manipulate rich results. Google has said there’s no need to proactively remove structured data that isn’t being used for a visible feature, and SearchPilot’s late-2024 test found removing it didn’t produce a statistically significant organic traffic change.

What is the difference between AEO and SEO?

SEO is primarily about ranking pages in a list of links. Answer Engine Optimization (AEO) is about getting your content selected and cited as the direct answer inside AI-powered features like Google’s AI Overviews. It’s a shift from chasing position to becoming the referenced source.

Does structured data still matter after this change?

Yes, structured data still matters. Even though FAQ rich results are gone, structured data can help machines interpret what a page contains. Just don’t treat any schema type as a guarantee of visibility in AI answers.

How do I measure the success of AEO after FAQ reporting disappears?

Start with page-level metrics in Search Console (clicks, impressions, CTR) and compare performance before and after May 7, 2026 for pages that previously benefited from FAQ dropdown visibility. For AEO, success shows up as brand visibility and share of voice inside AI-generated answers, not only as traditional keyword rankings. That typically requires tooling that can track when you’re cited across answer engines and queries, such as Vizup. For more on measurement pitfalls, see what it really means.