On May 7, 2026, Google did something it had been signaling for nearly three years: it permanently pulled the plug on Google FAQ rich results. No grace period, no gradual phase-out for the remaining eligible sites — just a clean, final deprecation confirmed directly in Google’s developer documentation. If your SEO strategy included the FAQPage schema as a reliable click-through lever, that lever no longer exists on Google Search. Search Console will stop reporting FAQ rich result data in June 2026, and API support follows in August 2026.
This isn’t a minor feature tweak. It closes a chapter that began in 2019 when Google opened FAQ rich results to virtually any website, briefly handing brands an outsized advantage in SERP real estate — and it reflects a clear philosophical shift in how Google thinks about structured data, user experience, and the relationship between markup and organic visibility. The businesses that understand why this happened, not just what happened, will be the ones positioned to make the right strategic moves next.
Key Takeaways
- Google stopped FAQ rich results on May 7, 2026.
- Search Console FAQ reporting will stop in June 2026.
- Search Console API support ends in August 2026.
- You can keep or remove the FAQ schema — your choice.
- The FAQ schema may still serve non-Google search engines.
- Shift focus to Product, HowTo, and Article structured data.
- Prioritize content quality over schema dependency.
- AI-driven search is reshaping what structured data matters.
Why Google Removed FAQ Rich Results
Here’s the part that doesn’t get enough attention: Google didn’t abandon FAQ rich results because the feature didn’t work. In fact, for a period, it worked rather well — pages with FAQ schema were getting significantly expanded SERP real estate, sometimes pushing competitor listings further down the page just by having a few questions marked up.
That was exactly the problem.
By 2023, Google had already pulled back FAQ rich results from most commercial and informational sites, restricting them only to government and health-focused domains. The rationale was clear: the feature was being used more as an SEO tactic than as a genuine user experience tool. Brands were stuffing FAQ schema everywhere — product pages, homepages, even contact pages — not because users needed those answers surfaced in Google, but because it inflated click-through rates artificially.
Google’s core concern has always been SERP real estate fairness and result quality. When the data showed that FAQ rich snippets weren’t improving user satisfaction in any meaningful way beyond the health and government context, the writing was on the wall. The final deprecation on May 7, 2026, was less a surprise and more an inevitability.
Timeline of Google’s FAQ Changes
Understanding this isn’t just recent news (it’s a multi-year story).
2019: Google launches FAQ rich results broadly, allowing almost any site to implement FAQPage schema and appear with expanded Q&A in search results. Click-through rates for pages with FAQ schema jump noticeably.
August 2023: Google significantly limits FAQ rich results to well-known, authoritative government and health sites. Most commercial websites lose their FAQ rich result eligibility overnight — triggering significant drops in CTR for many content-heavy sites that had relied heavily on the feature.
Late 2023 – 2025: Google Search Console continues reporting FAQ rich result data, but for the vast majority of sites, the feature is effectively dormant. A quiet period — but one that gave a false sense of stability.
May 7, 2026: Google officially removes all FAQ rich result support. Search Console will stop reporting on FAQ structured data, with the FAQ rich result report and support in the Rich Results Test dropping in June 2026, and Search Console API support being removed in August 2026.
SEO Impact of the Update
Let’s be direct: for most businesses, the practical traffic impact of this specific change in May 2026 is relatively small. Why? Because Google already gutted the feature for commercial sites back in 2023.
What this does affect is the psychological anchor that many SEO teams held onto — the idea that keeping FAQ schema in place was “doing no harm and possibly some good”, now you don’t have that safety net.
However, there’s a real cost worth naming: teams that built entire content templates around FAQ schema — templated landing pages, service pages, and pillar content structured around FAQPage markup — may find that a layer of their structured data strategy needs rethinking. It’s not catastrophic, but it does require an honest audit.
The more interesting SEO question isn’t about traffic loss. It’s about what this signals for the direction of Google structured data updates more broadly. Google is increasingly moving toward AI-generated overviews and surface-level summarization. Features that hand over information to Google for free display — without driving the user to your site — are being quietly deprecated. FAQ rich results fit that pattern perfectly.
Curious how your structured data strategy stacks up for AI-driven search? Talk to our team at 6S Marketers, and we’ll show you exactly where to focus.
Should You Remove FAQ Schema?
Short answer: not necessarily. Longer answer: it depends on what you’re optimizing for.
Google has confirmed that you can remove the FAQ structured data from your code if you want, but you can also leave it, as other search engines may be able to continue to process it and use it for their own purposes.
Bing, for instance, still processes schema markup for its own rich result formats. If your business has meaningful traffic from Bing or other non-Google search engines, removing FAQ schema could actually cost you visibility there.
The smarter move? Don’t treat this as a “remove everything” moment. Instead, do a structured audit: identify pages where FAQ schema was the primary structured data type and evaluate whether those pages would benefit more from HowTo, Article, or Product schema instead. If FAQ sections on your pages serve a genuine user purpose — which they should — keep the on-page content. Just don’t make the schema the center of your technical SEO bet.
Check out our complete schema markup guide for a breakdown of which structured data types still carry real weight in 2026.
What SEOs Should Do Next
Audit your Search Console data now. Before Google drops the FAQ rich result report in June 2026, export your historical data. If you’ve been tracking impressions and clicks from FAQ rich results, this data tells you which pages were actually benefiting — and that’s your baseline for comparison over the next 90 days.
Don’t panic-remove schema. Rushed schema removal without a replacement strategy is how sites accidentally tank their structured data signals across the board. Be deliberate.
Redirect your FAQ content energy. FAQ sections on your site still matter for organic search and for feeding AI-generated answer boxes, even if the specific JSON-LD FAQPage type no longer drives a rich result on Google. Write cleaner, more concise question-and-answer content and think about how your content can appear in AI systems like ChatGPT — that’s where the real emerging opportunity lies.
Monitor CTR changes by page. If the FAQ schema was already suppressed for your site since 2023, this update may register as near-zero impact. But for the rare health or government site that was still seeing FAQ rich results, watch your click-through rates weekly for the next two months.
Alternative Structured Data to Focus On
Here’s where to redirect your structured data investment in a post-FAQ world.
Product schema remains one of the most powerful for e-commerce and SaaS companies. It surfaces pricing, ratings, availability, and reviews — exactly the signals high-intent buyers look for before clicking through.
HowTo schema still drives rich results for instructional content. If your content educates prospects on solving problems your product addresses, this schema type is underused and undervalued by most commercial sites.
Article schema combined with strong E-E-A-T signals (Experience, Expertise, Authoritativeness, Trustworthiness) is increasingly relevant as Google leans harder into content quality signals for AI feature eligibility. For B2B content teams publishing thought leadership and technical content, this is where structured data energy belongs.
Review and AggregateRating schema consistently improve CTR for product-adjacent pages and continue to see active support from Google. Don’t overlook it in favor of newer schema types.
Want to build a structured data strategy that actually maps to business outcomes? Let’s talk.
Conclusion
The removal of Google FAQ rich results isn’t the end of structured data — it’s a reorientation. Google is telling us, clearly and finally, that it will no longer reward schema that inflates SERP presence without genuinely improving user experience or search quality.
For marketing leaders and content strategists, the takeaway is this: structured data is still a meaningful investment, but only when it’s tied to content that users actually need surfaced in a specific format. The FAQ era was, in retrospect, a chapter where SEOs found a loophole, and Google eventually closed it.
The next chapter favors teams who invest in content depth, schema that maps to genuine user intent, and visibility across AI-powered answer surfaces — not just traditional SERP features.
External Sources: