FAQ rich results are gone. What to do with the markup

What happened, with dates

Google’s FAQPage documentation states that as of 7 May 2026, FAQ rich results no longer appear in Google Search. The FAQ search appearance, the rich result report and support in the Rich Results Test were dropped in June 2026, and Search Console API support ends in August 2026.

There is no remaining eligibility for anyone. The earlier carve-out from August 2023, which had preserved FAQ rich results for well-known authoritative government and health sites, is superseded.

So the visible expanded question list under a result is finished, for every site.

What it does not mean

It does not mean FAQ content was a mistake. The rich result was a display treatment; the content was answering questions people ask.

It does not mean you must strip the markup. Google’s own guidance is that you may remove FAQPage structured data or leave it in place, since other search engines may still process it.

It does not mean structured data stopped mattering. Other types are unaffected, and this was one appearance being retired rather than a change of direction.

What we would actually do

Leave the markup unless you are cleaning up for another reason. Removing it costs developer time and buys nothing.

Keep the questions, and check they are still the questions being asked. An FAQ block written for a rich result tends to be written for the snippet rather than for a person, which shows.

Rewrite the answers to stand alone. The most useful property of a good answer now is that a model can lift it without ambiguity, and that means a complete sentence that makes sense on its own rather than a fragment that assumed the question was displayed above it.

Move anything load-bearing out of the accordion. Content a user has to click to reveal is content some crawlers and some readers never see, and if the answer matters commercially it belongs in the body.

The wider point

This is the second time in three years that a display feature people optimised for has been withdrawn. The pattern is worth internalising: features come and go, and the answer underneath is what survives.

Content built for a rich result dies with the rich result. Content built to answer the question keeps working in the next surface, whatever it turns out to be.

“This is the second time in three years that a display feature people optimised for has been withdrawn.”