SEO and Search Strategy

Google Killed FAQ Rich Results. Here Is What Nobody Is Telling You.

An honest analysis of the 7 May 2026 deprecation, the three-year pattern behind it, and why the most common advice you are reading right now is wrong.

Dragos, co-founder of Velena Lifestyle social media marketing agency, High Wycombe
By , Co-founder, Velena Lifestyle High Wycombe, Buckinghamshire 9 min read
Key Takeaways
  • Google deprecated FAQ rich results on 7 May 2026. The feature no longer appears in Google Search for any website. This is the completion of a process that started in August 2023, not a sudden reversal.
  • For most websites, FAQ rich results have been gone for nearly three years already. The May 2026 announcement removed them from the small number of government and health sites that still had them.
  • The most important line in Google's announcement is the one most coverage ignores: "Google will continue to use FAQ structured data to better understand pages." The display feature is dead. The schema is not.
  • Do not remove your FAQPage schema. FAQPage markup remains valid, is actively parsed by Bing, Perplexity, and AI retrieval crawlers, and contributes to how AI systems understand and cite your content.
  • The real strategic response is not about schema. It is about your title tags, meta descriptions and on-page content quality, because those are now your only visual levers in Google's organic results.
  • Export your FAQ rich result data from Google Search Console before June 2026. After that the report disappears. After August 2026 the API endpoint is removed.

On 7 May 2026, Google updated its Search Central documentation with a single deprecation notice: FAQ rich results are no longer appearing in Google Search. No blog post. No press release. No warning email. Just a quiet note at the top of a developer documentation page and a ripple across the SEO industry that has produced, in the two weeks since, a predictable flood of identical takes. Schema is dead. FAQ schema matters more than ever. Remove it immediately. Keep it forever. Most of it is wrong, some of it is right for the wrong reasons, and very little of it contains the single most consequential line in the entire announcement. This is our honest read.

What Actually Happened on 7 May 2026

The announcement has three parts and three deadlines. Here they are in plain language.

1
7 May 2026 — Already happened
FAQ rich results stopped appearing in Google Search for every website, including the government and health sites that had retained them since the 2023 restriction. The expandable question-and-answer dropdowns that used to appear beneath organic listings are gone. Permanently.
2
June 2026 — Act before this
Google removes the FAQ search appearance filter, the rich result report in Search Console, and support in the Rich Results Test. This is when the historical data disappears. Export your FAQ rich result data from Search Console now if you want to keep any record of previous performance.
3
August 2026 — For technical teams
Support for FAQ rich results in the Search Console API is removed. If you have automated dashboards, BigQuery exports, or API integrations pulling FAQ data, update those calls before August or you will get silent NULL returns in downstream reporting.

The announcement also includes a line that has been buried or skipped in most coverage: "Google will continue to use FAQ structured data to better understand pages, even though the rich result feature is gone." We will come back to this, because it is the most important sentence in the entire update.

This Was Not Sudden: The Three-Year Pattern

The first piece of honest analysis most articles are skipping is that for most businesses, this feature has been dead since August 2023. Understanding the full timeline is important because it changes how you should interpret the May 2026 announcement and what it signals about Google's direction with structured data more broadly.

August 2023: The first restriction

Google's John Mueller announced that FAQ rich results would only show for well-known, authoritative government and health websites. This removed eligibility from every commercial website, educational institution, news publisher, personal blog and agency site in one move. The stated reason, never formally confirmed but widely understood, was schema abuse. Businesses had been mass-adding FAQ sections not because visitors needed them but because they inflated SERP real estate. The questions were thin. The answers were written for the accordion, not the reader.

2023 to 2026: The restricted limbo

Between the 2023 restriction and the 2026 deprecation, FAQ rich results continued for a narrow category of qualifying sites. But even within that window, FAQ rich result impressions fell by roughly half in the months before the official deprecation, suggesting Google was already winding down the feature before announcing it.

May 2026: Full removal

The May 2026 announcement completes the withdrawal. It follows exactly the same pattern as HowTo rich results, which were restricted in 2023 and then fully deprecated. Google's approach to structured data abuse is now well established: widespread misuse, restriction to trusted verticals, then full removal. FAQ rich results are gone. They are not coming back.

The pattern is the signal: Google restricts rich results when the SEO industry abuses them at scale, then removes them entirely. If a structured data type becomes a ranking tactic rather than a content description tool, Google will eventually make it useless as a SERP lever. This is worth keeping in mind for every schema implementation decision you make going forward.

Dragos and Velena Nikolova, co-founders of Velena Lifestyle social media marketing agency, High Wycombe
Dragos and Velena Nikolova, co-founders of Velena Lifestyle, managing SEO and content strategy for UK businesses from High Wycombe, Buckinghamshire.

The Angle Nobody Is Covering: Google Replaced Its Own Feature

Here is the honest reason FAQ rich results were deprecated that Google did not publish a blog post to explain: AI Overviews made them redundant.

Think about what FAQ rich results actually did. They answered predictable questions directly in the search results, before the user clicked. They reduced the need to visit a page by surfacing answer previews in the SERP. They gave searchers information at the point of search rather than requiring a click to retrieve it.

Now consider what Google's AI Overviews do. They answer questions directly in the search results, before the user clicks. They reduce the need to visit a page by surfacing synthesised answers from multiple sources. They give searchers information at the point of search rather than requiring a click.

FAQ rich results were a static, publisher-controlled version of something Google's own AI can now do dynamically, more comprehensively, and without needing the publisher to tag the content correctly. Google did not just deprecate a feature because of schema abuse. Google deprecated a feature that its own product had superseded. AI Overviews now appear on between 25 and 50 per cent of searches depending on query type, according to studies ranging from Conductor to BrightEdge. FAQ rich results occupied the same real estate with a fraction of the capability.

This matters strategically because it explains the direction of travel for all SERP features that give publishers control over answer-presentation in the search results. The more Google's AI can synthesise answers from page content, the less value there is in giving publishers a direct visual channel into the SERP. The future of search visibility is not about owning more real estate in the results. It is about being the source Google's AI chooses to cite.

The Structured Data Paradox

This is the most important and most underreported dimension of the May 2026 deprecation, and the reason the most common advice you are reading is wrong.

At the exact moment Google stopped displaying FAQ rich results in its SERP, FAQ schema became more valuable for AI citation, not less. These are not contradictory. They describe two completely separate systems.

System 1: Google Search display. This is the blue links, the rich results, the AI Overviews, the SERP real estate. Google has just removed FAQPage as a display lever in this system. That loss is real and it does affect click-through rate on pages that previously had the expanded format.

System 2: AI retrieval and citation. This includes ChatGPT's browsing, Perplexity's indexing, Bing's Copilot, and the growing number of retrieval-augmented generation crawlers indexing the open web. These systems use structured data to understand what a page is about. FAQPage schema tells them: this content is structured as questions and answers, these are the specific questions, these are the definitive answers. Microsoft has confirmed that schema markup helps its LLMs understand content for Copilot. Google itself confirmed it will continue using FAQ structured data for page understanding.

The businesses that remove their FAQPage schema in response to this deprecation will lose a Google display feature they may not have been generating anyway, while simultaneously removing a signal that helps AI systems understand and cite their content. That is the wrong trade. Keep the schema.

The critical distinction: FAQPage structured data is a Schema.org type that describes content in machine-readable language. FAQ rich results were a Google Search display feature that used that markup to render visual SERP elements. Google deprecated the display feature. The markup language is still valid, still useful, and still being parsed by every major AI retrieval system. These are not the same thing.

The Wrong Reactions Flooding the Internet Right Now

Two weeks after the announcement, the SEO industry has split into predictable camps. Both are overcorrecting.

Wrong: Schema is dead
  • "Remove all FAQ schema immediately"
  • "Structured data investment was wasted"
  • "Schema markup has no future"
  • "Google doesn't care about FAQs anymore"
Also wrong: Schema matters more than ever
  • "This makes FAQ schema even more critical"
  • "AI engines are the new Google"
  • "Double down on every schema type"
  • "Schema is your AI visibility strategy"

The accurate position is quieter than either camp. FAQPage schema retains real value for AI retrieval and for Google's own page comprehension signals, as Google explicitly confirmed. But it is not a substitute for content quality, it is not a direct traffic lever, and its AI citation value is real but not yet measurable in a meaningful way for most sites. The instruction to keep FAQ schema in place is correct. The instruction to treat FAQ schema as a strategic priority in response to this change is not.

John Mueller's own response to the deprecation is worth noting: "If a site had the markup and wasn't one of those types, it was already being ignored. No need to change anything, but if you did it for search, you can remove the markup if you want." Mueller is describing a situation where most businesses are unaffected because they lost access in 2023. His phrasing also reveals something important: the purpose of the markup matters. If it was added to drive rich results, and rich results are gone, removing it is reasonable. If it was added to describe real question-and-answer content on the page, keep it.

What to Actually Do, in Order

Action checklist: FAQ rich results deprecation
  • Export your FAQ rich result data from Search Console before June 2026. After June the report is removed. Export it as a CSV now for historical reference. If you need to show clients or stakeholders what the feature was generating, this is your last chance.
  • Audit your FAQPage schema for quality. If your FAQ sections contain genuine, useful questions that visitors actually ask, keep the schema. If they were thin accordion sections added only to generate rich results, the sections can be removed or merged into proper on-page content.
  • Do not remove FAQPage schema from pages that have real FAQ content. The markup helps Google understand your pages and is actively parsed by AI retrieval systems. The display feature is gone. The comprehension signal is not.
  • Invest in your title tags and meta descriptions. These are now your primary visual levers in Google's organic results. A strong, specific meta description does more for CTR in 2026 than any rich result format that no longer displays.
  • If you use the Search Console API for automated reporting, update those calls before August 2026. The FAQ rich result endpoint is removed in August. Silent NULL returns in downstream dashboards are easy to miss and hard to diagnose weeks later.
  • If you have not yet audited your schema strategy against AI citation, this is the right moment to do it. Which of your schema types are genuinely describing your content versus chasing a display feature? That question now applies to every structured data implementation on your site.

What This Means for Our Own Site and Client Work

We are a UK social media marketing agency based in High Wycombe, as featured in Women's Health magazine. We manage social media, content and UGC content for UK businesses, and SEO-informed content strategy is part of how we think about every piece of content we produce.

Our own articles, including this one, carry FAQPage schema. We are keeping it. The reason is exactly what we have described above: Google will continue using FAQ structured data for page comprehension, and the AI retrieval systems that increasingly drive discovery and citation use it too. The display feature is gone. The structured data remains useful.

There is a certain irony in the fact that this article, about the deprecation of FAQ rich results, carries FAQPage schema at the bottom of the page. Google will not show it as a rich result in the SERP. But it will use it to understand what this article is about, and so will every AI system that indexes it. That is the correct use of the format in 2026.

For the businesses we work with, the practical change is straightforward. If you want a direct conversation about how this affects your specific site, get in touch here. The FAQ sections you added to product pages and service pages for rich result visibility are no longer producing that visibility. If those sections answered genuine customer questions, they remain valuable for on-page conversion, for AI citation, and for the customers who read them. If they were thin and tactical, this is a clean opportunity to remove them and simplify the page.

"Fantastic service. Been a client for 3 years and have seen fantastic results: increased viewers, followers and viral videos."

Darrell  |  CEO, No Escape London
Social Media Management Seed Plan by Velena Lifestyle
Seed Plan
From £497 / month
Core platform management, consistent posting and community engagement for UK businesses building their social presence.
Get Started
Social Media Management Grow Plan by Velena Lifestyle
Grow Plan
From £897 / month
Full management across two platforms with content creation, strategy and monthly reporting.
Get Started
Social Media Management Scale Plan by Velena Lifestyle
Scale Plan
From £1,497 / month
Multi-platform management with UGC content production and advanced analytics for scaling brands.
Get Started
Social Media Management Elite Plan by Velena Lifestyle
Elite Plan
From £2,497 / month
Full-service social media management across all platforms with dedicated account oversight and content production.
Get Started
Dragos, co-founder Velena Lifestyle
Dragos
Co-founder, Velena Lifestyle | 25K LinkedIn
Dragos is the co-founder and business strategist at Velena Lifestyle, a social media marketing agency based in High Wycombe, Buckinghamshire, as featured in Women's Health magazine. He works with UK businesses on social media strategy, UGC content and content strategy alongside Creative Director Velena Nikolova.

Further Reading

Frequently Asked Questions

Should I remove FAQPage schema from my website after Google's May 2026 deprecation?

No, not if the schema accurately describes real question-and-answer content on your pages. Google explicitly confirmed it will continue using FAQ structured data to understand pages, even though the rich result display feature is gone. The schema is also parsed by Bing, Perplexity and AI retrieval crawlers that power tools like ChatGPT and Copilot. The correct action is to remove FAQPage schema only from pages where the FAQ sections were thin and added purely to generate rich results, not from pages with genuinely useful FAQ content.

Why did Google remove FAQ rich results in May 2026?

Google did not publish a formal explanation, but the context is clear. The feature was restricted in August 2023 because of widespread schema abuse: businesses mass-adding thin FAQ sections to inflate SERP real estate rather than answer real customer questions. The May 2026 removal completes that three-year phase-out. There is also a product logic argument: Google's AI Overviews now answer questions directly in the SERP more dynamically than static FAQ rich results could. The display feature became redundant from Google's own product perspective.

What happens to FAQ data in Google Search Console?

The FAQ rich result report in Search Console is being removed in June 2026. The Search Console API support for FAQ rich results is removed in August 2026. Export any historical FAQ rich result data before June if you need it for reporting or to show clients what the feature was generating. After June the report is gone permanently.

Does this affect my organic rankings?

No. FAQ rich results were a display feature, not a ranking signal. Your organic positions are unaffected. What may change is your click-through rate if your listings previously had the expanded FAQ format, since that visual prominence is now gone. Pages that were generating traffic partly because the FAQ expansion made them more prominent in the SERP may see reduced CTR even if rankings remain identical. This is why title and meta description quality matters more now, not less.

Is FAQ schema still useful for AI visibility?

Yes, with an important caveat. FAQPage structured data is actively parsed by AI retrieval systems including those used by Perplexity, Bing Copilot and other AI search tools. It helps those systems understand the specific questions your content addresses and the answers you provide. Microsoft has confirmed that schema markup helps its LLMs understand content. Google also confirmed it will continue using FAQ data for page comprehension. However, the connection between having FAQPage schema and being cited in AI responses is not directly measurable for most sites yet. It is a real signal but not a guaranteed outcome.