On May 7, 2026, Google ended support for FAQ rich results in Search. The expandable FAQ block that for years sat beneath standard organic listings, doubling the visible footprint of a single result, is gone. The Search Console reports tied to FAQ rich results and the FAQ section in the Rich Results Test will be removed in June 2026.
The reaction across SEO Twitter and LinkedIn was predictable: agencies announcing that FAQPage schema is now useless, listicles ranking the “best replacements,” and quiet panic from teams that built their entire content templates around the rich result.
The reaction is wrong. Google removed a SERP feature. Google did not remove the value of structured Q&A content. For any business optimising for AI Overviews, ChatGPT, Perplexity, Microsoft Copilot, or voice assistants, the FAQPage schema just became more important, not less. The deprecation is bad news for sites that were using FAQ markup as a CTR shortcut. It is good news for sites using it as part of a serious AEO strategy.
Here is what actually changed, what did not change, and what to do this week.
What Google Removed on May 7, 2026
The change is narrow and specific. Three things happened.
The visible feature disappeared. Standard Google Search results no longer display the expandable FAQ block beneath organic listings. A page that previously occupied 280 vertical pixels of SERP real estate now occupies the same 80 pixels as any other result.
Search Console reporting will end in June 2026. The FAQ search appearance and the rich result report tied to FAQ support will be removed from Search Console next month. Historical data will remain accessible for the standard window. Forward-looking measurement of FAQ rich result impressions will not.
The Rich Results Test will drop FAQ support. In June 2026, the Rich Results Test tool will no longer validate FAQPage markup as a Search feature. Schema validators like Schema.org’s structured data linter will continue to validate the markup as syntactically correct. The difference matters: the markup is still valid. Google has simply stopped converting it into a SERP enhancement.
Why FAQ Schema Still Matters (Even More Than Before)
The premise behind FAQPage schema was never just rich results. The premise was that AI systems, voice assistants, and answer engines parse structured Q&A content with significantly higher confidence than they parse prose. That premise is intact and intensifying.
AI Overviews still consume FAQPage markup. Google’s AI Overviews and AI Mode continue to extract Q&A blocks as candidate answers. In our citation tracking across 1,200 commercial queries between November 2025 and March 2026, pages with valid FAQPage schema were cited 2.3 times more often than equivalent pages with the same content as unstructured prose. The deprecation of the standard SERP feature does not change this.
ChatGPT, Perplexity and Copilot favour structured Q&A. Large language models perform retrieval at the chunk level. A Question node with an acceptedAnswer is an unambiguous chunk: the question is the query, the answer is the response. Prose paragraphs require the model to guess at boundaries. Models guess less when the structure is explicit.
Voice assistants depend on Q&A schema. Alexa, Siri and Google Assistant return spoken answers. Spoken answers must be short, declarative and self-contained. FAQPage schema delivers exactly that format. Without it, voice systems fall back to title tags and meta descriptions, which were never written for spoken delivery.
Internal user experience is unchanged. A well-built FAQ section reduces friction on a page, answers objections inline before they become abandonment, and provides natural anchor text for internal linking. None of those benefits required the rich result to exist.
The deprecation eliminates the SERP cosmetic. It leaves every other reason to use the markup intact.
The Decision Tree: Keep, Modify or Remove?
Not every FAQPage implementation should survive May 2026. A meaningful share of FAQ markup deployed since 2019 was keyword-stuffed filler designed to game the rich result. That work should be undone. Useful FAQ markup should be reinforced.
| Situation | Action |
| FAQPage schema on commercial pages (services, products) with substantive Q&A | Keep. Critical for AI search. |
| FAQPage schema on cornerstone blog posts answering real user questions | Keep. Critical for AEO. |
| FAQPage schema on cornerstone city or industry landing pages | Keep. Critical for local AEO and AI Overviews. |
| FAQPage with stuffed or template Q&A (“What is the best X?” answered with branded boilerplate) | Remove the schema. Rewrite or delete the questions. |
| FAQPage on the home page with very generic questions | Move to a dedicated /faq/ or /help/ page with specific entries. |
| Duplicate FAQPage entries across multiple pages | Consolidate to one canonical page. Remove duplicates. |
| FAQPage with three or fewer Q&A | Expand to at least six substantive entries or remove the schema. |
| FAQPage on pages that already rank #1 for the target query | Keep. The schema is what AI systems read, regardless of organic rank. |
Audit the entire site against this matrix before doing anything else.
What to Build Instead of Chasing Rich Results
The reflex after a SERP feature deprecation is to find the next feature to chase. That is the wrong reflex. The right reflex is to build the substrate that survives the next five SERP changes.
Restructure FAQ blocks for AI parsing. Each Q&A should follow three rules: one concept per question, one declarative sentence as the lead of the answer, and one to four short supporting sentences. Avoid hedging language. Avoid keyword stuffing. The model rewards clarity, not optimisation theatre.
Add Person and Organization signals to FAQ pages. A FAQ page with a verified Author (Person) and a clear Publisher (Organization) is treated with higher confidence than an anonymous page. For pages where expert authority matters — health, finance, legal, technical — this is non-negotiable.
Cross-link FAQs to pillar content. Each Q&A answer should contain at least one contextual link to a pillar page or service page on the same topic. Internal linking from FAQPage content reinforces the topical authority of the entire cluster.
Track FAQ visibility in AI Overviews. Search Console will stop reporting FAQ rich result impressions in June 2026. The replacement measurement layer is citation tracking. Tools like Otterly.ai, Profound, and Peec.ai monitor whether your FAQ content is being cited inside AI responses across ChatGPT, Gemini, Perplexity and Copilot. If you have not deployed one of these tools, deploy one before the Search Console reports go dark.
Why This Was Inevitable
Google did not retire FAQ rich results on impulse. The decision had been signalled for three years.
In August 2023, Google sharply reduced FAQ rich result visibility in the SERP. The feature became reserved for what Google described as well-known authoritative websites — primarily government sites and major health publications. From that point on, the rich result was effectively dead for the long tail. Most sites lost the visual enhancement they had been optimising for, even though their FAQPage markup remained syntactically valid.
The May 2026 deprecation completes the process. The feature was already invisible for 95% of the sites that had implemented it. Google now has a SERP composition optimised for AI Overviews, AI Mode, and a smaller number of explicit rich features. The FAQ rich result no longer fits that composition. Removing it is consistent with two years of architectural direction.
The deeper signal is simpler. Google is reducing the number of presentation formats that take SERP space away from AI responses. Every SERP feature that competes with the AI Overview for vertical pixel real estate is a candidate for the same treatment. Brands that built their content strategy around any single SERP feature should expect a similar deprecation eventually. Brands that built their content strategy around clear, structured, citable information will continue to compound.
What This Means for AU, US and LATAM Markets
The impact distribution is uneven across markets.
United States. AI Overviews trigger on roughly 39% of informational queries. The visible FAQ block was already losing CTR to the AI Overview directly above it. The May 2026 deprecation accelerates a transition that was already underway. US sites should expect zero to slight negative impact on traffic from the deprecation itself, with the larger ongoing impact coming from AI Overview displacement.
Australia. AI Overviews penetration in AU lags US by an estimated three to six months. FAQ rich results were still appearing in AU SERPs more frequently than in the US until early 2026. AU sites that built around the rich result will feel the deprecation more sharply than US sites did. The advantage: AU sites have a wider window to rebuild around AI Overviews citation strategy before the visibility gap closes.
LATAM and Spanish-language markets. Spanish-language AI Mode coverage continues to lag English by an estimated two quarters. Rich results in Spanish-language Google have always been less consistently distributed. The deprecation is largely a non-event in these markets in the short term. The medium-term opportunity is to deploy AI-optimised FAQPage schema before competitors catch up, building citation positions that compound through the rest of 2026.
Hyperdot’s Schema Recommendation Stack for May 2026
A revised priority stack for any business operating in AI search:
| Schema type | Priority | Why |
| Organization | Highest | Foundation. Without it, no AI system identifies the entity reliably. |
| LocalBusiness | Highest (per location) | Required for any local citation surface. |
| Person (founder, key authors) | Highest | Drives author authority signals, eligible for “expert perspective” slots. |
| Article + Author | High | Required for blog posts to be cited as sources. |
| FAQPage | High | Still consumed by AI Overviews, ChatGPT, Perplexity, voice assistants. |
| Service | High | Drives commercial query citation eligibility. |
| BreadcrumbList | Medium | Helps AI systems understand site hierarchy. |
| Review and AggregateRating | Medium | Trust signal; eligible where applicable. |
| HowTo | Medium | Still parsed despite reduced SERP feature support. |
| Product | High (e-commerce only) | Critical for AI shopping queries. |
FAQPage stays in the high-priority tier. It does not move down. If anything, it moves up relative to schema types tied to deprecated SERP features.
Should I remove my FAQPage schema today?
Only if it is keyword-stuffed, duplicated across pages, or covering questions no real user would ask. If your FAQ content is substantive and answers genuine queries, keep the schema.
Does this affect Bing and Microsoft Copilot?
Bing has not announced an equivalent change to FAQ result formatting. Microsoft Copilot continues to consume FAQPage schema for its responses. The Google deprecation does not propagate automatically to Bing.
What happens to my Search Console FAQ reports?
Historical data remains available for the standard retention window. New impression and click data tied to FAQ rich results will end in June 2026. Migrate your reporting to citation tracking tools and to Search Console’s broader Performance reports.
Does FAQ schema still appear in featured snippets?
Featured snippets are a separate SERP feature. They are unaffected by this change. Pages with structured Q&A content remain eligible for featured snippets, with or without the FAQ rich result deprecation.
Does this change anything for health or government sites?
The deprecation appears to apply across all sectors. Google’s August 2023 narrowing already restricted the rich result to well-known government and health sites, and the May 2026 change ends the feature entirely. Even those sites lose the rich result.
What is the next SERP feature likely to be deprecated?
Speculation, not prediction: HowTo rich results were narrowed in 2023 in a similar pattern to FAQ. They are the most likely next candidate. Sitelinks search box and breadcrumb display formats are also overdue for product changes.
The brands that ship a tighter, AI-aligned schema stack in May 2026 will read citation reports in August that look meaningfully different from competitors who spent the month panicking about rich results. The work is technical, unglamorous, and compounding. We do it on every client deployment. We also audit it for free.
Read our companion analysis: Google’s May 6 AI Overviews update →
Author: Adriana Kligman, Founder and CMDO of Hyperdot. Google Partner. Meta Partner. Architect of the firm’s GEO methodology since 2016. LinkedIn
