FAQ schema being dead in Google Search is the most confidently wrong conclusion being drawn from one of the most significant structured data announcements of 2026 — and acting on that conclusion without understanding what actually changed could quietly damage your content strategy for years.
The announcement landed on May 7, 2026. Google added a deprecation notice to the top of its official FAQ structured data developer documentation. Within hours, the SEO industry split into two equally loud and equally incomplete camps. One side declared FAQ schema completely dead and started recommending its immediate removal from every website on the internet. The other side declared it more important than ever for AI search and started overselling it as the new secret weapon for AI visibility.
Both camps missed the point.
The rich result is dead. The schema is not. Those are two different things — and understanding the difference is what this article is actually about.
What Google actually said — and what it did not say
Before discussing implications, the exact wording of what Google announced matters. This is not a case where reading between the lines is required. Google’s own documentation stated:
“FAQ rich results are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich Results Test in June 2026. To allow time for adjusting your API calls, support for the FAQ rich result in the Search Console API will be removed in August 2026.”
Three things were deprecated — the visual rich result appearance in search, the Search Console reporting for FAQ structured data, and the Rich Results Test support for FAQ markup.
One thing was explicitly not deprecated — the FAQPage schema type itself.
Google’s documentation includes a line that most of the hot takes published after the announcement glossed over entirely: Google will continue to use FAQ structured data to better understand pages, even though the rich result feature is gone.
That single sentence changes the entire conversation. The feature that displayed expandable FAQ dropdowns in search results is gone. The underlying signal that FAQ structured data sends to Google’s understanding of a page is not.
The removal timeline — what is gone and when
For developers and SEO professionals managing sites with FAQ schema in place, the deprecation is being rolled out across three stages:
May 7, 2026 — Already live
FAQ rich results stopped appearing in Google Search entirely. This applies to all websites — including the government and health sites that had retained eligibility since the 2023 restriction. The visual SERP feature of expandable FAQ dropdowns is gone from Google Search results permanently.
June 2026 — Reporting and testing tools
Google will remove the FAQ search appearance filter from Search Console, the rich result status report for FAQ markup, and FAQ support inside the Rich Results Test tool. If you have been using the Rich Results Test at https://search.google.com/test/rich-results to validate FAQ schema, the FAQ-specific feedback will no longer be available from this point. The tool itself remains active for other schema types — Article, Product, Event, LocalBusiness, and others continue to be tested and reported normally.
August 2026 — Search Console API
Teams running automated dashboards or pulling structured data performance data through the Search Console API will need to update those calls before August. After this date, FAQ rich result data will return null from the API, which can silently break reporting pipelines that have not been updated.
This did not happen overnight — the history nobody is talking about
The May 2026 announcement is being discussed as though it came out of nowhere. It did not.
The full history matters for understanding why this change happened and what it signals about where Google is heading with structured data more broadly.
2016 to 2022 — FAQ rich results in their prime
FAQ schema worked consistently and visibly. Sites that implemented FAQPage markup correctly saw their search results expand with question and answer dropdowns directly in the SERP. Click-through rates improved. The search result took up more visual real estate. It was a genuine, measurable SEO advantage and the developer community responded — FAQ schema implementation became standard practice across millions of websites.
August 2023 — The first major restriction
Google announced that FAQ rich results would only be shown for what it called well-known, authoritative government and health websites. For the vast majority of commercial websites — businesses, eCommerce stores, agencies, blogs, service providers — FAQ rich results effectively disappeared at this point. Most sites already had their FAQ schema producing no visible SERP results by late 2023.
2023 to 2026 — The quiet period
FAQ schema remained in the code of millions of websites. Google continued crawling and processing it. The rich result simply did not appear for most of the web. Many developers and SEO professionals maintained the markup out of habit, or on the assumption that eligibility criteria might change, or because removing it felt riskier than leaving it.
May 7, 2026 — The final deprecation
The remaining eligibility — for government and health sites — was removed. The feature is closed completely. What changed on May 7 was not meaningfully different for most commercial websites from what changed in August 2023. The difference is that May 2026 made it official and final, including closing the reporting infrastructure around it.
Why the “remove all FAQ schema immediately” advice is wrong
The loudest reaction to the May 2026 announcement in certain corners of the SEO community was a call to action: find every instance of FAQPage markup on your site and remove it immediately. This advice is well-intentioned and technically harmless — but it is unnecessary and potentially counterproductive.
Google explicitly said you can leave it
Google’s own documentation states that unused structured data does not cause problems for Search. The FAQPage schema type is not banned. It is not penalised. It does not trigger manual actions or algorithmic penalties. Leaving it in place costs you nothing in terms of Google Search performance.
Other search engines are still using it
Google is not the only search engine that processes structured data. Bing, DuckDuckGo, and the various AI-powered retrieval crawlers that are indexing the web in 2026 — Perplexity, You.com, and others — continue to parse FAQPage markup and use it as a signal for content comprehension. A decision to remove FAQ schema based purely on Google’s rich result deprecation ignores every other system that processes your content.
The structured data validator still recognises it
You can verify this yourself at the official Schema.org validator at https://validator.schema.org/. Submit a page with FAQPage markup and it remains valid. The Schema.org vocabulary has not deprecated FAQPage — only Google’s specific rich result implementation of it has been retired. The schema type itself remains a legitimate, valid way to describe question and answer content on a web page.
Removal has a real cost
On a large site with FAQ schema implemented across hundreds of pages, removing it is not a trivial task. It requires development time, testing, and deployment. For what benefit? A slight reduction in JSON-LD payload size that will have zero measurable impact on page performance. The cost-benefit analysis of mass removal does not hold up to scrutiny.
The rational decision for most sites is straightforward: stop implementing new FAQ schema with the expectation of Google rich results, but do not invest time and resources removing schema that is already in place.
Why the “FAQ schema is now the secret to AI visibility” advice is also wrong
The opposite camp moved just as quickly and just as confidently in the other direction. The argument goes: Google deprecated FAQ rich results because it no longer needs the visual display feature — it has already ingested all that structured Q&A data to train its AI systems. Therefore, FAQ schema is now the key to appearing in AI Overviews, ChatGPT responses, Perplexity citations, and other AI-generated search surfaces.
This argument is directionally plausible and empirically unsupported.
What is true is that structured, machine-readable Q&A content — whether marked up as FAQPage schema or simply well-structured HTML — is inherently easier for AI retrieval systems to parse and cite. A question explicitly paired with its answer in a format a machine can read without ambiguity is more likely to be extracted accurately than the same information buried in flowing prose.
What is not supported by evidence is the claim that FAQPage markup specifically, as a JSON-LD schema type, produces measurable uplift in AI Overview appearances, ChatGPT citations, or Perplexity responses. Google itself has stated that there is no special schema needed for AI Overviews. Content quality, authority, relevance, and freshness remain the primary signals.
The honest position is this: FAQ schema may provide a marginal benefit for AI content comprehension. That benefit is real but modest, unquantified, and not a replacement for the foundational signals of content quality and domain authority.
What FAQ schema still legitimately does in 2026
Setting aside both the overcorrected pessimism and the overcorrected optimism, here is what FAQPage structured data genuinely still accomplishes in 2026:
Signals content structure to machines
The FAQPage schema explicitly communicates to any system parsing your page — search engine, AI crawler, browser, or accessibility tool — that this page contains a list of questions and answers, and here is the exact pairing. That is useful information regardless of whether it produces a visible rich result.
Supports non-Google search and AI platforms
Bing still processes FAQ schema. Perplexity crawlers process it. The AI retrieval infrastructure being built by multiple companies in 2026 is actively indexing the open web and processing structured data as a comprehension signal. Google removing its rich result does not remove these use cases.
Remains valid for Schema.org compliance
If your organisation has a structured data strategy that includes Schema.org compliance for semantic web purposes — beyond Google Search specifically — FAQPage markup remains a valid and legitimate part of that strategy.
Costs nothing to maintain
Existing, correctly implemented FAQ schema that is already in place requires no ongoing investment. It does not break anything. It does not slow down pages. It simply exists as machine-readable information about your content’s structure.
What developers and SEO professionals should actually do right now
Given everything above, here is the practical guidance for different scenarios:
If you have existing FAQ schema in place across your site: Do not remove it proactively. Stop tracking FAQ rich result performance in Search Console — that data is disappearing by June anyway. Export your historical FAQ performance data from Search Console before June if you want to retain it for records. Update any automated reporting that pulls FAQ rich result data from the Search Console API before August.
If you were planning to implement FAQ schema on new pages:
Implement it if the content genuinely contains Q&A pairs and the markup accurately reflects the visible page content. Do not implement it with the expectation of Google rich results — those are gone. Implement it as a content structure signal and for compatibility with non-Google systems. Validate your implementation at https://validator.schema.org/ to confirm it is correctly formed.
If you want to test whether existing FAQ schema is still technically valid:
Use the Rich Results Test at https://search.google.com/test/rich-results while it still supports FAQ markup — through June 2026. After June, use the Schema.org validator at https://validator.schema.org/ for ongoing validation. The Rich Results Test will continue working for all other supported schema types after FAQ support is retired.
If you manage FAQ schema at scale across many pages:
Prioritise updating your Search Console API integrations before August 2026. That is the only genuinely time-sensitive action item. Everything else can be evaluated and actioned without urgency.
If you are advising clients on structured data strategy:
Be honest about what changed and what did not. FAQ schema no longer produces Google rich results. It has not produced them for most commercial sites since August 2023. The foundational structured data types — Article, Product, LocalBusiness, Event, Organization, BreadcrumbList, Review — remain fully supported and actively rewarded with rich results. Shift the structured data conversation toward those types and away from FAQ specifically.
The broader lesson this deprecation teaches us
The FAQ rich result deprecation is one event in a pattern that has been visible across Google’s structured data strategy for several years. Course Info, Claim Review, Estimated Salary, HowTo on mobile, and now FAQ rich results — each was a visible rich result feature that became familiar enough to be widely implemented as an SEO tactic, and then was retired.
The pattern is not evidence that structured data is dying. It is evidence that Google is actively managing which structured data features provide genuine value to users versus which have become formulaic SEO implementation rather than meaningful content signals.
The structured data types that remain fully supported — Article, Product, Event, LocalBusiness, Review, Organization, Person, BreadcrumbList — are the ones that help users accomplish something concrete in search results. They surface prices, dates, locations, ratings, business hours. Information that genuinely improves the search experience.
FAQ rich results, at their peak, were useful. Over time they became a commodity — every page implemented them regardless of whether the Q&A content was genuinely useful to search users. Google removing the feature is consistent with its broader direction of rewarding genuine utility over structured data gaming.
The lesson is not to avoid structured data. The lesson is to implement structured data that accurately describes genuinely useful content — not to chase visible rich results as a click-through rate tactic.
Final thought
FAQ schema being dead in Google Search is accurate. FAQ schema being dead is not.
The distinction sounds pedantic until you consider what acting on the wrong version of that statement costs — either the wasted development time of removing schema from hundreds of pages for no measurable benefit, or the misplaced confidence of believing FAQ markup is now the key to AI search visibility when the evidence does not support that claim.
The honest, practical position is simpler than either extreme: a useful feature is gone, the underlying schema type remains valid, the time-sensitive actions are limited to updating Search Console API integrations before August, and the right response to this change is a calm, measured update to your structured data strategy — not a reactive overhaul in either direction.
The web changes. Google changes. The developers and SEO professionals who navigate those changes well are the ones who read the primary sources, understand the nuance, and resist the pull of confident but incomplete takes.
This is one of those moments that rewards exactly that approach.
References & Further Reading
For deeper reading on the ideas covered in this article, these resources are worth your time:
- Google Search Central — FAQ Structured Data Documentation
- Google Rich Results Test — Validate Your Schema
- Schema.org Official Validator
- Search Engine Journal — Google Drops FAQ Rich Results From Search
- Search Engine Land — Google to No Longer Support FAQ Rich Results
- NO-BS Marketplace — FAQ Schema May Matter More for AI Than for Search
- Alevdigital — FAQ Structured Data in 2026 — What Still Works
