FAQ rich results are mostly gone

If you've been relying on FAQ rich results to boost your search visibility, it's time to reassess your strategy. Google significantly limited FAQ rich results in 2023, restricting them almost exclusively to authoritative government and health websites. For the vast majority of us building platforms—whether e-commerce, SaaS, or community sites—the days of seeing our FAQPage markup displayed as fancy accordions in search results are behind us.

That doesn't mean FAQ content is worthless. It still helps your users. But the SEO motivation for adding structured data just to trigger a rich result has evaporated. In this post, I'll walk you through what changed, why it matters, and how to approach FAQ content pragmatically.

When and why Google restricted FAQ rich results

Back in 2020, Google introduced FAQ rich results as a way to highlight commonly asked questions and their answers in search results. For three years, if you marked up your FAQ section with proper FAQPage schema, you had a decent chance of seeing it render as an attractive feature in search results. This drove a lot of adoption.

By late 2022 and into 2023, Google realized something: the feature was being abused. Webmasters and SEO teams were stuffing pages with artificially created FAQ content—questions that nobody actually asked—purely to trigger the rich result. Low-effort FAQ pages flooded the index. The quality tanked. Users clicked on these results expecting genuine answers and found generic, keyword-stuffed content instead.

Google's response was decisive. They rolled out a policy update stating that FAQ rich results would only be shown for sites that Google considers highly authoritative in specific verticals: primarily government (.gov), health, and select other official sources. For everyone else, the FAQPage schema is now essentially invisible in search results.

This is frustrating if you were counting on that traffic, but it's actually good for the web. It removes the incentive to add fake FAQs.

Now shown mainly for authoritative gov and health sites

Today, FAQ rich results appear almost exclusively in search results for government and health websites. If you run a .gov site answering questions about tax deductions, or you're a health authority explaining vaccination side effects, Google will likely display your FAQPage structured data as a rich result. For everything else—your SaaS pricing questions, your e-commerce product FAQs, your travel site's common queries—forget about it.

I tested this extensively across our platforms. We run a ride-hailing backend where drivers frequently ask the same questions about payouts, ratings, and deactivation policies. We have proper FAQPage markup. It doesn't show. We run a travel booking platform with legitimate customer FAQs about cancellation policies and refunds. Same story: no rich result.

The eligibility criteria are opaque. Google hasn't published a definitive list of which sites qualify. But the pattern is clear: unless you're a recognized government entity or a major health organization, you won't see your FAQ markup rendered as a rich result. Your schema is valid, it won't cause errors, but it won't give you the visual boost you might have hoped for.

Here's what this means operationally: if you're deciding whether to implement FAQPage schema on a new feature, don't do it for the rich result. Do it only if it genuinely helps your structured data strategy, accessibility, or internal data pipelines.

FAQ content still helps users

Just because the rich result is gone doesn't mean FAQ content itself is useless. In fact, well-written FAQs remain one of the most valuable sections of any customer-facing platform.

On our e-commerce site, our FAQ page gets more organic traffic than our about page. Users don't want marketing fluff; they want answers to concrete questions: "What's your return window?", "Do you ship internationally?", "Can I track my order?" FAQ pages address real user intent. They reduce support tickets. They improve user trust and conversion rates.

The same applies to our CRM platform. New customers want to know how to import data, how permissions work, how to set up webhooks. An FAQ page targeting these questions ranks well for long-tail keywords and gives prospects confidence before they sign up.

From a UX perspective, FAQs are still powerful. They're scannable, they structure information clearly, and they address objections at the moment when users are evaluating your product or service. None of that changes because Google stopped displaying FAQ rich results.

What changes is your motivation and implementation strategy. You're no longer building FAQs to trigger a schema-based rich result. You're building them because they're genuinely useful to your audience and they help with SEO through better content quality and keyword coverage.

Keep FAQPage markup only if it is accurate

If you already have FAQPage schema in place, I recommend keeping it—but only if the FAQs themselves are accurate and authentic. Here's why.

First, there's no downside to valid schema markup. Google won't penalize you for having it. It won't cause indexing issues. Invalid or misleading markup is a different story, but accurate FAQPage schema is harmless.

Second, things change. Google's policies evolve. It's possible that FAQ rich results are re-enabled for certain domains in the future, or that the criteria expand. If your markup is correct and your FAQs are genuine, you'll benefit immediately when that happens. If you've already stripped out your schema, you'll have to rebuild it.

