FAQ Schema 2026: Google Retired It, Here's What Still Works

Featured Snippet Optimized Answer

Google retired FAQ rich results in Google Search on May 7, 2026. Search Console reporting and the Rich Results Test lose FAQ support in June 2026, and the API loses support in August 2026. FAQPage schema itself is not deprecated: it causes no errors or penalties, and other systems, including Bing and several AI answer engines, still read it.

Introduction

If you searched for this because your FAQ dropdowns vanished from Google Search, you are not imagining it. Google confirmed the change directly on its developer documentation: FAQ rich results stopped appearing in Search results as of May 7, 2026.

This is not the same event as the 2023 restriction, which limited FAQ rich results to government and health sites. That was a narrowing. This is a full removal, and it applies to every site, including the government and health sites that kept the feature after 2023.

The natural next question is whether FAQPage schema is now pointless. It is not, but the reasons to keep it have changed. This guide covers exactly what happened, what still reads FAQ markup, how to add it correctly without a CMS plugin, and what to build instead if your only goal was SERP real estate.

What Actually Changed in May 2026
Why Google Killed FAQ Rich Results
Is FAQPage Schema Dead, or Just the Display Feature?
What Still Reads FAQ Schema in 2026
Should You Remove FAQ Schema From Your Site?
How to Add FAQ Schema Without a Plugin
Common Mistakes to Avoid
Best Practices Going Forward
What to Build Instead of Chasing Rich Results
Frequently Asked Questions
Conclusion

What Actually Changed in May 2026

Google's own structured data documentation now carries a deprecation notice. The timeline runs in three stages:

Date	What happens
May 7, 2026	FAQ rich results stop appearing in Google Search for all sites
June 2026	The FAQ rich result report, the FAQ search appearance filter, and FAQ support in the Rich Results Test are all removed
August 2026	Search Console API support for FAQ rich results is removed

This is a full sunset, not a partial rollback. Before May 2026, the only sites still eligible for FAQ dropdowns were well-known government and health domains, a restriction Google put in place back in August 2023. The May 2026 change removes the feature for those sites too, so there is no longer any tier of site that gets the visual treatment.

Notice what Google did not say. There is no instruction to remove the markup, no warning about manual actions, and no suggestion that existing FAQPage schema will cause problems. The change is scoped narrowly to the visual feature and the tools used to test and report on it.

Why Google Killed FAQ Rich Results

The root cause goes back to August 2023. Google introduced the first restriction after widespread misuse of FAQ schema purely to expand SERP real estate. Sites added FAQ markup to pages with no genuine question-and-answer content, purely to win extra vertical space and push competitors down the page.

That first restriction narrowed eligibility to authoritative government and health sites. It did not fully solve the underlying incentive problem, since any surviving rich result format invites the same real-estate chasing behavior. The May 2026 change removes the incentive completely by removing the display feature itself.

This pattern is not unique to FAQ schema. Google has previously scaled back How-To rich results in a similar way, restricting the display to desktop only after seeing similar abuse patterns. The lesson for site owners: a rich result tied to a schema type is a Google product decision, not a permanent feature of the schema standard.

Is FAQPage Schema Dead, or Just the Display Feature?

This distinction matters more than most 2026 commentary gives it credit for. Schema markup and rich results are two separate things.

Schema markup is a machine-readable description of what a piece of content is. FAQPage schema tells any system reading your page's code that a specific block of text is a question, and a specific other block is its answer.

Rich results are the visual treatment a search engine chooses to apply based on that markup, at its own discretion, with no guarantee.

Google retired the rich result. It did not deprecate the schema type on schema.org, and it has not said FAQPage markup will trigger errors, warnings, or ranking penalties. If you leave existing FAQPage schema on your site, nothing breaks. Google simply stops using it for the one purpose it used to serve.

What Still Reads FAQ Schema in 2026

Google is the largest consumer of structured data, but it is not the only one. As of mid-2026, the following systems continue to parse FAQPage markup:

Bing and Microsoft Copilot still use FAQ schema for their own search features and have not announced any sunset.
DuckDuckGo continues to process structured data from indexed pages without a stated FAQ deprecation.
AI answer engines, including ChatGPT Search, Perplexity, and Claude's web search features, parse structured data as part of how they select and cite sources. Several SEO analysts have reported that pages with clean FAQ markup show a higher rate of citation in AI-generated answers, though this should be read as an observed pattern from third-party analysis rather than a confirmed ranking signal from any single AI provider.
Google's own AI Overviews are a separate surface from classic Search rich results. Google has not published guidance tying FAQ schema to AI Overview inclusion, and pages without any FAQ markup are routinely cited in AI Overviews. Treat this as unconfirmed rather than assume a direct benefit.

