FAQ Schema Markup in 2026: Why Google Dropped the Rich Result (And Whether to Still Add It)

If you added FAQ schema markup to a page hoping for the expandable FAQ dropdown in Google Search, stop waiting on it: Google deprecated FAQ rich results in Search entirely on May 7, 2026. The markup itself isn't broken and won't hurt you if you leave it in place, but it no longer produces a visible result for any site, including the government and health properties that were the last ones still eligible.

What Actually Changed, and When

FAQ rich results didn't disappear overnight. Google first cut back their visibility in April 2023, then made it official in August 2023: FAQ rich results would only appear for "well-known, authoritative government and health websites," with everyone else losing the dropdown entirely. That policy held for almost three years.

The May 2026 change closed the loop. Google added a deprecation notice to its FAQPage structured data documentation confirming that FAQ rich results stopped appearing in Search on May 7, 2026, for every site, government and health included. The rollout has three dates worth knowing if you rely on Search Console for monitoring:

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

Google didn't publish a blog post explaining the reasoning and hasn't said whether the removal is connected to abuse, to AI Overview changing how Google surfaces question-and-answer content, or something else. The documentation update is the only official word so far.

Do You Need to Remove FAQ Schema?

No. Google has been explicit, both in 2023 and again with this deprecation, that structured data your page isn't currently using for a rich result doesn't cause a penalty or a technical error. FAQPage is still a valid type in the schema.org vocabulary, and leaving old FAQ JSON-LD in place won't get flagged the way a broken required field would.

The practical question isn't "will this hurt me" — it's "is this worth the maintenance." Before May 2026, FAQ schema was a low-cost bet: a few minutes of markup for a shot at a bigger, more clickable search listing. That bet no longer pays off for the vast majority of sites, since the dropdown it was betting on is gone — see the AI Overview SEO Audit Checklist if you want the fuller list of what still moves the needle.

Does FAQ Schema Still Help With AI Overview or AI Search?

This is the part Google hasn't addressed directly. FAQ schema has shown up in a fair amount of AI-search-focused advice as a way to make question-and-answer content easier for AI systems to parse and cite, separate from whatever Google Search itself does with it. Google hasn't confirmed or denied a connection between the rich-result deprecation and how AI Overview or AI Mode select sources.

What's more defensible is the underlying practice, not the schema tag specifically: structuring a page so a question and its direct answer sit close together, in plain prose, is something How to Get Cited in Google AI Overview already covers as a core citation habit. FAQ schema was always a machine-readable label on top of that pattern, not a substitute for writing the answer clearly in the first place. If your FAQ section already answers real reader questions in the visible text, keeping or dropping the JSON-LD wrapper around it is unlikely to move the needle much either way.

If You're Adding a New FAQ Section, Here's the Markup

For sites that still want the structured data — for internal consistency, for a CMS plugin that adds it automatically, or on the chance it matters for non-Google AI crawlers — the JSON-LD format hasn't changed:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Does Google still show FAQ rich results?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "No. Google deprecated FAQ rich results for all sites on May 7, 2026, after restricting them to authoritative government and health sites in 2023."
    }
  }]
}

Two rules still matter if you keep it: every question and answer in the markup has to be visible on the page in the same wording, and each Question needs exactly one acceptedAnswer. Google treated content mismatches as spam before the deprecation, and there's no indication that standard has relaxed just because the reward disappeared.

What to Do With Existing FAQ Schema Right Now

A short, realistic checklist for a site that already has FAQ markup scattered across old posts:

1. Leave it if removing it is any real effort. There's no ranking or indexing downside documented anywhere in Google's guidance, so this isn't an urgent cleanup task.
2. Stop adding it as a growth tactic. If a plugin or template still auto-generates FAQ schema for every new post, it's not accomplishing what it used to. That time is better spent elsewhere.
3. Update anything that monitored FAQ rich results via the Search Console API before the August 2026 cutoff, since those calls will start failing once support is removed.
4. Keep the visible FAQ content regardless. The schema wrapper is what lost its reward; a clear, skimmable question-and-answer section is still a normal, useful thing to put on a page, with or without markup underneath it.

The Bigger Pattern

FAQ rich results are the second structured-data reward Google has pulled back in the last few years after HowTo, which was deprecated on mobile in the same August 2023 update. Neither removal changed the value of writing content that plainly answers a specific question — it changed the value of the JSON-LD badge announcing that you did. If you're tracking how Traffic Monitor surfaces GSC query and impression data for your own pages, this is a reasonable moment to check whether any of your top queries were leaning on a FAQ rich result for clicks, and to stop treating the schema itself as the thing doing the work.