Third, structured data has value beyond rich results. Search engines use schema to better understand your content. Accurate FAQPage markup helps Google parse your FAQ section, which can improve how your content appears in featured snippets, People Also Ask boxes, and other SERP features. The rich result was just one application.

Here's a real example. On our NestJS-based travel booking API, we document common integration questions in FAQPage format:

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "@id": "#q1",
      "name": "What is the rate limit for the booking endpoint?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The booking endpoint allows 100 requests per minute per API key. If you exceed this, you'll receive a 429 Too Many Requests response."
      }
    },
    {
      "@type": "Question",
      "@id": "#q2",
      "name": "Can I refund a booking after it's been confirmed?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, refunds are available up to 24 hours before the scheduled departure time, minus a 10% processing fee."
      }
    }
  ]
}
</script>

This markup is accurate. It reflects actual API behavior and business rules. Even though it won't render as a rich result, it's still there, it's correct, and it helps search engines understand our documentation.

Do not add FAQs just for rich results

This is the critical lesson. Do not, under any circumstances, add FAQ content or FAQPage markup purely in the hope of triggering a rich result. This was the exact behavior that caused Google to restrict the feature in the first place.

I've audited dozens of websites where teams added 15–20 FAQ items, clearly written by marketers trying to cover keyword variations rather than answering genuine customer questions. "What is X?", "Why choose X?", "How much does X cost?", "Where can I buy X?" All auto-generated, all targeting slightly different search queries, all adding no value to the user.

Users hate this. It wastes their time. They load your FAQ page expecting answers to their real problems and find a keyword-stuffed mess instead. Support tickets increase because people still can't find what they need.

Google detects this. Spam FAQ pages get deprioritized in rankings. Your site signals become weaker. You damage your domain's trustworthiness for no benefit.

The right approach: add FAQ sections only when you have genuine, frequently asked questions. How do you know if a question is frequent? Check your support ticket queue. Monitor your analytics to see which pages get the most traffic with unclear intent. Ask your customer success team. Read product review sites to see what complaints and questions come up repeatedly.

On our SaaS platform, we built our FAQ section by extracting the top 20 questions from our help desk system and from user interviews. Each answer is backed by actual customer confusion or a real use case. That FAQ page ranks well, gets clicked from search results, and reduces support load. No artificial padding. No schema gaming.

Common mistakes

Mistake 1: Keeping old FAQPage markup from when rich results worked and forgetting about it. Schema decay is real. Over time, your FAQs become outdated. Their answers no longer match your current product or policy. Even though the rich result won't display, search engines still use the markup to understand your content. Stale, inaccurate schema is worse than no schema. Audit your FAQPage markup quarterly and update answers when your product changes.

Mistake 2: Adding FAQs to every page. Some teams add a small FAQ section to their homepage, product pages, pricing page, blog posts—everywhere. This dilutes the value of your actual FAQ resource page. Consolidate genuine FAQs into a dedicated FAQ section or document. Link to it from relevant pages instead of duplicating content.

Mistake 3: Ignoring FAQ content because rich results are gone. The opposite extreme: teams completely abandon FAQ pages thinking they're now useless for SEO. They're not. A well-maintained FAQ page is still a top landing page on most websites, still ranks for long-tail keywords, and still converts users. Don't throw the baby out with the bathwater.

Mistake 4: Not validating your schema. Use Google's Rich Results Test or Schema.org validator to check your FAQPage markup. I've seen teams with malformed JSON-LD that breaks the entire schema block. Invalid markup helps nobody.

Key takeaways

FAQ rich results are now restricted to authoritative government and health websites. For most businesses, the rich result won't appear in search results.
Keep FAQPage structured data if it's accurate and your FAQs are genuine. Valid schema doesn't hurt and policies may change.
Continue writing FAQ content because it serves users, not because of rich results. Address real customer questions, not keyword variations.
Do not add artificial FAQs purely to trigger schema markup. This was the behavior Google cracked down on, and it damages your site's credibility.
Audit your existing FAQ pages and schema regularly. Remove outdated questions, update answers when your product changes, and consolidate duplicate content.
Expect FAQ pages to rank organically for long-tail, high-intent queries. This traffic is valuable even without the rich result visual.

FAQ rich results are mostly gone: lessons from production