Google Officially Deprecates FAQ Rich Results May 7, 2026: Search Console and Rich Results Test Support to Follow

What Google Announced

Google confirmed that FAQ rich results stopped appearing in Search on May 7, 2026, according to the updated Mark Up FAQs with Structured Data documentation on Google Search Central. Search Engine Land independently confirmed the timeline: Search Console reporting and the Rich Results Test will drop FAQ support in June 2026, and the Search Console API will retire FAQ performance data in August 2026.

For finance, fintech, and ecommerce brands that built out long FAQ blocks specifically to capture expanded SERP real estate, this closes a chapter that began when Google first narrowed FAQ eligibility to government and health sites in 2023. Now the feature is gone for everyone. If you are reassessing how organic real estate fits into your wider funnel, our take on SEO services for regulated industries is a good starting point.

The Migration and Export Window

Three deprecation milestones brands need to plan around.

Google Search Central Documentation; Search Engine Land, May 2026.

There is a narrow window to preserve historical performance data. Google's bulk data export supports filtering on is_tpf_faq = true, which lets you archive FAQ-rich impressions, clicks, CTR, and position into BigQuery before the June 2026 Search Console cutoff. Do this now, not in May. After that date, you lose the ability to baseline what FAQ markup was actually contributing to your top pages.

This matters for attribution arguments. If FAQ rich results were quietly driving a meaningful share of clicks on a money page, you want that on record before you redesign the template. The same kind of evidence-driven approach we apply to high-intent keyword research applies here: capture the data, then make the call.

FAQPage vs QAPage: Don't Confuse Them

FAQPage markup, used for site-authored questions and single answers, is the deprecated type. QAPage is different. QAPage is for pages with one user question and multiple user-submitted answers, such as community forums, and is not part of this announcement. If you run a community or marketplace surface, your QAPage implementation stays intact.

Brands selling on Amazon while building owned channels, a pattern we cover in how to diversify sales beyond Amazon, often have a mix of FAQ and Q&A surfaces. Audit which schema each template emits before you start ripping anything out.

What to Do With FAQ Content Now

The content is not the problem. The SERP feature is what is going away. Well-written FAQs still earn passages cited inside AI Overviews, ChatGPT, and Perplexity, and they still convert traffic when placed on the right pages. ZipTie.dev's review of FAQ schema for AI answers found mixed direct lift from the markup itself in AI citation tests, which means the win is in the answer copy, not the JSON-LD wrapper.

Practical reallocation for the next 90 days:

• Keep FAQ sections that answer real buyer questions, especially on product, pricing, and comparison pages.
• Tighten answers to a single quotable paragraph; that is the format AI engines extract.
• Remove FAQ blocks that exist only to game SERP space; they add bloat without payoff.
• Reinvest schema effort into Product, Article, HowTo, and Organization markup where rich results still render.

If you sell financial products, our SEO playbook for regulated industries covers how to structure trust-signal content without leaning on deprecated SERP features. Ecommerce teams should revisit the Shopify SEO checklist to make sure Product schema and internal linking are doing the heavy lifting that FAQ rich results used to share.

Our Read

This was telegraphed. Google has been pulling back on snippet features that incentivize keyword-stuffed FAQ blocks for years, and AI Overviews have absorbed the surface area. The brands that built genuinely useful answer content keep their traffic. The brands that bolted on twenty-question FAQ accordions to win pixels lose nothing of value.

If you want help auditing schema deployment and reallocating budget toward channels that still compound, book a strategy call with our team.