As of 7 May 2026, Google no longer shows FAQ rich results in Search – and it’s dismantling the reporting and tooling that sat around them. For an entire generation of SEOs and content teams who built FAQ sections and schema into their templates, this is more than a visual tweak; it’s the end of a playbook.
In this piece I’ll unpack what’s actually changing, why Google is doing it, and what this means for anyone still clinging to “add more FAQ schema” as an SEO strategy.
What Has Google Actually Changed?
Google has updated the FAQ structured data documentation with a clear, blunt notice: FAQ rich results are gone from Search. That single line sets off a short but important deprecation timeline.
- From 7 May 2026: FAQ rich results no longer appear in Google Search at all.
- In June 2026: Google will drop the FAQ search appearance in Search Console, remove the FAQ enhancement report, and remove support in the Rich Results Test.
- In August 2026: Support for FAQ rich results will be removed from the Search Console API.
The visual treatment – those expandable Q&A dropdowns under a blue link – is gone, and the ecosystem you used to monitor and debug them is being taken with it. If you still have FAQPage structured data on your pages, it no longer produces this specific rich result in Google’s SERPs.
Google isn’t telling you to rip out the markup. In fact, it explicitly notes that you can remove it if you want to, but you don’t have to: other search engines may still use it, and Google will continue to use FAQ structured data as a content understanding signal. But the days of “implement FAQ schema → get more SERP real estate” are over.
FAQ Rich Results Were Already on Life Support
This didn’t come out of nowhere. FAQ rich results have been on a slow road to deprecation for years.
Back in August 2023, Google announced it would “show fewer rich results” for FAQs and HowTos “to provide a cleaner and more consistent search experience.” FAQ displays were limited primarily to well‑known, authoritative government and health sites, while HowTo results became desktop‑only.
By 2025, Google had already started to prune other low‑value or niche rich result types – book actions, course info, estimated salary, special announcements and more – specifically citing an intent to simplify the search results page.
The 2026 announcement completes that arc. Commentators have rightly framed it as Google “nuking” FAQ rich results completely after cutting them back in 2023. What changes now is that even those favoured government and health domains no longer see the old FAQ panel in search, and the official monitoring/reporting scaffolding is being removed.
Why Would Google Kill a Feature SEOs Loved?
Officially, this is about quality and simplicity. Google has consistently described the earlier FAQ and HowTo changes as steps toward a “cleaner and more consistent” search experience. But if you look at the pattern – and the state of modern SERPs – there are deeper reasons.
1. Diminishing user value in an AI‑first SERP
FAQ panels made sense in a world of ten blue links and a few side dishes. In a world of AI Overviews, bigger “People also ask” modules, and answer‑style blocks everywhere, a set of templated dropdowns under a single listing offers less incremental value than it once did.
As more answers are synthesised into dedicated units, Google has less incentive to give one site a giant FAQ block just because it added the right schema.
2. Abuse, over‑templating, and noise
Once plugins and “FAQ schema checklists” went mainstream, FAQ markup became a commodity. It was poured into footers, bloated product pages, and content that was never really designed around user questions.
When a feature becomes heavily templated, overused and sometimes outright spammed, its value declines – both for users and for the engineers trying to maintain it. The fastest way to solve that problem is to turn off the visual reward.
3. Maintenance cost vs strategic importance
Every rich result type Google supports has to be:
- Defined and documented.
- Integrated into ranking, rendering, and evaluation.
- Supported in Search Console reports, the Rich Results Test, and APIs.
For a legacy format that’s already been heavily restricted and generates limited incremental user value, the ongoing maintenance cost simply isn’t worth it. Removing the UI, reports, and test support sends a strong signal: this is not a feature Google wants to carry into the next era of Search.
4. Clearing space for new answer experiences
As Google reworks the SERP around generative answer experiences, it needs predictable layouts and fewer legacy “bolt‑on” features. Hard‑coded FAQ panels are a constraint; flexible answer units that can pull in Q&A‑style content from multiple sources are not.
By killing the FAQ rich result surface but keeping FAQ structured data as an understanding signal, Google gains the freedom to reuse that information in AI Overviews and other modules without being bound to a specific, legacy presentation.
What This Means for Your FAQ Content and Schema
The obvious question: “Should we remove all our FAQ content?” The answer is no – but we do need to change why that content exists.
FAQ schema: remove, keep, or repurpose?
Given Google’s stance, you have three options:
- Leave the markup in place: It no longer produces a rich result in Google, but it may still help other search engines and could marginally improve Google’s understanding of your page.
- Strip it out over time: If it’s adding bloat or complexity to your codebase, this is now a low‑risk simplification, especially for sites where Google was your only meaningful search referrer.
- Repurpose your schema strategy: Treat FAQPage markup as one of several structured data types you use to clarify content, not as a lever for guaranteed SERP “bling”.
Importantly, keeping FAQ markup in place no longer needs to be a priority task in your Google‑centric roadmap. It is now a nice‑to‑have at best.
FAQ content: retire the tactic, keep the intent
What you absolutely should not do is take this as a signal that question‑led content is dead.
User questions still drive search behaviour. People still type “how”, “why”, “what” and “which” queries, and those questions still surface in “People also ask”, AI Overviews and other answer boxes.
The change is that you can no longer rely on a dedicated FAQ block under your listing as the primary way those answers appear in the SERP. Instead:
- Fold critical Q&A into the main body copy and headings, rather than banishing it to a separate FAQ appendix.
- Use question‑based sub‑headings where they genuinely match user intent, not as a mechanical keyword stuffing exercise.
- Focus on depth and clarity of answer, not volume of questions per page.
The user value of good FAQs hasn’t changed. Only the old UI reward has.
The End of “Markup → Guaranteed SERP Bling”
If you zoom out, the death of FAQ rich results is another reminder of a broader truth: structured data is an input, not a contract.
| Old mindset | New reality |
|---|---|
| Add FAQ schema, get FAQ snippets | Add structured data, maybe get used in various ways; no UI guaranteed. |
| Reports define success | Reports are a partial lens; features can vanish even if reports look fine. |
| Schema as a growth hack | Schema as hygiene for content understanding and eligibility. |
| Feature‑specific playbooks | Durable strategies around content quality, UX, and answer usefulness. |
Google’s own messaging underscores this. For both the 2023 FAQ/HowTo changes and the 2026 deprecation, the company stressed that rankings themselves were not the target; the goal was to simplify and standardise presentation.
For teams who have spent years selling “schema = rich snippets = higher CTR” internally, this is going to require a reset. FAQ rich results helped many sites boost click‑through rates when they were widely available – but that era is over.
How to Talk About This With Stakeholders
If you’re the person who championed FAQ schema, you now have to explain why the feature has disappeared without panicking your stakeholders. A few practical angles:
- Emphasise that this is a product decision by Google, not a penalty or a failure on your part.
- Show the timeline: 2023 restrictions, 2025 rich result simplifications, and 2026 deprecation. This wasn’t a sudden U‑turn; it’s the conclusion of a multi‑year trend.
- Reframe success around resilience: teams that treated FAQ schema as one tactic among many can adapt quickly; teams that depended on it as a pillar need to diversify.
- Use this as a teaching moment about the difference between formats (which come and go) and fundamentals (meeting user needs, clean information architecture, technical hygiene).
If you have historical data, it’s worth documenting the positive impact FAQ rich results once had on CTR and traffic, then showing how Google’s 2023 restrictions and 2026 kill switch gradually eroded that value. That helps stakeholders see this as an external shift, not a sudden performance “drop” that can be fixed with yet another plugin.
Where to Focus Next
So, where should the “FAQ budget” go now?
- Double down on question‑driven research: Use FAQs, People also ask, site search logs, and customer support data to inform your content topics and structures, not just footer sections.
- Invest in content that can be repurposed into multiple surfaces: on‑page answers, support documentation, knowledge bases, and assets that can feed emerging AI search experiences.
- Maintain a lean, purposeful schema strategy: prioritise types that still have clear value (e.g., Product, Organization, Article, LocalBusiness, Breadcrumb) and keep your implementation clean.
- Watch how Google and other engines reuse Q&A‑style content in AI Overviews and related modules; that’s the new “rich result”, even if it doesn’t carry that label.
FAQ rich results are gone, but searchers are still asking questions. The teams that win the next phase of Search will be the ones who stop chasing specific UI treatments and start designing content that can survive product decisions like this one.
