The FAQ rich result—those expandable dropdowns that once made search listings visually dominant—is effectively dead for most websites. Google restricted the feature to government and health authority sites in August 2023. But the content format itself retains value through different mechanisms: topical depth signals, People Also Ask capture, AI Overview extraction, and machine readability for emerging search interfaces. The calculation has shifted from “will this show rich results” to “does this content serve users and search engines in ways that don’t depend on a deprecated feature.”
For the Site Owner Who Lost Rich Results
My FAQs used to expand in search results. Now they don’t show at all, even though Rich Results Test says my schema is valid. What happened, and is it worth keeping FAQ content on my site?
You’re experiencing the aftermath of Google’s August 2023 change, not a technical problem with your implementation. The Rich Results Test validates syntax—whether your code is correctly formatted—but validation no longer guarantees display. Google now reserves FAQ rich results almost exclusively for government agencies, healthcare institutions, and sites it considers authoritative sources on sensitive topics. Your schema isn’t broken. The feature simply isn’t available to you anymore.
What the Rich Results Test Actually Tells You Now
The test confirms your structured data is parseable. Nothing more. Think of it like a spell-checker approving a job application—correct spelling doesn’t mean you’ll get the interview. Google’s systems read your FAQ schema, understand what it contains, and then decide whether to display it based on criteria that have nothing to do with technical correctness.
This creates genuine confusion. You followed the documentation, implemented correctly, tested successfully, and got nothing. The disconnect isn’t a bug. Google simply stopped communicating that eligibility changed while the validation tool remained unchanged.
The Value That Remains
FAQ content still contributes to your site in ways that don’t depend on rich results.
Topical depth perception. Comprehensive FAQ sections signal that you’ve anticipated user questions and provided answers. This aligns with how Google evaluates content quality broadly—not through schema detection, but through coverage assessment. A page addressing twelve specific questions about a topic demonstrates deeper engagement than one addressing three.
People Also Ask capture. Google’s PAA boxes pull from content that directly answers common queries. Consider the difference:
A thin FAQ written for rich results: “What is our return policy? We have a great return policy. Contact us for details.”
A PAA-aligned FAQ: “How long do I have to return an item? You have 30 days from delivery for a full refund. Items must be unworn with tags attached. Exchanges are free; refunds process within 5-7 business days.”
The second version answers what users actually type into Google. It matches PAA phrasing (“How long do I have to…”) and provides specific, complete information. This format surfaces in PAA boxes regardless of schema—the content quality and question-answer alignment determine visibility, not the markup.
AI Overviews and answer extraction. Google’s AI-generated answers at the top of search results pull from content that directly addresses queries in clear, extractable formats. FAQ structures are particularly well-suited because they’re already in question-answer form—exactly what the AI needs to synthesize responses.
When someone searches “how long can I return something to [brand],” Google’s AI Overview may quote your FAQ directly if the answer is specific and well-formatted. This visibility mechanism operates entirely outside the rich results system. You won’t see it in Rich Results Test, but your FAQ content may appear in AI-generated snippets that reach users before they ever click a link.
The same logic applies to ChatGPT, Perplexity, and other AI search tools. These systems train on and retrieve from clearly structured Q&A content. FAQ formatting isn’t just for Google anymore—it’s becoming the standard readable format for any system trying to extract answers from web content.
The Honest Calculation
Keeping existing FAQ content costs nothing. Removing it gains nothing. The question is whether you should invest additional effort creating or maintaining FAQ sections.
If your FAQs genuinely address questions your customers ask, keep them. They serve users directly and contribute to content quality signals indirectly. If they were created purely to trigger rich results and don’t reflect actual user needs, their value was always thin—the rich result visibility just masked that.
The practitioners in current discussions offer a practical consensus: add FAQs where relevant to content quality, but don’t expect or optimize for rich result display. One SEO noting they “add FAQs to the bottom of pages for PAA and related searches but not FAQ schema anymore” reflects this adjusted strategy—the content matters, the markup is now optional.
Sources:
- FAQ rich result deprecation timeline: Google Search Central documentation updates, August 2023
- Rich Results Test behavior: Google Search Central (developers.google.com/search/docs/appearance/structured-data)
- AI Overview content extraction patterns: Google Search Generative Experience documentation
- Practitioner perspectives: r/SEO community discussion, December 2025
For the SEO Practitioner Updating Client Recommendations
Clients keep asking whether they should still implement FAQ schema. I need a defensible position based on how things actually work now, not outdated best practices.
The short answer you can give clients: FAQ content yes, FAQ schema optional, FAQ rich results no (unless they’re a government or health authority). But the reasoning behind that answer matters for your credibility, so here’s the fuller picture.
What Changed and Why It Matters for Recommendations
Google’s August 2023 update didn’t eliminate FAQ schema from the specification—it restricted which sites qualify for visual display. The markup remains valid, Google still parses it, but the reward mechanism disappeared for 99% of sites. This creates an awkward situation where technically correct advice (“implement FAQ schema per Google’s documentation”) produces no visible benefit.
The moderator position from current practitioner discussions is worth internalizing: “Google has never prioritized schema” and “schema doesn’t have a positive impact” on rankings. This isn’t nihilism—it’s precision. Structured data enables features; it doesn’t boost rankings. When the feature is unavailable, the ranking-neutral nature of schema becomes more apparent.
The Authority Threshold You Can’t Shortcut
FAQ rich results now function as an authority signal rather than a content signal. Only sites Google already trusts for sensitive information receive the visual treatment. This matters for client conversations because it reframes expectations.
A new business site won’t display FAQ rich results regardless of implementation quality. An established site in a non-sensitive category won’t either. The feature has become a marker of existing trust, not a tool for building it. Clients expecting “we add FAQs and get those expandable listings” need this expectation corrected before they measure your work against impossible outcomes.
Building Your Recommendation Framework
For clients with genuine FAQ content needs: Implement FAQs as content. The format serves users who have questions. Structure them clearly with actual questions as headers. Schema is low-effort to add, so include it, but set expectations that rich results won’t appear. Value comes from content quality contribution, PAA capture potential, and AI system readability.
For clients creating FAQs purely for SEO: This motivation no longer justifies the effort. FAQs that don’t reflect real user questions were always thin—rich results just provided visible ROI that masked the content’s actual value. Without that visibility, the gap between effort and outcome becomes harder to justify. Redirect that effort toward content that serves users directly.
For enterprise or authority-track clients: If the client operates in health, government, or finance sectors and has legitimate authority, FAQ rich results remain possible. For these clients, schema implementation matters more because the feature is available. But the content quality bar is also higher—Google isn’t displaying FAQ rich results for sites merely implementing correct markup.
Handling Client Pushback and Budget Conversations
“We used to get great results from FAQs. Why should we stop?” You shouldn’t stop—you should recalibrate expectations. The content value remains. What’s gone is the visual SERP real estate. If their FAQs genuinely answer customer questions, the work was never wasted. If the FAQs were thin content created purely to trigger dropdowns, that approach no longer produces visible return.
“Our competitor still shows FAQ rich results.” Check the competitor’s domain. If they’re a government agency, healthcare institution, or established authority in a sensitive category, they qualify for a feature your client doesn’t. This isn’t about implementation quality—it’s about domain authority thresholds that can’t be shortcut through better schema.
“Should we reallocate FAQ budget to something else?” Depends on what the budget was funding. Content creation for genuine FAQs: keep it, it serves users and contributes to topical depth. Schema implementation and rich result optimization specifically: reallocate. That ROI equation broke.
A practical reallocation: shift FAQ-specific schema optimization time toward ensuring FAQ content aligns with actual PAA queries in your space. Research what questions appear in People Also Ask for your target terms, then structure FAQ content to match those phrasings exactly. The visibility mechanism changed, but visibility itself remains achievable through different channels.
The Implementation ROI Conversation
Clients want to know if FAQ work is worth the cost. Here’s how to frame it:
Creating quality FAQ content that addresses genuine customer questions: worth it. This content serves users, contributes to topical depth, and positions pages for both PAA capture and AI Overview extraction. The ROI is indirect but real.
Adding FAQ schema to existing FAQ content: minimal additional effort, so yes, include it. The downside is negligible. Potential upside exists if Google’s policies change or if other systems use the structured data.
Creating FAQ content and schema purely to chase rich results: not worth it. The mechanism is broken for most sites, and content created for a feature rather than for users rarely performs well when that feature disappears.
Defending Your Position
When clients or stakeholders push back with “but we used to get those expandable results,” acknowledge that reality changed. Point to Google’s documentation updates from August 2023. Reference that other practitioners have observed the same pattern. The Rich Results Test validation without display is a known phenomenon, not a mystery to solve.
If someone insists schema “must help somehow,” you can accurately say: Google parses it, which aids their understanding of content structure, but understanding doesn’t mean preferential ranking. The evidence for schema as ranking factor has never materialized despite years of claims. What schema provides is feature eligibility—and for FAQs, that eligibility is now severely restricted.
Your recommendation should be defensible because it’s grounded in observable behavior and clear mechanism understanding, not speculation about what Google might secretly value.
Sources:
- FAQ rich result eligibility restrictions: Google Search Central documentation, August 2023 update
- Schema ranking factor analysis: Multiple SEO industry studies showing no ranking correlation
- Current practitioner consensus: r/SEO community discussion, December 2025
- Structured data parsing behavior: Google Search Central technical documentation
- AI Overview extraction patterns: Google Search Generative Experience observations
The Bottom Line
FAQ content and FAQ rich results are now separate considerations. The content format retains value for topical depth, user service, PAA capture, and AI answer extraction. The rich result feature is restricted to high-authority sites in sensitive categories—effectively unavailable to most publishers.
The strategic adjustment is straightforward: create FAQ content when it genuinely serves your users and demonstrates topic coverage. Structure questions to match how people actually search—PAA research tells you exactly what phrasings to use. Include schema if it’s low-effort to implement. But don’t measure success by rich result display—that metric is broken for most sites and unlikely to return.
For practitioners advising clients: the conversation has shifted from “implement FAQs for rich results” to “create FAQ content for content quality, PAA visibility, and AI extractability.” Clients who understood FAQs as a visibility tactic need recalibration. Those who created FAQs because they genuinely had questions to answer can continue without changing approach—they were doing it right all along.
The sites still winning with FAQ content in 2025 aren’t the ones with perfect schema. They’re the ones whose FAQs answer real questions in specific, useful ways. The format works. The feature doesn’t. Build for the format.