Google Retired FAQ Rich Results: What to Do With FAQ Schema

If your SEO checklist still says "add FAQ schema," it's out of date. As of May 7, 2026, Google no longer shows FAQ rich results for any website. In June, it deleted the documentation for the feature too.

We're not pointing fingers. Until October 6, 2026, our own SEO Checker still suggested FAQPage for pages with no structured data. We've fixed that, along with a related bug we found in the process, and we'll walk through both below. First, the part that matters for your site.

What Is FAQ Schema?

FAQ schema is structured data that describes a page's question-and-answer section in a format machines can read. Its technical name is FAQPage, from the shared schema.org vocabulary. Most sites add it as a small JSON-LD block in the page code:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How long does shipping take?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Orders ship within 2 business days."
    }
  }]
}

For years, Google rewarded this markup generously. Your questions appeared as expandable rows right under your search result. The result took up more of the page and pushed competitors further down. No wonder it landed on nearly every SEO checklist.

How Google Phased Out FAQ Rich Results

The reward didn't disappear overnight. Google closed the door step by step over nearly three years:

So for a typical business site, the FAQ rich result has been out of reach since 2023. The 2026 change simply removed the last exception. The dates come from Google's 2023 announcement and its Search Central changelog.

Should You Remove FAQ Schema?

No need to rush. Google answered this directly when it first restricted the feature in 2023:

Nothing in the 2026 changelog says otherwise. Our practical take:

• Leave existing markup alone until you're editing those pages anyway. Ripping it out is not worth a dedicated sprint.
• Stop adding it to new pages in the hope of a rich result. The effort no longer pays off.
• Keep the FAQ section itself if it answers real questions. Good answers still help your readers; only the search appearance changed.

Does AI Search Need FAQ Schema?

A common objection since May goes like this: "Google may not show it, but AI reads it." Google has been clear on this, at least for its own AI features. Its AI optimization guide says: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add."

The same guide still recommends structured data as part of your SEO, because that's how pages become eligible for rich results. In other words, schema is useful, but it's not a secret key to AI answers. We cover what actually gets a page cited in our guide to Google AI Overviews.

"How to Add FAQ Schema" Is Now the Wrong Question

People still search for how to add FAQ schema. The better question is which structured data still pays off in Google Search. The search gallery lists plenty. Pick the type that matches your site:

That QAPage line matters more than it looks. FAQ and Q&A sound alike, but they're different results, and the difference tripped up our own tool. More on that below.

What We Found Across 427 Sites

Before writing this, we checked our own data. We counted every site run through our SEO Checker between September 6 and October 6, 2026. We kept only the latest analysis per site and only pages that loaded.

Two caveats. The sample is made up of sites people chose to test with our tool, so it isn't a census of the web. And most people enter their homepage, while FAQ markup usually lives on inner pages. The real share is probably a bit higher.

Two out of three sites we analyzed had no structured data at all. Filling that gap is worth far more than mourning FAQ.

What We Changed in Our Own Tools

A tool that audits your site has to follow Google's current rules, not last year's. In early October, we reviewed every one of our tools that touches structured data. Here's what changed:

• Our SEO Checker no longer recommends FAQPage. When a page had no structured data, it used to list FAQPage among the suggested types. As of October 6, 2026, it suggests Article, Product, Breadcrumb, and Organization instead. The "why it matters" text now uses examples that still work: ratings, prices, and breadcrumbs.
• We found and fixed a bug. Every question inside FAQPage is technically a Question node. Our checker treated those questions as standalone Q&A content and labeled the page eligible for the Q&A rich result. That was wrong: Q&A requires QAPage. Fixed on October 7, 2026.
• Our SERP Simulator & Meta Optimizer already knew. When it sees FAQ markup, its preview notes that the result was retired in May 2026.
• Our WordPress plugin, Turksem GEO SEO, will ship the same fixes in its next release.

We also made a call about our own blog. We keep marking up the FAQ sections of our articles as FAQPage, including the one below. The markup is generated from the questions you can see on the page, and per Google it does no harm. What we no longer do is promise anyone a rich result from it.

Frequently Asked Questions

Is FAQ Schema Dead?

As a Google rich result, yes. Google stopped showing FAQ rich results on May 7, 2026. The markup itself is still valid schema.org and does no harm on your pages.

Does FAQ Schema Hurt Rankings?

No. Google has said that structured data it doesn't use causes no problems for Search. It also stated that the 2023 restriction should not be considered a ranking change.

Do Government and Health Sites Still Get FAQ Rich Results?

No. They were the last exception after 2023, and the May 7, 2026, change removed the feature for everyone.

What Is the Difference Between FAQPage and QAPage?

On an FAQ page, the site owner writes both the questions and the answers. On a Q&A page, one question gets answers from many users, as on a forum. Google still shows Q&A rich results for pages marked up with QAPage.

Do AI Overviews Need FAQ Schema?

No. Google says structured data isn't required for its generative AI features and that there's no special schema.org markup to add.