Google drops FAQ rich results

Google has basically finished killing FAQ rich results. The visible part already happened on May 7, 2026 — FAQ expansions stopped showing in Google Search. The rest is cleanup. In June 2026, Google says it will remove the FAQ search appearance, the FAQ rich result report, and FAQ support in the Rich Results Test, and in August 2026 it will stop exposing FAQ rich-result data through the Search Console API. ### What exactly disappeared? The old FAQ treatment was the expandable list of questions and answers that could sit under a normal blue link in search results. That feature is what Google says it is dropping from Search, not just hiding from reporting. The dates matter here: no more FAQ rich results in Search as of May 7, then no more dedicated FAQ reporting or testing support in June, then no more API support in August. (searchenginejournal.com) ### Wasn’t FAQ already mostly gone? Yes — that is the important context. Back in 2023, Google sharply limited FAQ rich results to “well-known, authoritative” government and health sites. So for most publishers, retailers, and affiliate sites, the feature had already stopped being a real traffic lever a while ago. What changed this week is that Google’s own documentation now points to a full retirement path, not just a narrow eligibility rule. (searchenginejournal.com) ### What’s changing inside Search Console? A lot of SEO teams won’t feel the loss in rankings, but they will feel it in tooling. Google says the FAQ search appearance and rich result report are going away in June 2026. That means dashboards, saved filters, and any workflows built around FAQ-specific Search Console views will lose that slice of data. The API sunset in August gives teams a short grace period to rewrite those calls. (developers.google.com) ### Does the markup itself become useless? Not completely. Google’s structured-data docs still say structured data helps Google understand page content more broadly, even when a specific rich result is gone. And other search engines may still read FAQPage markup. But if your reason for adding FAQ schema was “get the accordion in Google,” that reason is over. (searchenginejournal.com) ### Should sites remove FAQPage markup now? Probably only if you want to simplify templates or reduce maintenance. Google isn’t saying you must rip it out immediately. The more urgent task is operational — export any historical FAQ reporting you still need, update API-dependent scripts before August, and stop treating FAQ schema as a visibility tactic in Google Search. That is the real break. (developers.google.com) ### What about Q&A pages? Those are different. Google’s QAPage documentation still describes a supported rich result for pages built around one question and multiple answers, like forums or help communities. So this is not Google abandoning every question-and-answer format. It is specifically shutting down FAQ rich results. ### Why did Google do this? (searchenginejournal.com) Google has not given a public explanation in the material now showing the change. But the direction is pretty clear: over the last few years, Google has been trimming SERP features that got overused, cluttered results, or added little value at scale. FAQ rich results were an obvious candidate because they spread far beyond the narrow cases where they were genuinely helpful. That last part is an inference — but it fits the 2023 restriction and the 2026 removal path. (developers.google.com) ### So what’s the bottom line? For most sites, this is less a sudden traffic apocalypse than the final paperwork on a feature Google had already put on life support. But if your team still tracks FAQ rich results in Search Console or through the API, the clock is real now — June 2026 for the interface and August 2026 for automation. (searchenginejournal.com) (developers.google.com)