Search all pages  ·  Press Esc to close  ·  ↑↓ to navigate
Content Strategy Local SEO GMB Prompts Technical SEO E-E-A-T Guest Post GA4 Analytics
Structured Data · AlgoBlueprints · June 2026

Google Killed FAQ Rich Results on May 7, 2026 — Here Is Exactly What Changed, What Didn't, and What to Do Right Now

Table of Contents

Google removed FAQ rich results on May 7, 2026 with no blog post and no advance warning — just a small deprecation banner on the FAQ structured data developer documentation page. Within 24 hours, the SEO industry split into two panicked camps: one declaring schema dead, the other insisting FAQ markup had become more important than ever for AI search. Both camps got it wrong, and the noise they generated has buried the simple, actionable truth that every site owner needs right now.

I've been managing structured data implementations across healthcare, legal services, hospitality, and e-commerce clients since FAQ rich results first appeared in 2019. I watched teams spend hours engineering FAQ schemas onto thousands of pages — product pages, category pages, about pages — purely for the SERP dropdown real estate. When Google removed that real estate, those same teams panicked. My response was different: a calm audit, a measured content pivot, and a clear redirect of structured data effort toward what actually earns AI citations in 2026. This article walks you through exactly what changed, what it didn't change, and the precise six-step response that protects your AI visibility while retiring the tactics that no longer serve you.


Exactly What Google Removed — and What It Kept

Google removed one thing: the expandable FAQ dropdown that appeared beneath organic listings in search results. That's the only thing that changed on May 7, 2026. The FAQPage schema type remains valid. Google continues parsing the markup. Unused structured data does not cause problems for Search — Google confirmed this explicitly in its own documentation. The two things teams conflate — the SERP display feature and the markup type — are separate, and the deprecation ended only one of them.

FAQ Rich Results — The Complete Deprecation Timeline
August 2023 — First Restriction
Google restricts FAQ rich results to government and health sites only
After years of watching marketers stuff irrelevant FAQ schemas onto every product page and category page imaginable, Google dramatically narrowed eligibility. Most commercial sites lost the feature overnight, with only well-known authoritative government and health domains retaining it.
May 7, 2026 — Full Deprecation
FAQ rich results stop appearing in Google Search for every site type
Google adds a deprecation banner to its FAQ structured data developer documentation. No blog post. No advance notice. The feature stops firing immediately for every site type including the government and health domains that had retained eligibility since 2023. The FAQPage schema type remains valid with no penalties.
June 2026 — Reporting Removal
Search Console FAQ report, FAQ filter, and Rich Results Test support removed
The supporting measurement infrastructure disappears. Teams using the Rich Results Test as a QA gate for FAQ implementations need a new workflow. Any dashboard or reporting pipeline tracking FAQ appearance data needs updating before the next phase.
August 2026 — API Support Ends
Search Console API support for FAQ rich result data removed
Automated dashboards, BigQuery exports, and API pipelines that pull FAQ rich-result data will silently return empty values unless teams update them before this date. Update your pipelines now — the deadline is approaching.
May 7
2026 — Date FAQ rich results stopped appearing in Google Search for all site types
Aug 2023
When most commercial sites already lost the feature — May 2026 simply removed the last remaining eligibility
Aug 2026
Deadline to update Search Console API pipelines before FAQ data support ends
No Penalty
Google confirmed unused structured data does not cause search problems — leaving FAQ schema in place harms nothing

Why Google Removed It — The Three Real Drivers

Google published no official rationale for the May 2026 removal. But the pattern of structured data deprecations over the past three years tells a clear story when you read it honestly. Teams abused FAQ schema at scale — product pages carried pseudo-questions like "Is this product good?" answered by "Yes, our product is very good," purely to win dropdown real estate. Quality control at that scale became impossible. The incentives were backwards, and users paid the cost by seeing SERP space consumed by irrelevant generated content masquerading as helpful answers.

The second driver is SERP simplification. Since 2023, Google has systematically removed structured data features that gave third-party content extra display real estate — HowTo rich results, then several other types in 2025, now FAQ. Each removal reclaims SERP space for Google's own AI Overviews. The direction is consistent and deliberate: Google is redesigning the results page around its own answer experiences, and FAQ dropdowns consumed the exact pixel territory Google's AI features now occupy.

