Is FAQ Schema Deprecated? What Google's Changes Mean for Your Site in 2026

The phrase "FAQ schema deprecated" generates a startling amount of search volume in 2026, three years after the only event that arguably justifies the question. The short answer: FAQ schema is not deprecated. The longer answer involves what Google actually announced in August 2023, why that announcement triggered confusion that still hasn't faded, and why FAQ schema is in fact more valuable in 2026 than it was in 2022.

This guide walks through what happened, what didn't, what still works, and how to think about FAQPage schema in your stack today.

The short answer

FAQ schema — formally the FAQPage type in the Schema.org vocabulary — is not deprecated. The vocabulary is current, the syntax is current, and the schema is parsed and weighted by every major search engine and AI model that consumes structured data. There has been no announcement from Schema.org, Google, or any other ecosystem participant deprecating the FAQPage type. The spec page at schema.org/FAQPage is active and unchanged.

What changed was a single Google product decision in August 2023 about which sites are eligible to display the FAQ rich-result accordion in classic search. That decision affected presentation in one Google surface. It did not change the schema vocabulary, did not affect AI search engines, did not affect Bing or other engines, and did not affect voice assistants.

Three years later, the rumor of "FAQ schema deprecated" still floats through SEO threads and content briefs. It's mostly residue from 2023 commentary that conflated "rich result restricted" with "schema deprecated." Those are very different things.

What actually changed in August 2023

Google announced two changes that summer:

HowTo rich results were retired entirely from desktop and reduced significantly on mobile.
FAQ rich results were restricted to authoritative government and health websites. Most other sites stopped showing the visible FAQ accordion under their search listings.

The second point is what fueled the deprecation rumor. SEO publications wrote headlines like "Google kills FAQ rich results" and "FAQ schema is dead," and a meaningful portion of readers walked away thinking the schema itself had been dropped from the spec.

What Google actually changed was rich-result eligibility — which sites get the visual treatment in their search results page. The schema continued to be parsed, indexed, and used as a ranking signal. AI engines, which were just beginning to gain importance at the time, kept reading it normally and continue to do so today.

Three meanings of "deprecated" — and which one applies

Confusion around the FAQ schema question comes from people using "deprecated" to mean three different things:

Vocabulary-level deprecation. This would mean Schema.org has formally marked the FAQPage type as obsolete and replaced it with something else. This has not happened. The vocabulary is current.

Rich-result deprecation. This would mean Google no longer renders FAQ rich results in classic search for the relevant sites. This is what actually happened — for most sites — in August 2023. But "Google doesn't render the rich result" doesn't mean "the schema doesn't matter." Rich results are one of many uses of structured data; AI citation is another, voice assistant lookup is another, Bing's parsing is another.

Recommended-practice deprecation. This would mean industry consensus has shifted away from using FAQ schema. This has not happened. Quite the opposite — best-practice content from the major SEO software vendors, AI search optimization specialists, and Schema.org itself continues to recommend FAQPage schema as a high-leverage implementation.

None of the three deprecation senses applies to FAQ schema in 2026.

What still works in 2026

Despite the rich-result restriction, the FAQPage type remains valuable in many surfaces:

ChatGPT with browsing and the OpenAI search index reads FAQPage schema and cites FAQ-marked pages disproportionately when responding to question-style queries.
Perplexity treats FAQPage as a primary source-ranking signal. Pages with clean FAQ schema appear in answer citations far more often than pages without.
Google AI Overviews — the AI-generated summaries that now appear above many search results — pull from FAQ-marked pages aggressively. AI Overviews are arguably a replacement for the rich-result accordion, and they favor FAQ schema as input.
Bing Chat / Copilot continues to weight FAQPage schema positively for both classic Bing results and Copilot responses.
Voice assistants (Alexa, Google Assistant, Siri) use FAQPage for direct-answer matching. Spoken questions get spoken answers pulled from FAQ-marked pages more reliably than unstructured prose.
Bing rich results remain available without the same restrictions Google placed on FAQ rich results.

The result: FAQ schema is more valuable in 2026 than it was in 2022, because the AI surfaces it powers (AI Overviews, ChatGPT, Perplexity) didn't exist or were nascent three years ago. Our FAQ schema complete guide goes deeper on the implementation details; the strategic case is straightforward.

Should you remove FAQ schema from your site?

No. There's no upside and there's real downside.

