FAQ rich results are no longer shown for most websites. In 2023 Google restricted FAQPage rich results to a small set of authoritative government and health sites, and that restriction still stands in 2026. So is FAQ schema dead? Not quite — the visual rich result is gone for almost everyone, but the underlying FAQPage markup still helps machines understand your content, and well-structured Q&A remains one of the strongest formats for getting lifted into AI answers. The mistake is treating the lost rich result as a reason to delete good structure.
What actually changed — and what didn't
Google stopped displaying the expandable FAQ dropdowns in search results for ordinary sites. That means adding FAQPage schema will not, for most domains, produce a visible enhancement in Google's blue-link results anymore. What did not change: the markup is still valid, still parsed, and still a clean way to tell any consumer of your page "this is a question, and this is its answer." AI assistants, which assemble answers rather than render Google's specific UI, benefit from that clarity regardless of whether Google draws a dropdown.
So the honest position for 2026 is: don't add FAQPage schema expecting a rich result, but don't rip it out either if your Q&A content is genuine. Remove markup only when it's invalid, hidden, or slapped onto content that isn't really a question and answer — the same cleanup logic we covered for HowTo schema after its deprecation.
The abuse that got FAQ results killed
It's worth understanding why the rich result disappeared, because the lesson still applies. Sites stuffed FAQPage markup onto pages that had no real FAQ, invented questions nobody asked to grab extra search real estate, and marked up content that wasn't visible on the page. Google's requirement has always been that structured data reflect content actually shown to users. When markup describes questions users can't see, it's a policy violation — and that mismatch is exactly what structured data validation and manual reviews catch. The rich result was withdrawn largely because the signal had been gamed into meaninglessness.
How to use Q&A content well in 2026
The format still works; the framing changes. Instead of "add FAQ schema to rank," think "structure genuine questions so AI can lift them." That means:
- Write real questions your audience actually asks, phrased the way they'd type or speak them.
- Give each question a complete, self-contained answer that makes sense on its own.
- Keep the visible page and the markup in perfect sync — every marked-up Q&A must appear on the page.
- Reserve FAQPage for true FAQ pages; for a single community question use QAPage instead.
Conversational, question-shaped content is precisely what AI answer engines retrieve, because people query assistants in full questions. Aligning your headings and answers with real queries is the heart of optimizing for conversational long-tail queries, and it pays off whether or not a dropdown ever appears.
FAQPage vs QAPage vs plain content
Choose the type that matches reality. FAQPage is for a page of questions the site itself answers — a support or product FAQ. QAPage is for a single user-posed question with community answers, like a forum thread. And plenty of pages don't need Q&A markup at all — a well-written article with clear headings that answer questions is already retrievable by AI without any FAQ schema. Don't force the structure where it doesn't fit; the format should follow the content, not the other way around.
The takeaway: FAQ schema isn't dead, it's demoted from a ranking gimmick to what it should always have been — an honest description of real question-and-answer content that helps machines, including AI assistants, understand and cite you. Keep it where it's genuine, validate it, and let the quality of the answers do the work.
Want to check whether your structured data is valid and your Q&A content is visible to AI crawlers? Run the CheckMy.site scanner to see how your pages parse for the assistants deciding which answers to trust.