From My Practice — Akif Qureshi

"I audited three client sites the week after the May 7 deprecation. Every single one had FAQ schemas on pages where the questions were clearly engineered for SERP real estate, not written for actual user intent. A healthcare client had FAQ blocks on their appointment booking page asking 'What is physiotherapy?' — the page had nothing to do with explaining physiotherapy, it was a booking form. A legal services client had FAQ schemas on their contact page. None of these implementations were surviving the August 2023 restriction anyway. The May 2026 deprecation forced the audit that should have happened eighteen months earlier. We removed the decorative schemas, kept the genuinely Q&A-structured content on the right pages, and shifted measurement to AI citation tracking instead of rich result impressions."

Does FAQ Schema Still Help AI Overviews, ChatGPT, or Perplexity?

This is the question that generated the most noise after May 7 — and the honest answer requires separating what different AI platforms actually do with your markup.

❌ What FAQ Schema Does NOT Do for AI
  • 🔴 Google has not confirmed FAQPage markup as a signal for AI Overviews or AI Mode
  • 🔴 No confirmed mechanism connects FAQPage markup to AI Overview citation selection
  • 🔴 Pages get cited in AI Overviews constantly without any FAQ schema present
  • 🔴 The widely-shared "3.2x more likely to appear in AI Overviews" stat traces to a source that no longer exists with no primary study behind it
  • 🔴 ChatGPT tokenizes HTML text including schema blocks but does not parse it as structured data — it reads your visible page text
✅ What FAQ Schema Still Does
  • 🟢 Google continues parsing the markup to understand page structure and content relationships
  • 🟢 The markup makes your intent unambiguous — it tells crawlers exactly which text is a question and which is an answer
  • 🟢 Perplexity shows stronger correlation with structured data than ChatGPT — schema helps on that platform specifically
  • 🟢 Well-written Q&A content — regardless of schema — is what AI systems extract and cite
  • 🟢 The schema may contribute to training signals for future AI generations, even where it provides no confirmed live citation benefit today

Your Six-Step Response — What to Actually Do Now

1

Export Your Historical FAQ Rich Result Data from Search Console Before June

Pull your FAQ appearance data — impressions, clicks, CTR, position — from Search Console before the reporting removal completes in June 2026. Export it as a CSV baseline and store it outside Search Console. This data becomes permanently unavailable after the reporting is removed, and you need it for any before-and-after CTR analysis your clients or leadership might request later.

2

Update Your API Pipelines Before August 2026

If your team or agency runs automated reporting through the Search Console API and pulls FAQ rich result data, update those API calls now — not in July, now. The August 2026 API support removal will cause those calls to silently return empty values, breaking dashboards without warning. Identify every pipeline, dashboard, or BigQuery export that touches FAQ data and document the update required before the deadline lands.

3

Audit Every Page Carrying FAQ Schema

Use Screaming Frog or your preferred crawler to generate a list of every URL on your site that contains FAQPage markup. For each URL, ask one question: does this page genuinely contain questions and answers that users actually ask, visible in the HTML? If yes, keep the schema. If the FAQ block was added to chase SERP real estate on a page that isn't truly Q&A in nature — a product page, a category page, a homepage — remove the schema. The cleanup costs developer time but earns nothing by keeping decorative markup that never fire anymore.

4

Switch from Rich Results Test to Schema.org Validator for FAQ QA

Teams that used the Rich Results Test as a QA gate for FAQ schema implementations need a replacement workflow — the Rich Results Test stops supporting FAQ in June 2026. Use the Schema.org validator (validator.schema.org) to confirm FAQPage markup is syntactically valid. It doesn't check rich result eligibility — because there's no rich result left to check — but it confirms your markup correctly follows the schema.org specification, which is the remaining validation that matters.

5

Measure CTR Impact Honestly — Compare 28 Days Before vs After May 7

In Search Console, run a date comparison of pages that previously showed FAQ rich results: 28 days before May 7 versus the 28 days after. For most commercial sites, the impact is smaller than feared — because most commercial sites already lost FAQ rich results in August 2023. The sites most likely to see a meaningful CTR dip are government and health domains that retained eligibility until the May 2026 final removal. If your site is in neither category, the May 2026 change likely had minimal new impact on traffic.

