FAQ Schema: Why You Still Keep It After Google Retired the Rich Result

Here is the argument that keeps surfacing in technical-SEO reviews: "Google retired FAQ rich results, so rip out the FAQPage schema." It is half right, and the wrong half is the one that costs you. Google did retire the FAQ rich result for almost every site. That is true, and you should say so out loud. But the schema itself is still a supported, useful, near-zero-cost asset, and removing it gains you nothing.

This is the full, receipt-backed picture, so you can make the call on purpose instead of on a rumour: what Google actually changed, what it did not change, and exactly when keeping FAQPage markup is worth it.

📌 The receipt: what Google actually announced

On 8 August 2023, Google published "Changes to FAQ and HowTo rich results" on Search Central. The two concrete changes:

• FAQ rich results would only be shown for "well-known, authoritative government and health websites." For every other site, the expandable FAQ treatment in search results was switched off, globally, rolling out over the following weeks.
• HowTo rich results were limited to desktop, and then removed entirely; Google later deprecated HowTo structured data reporting altogether.

Google's stated reason was a cleaner, less cluttered results page. Crucially, the announcement was about when the rich result appears. Google did not deprecate the FAQPage type, did not ask anyone to remove existing markup, and kept the structured-data documentation live (updated to note the new eligibility limit). So the honest framing for any deck or audit is: "Google retired the FAQ rich result for non-gov/health sites in 2023", not "FAQ schema is dead."

🔍 What changed vs. what didn't

🤖 Why keep it: the case for FAQPage in an AI-search world

The strongest reason to keep FAQPage isn't the old rich result, it's that structured data is the cheapest way to make your content unambiguous to machines. A Q&A buried in prose has to be inferred. A FAQPage block states it: this is the question, this is the answer, full stop.

• It's a shared vocabulary, not a Google feature. Schema.org is consumed by many systems, search engines, voice assistants, and AI answer engines that parse JSON-LD to extract entities and relationships. Marking up Q&A pairs removes guesswork for any of them. (Be precise: no major AI engine has publicly confirmed FAQPage as a ranking signal, see the limitations below, but the parsing benefit is mechanical and real.)
• It forces good content architecture. Writing genuine, scannable FAQs that map to real user questions is exactly what wins featured snippets and PAA placements, with or without the rich result.
• The cost is a rounding error. A FAQPage block is a few kilobytes of JSON-LD in the head. There is no rendering cost, no CrUX impact, no maintenance burden beyond keeping it accurate.
• It's forward-compatible optionality. Eligibility rules have changed before and can change again. If Google re-expands the rich result, marked-up sites benefit immediately; unmarked sites scramble.

Put bluntly: removing valid FAQPage markup gives you nothing and quietly removes optionality. That is a bad trade.

🧭 The bigger reason: don't architect only for Google

There is a strategic point underneath the tactical one. Google retired the FAQ rich result on its own timetable, with little notice, the same way it introduced FAQ results and then took them away. If your structured-data strategy is built purely around Google's current display decisions, you are signing up to rebuild it every time Google changes its mind. That is not a stable foundation; it is a dependency on a single vendor's roadmap.

And Google is no longer the only audience that matters. Search is fragmenting. AI assistants and answer engines increasingly sit between people and the open web, and they read the same structured signals to decide what to surface and cite. A markup choice that looks pointless through a Google-only lens looks very different once you count every engine that parses your pages. Optimising for the durable, shared layer, clean, machine-readable structure that any consumer can use, ages far better than optimising for one company's rich-result policy. Keep the schema for the web that is coming, not just the SERP that exists today.

🚦 When to keep it, add it, or skip it

🔧 Implementation: a correct FAQPage block

JSON-LD in the <head>, one Question per real on-page FAQ, with the answer text matching what users actually see:

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "FAQPage",
 "mainEntity": [{
 "@type": "Question",
 "name": "Does FAQ schema still work in 2026?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Yes. The FAQPage type is still supported; only the
 Google rich result is now limited to authoritative
 government and health sites."
 }
 }]
}
</script>

Validate with the Schema.org validator or Google's Rich Results Test. The Rich Results Test will tell you the markup is valid even though it won't preview a rich result for a non-eligible site, that is expected, not an error.

🚧 What FAQ schema will not do

Balance is the point of a real analysis, so here are the honest limits, the same caveats that make the "keep it" case credible:

• It will not restore the rich result for non-gov/health sites. The deck call-out is correct on this; don't promise stakeholders the accordions are coming back.
• It is not a confirmed AI ranking or citation signal. The parsing benefit is mechanical and plausible, but no major AI engine has publicly documented FAQPage as a weighting factor. Sell it as content hygiene and optionality, not a magic lever.
• It will not rescue thin content. Schema describes a page; it doesn't improve one. Fake or hidden FAQs marked up to chase features violate Google's structured-data guidelines and can earn a "spammy structured markup" manual action.
• It will not move traffic on its own. Treat it as an enabler that compounds with genuinely good Q&A content, not a standalone tactic.

✅ The one-line recommendation

Keep FAQPage schema wherever you have real, visible FAQ content. State plainly that Google retired the rich result for non-gov/health sites in 2023, that's accurate and builds trust, and keep the markup anyway, because it is machine-readable, future-proof, and costs essentially nothing. The only place to remove it is where the FAQs aren't genuinely on the page. That's the entire decision.