Google officially deprecates FAQ rich results as of May 2026

What happened

Google confirmed that FAQ rich results are no longer appearing in Search as of May 7, 2026. The announcement, shared on r/TechSEO and sourced from Google’s developer documentation, lays out a three-phase deprecation timeline:

• May 7, 2026: FAQ rich results stop appearing in Google Search.
• June 2026: Google removes the FAQ search appearance filter, the rich result report in Search Console, and FAQ support in the Rich Results Test tool.
• August 2026: Search Console API support for FAQ rich result data is removed.

The Google Search docs changelog also documents the update. Search Engine Land covered the news as well.

Why it matters

FAQ rich results have been declining in visibility since Google restricted them to government and health authority sites in August 2023. The formal deprecation removes one more SERP feature that SEOs once used to capture additional real estate in search results.

The practical impact varies by team size and tooling. Enterprise content teams managing thousands of FAQ pages face a decision about when and how to remove FAQ schema from templates. A passive template deploy means Googlebot picks up the changes as it naturally re-crawls pages on its own schedule, not as an immediate site-wide surge. Leaving the markup in place is harmless for now, but creates monitoring noise.

SaaS platforms and agencies with automated reporting pipelines face a harder deadline. Any Search Console API integration that queries FAQ rich result data will break in August 2026. Teams running automated SEO health dashboards that track FAQ appearance metrics need to update those queries before the cutoff.

For smaller sites, the impact is minimal. FAQ schema wasn’t generating rich results for the vast majority of domains already. The markup can stay or go without meaningful consequence.

The FAQPage type at schema.org remains a valid schema definition. Google choosing not to render it does not make the markup invalid. The distinction matters if you use FAQ schema for purposes beyond Google, such as feeding other search engines or internal tooling.

The deprecation raises an open question for AI search surfaces. Google is removing FAQ rich results from classical search, but FAQ structured data could still play a role in AI contexts. Retrieval pipelines used by AI search products may use structured Q&A pairs during document selection, even though the LLM itself does not parse schema tags. Whether AI Overviews, ChatGPT search, or Perplexity use FAQPage schema in their retrieval layers is undocumented. Practitioners deciding whether to remove FAQ markup should factor this uncertainty into the timeline.

What to do

Don’t rush to remove FAQ schema markup. The markup is inert now. Google isn’t penalizing it, and removing it from thousands of pages creates unnecessary work. If you do want to clean it up, batch the removal over time rather than deploying a site-wide template change that forces re-crawling of every affected URL at once. If you run Shopify, also check for third-party FAQ schema injections you may not have added yourself.

Audit your Search Console API integrations now. If you pull FAQ rich result data from the Search Console API, you have until August 2026 before those calls stop returning data. Check whether your monitoring dashboards, automated reports, or alerting systems reference the FAQ search appearance. Update or remove those queries before August to avoid silent failures.

Expect false positives in Search Console during the transition. Between now and June, FAQ data may still appear in Search Console reports even though the rich results are gone from SERPs. Don’t interpret lingering report data as evidence that FAQ results are still live.

Check JavaScript-rendered FAQ content separately. If your FAQ schema is injected via client-side JavaScript, confirming removal after deployment is harder. Use URL Inspection’s “Test Live URL” option, which fetches and renders the page in real time. The default view shows cached crawl state, not current output. For large-scale audits, run a renderer-enabled crawler like Screaming Frog.

Factor AI search surfaces into your keep-or-remove decision. FAQ schema costs nothing to maintain and may have undocumented value for AI retrieval pipelines. If you have no urgent reason to remove it, leaving it in place preserves optionality.

Leave FAQ content in place. The schema is deprecated, not the content. FAQ-style content still has value for users and can surface in AI Overviews or standard organic results. Only the structured data rendering is affected.

Watch out for

Template-level removal on large sites. Sites that baked FAQ schema into product or category templates should avoid force-requesting re-crawls for all affected URLs at once. Let the normal crawl schedule pick up the changes. For most sites, passive schema removal carries no meaningful crawl budget risk.

Multi-language sites with separate crawl schedules. Removing FAQ schema from one language version doesn’t guarantee other hreflang variants get re-crawled on the same timeline. Verify each language variant individually.