6

Redirect Your Q&A Investment Toward AI Citation Content

The most important redirect in your strategy isn't the schema cleanup — it's where you send the content effort that previously targeted FAQ rich result real estate. Write genuinely useful Q&A content, structure it with clear headings and direct answers, and optimise it for AI extraction rather than SERP dropdowns. The content that earns AI Overview citations is the same content that earns ChatGPT and Perplexity citations: direct, question-led, substantive answers written for human readers — not FAQ boxes engineered for pixel width.

The Pattern That Predicts What's Next

FAQ joins HowTo (2023) and seven other structured data types (2025) in Google's systematic removal of features that gave third-party content extra SERP real estate. The direction is clear: Google retires third-party visual treatments and replaces them with AI Overview space. Stop investing in individual SERP feature chasing and start optimising for the underlying signals that earn citations across all surfaces: entity authority, genuinely useful content, and strong topical coverage. Those signals survive every feature deprecation because they're what all AI systems ultimately evaluate.


Frequently Asked Questions

Should I remove all FAQ schema from my site immediately?
No. Google explicitly confirmed that unused structured data does not cause Search problems, and FAQPage remains a valid schema.org type. A blanket removal project wastes developer time for no measurable benefit. The right approach is selective: remove FAQ schema from pages where it was added decoratively to chase rich result real estate, and keep it on pages where the content is genuinely Q&A-structured and visible. Focus the cleanup on schema that was never earning the feature anyway.
Does this change affect HowTo or other schema types?
Not directly — HowTo rich results on desktop were already deprecated in 2023, making that change earlier in the same pattern. The May 2026 FAQ removal follows the same trajectory: a SERP feature that gave third-party content extra visual real estate is retired, while the underlying schema type remains valid. Google continues pruning display features while keeping the underlying markup types available. Plan for additional structured data display features to follow this pattern through 2026 and beyond.
Does FAQ schema help me get cited in AI Overviews or ChatGPT?
No confirmed mechanism connects FAQPage markup to AI Overview citation selection, and Google's own AI features guidance states no special schema is required for AI Overviews or AI Mode. Pages get cited in AI Overviews constantly with no FAQ schema. What earns AI citations is clear, direct, question-led content written with genuine answers — the content matters, not the schema wrapper around it. Focus on writing excellent Q&A content, and the AI citation probability rises regardless of whether FAQPage markup accompanies it.

The Bottom Line

Google removed the FAQ rich result SERP feature on May 7, 2026 — not the FAQPage schema type. The display is gone. The underlying markup is still valid, still parsed, and still carries no penalty. Export your historical FAQ data before June reporting removal. Update your API pipelines before August. Audit every page carrying FAQ schema and remove the decorative instances that were never earning the feature anyway. Then redirect the content investment that previously targeted FAQ dropdowns toward genuine Q&A content structured for AI extraction. The schema was never doing the work. The content always was — and that truth becomes more valuable every time a SERP feature disappears.

Akif Qureshi
Akif Qureshi
Senior SEO Specialist & Marketing Analyst | Content Strategist
5+ yrs experience Google Certified 6 guides

Driven by advanced SEO expertise, deep marketing analytics, high-impact content strategy

With 5+ years of hands-on experience, I specialize in holistic search strategies that don’t just rank—they drive real, measurable business growth. I’ve worked across industries including healthcare, hospitality, legal, e-commerce, and professional services, helping brands dominate their target markets. My approach bridges the gap between raw data and creative execution. Every strategy I build is rooted in rigorous market analysis, structured SEO frameworks, and tailored content ecosystems—no templates, no shortcuts. Whether you’re a single-location brand or scaling across multiple cities, I create data-driven marketing systems designed to compound results and grow with you.

No sponsored content No affiliate links Reader supported

Need Help Optimizing Your Structured Data for 2026?

Get a complete structured data audit, FAQPage schema review, and AI search optimization strategy tailored to Google's latest Search and AI Overview updates.

Book a Free Schema Audit →

© 2026 Algoblueprints. All rights reserved.