Google Kills FAQ Rich Results May 2026: Your FAQ Schema Isn't Dead — It Just Moved

The Seven-Year FAQ Rich Results Lifecycle

The May 7 deprecation didn't come out of nowhere. It's the final chapter in a multi-year rollback that long-time SEOs saw coming. Understanding the timeline helps explain Google's motivations and what comes next for structured data.

For SEOs who were still hoping their carefully-implemented FAQ schema would magically come back to the SERPs after 2023, the May 7 announcement is the formal goodbye. But anyone who's been paying attention to the rise of AI Overviews already knows: the action moved.

Why This Matters for SEOs and Publishers

Google has been explicit that the deprecation is a display change, not a ranking change. Page positions don't move because of this. But the practical implications run deeper than just “CTR may drop slightly.”

Who's Affected

• Government and health publishers: These were the only sites still getting FAQ rich results after the 2023 restriction. They lose a visible SERP feature they relied on for citizen-facing and patient-facing queries. Expect CTR drops on previously-enriched pages.
• E-commerce and SaaS sites: Most lost FAQ rich results in 2023, but many still ship FAQ schema with every product and pricing page. The schema continues to feed AI extraction. Don't remove it.
• Content sites running AEO playbooks: FAQ schema has been a cornerstone of generative engine optimization (GEO) advice for the past two years. Templated FAQ schema at scale is one of the patterns AEO consultants pushed hardest. Those investments are still valid — provided the FAQs answer real questions.
• Agency clients with FAQ-heavy strategies: Account managers should preempt the “why did our rich result disappear?” conversation by explaining that the schema is still doing work — just on AI surfaces rather than blue links.

Notably, this is the third major rich-result deprecation in Google's recent push to simplify SERPs: HowTo (mobile, 2023), FAQ (2023 restriction, 2026 removal). The trajectory is clear — Google is consolidating rich features and pushing answer-style content into AI surfaces instead.

What Experts Are Saying

The SEO community has had a measured reaction to the announcement — equal parts “we saw this coming” and “what does this mean for our AEO strategy?”

“Interesting timing: Google is dropping rich results support for all FAQ Schema, and is removing FAQ structured data reporting from GSC. I wonder why they decided to do this right now in May 2026? Google had already deprecated FAQ rich results back in 2023 for most sites. So, this wouldn't be the first time that Google is playing the cat and mouse game when they see too many sites using the same exact techniques 'for SEO/GEO.'”

Ray's point about pattern abuse is significant. Over the past two years, AEO and GEO advice has emphasized adding FAQ schema across as many pages as possible to surface in AI answers. The result was a flood of templated, sometimes irrelevant FAQ markup. Removing the rich result removes the SEO incentive to game the system without removing the legitimate use case for structured Q&A.

“Google is clearly saying FAQ structured data is not important for ranking across its AI surfaces like AI Overviews and AI Mode — at least not as a guaranteed display signal. But that doesn't mean the schema is useless. It still helps Google understand your page structure.”

Gabe, one of the industry's most respected algorithm analysts, draws an important distinction: Google's deprecation removes the visual display, not the underlying understanding signal. His read aligns with Google's own documentation language — “Google will continue to use it to better understand pages.”

“Publishers should monitor traffic impact on pages with FAQ structured data, though removing the code is optional. Rich results have historically improved click-through rates — losing the display feature can reduce CTR even when rankings stay flat.”

Schwartz's framing captures the practical takeaway. There's no urgent action required — no mass schema removal, no panicked rewrites — but there is real work in monitoring whether the loss of the rich result is showing up in your click data. Pages that previously benefited from the expandable FAQ display may see CTR softening even with stable positions.

The AEO Pivot: Your FAQ Schema Just Got More Valuable

Here's the part most coverage of this deprecation buries: FAQ schema visibility didn't disappear. It moved. The same structured Q&A data that powered SERP rich results from 2019–2023 now powers AI Overview citations, ChatGPT Search extractions, Perplexity answer cards, and Gemini responses. The visibility just shifted surfaces.

Industry AEO benchmarks consistently show that pages with FAQPage structured data are cited at significantly higher rates by AI engines than equivalent pages without. The mechanism is intuitive: AI engines need to extract clean question-answer pairs to generate conversational responses. Pages that pre-formatted that data save the model the work and increase the probability of accurate extraction.

This dovetails with Google's broader AI Mode and AI Overviews rollout, which is increasingly the surface where high-intent search traffic lives. AI Overviews already trigger on 30%+ of queries in 2026, and structured Q&A content is one of the cleanest extraction patterns those systems have to work with.

