In May 2026, Google pulled FAQ rich results from search altogether. No announcement, no explanatory blog post — just a documentation status change, and thousands of sites losing a Q&A accordion overnight that many had spent months optimizing for. Site owners are now asking the same question: keep the FAQPage markup, remove it, or rework it?
This guide covers the exact deprecation timeline, what to actually do with your existing schema, and an angle almost nobody else covers: what this removal changes — and, more importantly, doesn't change — for your visibility in AI engines.
The exact deprecation timeline
The removal rolled out in three waves, all documented in Google Search Central's changelog:
| Date | What disappears |
|---|---|
| May 7, 2026 | FAQ rich results (the Q&A accordion under the snippet) stop appearing entirely in search results, including for government and health sites, the last category still eligible |
| June 2026 | The "FAQ" filter in Search Console's search appearance report is removed, along with FAQ support in the Rich Results Test |
| August 2026 | Support for this rich result type is dropped from the Search Console API; automated dashboards or exports relying on it will silently return null values if not updated beforehand |
No official reason was given. The timing overlaps with the rise of AI Overviews and AI Mode, but Google has never drawn an explicit line between the two.
Not a surprise: a three-year phase-out
What's landing in 2026 is the endpoint of a much longer process, and that's where a lot of sites get the diagnosis wrong:
- September 2023:
HowToschema already lost its rich result display on desktop. If you were still building a content strategy around that format, it hasn't produced any visible SERP effect for nearly three years. - August 2023: Google first restricted FAQ rich result eligibility to "well-known, authoritative government and health websites." For the vast majority of sites, the FAQ accordion had already vanished from results at that point — most site owners simply never noticed, because nothing in Search Console flagged it clearly.
- May 2026: the feature disappears entirely, including for the remaining eligible sites.
The real story of 2026 isn't "Google removes the FAQ rich result." It's the official, documented end of a feature that had already been invisible for most sites since 2023.
Should you remove your FAQPage markup? A decision matrix
FAQPage remains a perfectly valid Schema.org type. Unused structured data causes no error and no penalty in Search Console. So this isn't really a technical question — it's an editorial one: does your FAQ content still deserve to exist as-is?
| Situation | Recommended action |
|---|---|
| FAQ visible on the page, genuinely useful content (support, recurring product questions) | Leave the markup as-is. Nothing to change, it still accurately describes your page |
| FAQ added purely to chase the old rich result, generic questions with little real information | Remove the schema, or rewrite the section as real editorial content instead of decoration |
| The same Q&A block copied across multiple pages on the site | Keep a single canonical version and remove the duplicates — a duplicate-content signal Google treats independently of the rich result question |
FAQPage markup describing questions that no longer appear visually on the page | Fix this first: it's a structured-data compliance issue, unrelated to the deprecation itself |
The first three cases: nothing urgent. The last one carries the same urgency it always did, before or after May 2026 — structured markup that doesn't match visible content is a problem with or without a rich result attached to it.
What this changes (and doesn't change) for your AI visibility
This is the most misunderstood part of the whole deprecation. FAQPage schema was never, strictly speaking, a citation mechanism for AI engines. It was always a classic SERP formatting signal — a visual accordion, nothing more. What Google AI Overviews, AI Mode, ChatGPT, and Perplexity actually consume first is the visible Q&A text sitting directly in the HTML, not the JSON-LD block attached to it.
In practice, that means the disappearance of the FAQ rich result changes almost nothing about your citability in AI engines, because the JSON-LD was never the thing doing that work in the first place. If you've read elsewhere — including in some of our own older articles — that FAQPage markup "increases your chances of being cited in an AI Overview," treat that claim with caution: the causal link was never demonstrated that directly, and the CTR-gain argument tied to the rich result simply no longer applies, because the feature itself is gone.
What actually matters for AI citability is still what our schema markup and AI citations guide covers: a clear page structure, a direct answer in the first paragraph, genuinely visible and human-readable Q&A content — markup supports disambiguation, it never substitutes for the content itself.
The schema types that aren't going anywhere — and where to put your effort now
FAQ rich result removal touches only one type out of roughly a dozen you can use. These keep their full visual weight in 2026 SERPs:
Product/Offer: price, availability, merchant listing eligibility — still fully active, and increasingly read by AI shopping agents.Review/AggregateRating: star ratings under a result remain one of the rich results with the best measured CTR impact.BreadcrumbList: the breadcrumb trail shown in a result's URL was never touched by this deprecation.Organization/Article: identity and authority signals stay the foundation Google and AI engines use to build trust in a source.- Google Business Profile Q&A: a separate surface from schema.org markup entirely, untouched by this removal, and frequently underused by local businesses.
The general rule: don't reinvest the time freed up by dropping FAQPage into some other schema type "just in case." Put it into the types that still carry visual weight, and above all into the visible content AI engines actually read.
Post-deprecation schema audit checklist
- Export your historical FAQ rich result performance data from Search Console before it becomes inaccessible (June 2026 deadline).
- Find pages where
FAQPagedescribes questions that no longer appear visually — fix or remove these first. - Leave markup in place on pages where the FAQ is genuinely useful content for users (support, product questions).
- Stop adding
FAQPageas an SEO "quick win" on generic content — it produces zero visible SERP gain now. - Verify your
Product/Offer,Review,BreadcrumbList, andOrganizationmarkup is still valid — these carry the remaining visual weight in 2026. - Update any dashboards or automated exports relying on the Search Console API before the August 2026 deadline, to avoid silently broken reports.
- If you manage a Google Business Profile, keep its Q&A section active: a local surface still fully live, entirely separate from this removal.
- Redirect your remaining schema effort toward whatever your technical SEO audit flags as a priority for your specific site, rather than a generic checklist.
Key takeaways
The FAQ rich result disappeared in three waves between May and August 2026, continuing a process that started back in 2023 with the FAQ restriction to government and health sites, and the earlier removal of the HowTo rich result. FAQPage remains a valid Schema.org type: no obligation to remove it, unless it describes content that no longer exists on the page. AI engine citability was never really built on this specific JSON-LD block — it depends on visible, structured, clear content. Redirect your attention to the schema types that still carry visual weight (Product, Review, BreadcrumbList) and to the actual quality of your Q&A content rather than its technical wrapper.
FAQ
Should I remove all my FAQPage markup now that the rich result is gone?
No, there's no obligation to. Unused schema causes no error or penalty in Search Console. Keep it on pages where the FAQ is genuinely useful content, and only remove it where it describes questions that no longer appear on the page or existed solely to chase the old rich result.
Does FAQPage schema still help with being cited by ChatGPT or AI Overviews?
Only indirectly, and it never did so directly. What AI engines consume first is the visible Q&A text in the HTML, not the accompanying JSON-LD block. Markup helps with disambiguation; it never replaces clearly written content.
Does this removal also apply to HowTo schema?
The HowTo rich result disappeared much earlier, in September 2023. The type remains valid on the Schema.org side, exactly like FAQPage today, but it hasn't produced any visible rich display in search results since that date.
How do I check whether my pages have FAQPage markup out of sync with their content?
Manually compare, or use a structured-data validation tool to compare, the FAQPage JSON-LD block against the questions and answers actually visible in the page's HTML. Any mismatch — a removed question, an answer edited without updating the schema — should be fixed first, independently of the rich result deprecation.
A rich result deprecation is just one of many signals worth tracking on your site. Run the free SeAudit audit to get your /100 score and a list of priorities ranked by impact, or go straight to the full report for a detailed review of your structured data.