Google has officially announced a major change — as of May 7, 2026, FAQ rich results are no longer appearing in Google Search. If you’ve been using FAQPage structured data on your site, here’s everything you need to know. Posted

What Were FAQ Rich Results?

FAQPage is a Schema.org structured data markup. When implemented correctly on a webpage, it allowed Google to display questions and answers directly in the search results — this was called an FAQ Rich Result. It helped sites improve their click-through rate (CTR) and occupy more real estate on the SERP.

Deprecation Timeline

May 7, 2026 — Already in Effect FAQ rich results have stopped appearing in Google Search completely.

June 2026 Google will remove the FAQ search appearance report from Search Console, drop FAQ support from the Rich Results Test tool, and stop showing FAQ as a valid rich result type.

August 2026 Support for FAQ rich results in the Search Console API will be fully removed. Developers who pull FAQ rich result data via API need to update their integrations before this date.

Who Was Eligible in the First Place?

This is worth noting. FAQ rich results were never available to everyone. According to Google’s documentation, the feature was only available to well-known, authoritative websites that are government-focused or health-focused. General commercial websites, blogs, and news sites had very limited or no access to this feature.

FAQPage vs. QAPage — What’s the Difference?

Many people confuse these two. Here’s the distinction:

FAQPage — The site itself controls both the questions and the answers. Users cannot submit answers. Example: a government health FAQ page.

QAPage — A single question where multiple users can submit answers. Example: Stack Overflow, Quora-style platforms.

The important thing to note: QAPage structured data is still supported by Google. Only FAQPage rich results are being deprecated. If your site allows users to submit answers to questions, switch to QAPage markup — it still works and can still generate rich results.

What Should You Do Now?

1. Check your Search Console data Before June 2026, go into Search Console and save any historical FAQ rich result data you want to keep. Once Google removes the report, that data will be gone.

2. Update your API integrations If your platform pulls FAQ rich result data through the Search Console API, you must update those calls before August 2026 to avoid errors.

3. Don’t panic about existing FAQPage markup You don’t need to rush and remove all FAQPage structured data from your site. It won’t hurt your rankings. It just won’t generate a rich result anymore. That said, don’t add it to new pages going forward — there’s no point.

4. Focus on Featured Snippets instead Even without structured data, Google can still pull your FAQ-style content into a Featured Snippet. Clear, well-structured Q&A content written in plain language still has value. The markup is gone, but the content strategy isn’t.

5. Consider QAPage if applicable If your site has community-driven answers, migrating to QAPage structured data is a smart move since Google still supports it.

Will This Hurt Your SEO?

For most sites — not significantly. FAQ rich results were already restricted to government and health sites, so the majority of websites weren’t benefiting from them anyway. For those that were, the loss of the rich result means less SERP real estate and potentially lower CTR.

However, since this change affects everyone equally, the competitive landscape doesn’t shift dramatically. The bigger risk is for developers and agencies who haven’t updated their API integrations before the August deadline.

Key Takeaways

FAQ rich results are gone as of May 7, 2026 — this is already live.
Google will remove FAQ from Search Console reports in June 2026 and from the API in August 2026.
FAQPage markup won’t hurt your site, but it no longer provides any benefit.
QAPage structured data is still supported — use it if your content model fits.
Well-written Q&A content can still earn Featured Snippets without structured data.

Sources: Google Search Central Documentation