On May 7, Google added a quiet deprecation banner to the top of its FAQ structured data documentation. No blog post, no announcement video, just a banner. Within hours, my LinkedIn feed was split between people declaring schema dead and people declaring FAQ schema more important than ever.
Both takes are wrong, but the second one is closer to right. Here’s what actually changed and what to do about it before August.
What actually happened
FAQ rich results, those expandable question dropdowns that used to puff up your organic listings with three to five extra lines of SERP real estate, are gone. Google stopped firing them in Search on May 7, 2026.
The phase-out runs on a calendar:
- May 7, 2026: FAQ rich results stop appearing in Search
- June 2026: FAQ reporting in Search Console and FAQ validation in the Rich Results Test get dropped
- August 2026: Search Console API support for FAQ rich result data ends
If you have any reporting pipelines pulling FAQ rich result data into Looker Studio or BigQuery, you have about three months before they start returning errors or stale numbers.
What did NOT happen
This is where most of the LinkedIn takes go sideways.
FAQPage structured data itself is not deprecated. Google did not say FAQ schema is dead or broken. There is no penalty for keeping it. The schema.org spec still defines FAQPage as a valid type. Your markup will continue to validate. Your rankings will not move because of FAQ schema, in either direction. Google has confirmed this directly.
What got killed is the display feature, not the data spec. Those are two different things, and the difference matters.
The pattern
If you have been doing SEO for a while, you have seen this movie. FAQ rich results launched in May 2019, got abused immediately by teams stuffing artificial Q&A blocks onto every commercial page, got restricted to government and health sites in August 2023, and finally got killed entirely in May 2026.
HowTo rich results walked the same path a couple of years earlier. Launch, abuse, restriction, deprecation. Google’s response to schema abuse is no longer to police implementation. It is to remove the display feature and move on.
The takeaway for 2026 structured data strategy is simple. If you are adding schema primarily to capture a SERP feature, the feature can disappear. If you are adding schema to help machines understand your content, you are still in good shape.
The AI search angle
The interesting part of this story is not the death of the rich result. It is what FAQPage schema is becoming.
AI systems are extraction layers. ChatGPT Search, Perplexity, Gemini, and Google’s own AI Overviews all need to pull discrete facts out of pages and cite them with confidence. Content that comes pre-labeled as a question and its corresponding answer, in machine-readable JSON-LD, is easier for an extraction system to parse than a wall of prose.
I am not going to quote vendor statistics on AI citation lift, because most of them are unverified. The directional logic is sound, though. If you have real questions with real answers on your page, marking them up as FAQPage continues to help AI systems find them and cite them with the right pairing.
The job description for FAQ schema changed. It used to be a SERP feature trigger. It is now an AI citation aid.
What to do this week
For pages with existing FAQ schema:
Leave it alone. Don’t run a sitewide strip just because Google killed the dropdown. Valid schema costs you nothing. Other search engines and AI crawlers continue to parse it. The maintenance cost of removing it across a large site is real, the benefit is zero.
For your reporting:
Pull a list of pages that historically earned FAQ rich result impressions in Search Console. Note the CTR baseline before May 7. You are going to see CTR compression on those pages over the next few months, and you want to be able to isolate that from any other SEO changes you make in the same window. Six to twelve weeks of data is a reasonable lookback before drawing conclusions.
Audit any Search Console API integrations or BigQuery exports that pull FAQ rich result dimensions. Get those updated before August 2026, or they will start returning errors.
For new content:
Stop adding FAQ sections just to grab a SERP feature, because the feature is gone. Add FAQ sections where you have real questions from real customers that deserve answers on the page. Mark those up with FAQPage schema if you want AI systems to extract them cleanly. The bar is now usefulness, not display real estate.
The bigger shift
Google has been quietly narrowing the set of supported rich results for three years. FAQ is the latest. Product, Article, Recipe, Video, Organization, LocalBusiness, and BreadcrumbList still produce visible enhancements. Most of the rest have been phased out or restricted.
At the same time, AI Overviews now appear on roughly a third of search result pages, and position one organic CTR has dropped sharply year over year. Traditional click volume from high rankings is compressing across the board. The visibility game in 2026 is less about which SERP features you can stack and more about whether your content is structured and useful enough for both Google and the AI layer sitting on top of it.
FAQ rich results going away is not a strategic earthquake. It is a small piece of a larger shift that has been visible to anyone watching the data for two years.
Don’t panic. Don’t strip your schema. Update your dashboards. Keep writing real answers to real questions.