FAQ rich results are being retired: what to do next

Google now says FAQ rich results stopped appearing in Google Search on May 7, 2026. The FAQ search appearance, rich-result report, and FAQ support in the Rich Results Test are scheduled to be removed in June 2026, with Search Console API support ending in August 2026. If your site relies on FAQPage schema for SERP visibility, the click-through-rate boost is gone. The schema is not banned, but it no longer earns FAQ rich snippets in Google.

This is the practical migration plan: what to keep, what to delete, and what to ship instead.

What is changing

Three things are going away:

1. The FAQ rich result on Google Search stopped appearing on May 7, 2026.
2. The FAQ search appearance and Search Console rich result report are scheduled for removal in June 2026.
3. FAQPage support in Google's Rich Results Test is scheduled for removal in June 2026, and Search Console API support follows in August 2026.

What does not change:

1. FAQPage schema itself remains valid in schema.org.
2. Bing, DuckDuckGo, and other search engines may still parse it.
3. AI assistants that read structured data may still extract Q&A pairs from FAQPage markup.

The schema is not malware. It is just no longer earning the SERP feature you put it there for.

Should you delete the markup?

Not automatically. Three scenarios:

Keep it if you use it for AI

Sites that publish docs or product FAQs sometimes report cleaner extraction by AI assistants when FAQPage markup is present. If you have any signal that AI engines parse it usefully on your site, keep the markup. The cost is a few KB per page.

Update it if it is hidden

If you ever shipped FAQPage schema for content that was not visibly displayed on the page, that was a violation of Google's policy from the start. Now is a good time to clean it up. Either make the FAQ visible or delete the markup.

Replace it if it is the only structured data

If FAQPage is the only schema on the page, replace it with a more durable type. Article works for blog content. WebPage works as a generic fallback. The page should always have something.

What to ship instead

Three types remain valuable in 2026 even after the FAQPage change.

Article on long-form pages

The most reliable type for ongoing rich-result eligibility. Required fields are aggressive but the gain is durable. See the schema.org for AI agents guide for the full template.

BreadcrumbList on inner pages

Cheap, well-supported, helps both Google and AI agents understand site hierarchy.

Step-by-step structure for procedural pages

If your FAQ was really a procedure, move it into visible step-by-step content first. You can still use HowTo schema for non-Google consumers that parse structured data, but do not expect Google rich-result visibility: Google deprecated HowTo rich results in 2023.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to deploy a sitemap.xml",
  "step": [
    { "@type": "HowToStep", "text": "Generate the file" },
    { "@type": "HowToStep", "text": "Upload to your domain root" },
    { "@type": "HowToStep", "text": "Reference it from robots.txt" }
  ]
}

How to migrate

Three steps. None of them require taking pages offline.

Step 1: Inventory

Find every page with FAQPage markup. The fastest way: run a site-wide scan or grep your CMS export for "@type":"FAQPage".

Step 2: Decide per page

For each page, pick one of four outcomes:

• Keep: page has visible FAQ content and you want it for AI extraction.
• Replace: convert to Article or HowTo if those fit better.
• Delete: page has no visible FAQ or you do not want the markup at all.
• Move to body: pull the Q&A out of structured data and into rendered HTML using clear h2 questions and paragraph answers. Often the cleanest outcome.

Step 3: Validate

After changes, validate the remaining schema with the Structured Data Validator. Use Google's Rich Results Test for still-supported Google rich result types, but do not be alarmed when FAQ support disappears from that tool in June 2026.

A pattern that ages well

Even before this announcement, the durable pattern for FAQs has been:

1. Visible Q&A in the page body using h2 for each question and a paragraph for each answer. AI assistants extract these well.
2. Optional FAQPage schema if you want machine extraction beyond what visible HTML provides.
3. Strong page-level metadata: a focused title, a 150-160 char description, BreadcrumbList schema, and Article schema on long-form pages.

This pattern survives the FAQPage retirement intact because the value comes from visible content, not the rich-snippet feature.

What about other deprecated types

Worth knowing about for completeness:

• HowTo rich results have been narrowed over the years. They still work but are less prominent than they used to be.
• QAPage (different from FAQPage) is for community Q&A sites and is unaffected by this change.
• News articles continue to have first-class support via Article and NewsArticle.

Keep the rest of your structured data

The FAQPage change is specific. Do not delete unrelated schema in a panic. Organization, WebSite, Article, BreadcrumbList, and Product all remain valuable.

If you generate schema with the JSON-LD Generator, the FAQPage option there now shows a deprecation notice but still produces valid markup for sites that want it.

Why this matters

Schema deprecations are part of life on the structured-data web. The leverage is in maintaining a portfolio of types so a single deprecation does not torch your SERP features. Sites that diversified beyond FAQPage years ago will barely notice. Sites that built their CTR strategy on it should plan a migration this quarter.

The plan: identify, decide, replace, validate. Most sites can finish in a day.