If you’ve ever spent time carefully adding FAQ schema to your web pages hoping to snag those eye-catching expandable question boxes in Google search results — well, I’ve got some news for you. Google has officially pulled the plug on FAQ rich results, and this time, it’s permanent.
Let’s break down what actually happened, why it matters, and more importantly what you should (and shouldn’t) do about it.
What Happened, Exactly?
On May 7, 2026, Google quietly deprecated its FAQ rich results feature. No big announcement, no blog post, no fanfare. Just a notice tucked into Google’s structured data documentation that reads something like: “FAQ rich results are no longer appearing in Google Search.”
That’s it. Three years of gradually stepping back from this feature, and it ended with a single sentence in the docs.
Here’s the timeline you need to know:
- May 7, 2026 — FAQ rich results stopped showing in search results entirely
- June 2026 — Google will remove the FAQ report, rich result filter, and Rich Results Test support in Search Console
- August 2026 — Search Console API support for FAQ rich results will be removed
So if your team is pulling FAQ data through the Search Console API, you’ve got until August to update those integrations. Don’t ignore that deadline.
This Wasn’t Exactly a Surprise
Honestly? This has been coming for a while. Google first started pulling back from FAQ rich results back in 2023, when it quietly reduced their visibility in search results. Then in August of that same year, Google made a bigger announcement: FAQ rich results would only appear for government and health websites — the kind of sites Google considers highly authoritative.
Every other site? Already cut off.
This latest move appears to end even that limited exception. Government and health sites are now out too. It’s a full shutdown across the board.
Do You Need to Rip Out Your FAQ Schema?
Here’s the part that’ll save you a headache: no, you don’t.
Google has been clear that having structured data on your page that isn’t actively producing rich results won’t hurt your site. FAQPage is still a valid Schema.org type, and leaving the markup in place won’t penalize you in any way.
That said, if you’re maintaining a large site and your developers want to clean up the codebase, removing unused schema is perfectly reasonable too. It’s a judgment call, not an emergency.
What you don’t need to do is panic and start a site-wide audit this week.
The Bigger Picture: Where Is Google Headed?
This move fits into a larger pattern. Google has been trimming back rich result types for a while now — HowTo rich results on mobile were deprecated around the same time as the 2023 FAQ restrictions.
What’s driving this? Google hasn’t said. But it’s worth noting that FAQ schema has come up in a lot of AI-search optimization advice lately — the idea being that clearly structured Q&A content is easier for AI systems to parse and cite. Whether Google’s deprecation is a response to that trend or just routine housekeeping, we honestly don’t know. Google hasn’t connected the dots for us.
What we do know is that search is evolving fast, and features that were SEO gold a few years ago can quietly disappear. That’s just the reality of working in this space.
What Should You Focus on Instead?
If FAQ schema was part of your SERP visibility strategy, it’s time to redirect that energy. Here are a few areas worth your attention:
- Content quality over schema tricks — Google’s AI-powered features reward genuinely helpful, well-structured content more than any markup hack
- Other structured data types — Product, Review, Article, and How-To (in certain contexts) schemas still deliver value
- AI search optimization — With AI Overviews and similar features growing, focusing on clear, authoritative, well-cited content is increasingly important
- E-E-A-T signals Experience, Expertise, Authoritativeness, and Trustworthiness remain the foundation of long-term search visibility
Final Thoughts
Look, change is constant in SEO. Google quietly deprecating a feature that was already on life support for two years isn’t the end of the world it’s just a reminder to stay adaptable.
If you built a strategy around FAQ rich results, use this as a nudge to audit what’s actually driving your visibility today and where to invest your schema efforts going forward. The sites that win long-term are the ones that focus on genuine content quality and user value, not on chasing markup shortcuts.
And honestly? If a feature disappears and your traffic doesn’t move, that’s a useful data point too.
FAQs
Will removing FAQ schema from my site hurt my rankings?
No, it won’t. Google has confirmed that unused or removed structured data doesn’t negatively impact your search rankings. The markup simply won’t produce visible rich results anymore. Whether you keep it or remove it is entirely your call there’s no SEO penalty either way.
My site is a government or health website am I also affected?
Yes. While the 2023 restrictions left FAQ rich results active only for authoritative government and health sites, this latest deprecation appears to cover everyone. As of May 7, 2026, FAQ rich results are no longer showing for any site, regardless of industry or authority level.
Search Console is showing FAQ data right now should I be worried?
Not immediately. Google has said that the FAQ report and related Search Console features will be removed in June 2026. What you’re seeing now is legacy data. Just be aware that the report will disappear next month, so export any data you want to keep before then.
I use the Search Console API to pull FAQ data when do I need to act?
You have until August 2026 before Google removes Search Console API support for FAQ rich results. That’s your runway to update any integrations or dashboards that depend on that data. Don’t leave it to the last minute August will come faster than you think.
Does FAQ schema still help with AI search tools like ChatGPT or Perplexity?
This is a genuinely interesting question, and the honest answer is: maybe. Some SEO practitioners have suggested that clearly structured Q&A markup helps AI systems parse and cite your content more easily. But Google hasn’t confirmed or denied any connection between FAQ schema and AI search performance. Keep an eye on this space it’s evolving quickly.
What structured data types should I prioritize going forward?
The ones tied to actual search features that are still active. Think Article schema for news and blog content, Product and Review schema for e-commerce, Recipe schema for food sites, and Event schema if applicable. The key is to use structured data that corresponds to a live Google feature not to chase features that have already been deprecated.