Stop panic-deleting your FAQ schema — do this audit instead

Google killed FAQ rich results on May 7. Here's what to actually do about your schema.

If you added FAQ schema hoping to get those accordion-style question-and-answer boxes in Google Search — those are gone now. But a lot of the advice circulating this week is wrong in the other direction: "delete all your FAQ markup immediately" is not the right call either.

Here's what changed, why it matters less than the panic suggests, and the one audit you should run today.

What changed on May 7

As of May 7, 2026, Google no longer displays FAQ rich results anywhere in search.1 The feature is being phased out in three stages:

Stage	Date	What happens
Search results	May 7, 2026	FAQ snippets no longer appear in Google Search
Search Console & Rich Results Test	June 2026	FAQ reporting and testing tools are removed
Search Console API	August 2026	API endpoints for FAQ data are turned off

This isn't a surprise move. Google first cut FAQ visibility for most sites back in April 2023, then restricted the feature to government and health sites in August 2023.2 May 7 ended eligibility for those remaining sites too.

Google published no blog post explaining the removal. The only announcement was a notice added quietly to the official FAQ structured data documentation.3

The trap: removing schema you might still need

The instinct is to run grep -r "FAQPage" . and delete everything. Don't do that yet.

Google's own documentation confirms that FAQ structured data still exists as a valid Schema.org type and won't cause any problems if left in place.1 More importantly, other systems outside Google Search still read it:

AI retrieval systems — AI Overviews, ChatGPT search, Perplexity, and Claude's web search all benefit from clearly structured Q&A content when deciding what to cite
Voice search — devices parsing FAQ markup to generate spoken answers
Other search engines — Bing, DuckDuckGo, and others still support FAQ schema for their own features

The practitioner discussion this week on r/DigitalMarketing flagged the same point: the real shift isn't "FAQ schema is dead," it's "FAQ schema added purely to game Google rich results is now pointless — but FAQ schema that genuinely helps users still serves multiple channels."

The one audit to run today

Open your site in a text editor or your CMS template, and for each page that has FAQPage schema, ask one question: "Did I add this FAQ content because it helps a user who lands here, or because I wanted the accordion in Google?"

Keep it if the FAQ section exists because the questions are ones real users actually have — support pages, product pages where common objections are addressed, documentation pages. The schema still works for AI retrieval and voice, and removing it has zero upside.

Remove it if the FAQ was written purely to generate rich results — generic questions stuffed in to trigger the snippet, questions that don't match what the page is actually about, or Q&A blocks on pages where no one would naturally ask anything. You're wasting crawl budget and giving AI systems confusing signals.

For the removal, the cleanest approach is to strip the <script type="application/ld+json"> block containing "@type": "FAQPage" from the page template. No redirect needed, no 301, just delete the JSON-LD. If your FAQ content itself is useful (the text Q&A on the page), keep the text — just drop the structured markup.

One more note for teams pulling data through the Search Console API: you have until August 2026 before the FAQ rich result endpoints are removed.3 If any of your dashboards or scripts query that endpoint, update them before then — it's a clean deadline to schedule the work now rather than deal with broken monitoring in three months.

How to verify

After removing decorative FAQ schema from a page, run that URL through Google's Rich Results Test — you should see no FAQ-related results, which confirms the removal was picked up. Wait for a Googlebot recrawl (typically a few days for active pages), then check Search Console for any new structured data errors. There shouldn't be any, since you're removing rather than replacing.

If you keep FAQ schema on a page for AI/voice purposes, Schema.org's validator at validator.schema.org will still confirm the markup is well-formed — the Rich Results Test will drop support for FAQ testing in June 2026, so it's worth switching your validation workflow to the Schema.org tool now.1