Google’s FAQ change is no longer just a narrower eligibility rule. Google’s FAQ structured data documentation now says that, as of May 7, 2026, FAQ rich results are no longer appearing in Google Search. Google also plans to remove the FAQ search appearance, rich result report, and Rich Results Test support in June 2026, then remove FAQ rich result support from the Search Console API in August 2026. SEO teams should stop treating FAQ markup as a SERP real-estate tactic and start treating FAQ content as a clear answer asset for users, search engines, and AI answer systems.
Last updated: 2026-05-09
45-second explainer: after FAQ rich results disappear, SEO teams should rebuild FAQ as visible, citable answer assets.Core idea: FAQ value moves from expandable SERP space to visible answers, trusted sources, and measurable citations.
Key Takeaways
FAQ rich results are in a deprecation phase. In 2023, Google limited FAQ rich results mostly to well-known authoritative government and health websites. In May 2026, Google’s documentation says FAQ rich results no longer appear in Search.
A missing FAQ rich result is not automatically a structured data bug. The markup may still parse, but it no longer produces the old expandable FAQ treatment in Google Search.
For most commercial sites, FAQ value should move toward user support, content clarity, internal linking, AI-citable answers, and decision support.
Keeping compliant FAQPage markup is acceptable when the FAQ is visible and useful, but it should no longer be a core SEO KPI.
The best response is to audit FAQ quality, remove repeated filler, and upgrade important questions into answer blocks, comparison tables, checklists, or full support pages.
What Changed With Google FAQ Rich Results?
Google’s FAQ rich result change happened in two stages. First, on August 8, 2023, Google announced that FAQ rich results from FAQPage structured data would only be shown for well-known, authoritative government and health websites. Second, Google’s FAQPage documentation was updated in May 2026 to say that FAQ rich results stopped appearing in Google Search on May 7, 2026.
That breaks an old SEO habit: adding FAQ schema no longer means a realistic chance of winning an expandable FAQ block in the search result. Google also says the related Search Console appearance, rich result report, Rich Results Test support, and Search Console API support are being removed on a staged timeline.
This does not mean FAQ content is useless. Buyers, users, and practitioners still ask questions before they trust a page. AI search systems also need clear, verifiable, self-contained answers. The change is about the reward model: FAQ is no longer a stable rich-result tactic. It is now a content quality, information architecture, and answer extraction task.
You can keep FAQPage schema when the page truly has visible FAQs and each question has one clear answer. For most commercial sites, the benefit is no longer a Google FAQ rich result. The benefit is consistency between structured data and visible content. If the FAQ is repeated, promotional, hidden, or not useful, remove or rewrite it.
Google’s FAQ documentation still describes FAQPage, Question, and Answer properties. It also repeats the core rules: FAQ content must be visible to users; FAQPage should not be used for advertising; pages with user-submitted multiple answers should use QAPage instead; repeated FAQ content should not be marked up everywhere across the site. These rules still matter because they are really saying one thing: your markup should not misrepresent the page.
Page situation
Recommendation
Why
Authoritative government or health site with visible official FAQs
This was the narrow retained eligibility group, but the 2026 deprecation note still matters
B2B SaaS, tool site, ecommerce, or publisher with strong visible FAQs
Keep selectively, but do not use FAQ rich results as a KPI
Accurate structured data is fine, but display value is gone
Repeated template FAQs across many pages
Remove markup and rewrite the content
Repetition weakens page focus and user value
Product pages stuffed with FAQ solely for SERP space
Stop expanding this pattern
The old incentive is gone; page clarity matters more
FAQ content only exists in JSON-LD
Fix or remove it
Google requires FAQ content to be visible on the page
How Should SEO Teams Audit FAQ Content Now?
SEO teams should first move FAQ out of the “rich result feature” bucket. Then run a site-level FAQ audit. The goal is not to delete every FAQ schema block. The goal is to decide which questions still help users, which should become full content sections, and which dashboards will break when Google removes FAQ reporting and API support.
Use this six-step process:
Export historical FAQ search appearance data from Search Console. Do not treat post-May 2026 declines as a ranking loss by default.
Check automated reports, Looker Studio dashboards, scripts, and API jobs. If they depend on FAQ rich result fields, replace those fields before August 2026.
Crawl FAQPage JSON-LD and sample the visible page content. The question and answer in markup should match what users can read.
Mark repeated FAQs. Generic questions like “How much does it cost?” or “How long does it take?” should become page-specific answers.
Upgrade high-value questions into body sections. A question like “Is FAQ schema still useful?” deserves a section with conditions, exceptions, actions, and sources.
Replace the KPI. Track section engagement, related query coverage, internal clicks, support ticket reduction, and AI-search citation accuracy. For page-level checks, connect this work to a live URL audit and the broader SEO content hub.
FAQ Audit Checklist
Check
Passing standard
Fix when you see
Visibility
Questions and answers are visible in HTML
Content only exists in JSON-LD
Uniqueness
The question is specific to the page
The same FAQ appears on dozens of pages
Answer quality
The answer gives a conclusion, condition, and next step
AI-search-friendly FAQ content is not a pile of short accordion answers. It is a clear answer module that explains a real question with context, evidence, examples, and a next step. For a GEO and LLM monitoring product such as Convertos.ai, the goal is to make answers easy to understand, verify, and quote accurately. This is the same pattern used in AI-citable content and definition block templates: put the answer in visible body text, not only in structured data.
Treat FAQ questions in three ways:
FAQ type
Better content format
Example
Definition question
H2 or H3 answer block
Turn “What is FAQPage schema?” into a definition and eligibility section
Decision question
Comparison or scoring table
Turn “Should we keep FAQ schema?” into a page-type decision table
Action question
Checklist or template
Turn “How do we audit FAQ content?” into a step-by-step checklist
This helps both readers and answer engines. Readers can scan the answer without opening a hidden accordion. AI systems are more likely to extract the answer with the condition and caveat still attached.
A useful answer template is:
Direct answer: answer the question in one sentence.
Condition: explain when the answer applies.
Evidence: cite official documentation, a test, or site data.
Next action: tell the reader what to do.
Exception: name the case where the answer does not apply.
Common Mistakes After The FAQ Change
The biggest risk after Google’s FAQ change is bad attribution. Teams may see disappearing reports, testing changes, or lower rich result visibility and assume their site was demoted. A safer approach is to separate a Google feature removal from actual site performance problems.
Mistake
Why it is wrong
Better check
“FAQ visibility is gone, so rankings dropped”
Google described the 2023 change as a search appearance change, not a ranking change
Compare average position, CTR, normal impressions, and landing page traffic
“Rich Results Test no longer supports it, so the code is broken”
Google plans to remove FAQ rich result test support
Use schema parsers for syntax and page audits for visibility
“No rich result means delete all FAQs”
FAQ content can still help users and answer extraction
Remove low-quality repeats, keep real questions
“More schema will restore the display”
Display depends on Google feature support and eligibility, not schema quantity
Improve answer quality, internal links, and topical coverage
“AI search will definitely read FAQ schema”
AI vendors do not share one universal guarantee for schema use
Put the answer in visible body text and support it with sources
What Each Team Should Do
This should be led by SEO, but it should not be handled only as an SEO plugin task. Content owns question quality. Technical SEO owns markup and templates. Data owns dashboard migration. If these teams do not coordinate, the site can end up with valid markup nobody reads and reports that keep tracking a retired feature.
Role
This week’s task
Done when
SEO lead
Update FAQ KPIs and monitoring language
FAQ rich result impressions are no longer a core goal
No hidden FAQ, wrong schema type, or repeated template abuse
Content lead
Merge repeated FAQs and upgrade important questions
Key questions become answer blocks, tables, or guide sections
Data team
Check GSC API and Looker Studio fields
Reports will not fail after August 2026 API removal
GEO / AI search lead
Build an AI prompt test set
The team can monitor brand answer inclusion and accuracy
FAQ
These FAQ questions are based on public search question patterns, Google’s own Feature availability and Troubleshooting sections, and recurring SEO community discussions about whether FAQ schema still works.
Are Google FAQ rich results completely gone?
Source signal: Google’s May 2026 FAQ documentation update and public related questions.
Google’s FAQ documentation says that, as of May 7, 2026, FAQ rich results are no longer appearing in Google Search. Google also lists a staged removal of related reports, testing support, and API support.
Should websites still write FAQ sections?
Source signal: SEO community discussions and related questions about whether FAQ schema still works.
Yes, when the questions are real and useful. The purpose should be helping users understand, compare, and act, not winning extra SERP space.
Source signal: Google’s 2023 announcement, Google FAQ troubleshooting guidance, and structured data related questions.
Accurate, visible, compliant structured data is not the issue. Google’s 2023 announcement said unused structured data did not need proactive removal, but hidden, repeated, promotional, or wrong-type markup should be fixed because it misrepresents the page.
Should B2B SaaS websites keep FAQ schema?
They can keep it selectively on high-quality visible FAQs, but it should not be treated as a growth tactic. Important questions usually deserve answer blocks, comparison tables, or workflow sections.
How should teams monitor FAQ performance after Search Console reports disappear?
Use normal search performance, related query coverage, FAQ section engagement, internal clicks, support ticket reduction, and AI-search prompt tests for answer inclusion and accuracy.
Source Statement
This article is based on Google Search Central’s FAQPage documentation, Google’s 2023 HowTo/FAQ rich result announcement, Google structured data guidance, and public SERP question signals. Google Search features and Search Console support can change; verify the latest official documentation and your own site data before making large template changes.