The practical takeaway: FAQ schema shifts from a Google Search ranking and display tactic to a general-purpose machine-readability signal. It is less about winning a dropdown in Google and more about making your Q&A content easy for any system, human or automated, to parse correctly.

Should You Remove FAQ Schema From Your Site?

Not automatically. Use this decision framework instead of a blanket policy.

Keep your visible FAQ content regardless of schema. A well-written FAQ section helps human readers, supports internal linking, and can still earn a citation in AI-generated answers. Removing the content itself because the rich result disappeared throws away the part that mattered most.

Keep FAQPage schema on pages where it's still accurate and low-maintenance. If the markup matches genuine, unique questions and answers on the page, there is little cost to leaving it in place. It will not help you win Google SERP space anymore, but it costs nothing to maintain and may still help Bing, DuckDuckGo, and AI crawlers.

Remove FAQPage schema where it was only added to chase rich results. If a product page has three generic questions bolted on purely for the old dropdown feature, and the content does not serve the reader, simplify. Maintaining schema that adds no value is wasted engineering time.

Export your Search Console FAQ data before June 2026. Once Google removes the FAQ report and search appearance filter, you lose the ability to see historical performance for this feature inside Search Console. If your team relies on that data for reporting, pull it now.

Stop reporting FAQ rich result metrics as a KPI. Any dashboard or agency report that still tracks "FAQ rich result impressions" as a success metric needs to be retired alongside the feature itself.

How to Add FAQ Schema Without a Plugin

If you have decided FAQ schema still earns its place on a page, here is how to implement it directly in JSON-LD, without relying on a CMS plugin.

Step 1: Identify genuine Q&A content

Only mark up real questions with real, substantive answers already visible on the page. Do not write questions solely to wrap them in schema.

Step 2: Write the JSON-LD block

Place this inside a <script type="application/ld+json"> tag in your page's <head> or before the closing </body> tag.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do I need FAQ schema in 2026?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Not for Google rich results, since Google retired that display feature in May 2026. You may still want it for Bing, DuckDuckGo, and AI answer engines that continue to read FAQPage markup."
      }
    },
    {
      "@type": "Question",
      "name": "Will FAQ schema hurt my Google rankings?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Google has said FAQ markup is not a ranking factor, and leaving valid FAQPage schema on a page does not trigger errors or manual actions."
      }
    }
  ]
}

Step 3: Match the schema exactly to visible content

Every question and answer in the JSON-LD must correspond to text a visitor can actually read on the page. Marking up hidden or fabricated content violates Google's general structured data guidelines and risks a manual action on other rich result types you may still rely on.

Step 4: Validate the markup

Until June 2026, Google's Rich Results Test still checks FAQ syntax, though it will not show a rich result preview. After that, use the Schema.org Validator or Google's general Rich Results Test for any other schema types on the same page.

Step 5: Consider a generator over hand-coding

For sites publishing many pages with question-and-answer sections, hand-writing JSON-LD does not scale well. A schema markup generator lets you paste your questions and answers and receive validated JSON-LD output, which reduces the chance of a stray comma or bracket breaking the entire block.

Common Mistakes to Avoid

Marking up hidden accordion content that never displays as visible text. Google's structured data guidelines require the marked-up content to be visible to users, not just present in the page's source.
Writing generic questions with no real informational value, purely to fill out schema. This was the exact behavior that triggered both the 2023 restriction and the 2026 removal.
Duplicating the same FAQ block across many unrelated pages. This looks like manipulation to search engines and adds no unique value per page.
Treating the Rich Results Test's green checkmark as a guarantee of display. Google has repeatedly said passing validation does not guarantee any rich result will appear, and this is doubly true now that the FAQ rich result itself is retired.
Continuing to report FAQ rich result impressions as a live KPI after the June 2026 reporting removal, using stale cached data instead of acknowledging the metric no longer updates.

Best Practices Going Forward

Write FAQ content for the reader first. If a question would not naturally appear in a knowledgeable person's explanation of the topic, it likely does not belong in your FAQ section.
Use semantic HTML alongside schema. Native <details> and <summary> elements or clear heading structure help both human readers and machine parsers, independent of any JSON-LD you add.
Reserve FAQPage schema for pages where the FAQ is a primary purpose of the page, not a bolted-on afterthought.
Keep investing in the schema types that still earn rich results in Google Search, including Product, Review, Event, and Article structured data, none of which were affected by this change.
Monitor Bing Webmaster Tools separately if a meaningful share of your traffic comes from Bing, since its rich result reporting is unaffected by Google's changes.

What to Build Instead of Chasing Rich Results

If your FAQ schema strategy existed purely to win Google SERP space, redirect that effort toward formats Google still rewards directly:

Article schema for blog posts and guides, which supports author, publish date, and headline display in Search.
Breadcrumb schema, which still generates the breadcrumb trail display beneath a result's URL.
Product and Review schema, if you sell anything, which remain among the most visually prominent rich results available.
Clear on-page heading structure and concise, direct answers near the top of the page, which is what tends to earn citations in AI Overviews and other AI-generated answers regardless of schema.

Frequently Asked Questions

Is FAQ schema dead in 2026? The FAQ rich result display is retired in Google Search as of May 7, 2026. The FAQPage schema type itself is not deprecated and remains valid for other search engines and AI systems.

Should I remove all FAQPage schema from my site? Not automatically. Remove it where it was only added to chase rich results and adds no value. Keep it where it accurately describes genuine Q&A content, since it costs little to maintain.

Will removing FAQ schema hurt my SEO? No. Since the rich result is gone regardless of markup, removing accurate but now-unrewarded schema has no negative SEO impact.

Does Bing still support FAQ rich results? Yes, as of mid-2026, Bing and Microsoft Copilot continue to process FAQPage schema without an announced sunset.

Does FAQ schema help with Google AI Overviews? This is unconfirmed. Google has not published guidance linking FAQPage schema to AI Overview inclusion, and pages without any FAQ schema are regularly cited. Treat any claimed benefit as an observed pattern, not a documented ranking signal.

What happens to my Search Console FAQ data? The FAQ rich result report and search appearance filter are scheduled for removal in June 2026. Export any historical data you need before that date.

When does Search Console API support for FAQ rich results end? August 2026, according to Google's developer documentation.

Can I still test FAQ schema syntax after the change? Until June 2026, Google's Rich Results Test still validates FAQ syntax. After that, use the general Schema.org Validator.

Why did Google remove FAQ rich results in the first place? Google cited widespread misuse of the format purely to expand search result real estate, without providing corresponding value to searchers.

Is this the same as the 2023 FAQ restriction? No. The 2023 change limited FAQ rich results to government and health sites. The 2026 change removes the feature entirely, including for those previously eligible sites.

Do I need a plugin to add FAQ schema? No. FAQ schema is a JSON-LD script block you can add directly to your page's HTML, or generate using a schema markup tool, without any CMS plugin.

Will adding FAQ schema to a new page in 2026 do anything for my rankings? Google has stated FAQ markup is not a ranking factor. Adding it will not move your rankings up or down, since there is no rich result left to earn.

Conclusion

Google's May 2026 retirement of FAQ rich results closes a chapter that started with the August 2023 restriction. The visual feature is gone for every site, the reporting tools are being removed on a set timeline, and there is no indication this reverses.

None of that means FAQPage schema itself is obsolete. It remains valid, error-free, and still useful to Bing, DuckDuckGo, and a growing set of AI answer engines that parse structured data independently of Google's rich result decisions. The shift is in purpose: from a Google SERP tactic to a general machine-readability signal.

If you are deciding what to do with existing markup, keep the content that serves your readers, keep the schema where it is accurate and low-maintenance, and stop treating FAQ rich results as a metric worth chasing in 2026. If you need to generate or validate FAQPage, Article, or Breadcrumb JSON-LD without hand-coding it, NitroSERP's Schema Markup Generator produces validated output for all three types in your browser, with no signup required.

Internal Linking Suggestions

Schema Markup Generator tool page
Breadcrumb Schema: A Practical Guide
"Article Schema for Blog Posts: Complete Guide" (new post idea)
Open Graph Tags: What Still Matters in 2026
Title Tag Length: What Actually Gets Truncated in 2026
XML Sitemap Best Practices for 2026
How to Use Hreflang Tags Correctly
UTM Parameters Explained
How to Optimize Meta Tags for SEO in 2026
Canonical URL Generator tool page

External References

Schema (JSON-LD)

Article Schema

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "FAQ Schema in 2026: Why Google Retired It (and What Still Works)",
  "author": {
    "@type": "Organization",
    "name": "NitroSERP Editorial Team"
  },
  "publisher": {
    "@type": "Organization",
    "name": "NitroSERP"
  },
  "datePublished": "2026-07-24",
  "mainEntityOfPage": "https://www.nitroserp.com/blog/faq-schema-2026-what-still-works"
}

FAQ Schema (example only, shown for Bing/AI-grounding use, not Google rich results)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Is FAQ schema dead in 2026?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The FAQ rich result display is retired in Google Search as of May 7, 2026. The schema type itself is not deprecated and remains valid for other search engines and AI systems."
      }
    }
  ]
}

Breadcrumb Schema (example)

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Blog",
      "item": "https://www.nitroserp.com/blog"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "FAQ Schema in 2026",
      "item": "https://www.nitroserp.com/blog/faq-schema-2026-what-still-works"
    }
  ]
}