For practitioners who manage AI citation strategies across platforms, the takeaway is straightforward: FAQ schema graduates from being a SERP feature investment to being an AEO infrastructure investment. The schema gets a longer working life precisely because it can now be optimized purely for AI extraction quality, without the SEO baggage of trying to game a visual SERP feature that's no longer there.

What to Do Now: Your 6-Step Action Plan

Here's the practical sequence for adapting to the May 7 change — ordered by urgency. None of this is panic work; it's the kind of structured response that pays off over the next quarter.

Step 1: Audit CTR Impact on Previously-Enriched Pages

Open Google Search Console and identify the pages that were getting FAQ rich results before May 7 (especially relevant if you're a government or health publisher). Compare CTR for those URLs week-over-week, May 1–6 vs May 7–13. If you see a drop in CTR while average position holds steady, that's the rich-result loss showing up in your data. Document it now — you'll want the baseline.

Step 2: Keep Your FAQ Schema — Don't Mass-Remove It

The single most common mistake we expect to see in the next month is sites stripping FAQ schema in response to the rich result going away. Don't do this. Google explicitly said the schema is still valid, still helps with page understanding, and unused structured data does not hurt Search. Beyond that, AI engines actively use the markup. Removing it costs you AEO visibility for zero gain.

Step 3: Audit Your FAQs for Real Answer Quality

With AI extraction as the new primary use case, FAQ content quality matters more than markup count. Pull your top 20 FAQ-bearing pages and ask: are these answers real, complete, and based on user questions people actually ask? Or are they templated filler added “for SEO/AEO”? The templated ones don't earn AI citations — AI engines pull answers that look like answers a human would write.

To regenerate a fresh batch of question-answer pairs based on real search intent, our free FAQ Generator produces answer-quality Q&As you can drop into pages — especially useful for old FAQ blocks that read like robotic placeholders.

Step 4: Validate and Refresh Your FAQ Markup

Now is a good moment to make sure the schema you're carrying is actually clean. Stale FAQ markup — outdated questions, broken HTML in answers, missing required fields — was always a problem; it just wasn't visible. AI engines are less forgiving than the rich result snippet generator was. Validate your markup with our free FAQ Schema Generator or run a sample page through Google's Rich Results Test (while it's still available through June 2026).

Step 5: Track AI Overview Citation Coverage

Since the FAQ rich result report is going away in Search Console, you need a replacement signal for whether your structured Q&A is being used. Sample 10–20 of your highest-priority queries and check whether your FAQ-bearing pages are surfacing as citations in Google AI Overviews and AI Mode responses. Track this monthly. If citation rates rise, your AEO investment is working. If they fall, your FAQ content quality (not your schema) likely needs attention.

Our free AI Overview Analyzer can help by showing whether your domain is being cited in AI Overviews for specific queries — useful as a replacement signal for the disappearing rich result reports.

Step 6: Don't Add FAQ Schema Where It Doesn't Belong

Lily Ray's observation about templated FAQ schema is a warning, not just commentary. If your strategy was “add FAQ schema to every page so it gets surfaced more,” that strategy was always weak and is now demonstrably out of step with Google's direction. Reserve FAQ schema for pages that genuinely contain questions and answers users care about — product detail pages, service pages, how-to articles, support content. Don't pad blog posts with synthetic FAQs to try to game AI citations.

Tools to Help You Adapt

The right tools make the difference between guessing and knowing what's working. These are the most useful for navigating the FAQ rich results deprecation and pivoting to AEO.

External Validation Resources

What to Expect Next

The FAQ rich results deprecation is part of a clear pattern: Google is consolidating rich SERP features and pushing answer-style content into AI surfaces. Expect this trajectory to continue. HowTo rich results were already restricted on mobile; FAQ is now gone entirely. Other display features that emerged in the 2018–2020 schema rush could follow.

The bigger signal is Google's growing comfort with letting structured data do its work invisibly — feeding page understanding, AI Overview citations, and entity graphs without rewarding implementors with a visible rich result every time. That's a maturation of how structured data is treated: less “here's a SERP perk for using markup,” more “here's an infrastructure layer for our retrieval systems.”

On the practical side, watch for two follow-ons. First, the June 2026 removal of FAQ reporting in Search Console will be the actual moment when many SEOs notice the change — that's when the report literally disappears from their dashboards. Second, Search Console API users have until August 2026 to migrate any tooling that depends on FAQ rich result data. If your team uses the API in dashboards or reports, plan that migration now.

We'll update this article as the rollout completes through August 2026. If Google issues additional guidance on related schema types — especially Article, QAPage, and HowTo — we'll add the details here.

Frequently Asked Questions