Google FAQ Schema Rich Results: What the Deprecation Teaches SEO Teams
Google FAQ rich results are retired in Search, but useful FAQ content is not dead. If you are checking this because your FAQ enhancement report disappeared or your FAQ snippets stopped showing, the short answer is: do not delete every FAQ section. Do stop treating FAQPage schema as a traffic lever.
As of May 7, 2026, FAQ rich results are no longer shown in Google Search. Google also said support for FAQ rich results would be removed from the Search Console rich result report and Rich Results Test in June 2026, with Search Console API support removed in August 2026.
Do not remove useful FAQs just because dropdowns disappeared. Remove or simplify FAQPage schema when it creates maintenance work without value, but keep visible Q&A content when it helps readers make a decision.
What happened to Google FAQ rich results?
Google retired FAQ rich results as a visible Search appearance. The change came after years of reduced eligibility: FAQ rich results were broadly used by publishers, then restricted mostly to well-known authoritative government and health sites in August 2023, and then retired in Google Search on May 7, 2026.
The source of truth is Google's FAQPage structured data documentation. It states that FAQ rich results are no longer appearing in Google Search as of May 7, 2026, and that Search Console and testing support are being removed in stages.
Google's earlier August 2023 update already made the direction clear. FAQ rich results were narrowed to a much smaller set of authoritative sites, while HowTo rich results were removed from desktop. The 2026 retirement is the final step of that same trend.
What changed in 2026?
The 2026 change affects both the Search appearance and the tools SEO teams used to monitor it. FAQPage markup can still exist on a page, but Google Search no longer uses it to show FAQ dropdown rich results. That changes what teams should measure and what they should maintain.
| Date | Change | What SEO teams should do |
|---|---|---|
| August 2023 | FAQ rich results restricted mostly to authoritative government and health sites | Stop treating FAQ schema as a broad SERP expansion tactic |
| May 7, 2026 | FAQ rich results no longer shown in Google Search | Review whether FAQPage schema still earns its maintenance cost |
| June 2026 | Search Console rich result report and Rich Results Test support removed | Remove FAQ rich result appearance from SEO dashboards |
| August 2026 | Search Console API support for FAQ rich result removed | Update automated reporting jobs and API dependencies |
The important distinction is that a rich result can retire while the underlying content format still remains useful. FAQ content can still help readers, sales teams, support teams, and AI systems understand the page. The retired part is Google's FAQ dropdown treatment in Search.
Should you keep or remove FAQPage schema?
Keep FAQPage schema only when it accurately describes visible FAQ content that is useful to readers and inexpensive to maintain. Remove it when the page has no visible FAQ, when the markup is stale, or when your team is maintaining it only because it once produced rich results.
| Situation | Recommendation | Reason |
|---|---|---|
| The page has visible FAQs that answer real objections | Keep the FAQ content; schema is optional | The user value still exists even without Google dropdowns |
| The FAQ answers are outdated or duplicated across many pages | Rewrite or consolidate | Stale Q&A blocks can reduce trust |
| The markup describes content users cannot see | Remove the schema | Structured data should match visible page content |
| Your dashboard tracks FAQ rich result impressions | Retire that KPI | The Search appearance is no longer available |
| The FAQ section helps conversions or support | Keep the section and measure page outcomes | Business value is not the same as rich result eligibility |
For most content teams, the best answer is not "delete all FAQ schema." It is "audit FAQ sections like normal content." If the answer helps a reader understand pricing, implementation, compliance, or comparison criteria, keep it. If it exists only because a keyword tool suggested FAQ snippets, cut it.
What to do instead of chasing retired rich results
Replace the old FAQ-rich-result playbook with a content-quality playbook. FAQ blocks should answer real reader questions, but they should not carry the whole article. Use the format that best solves the search intent: definitions, comparison tables, screenshots, code examples, checklists, or internal links.
| Old tactic | Better replacement | Why it is more durable |
|---|---|---|
| Add generic FAQs to every post | Add FAQs only where readers have real follow-up questions | Quality survives feature changes |
| Measure FAQ rich result appearances | Measure page clicks, assisted conversions, scroll depth, and CTA clicks | Business outcomes matter more than a retired SERP treatment |
| Use schema to make thin content look rich | Improve the article with examples, tables, and sources | Structured data cannot rescue shallow pages |
| Duplicate the same FAQ across many pages | Create page-specific answers tied to the main intent | Specific answers are more useful and more citeable |
This is the same lesson we cover in our schema markup guide: structured data is a support layer, not the content strategy. For GEO work, pair clear Q&A sections with answer-first writing, source links, and examples. Our GEO meaning guide explains that broader shift.
FAQPage JSON-LD example: when it is still acceptable
If a page still has visible FAQ content, FAQPage JSON-LD can still describe the content structure. The key rule is consistency: the marked-up question and answer should appear on the page, and the markup should not imply eligibility for a Google rich result that no longer exists.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Does FAQ schema still matter?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Use FAQPage only for visible Q&A that helps readers."
}
}
]
}Practical rule: keep schema when it describes real content; remove it when it exists only to chase a rich result that Google no longer shows.
What this means for GEO and AI search
FAQ rich result retirement does not make Q&A structure useless for GEO. AI systems still benefit from clear, self-contained answers. What changes is the reason for using the format: you are no longer writing FAQs to expand a Google result. You are writing them to answer intent clearly and make the page easier to understand.
For AI search, the stronger pattern is answer-first content supported by evidence. A well-written paragraph, comparison table, or checklist can be more useful than forcing every answer into a FAQ block. That also connects to query fan-out, where one user question can expand into multiple related subquestions.
FAQ about FAQ rich result retirement
Is FAQ schema dead?
No. FAQPage schema is not dead as a structured data vocabulary, but Google FAQ rich results are retired in Search. The markup no longer creates FAQ dropdowns in Google Search results.
Should I remove all FAQPage schema?
No. Remove schema that is stale, inaccurate, hidden from users, or maintained only for rich result eligibility. Keep visible FAQ content when it helps readers, and treat schema as optional support.
Will FAQPage schema help AI visibility?
It can help describe page structure, but it is not a special AI visibility trick. Clear answers, evidence, entity clarity, and helpful content matter more than adding schema to weak content.
What should replace FAQ rich result reporting?
Replace it with page-level reporting: organic clicks, impressions, conversions, CTA clicks, assisted pipeline, and content refresh impact. If a FAQ section helps users convert or self-qualify, it can still be valuable without a rich result.
The takeaway
Google FAQ rich results are retired, but the lesson is bigger than FAQPage schema. Durable SEO does not depend on a single Search display feature. Use structured data to describe useful content, not to compensate for weak content.
The strongest next step is an audit: keep useful visible FAQs, remove stale or hidden markup, update dashboards that still track FAQ rich results, and invest in content sections that solve the reader's real intent.