On May 7, 2026, Google quietly stopped showing FAQ rich results in Search. There was no blog post and no explanation, just a deprecation notice added to the FAQ structured data documentation. For anyone who spent the last few years adding FAQ schema to win those expandable question-and-answer dropdowns in the results, the feature you were optimizing for is now gone.
The reaction online split into two loud and equally wrong camps. One says structured data is dead. The other says FAQ schema now matters more than ever for AI search. Neither is accurate, and acting on either one will waste your time. The practical reality sits in between, and the actions you actually need to take are smaller than most of the takes suggest.
This article explains exactly what changed, what it does and does not affect, and what to do with your existing FAQ markup, whether you run a global site, a local business page, or a bilingual site targeting more than one audience.
What Google actually changed
The change is narrow and specific. According to Google's own FAQ structured data documentation, the deprecation has three stages. As of May 7, 2026, FAQ rich results no longer appear in Google Search. In June 2026, Google removes the FAQ search appearance filter, the rich result report, and FAQ support in the Rich Results Test. In August 2026, support for the FAQ rich result in the Search Console API is removed, which as PPC Land notes gives developers a grace period to adjust automated pipelines before the data disappears entirely.
The single most important line in that notice is easy to miss. Google states it will continue to use FAQ structured data to better understand pages, even though the visual rich result is gone. In other words, the display feature is retired, but the markup itself is not banned, penalized, or treated as a problem. As Search Engine Journal reported, FAQPage remains a valid Schema.org type and leaving it on your pages does not hurt your search visibility.
It was also not sudden. The deprecation completes a process that started in August 2023, when Google first restricted FAQ rich results to well-known, authoritative government and health sites. For most of the web, the FAQ dropdown had already been gone for nearly three years. The May 2026 change simply removes it for everyone, including the government and health sites that had kept it.
Why Google did this
Google did not publish a reason, so anyone claiming to know the definitive why is guessing. But the pattern is clear enough to make a fair inference.
FAQ rich results followed the same path as HowTo rich results, which Google restricted in 2023 and then deprecated. Both share a common cause: the format was widely abused. The history here is well documented. As PPC Land traces it, the feature went from a genuine user-experience enhancement in 2019 to a mechanism for injecting promotional internal links into search results, and concerns about misuse were being raised from the earliest days. When a feature becomes a manipulation target more than a user benefit, Google's typical response is to remove the display feature entirely rather than police every implementation.
The honest reading is that Google is pruning a low-value visual treatment that got gamed, not declaring structured data irrelevant. That distinction matters, because it tells you which of your schema investments are safe and which were never going to last.
What this does and does not affect
This is where the two overreactions fall apart, so let me be precise.
What it affects: the FAQ dropdown that expanded your listing in the results is gone, on desktop and mobile, in every country and language. If a meaningful share of your clicks came from that extra real estate, you have already lost it. SearchPilot's own testing is instructive on how much that real estate was worth: when they first tested adding FAQ schema, they measured organic traffic uplifts in the range of roughly 4 to 15 percent, and in one case 25 percent, almost entirely because the listing took up more space and won more clicks, not because rankings improved. That is exactly the upside that has now been removed.
What it does not affect: your rankings, your crawlability, and the validity of your markup. Removing FAQ schema is not required. SearchPilot also tested removing valid FAQ schema and found no statistically significant change in organic traffic either way, which tells you the markup was rarely the thing driving your results once the rich result was gone. If your FAQ content consists of real questions your customers actually ask, answered with genuine expertise, this change touches your visibility a little and your credibility not at all.
It also helps to keep the bigger picture in view. The reporting tools that tracked FAQ performance are being retired through June and August, so any dashboard, Looker Studio connector, or automated Search Console API pull that depends on FAQ rich result data needs updating before those dates or it will start returning empty values.
What this is not: the AI search myth
The most common piece of advice circulating right now is that FAQ schema is now essential for showing up in AI search and AI Overviews. Be careful with this one.
Google's own AI features guidance states there is no special structured data required for AI Overviews or AI Mode, while also noting that any structured data you use should match the visible content on the page. So the idea that adding FAQ markup is a reliable lever for AI visibility is not supported by Google's documentation. FAQPage markup is still crawlable by AI systems and retrieval crawlers, and clean, well-structured Q&A content can genuinely help machines parse your page. But that is a content-quality argument, not a schema trick. Adding FAQ JSON-LD to a thin page will not earn you AI citations.
This matters more than usual right now because AI-driven results are eating into traditional clicks at the same time. Industry tracking cited by Launchcodex put AI Overviews on roughly 31 percent of search result pages, with position-one organic click-through rates down sharply year over year. The useful response to that shift is not a schema shortcut. It is the slower work of becoming the source AI systems actually cite, which is the core of answer engine and generative engine optimization. Structured data earns its keep when it describes real, visible, high-quality content. It does nothing when it is used as a shortcut.
What to actually do now
Here is the practical checklist, in order of priority.
First, fix your reporting before the deadlines. If you pull FAQ rich result data through the Search Console API or feed it into dashboards, update those calls before August 2026 to avoid silent gaps. If you want historical FAQ performance data for year-over-year comparisons, export it before June 2026, because the report disappears then.
Second, leave your existing FAQ markup in place unless you have a specific reason to remove it. Google has explicitly said unused structured data does not cause problems, and SearchPilot's removal test showed no traffic benefit to ripping it out. Removing it is busywork unless it is part of a broader template cleanup you were doing anyway, or the markup was thin, keyword-stuffed, or added purely to manipulate the old rich result.
Third, shift your structured data effort toward the types that still produce results. Product, Article, LocalBusiness, Event, and Review or AggregateRating markup all continue to generate rich results in Google Search. Organization and Person schema remain important for helping search engines and AI systems correctly identify your brand as an entity. These are where structured data still pays off.
Fourth, keep your FAQ content if it serves users. A clear FAQ section that answers genuine objections is good for conversion and good for the humans reading your page, regardless of whether it triggers a rich result. Keep it because it helps people decide, not because it wins a SERP feature.
Fifth, stop treating any display feature as the reason to implement schema. The lesson of both the FAQ and HowTo deprecations is that visual SERP features come and go, often because they get abused. Schema that describes real content survives these changes. Schema added purely to grab search real estate does not.
A note for bilingual and multi-market sites
If you run a site that targets more than one audience, for example an English and Japanese version, there is a small extra consideration. The deprecation applies in every language and country, so nothing here is region-specific. But markets differ in how much search behavior is shifting toward AI-assisted answers, and in Japan in particular a meaningful share of search still runs through Yahoo! JAPAN alongside Google, each with its own evolving AI answer features. We covered the broader Japan search and platform picture in our guide to paid advertising in Japan.
The practical implication is the same as the global advice, applied per audience: make sure your structured data matches the visible content in each language, do not assume a schema tactic that is fading on Google will quietly help you elsewhere, and prioritize genuinely helpful, well-structured content in each language over markup shortcuts. For businesses serving both local and international audiences, that clarity tends to matter more than any single rich result ever did.
Common mistakes to avoid
Three predictable errors are already showing up in response to this change.
Ripping out all FAQ schema in a panic. There is no proven traffic benefit, and it can introduce template errors. Leave it unless you have a reason.
Doubling down on FAQ schema as an AI search hack. Google's guidance does not support it. You will spend effort on a tactic that does not deliver.
Forgetting the reporting deadlines. This is the one with a real cost. If your dashboards depend on FAQ rich result data, update them before June and August or your reporting will quietly break.
How we help
We help businesses sort signal from noise on exactly this kind of change, where the headline sounds alarming but the right response is specific and limited. That means auditing which structured data types are still worth your investment, cleaning up reporting that depends on retired features, and building FAQ and content structures that serve both human readers and the search and AI systems that increasingly summarize them. That work sits at the center of our AEO and GEO services, and it connects directly to search engine marketing for the Japanese market for companies operating across more than one language or audience.
If you are unsure whether your current structured data is helping you, hurting you, or simply sitting there, that is a quick thing to check before you make changes you do not need.
FAQ
Do I need to remove FAQ schema from my website?
No. Google has stated that unused structured data does not cause problems for Search, and FAQPage remains a valid Schema.org type. SearchPilot's split test on removing valid FAQ schema found no statistically significant change in organic traffic. Leave it in place unless you are doing a broader template cleanup or the markup was thin or manipulative.
Will this hurt my Google rankings?
No. The change removes a visual search feature, not a ranking signal. Google has said it will continue to use FAQ structured data to better understand pages. What you lose is the expandable FAQ dropdown that gave your listing extra space, not ranking position.
Does FAQ schema help with AI search and AI Overviews?
Not as a standalone tactic. Google's AI features guidance says no special structured data is required for AI Overviews or AI Mode, though any structured data you use should match the visible page content. Clean, well-structured Q&A content can help AI systems parse a page, but adding FAQ markup to thin content will not earn AI citations.
What are the important dates I need to know?
FAQ rich results stopped appearing on May 7, 2026. The FAQ search appearance filter, rich result report, and Rich Results Test support are removed in June 2026. Search Console API support for FAQ rich result data ends in August 2026. If you rely on that data for reporting, export it before June and update API calls before August.
Which structured data types still produce rich results?
Product, Article, LocalBusiness, Event, and Review or AggregateRating markup all still generate rich results in Google Search. Organization and Person schema remain valuable for entity recognition in both search and AI systems. These are where structured data effort still pays off.
Should I stop writing FAQ sections on my pages?
No. A genuine FAQ section that answers real customer questions is good for conversion and good for readers, whether or not it triggers a rich result. Keep FAQ content because it helps people decide, and write it for humans first.
Ready to make sure your structured data is actually working?
We help businesses audit their structured data, clean up reporting tied to retired search features, and build content that serves both human readers and AI systems, across one market or several. Contact us if you want a quick read on whether your current setup is helping or just sitting there.
