Google Ends FAQ Rich Results In Search

Google has confirmed it will no longer support FAQ rich results in Search. The change took effect on 7 May 2026 via a quiet notice added to Google’s structured data documentation rather than a blog post or wider announcement. For the many sites that built FAQ blocks into product, service and blog content in pursuit of expanded search listings, this marks the formal end of a tactic that had been losing ground since 2023.

What’s Changing And When

FAQ rich results were the expandable question-and- answer panels that appeared beneath standard organic listings, typically pulling content from pages marked up with FAQPage structured data. The format gave listings additional vertical space in the results and let publishers answer common questions before a user clicked through, which often produced a modest click-through rate uplift on suitable pages.

The retirement is being rolled out in three stages, with the most immediately visible change being that FAQ rich results stopped appearing in Search on 7 May 2026. From June 2026, Google will withdraw the FAQ search appearance filter, the rich result report tied to FAQ markup and FAQ support inside the Rich Results Test. The final stage comes in August 2026, when support for the FAQ rich result will be removed from the Search Console API, giving development teams a window to update any monitoring or reporting that pulls FAQ data programmatically.

FAQPage itself remains a valid Schema.org type, and Google has been clear that markup left in place won’t cause problems for Search. The structured data simply won’t trigger a visible result, though other search engines and AI systems that parse structured data may still read and use the markup for their own purposes.

A Three-Year Wind-Down And Why It Happened

The retirement isn’t really sudden, even if the announcement itself was. In August 2023, Google reduced FAQ rich result visibility and limited the feature to well-known, authoritative government and health websites. For commercial, ecommerce and B2B sites, the visible benefit ended at that point, more than two years before the formal removal. The 2026 announcement ends eligibility for the few remaining sites and retires the supporting reporting infrastructure.

The reason behind the wind-down is closely tied to how the feature was used. FAQ rich results were straightforward to implement, particularly on WordPress, where plugins such as Yoast, RankMath and various dedicated schema tools made it possible to add FAQPage markup with minimal technical effort. Block patterns and page builder templates accelerated the trend and FAQ sections soon appeared across product pages, service pages and blog posts that didn’t really need them. The questions often followed the template rather than the user, and the content frequently read as filler written for the markup rather than the reader. Google’s 2023 restriction was a direct response to that saturation, and the May 2026 retirement closes the chapter formally. FAQ rich results have followed a familiar pattern in search, where a useful SERP feature becomes overused to the point of no longer improving result quality and is quietly retired.

Should You Remove FAQ Schema From Your Site

For most WordPress sites, there is no immediate need to remove FAQ markup. Google’s own guidance is that valid FAQPage structured data left in place causes no problems for Search. The page simply won’t trigger the rich result it previously could, and stripping schema from hundreds of templated pages on the basis that the feature has retired creates engineering work without meaningful return.

That said, there are scenarios where a review is worth the time. Sites running multiple SEO or schema plugins sometimes produce duplicate or conflicting FAQPage markup, which is worth catching whether the rich result still exists or not. Templates that inject identical FAQ blocks across every service page or location page often carry technical debt that’s easier to address now than later.

Markup that no longer matches the visible content of a page is the other case worth flagging. It can create validation issues and contradicts Google’s general structured data guidelines, which still require markup to reflect the on-page experience. The retirement is a sensible prompt to audit what your CMS is outputting, particularly on sites that have accumulated layers of legacy markup from previous templates or plugin migrations.

A separate but related question is whether the FAQ content itself still belongs on the page. The most useful test we apply during content audits is to ask whether the section would still earn its place if FAQ rich results had never existed. Where the answer is no, the content was probably written for the markup rather than the reader, and the retirement is a good moment to remove or rewrite it.

Reporting And Workflow Implications

The more immediate operational concern is what happens to existing measurement workflows. Agencies and in-house teams have built rich result reports, schema validation checks and Search Console exports around FAQ markup over the years, and a meaningful portion of that infrastructure is about to stop producing useful data.

The Search Console interface will lose the FAQ search appearance filter and the FAQ rich result report in June 2026, and any QA process that uses the Rich Results Test to validate FAQ markup will need to update its expectations because FAQ support is being removed from that tool in the same window. For development teams running automated reporting via the Search Console API, the August 2026 cut-off matters more since scripts pulling FAQ rich result data will stop returning anything once support is withdrawn. Updating reporting now is generally less disruptive than fielding internal questions later about why FAQ numbers have collapsed, and the same applies to client reporting, where removing the FAQ panel from monthly performance reports and noting the change in the commentary avoids unnecessary confusion further down the line.

Where FAQ Content Still Earns Its Place

The disappearance of the rich result doesn’t render FAQ content irrelevant. Well-written question and answer sections continue to serve a real purpose on pages where readers arrive with predictable questions, objections or information gaps. Product specifications, service eligibility, pricing context, support documentation and policy explanations are all areas where a focused FAQ section can sharpen a page and reduce friction for the reader. The format also supports scanability, internal linking and topical coverage in ways that are independent of any search feature.

What stops working is the use of FAQs as a route to SERP real estate or as a way to bulk up word count on thin pages. That approach was always weak from a content quality perspective, and the May change removes the last remaining excuse for it. A page with five sharp, customer-led questions answered properly is far more useful than one with twenty templated entries written for keyword coverage.

The shift also matters for sites focused on AI search visibility through AEO, GEO and similar disciplines. Generative engines including AI Overviews, ChatGPT and Perplexity continue to parse structured content when forming responses and clear, well-organised question-led sections can support that work where the questions reflect real user intent.

The underlying principle holds across traditional and generative search. Pages that answer questions directly, in plain language and with a logical structure, tend to perform regardless of the search environment. FAQ formatting can contribute to that, but only when the questions are grounded in real user need.

Recommended Next Steps

For most sites, a measured response is more useful than a wholesale schema purge. The following sequence keeps the work proportionate to the change:

• Run an audit of which templates, plugins and pages are currently outputting FAQPage schema. WordPress sites should pay particular attention to overlapping plugin output and any custom theme schema injection.
• Remove or consolidate thin, duplicate or templated FAQ blocks that were added primarily for markup rather than user value.
• Update Search Console reporting, validation workflows and API-driven dashboards ahead of the June and August removal dates.
• Rewrite weaker FAQ sections so they reflect real customer questions, drawing on support tickets, sales conversations, on-site search data and AI search prompt research where available.
• Review where FAQ content has been used in place of better page structure. In many cases, what reads as a long FAQ list would work better as proper subsections, comparison content or a clearer process explanation.

The retirement of FAQ rich results closes a recognisable chapter in modern SEO, but the underlying work hasn’t changed. Readers continue to arrive with questions, compare options and look for clear answers before they act. While the display feature has gone, the job of answering those questions well remains exactly where it always was.