No upside. The Google rich-result accordion was already gone for most sites in late 2023. Removing FAQ schema in 2026 doesn't get you anything you weren't already getting (you weren't getting the rich result; that ship sailed). It doesn't free up much code — FAQPage JSON-LD is small. It doesn't speed up your page meaningfully — JSON-LD is parsed once at crawl time, not at render time.

Real downside. You stop being eligible for AI citation in ChatGPT, Perplexity, AI Overviews, and Bing Chat for those questions. You stop being a voice-assistant answer source. You give up the long-tail traffic that comes from being the cited source for specific question-style queries.

The only valid reason to remove FAQ schema is if your existing implementation is so broken (cloaked content, mismatched questions, fake answers stuffed for keyword purposes) that fixing it would be slower than starting over. In that case, remove the broken schema and rebuild it correctly. Don't leave broken schema in place.

How to use FAQ schema correctly in 2026

The fundamentals haven't changed, but the AI-search context raises the stakes for getting it right:

Write questions users actually ask. Natural language with question marks, not keyword-stuffed phrases. "What is FAQ schema?" beats "FAQ schema definition meaning."

Keep answers self-contained and 80–200 words. AI engines often quote answers in isolation. Each answer should make sense if extracted alone.

Match visible content exactly. Every Q&A pair in your schema must appear in the visible DOM with the same wording. Cross-checking is automated by both Google and AI engines.

Aim for 5–10 Q&A pairs per page. Fewer feels thin; more dilutes signal and looks like keyword farming.

Validate before shipping. Run your output through our validator — it catches structural mistakes, missing fields, and cloaking risk.

Generate, don't hand-write. Use our FAQ schema generator or your CMS's schema builder. Hand-written JSON-LD is error-prone and rots over time as content gets updated and schema doesn't.

Auditing existing FAQ schema on your site

If you're worried that some of your FAQ schema might be doing more harm than good, run this audit:

Find every page with FAQPage schema. A site crawl with structured-data extraction works well. Or use Google Search Console's structured-data report.
Spot-check ten pages. For each: does the schema's question text exactly match a visible question on the page? Does the answer text exactly match the visible answer? If not, you have a cloaking problem — fix or remove.
Check answer length. Answers under 50 words are too short to be quote-worthy by AI engines. Either expand them substantively or remove the Q&A pair.
Check for duplicate FAQPage scripts. Some sites have two on the same page from competing plugins. Pick one and remove the other.
Run the AI Readiness Score on the same pages. Low scores point to specific fixes — usually missing dates, generic descriptions, or cloaking.

Most sites that audit existing FAQ schema find a mix of "working well, leave it," "needs minor fixes" (expand answer length, sync visible text), and "remove and rebuild" (cloaked or broken). The proportions vary, but very few sites end up removing FAQ schema entirely after a real audit.

Why the deprecation rumor persists

A few reasons the "FAQ schema deprecated" framing keeps surfacing three years later:

Headlines outlive context. Articles published in late 2023 with sensational headlines about "the death of FAQ schema" still rank on the relevant queries. Readers in 2026 see them and assume the information is current.
The rich-result loss was painful. Sites that had relied on the FAQ accordion for visual differentiation in classic search lost something tangible. The pain coloured the broader narrative.
Schema is hard to verify. Most marketers can't easily check whether AI engines are citing their FAQ schema. Without that feedback loop, a vacuum of evidence got filled with the deprecation rumor.
AI search adoption was uneven. Sites that prioritized AI search early saw the continuing value of FAQ schema. Sites that didn't, didn't.

The corrective: if you're hearing "FAQ schema is deprecated" in your team or organization, the right response is to point at the schema.org page, point at any AI search engine's documentation, and run an actual citation audit. The data is there; the rumor doesn't survive contact with it.

Frequently Asked Questions

Is FAQ schema deprecated?

No. FAQ schema (the FAQPage type in Schema.org) is not deprecated. The vocabulary is still actively maintained, still parsed by every major search engine and AI model, and still recommended for question-and-answer content. What changed in August 2023 was Google's rich-result eligibility — the visible FAQ accordion in classic search results was restricted to government and health sites. The schema itself remains fully supported.

What did Google actually change in 2023?

In August 2023, Google announced that FAQ rich results in classic search would be limited to authoritative government and health websites. Most other sites stopped seeing the expandable FAQ accordion appear under their search listings. This was a presentation change affecting one specific Google search surface — not a deprecation of the FAQPage schema vocabulary.

Should I remove FAQ schema from my pages?

No, you should keep it and in many cases expand it. FAQ schema continues to drive AI citation in ChatGPT, Perplexity, Google AI Overviews, Bing Chat, and Gemini. It's also still parsed by voice assistants. Removing FAQ schema costs you AI citation visibility while gaining nothing — the rich result was already gone for most sites, so there's no upside to deletion.

Does FAQ schema still help with SEO in 2026?

Yes, primarily through AI search engines rather than classic Google rich results. AI Overviews, ChatGPT browsing, Perplexity, and similar AI surfaces use FAQ schema as a primary extraction signal — pages with clean FAQPage markup are cited disproportionately more often than pages without it. For traditional Google blue-link ranking, FAQ schema provides modest indirect benefits via clearer page understanding.

Are AI engines like ChatGPT actually reading FAQ schema?

Yes, all major AI search engines parse FAQPage JSON-LD when they crawl pages. The structured question-and-answer format matches the patterns these models were trained on (forum posts, Stack Overflow, support docs), so they extract and cite FAQ-marked pages with high confidence. Citation rates for pages with valid FAQPage schema are measurably higher than for equivalent pages without it.

How many FAQ pairs should a page have in 2026?

Five to ten substantive question-answer pairs per page is the sweet spot. Fewer feels thin and gives AI engines limited coverage of likely follow-up questions; more dilutes per-question weight and can be interpreted as keyword stuffing. Each answer should be 80–200 words, written in natural language that stands alone if quoted out of context.

What's the difference between FAQ schema and Q&A schema?

FAQPage is for pre-written, authoritative question-and-answer content where the page owner provides both the questions and the answers. QAPage is for community Q&A formats like Stack Overflow or forum threads where users ask questions and other users answer. Most websites should use FAQPage. QAPage is appropriate only for community-generated Q&A platforms.

FAQ schema is not deprecated, and acting as if it is costs you AI citation visibility every day the assumption goes unchecked. The 2023 Google rich-result restriction was a presentation change in one search surface, not a vocabulary deprecation, and the AI surfaces that have grown since then — ChatGPT, Perplexity, AI Overviews, Bing Chat — make FAQPage schema more valuable in 2026 than it was in 2022. Keep your existing FAQ schema, audit it for quality, fix what's broken, and generate new pages through our FAQ schema generator and validator. The compounding payoff in AI citations is real.