FAQ schema in 2026: is it still worth adding?

FAQ schema used to be one of the easiest SEO wins around. Add a few questions in JSON-LD, and Google might expand your result with drop-down answers that pushed competitors down the page.

That result is gone. Google stopped showing FAQ rich results on 7 May 2026, and plenty of guides still haven't caught up. We went through Google's changelog, its AI search guidance, and the schema.org spec on 8 October 2026 to work out what FAQ schema still does and whether it's worth your time.

What is FAQ schema?

FAQ schema is structured data using the schema.org FAQPage type. It tells machines, "this page contains these questions, and these are the answers." Most sites add it as JSON-LD in the page head:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does Stripe charge a monthly fee?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Stripe doesn't charge setup, monthly, or closure fees on standard pricing."
      }
    }
  ]
}

It's still widely used. Schema.org reports FAQPage on 1 million to 10 million domains, based on Google's web index for August 2026.

What did Google change about FAQ rich results?

The decline happened in two steps, three years apart.

1. 14 September 2023. Google updated its FAQ documentation to say the rich result would only show for "well-known, authoritative government and health websites." For most sites, the feature effectively ended here.
2. 7 May 2026. FAQ rich results stopped appearing in Google Search entirely. Google added a deprecation notice on 8 May.
3. 15 June 2026. Google removed the FAQ rich result documentation. Its stated reason: "The FAQ rich result feature is no longer shown in Google Search results."

All three entries are in Google's documentation updates changelog.

Was FAQ the only rich result Google retired?

No. The same 14 September 2023 changelog entry removed the How-to structured data documentation, because that rich result was "no longer shown in search results, on both desktop and mobile devices."

The pattern is worth noticing. Both features let a site take up extra room on the results page with content Google could show directly, and both are now gone. If you're deciding where to spend structured data effort, favor markup tied to things Google still lists in its search gallery.

For a typical publisher or SaaS site, that list still includes:

• Article and Breadcrumb, for blog posts and site hierarchy
• Organization, for your logo and company details
• Product snippet, Review snippet, and Software app, for product and review pages
• Video, if you embed video
• Discussion forum and Q&A, for community content

Check each feature's own guidelines before you add it. Eligibility rules differ by type, and none of them guarantee a rich result.

Does FAQ schema help with AI Overviews or ChatGPT?

For Google, no. Its guide to optimizing for generative AI features, published in May 2026, is clear on this:

• "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add."
• AI Overviews and AI Mode rely on Google's core ranking and quality systems to pick pages.
• The same guide still recommends structured data in general, "as it helps with being eligible for rich results on Google Search."

So FAQ markup no longer earns a rich result, and Google says it isn't an AI shortcut either.

For other AI tools, we couldn't find current public documentation from OpenAI, Anthropic, Perplexity, or Microsoft saying how they treat FAQPage markup. Plenty of blog posts claim it boosts AI citations. We haven't seen evidence for that, so we're not repeating it.

Is FAQ schema still worth adding in 2026?

Here's where we land:

Our honest take: FAQ schema is now a hygiene item. It costs almost nothing to output if your FAQ already exists, and there's no documented penalty for valid markup. It's also no longer something to plan content around.

For transparency, this article carries FAQPage markup. MorningStacks generates it automatically from the visible FAQ section at the bottom of each article, so it always matches what you can read.

Can you switch FAQ markup to QAPage?

Usually not. Google's QAPage documentation is for pages where users can submit answers to a single question.

It lists "an FAQ page written by the site itself with no way for users to submit alternative answers" as an invalid use. Blog posts and how-to guides that answer a question are invalid too. Swapping types to chase a different rich result is a quick way to get structured data ignored.

What should you do with the FAQs you already have?

The FAQ section can still earn its place on the page, for readers. A good FAQ answers the follow-up questions people actually ask, in the first sentence of each answer.

1. Audit where the markup lives

Search your templates for FAQPage. List every page type that outputs it.

2. Check that every marked-up question is visible

Open each page type and compare the JSON-LD with the page. If the markup has questions the page doesn't show, fix or remove it.

3. Cut filler questions

"What is [our product]?" on a page about that product isn't helping anyone. Keep questions that answer real doubts, like price, limits, or how something compares.

4. Put the answer first

Start each answer with the direct answer, then the detail. That's good writing, and it's what any system quoting your page needs.

5. Stop reporting on FAQ rich results

If a dashboard or client report still tracks FAQ rich result impressions, retire it. The feature doesn't exist in Google Search anymore.

How do you check the FAQ markup your site outputs?

Two quick checks, neither of which needs a paid tool:

1. View the rendered source. Open a page, view source, and search for FAQPage. Many themes and SEO plugins output it without you knowing.
2. Run the Schema Markup Validator at validator.schema.org. It checks markup against the schema.org vocabulary itself, independent of which Google features exist.

If your SEO plugin has a setting for FAQ blocks, read what it outputs. Some add FAQPage to every page that uses an accordion, whether or not the content is a real FAQ.

What actually helps Google and AI search now?

Google's guidance comes back to the same basics: indexable pages, useful and original content, and a clear structure. Its AI guide calls out "non-commodity content" that offers first-hand knowledge or a unique view.

If you want a concrete next step, make sure your important pages are indexed (our Search Console indexing guide walks through it). And if someone suggests llms.txt as the next AI search fix, read what llms.txt does and doesn't do first. Google ignores it too.