FAQ Schema Markup: JSON-LD Tutorial with Examples (2026)

Let's be honest up front, because most FAQ-schema tutorials still aren't: as of May 2026, FAQ rich results no longer appear in Google Search for anyone. Not for your blog, not for big brands, and no longer for the government and health sites that were the last exception. The collapsible Q&A dropdown that FAQ schema used to earn is gone.

That doesn't make the markup worthless, but it changes why you'd add it. This tutorial gives you the working JSON-LD, the honest timeline of what happened, and a clear-eyed answer to the only question that matters now: should you still bother?

For the wider catalogue of types, see Schema Markup Types Explained; for the basics of JSON-LD, the Schema Markup Guide.

What actually happened, on a timeline

| Date | Change | | --- | --- | | Pre-2023 | FAQ schema earned a collapsible Q&A block under your result for most sites. | | August 2023 | Google restricted FAQ rich results to "well-known authoritative government and health" sites. For everyone else, the dropdown vanished. | | May 7, 2026 | FAQ rich results stopped appearing entirely; the government/health exception was removed too. | | June 2026 | Search Console's FAQ search-appearance filter and the FAQ Rich Results Test support are being removed. | | August 2026 | Search Console API stops returning FAQ rich-result data; dashboards pulling it will get null. |

So if you read a guide promising FAQ "rich snippets that boost CTR," check its date. That advice expired in stages, and the last of it expired this spring. The FAQPage type on schema.org is still valid and Google still parses it without complaint; only the visual SERP feature is gone.

The full JSON-LD example

The structure is a FAQPage whose mainEntity is an array of Question objects, each with one acceptedAnswer:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How do I add FAQ schema to my page?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add a JSON-LD script with @type FAQPage and a mainEntity array of Question/Answer pairs. Each question's text must also be visible on the page."
      }
    },
    {
      "@type": "Question",
      "name": "Where does the script go?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Inside the head element or anywhere in the body. Google reads both; what matters is that it appears in the rendered HTML."
      }
    }
  ]
}
</script>

Three things that trip people up:

JSON has no comments. Don't paste // like this into the block; it makes the JSON invalid and the whole thing is ignored.
The answer text accepts limited HTML (<br>, <a>, <p>, lists) but not scripts or images. Plain text is safest.
Every question and answer must be visible on the page. Marking up Q&A that a user can't see was always a policy violation; it still is, even with no rich result on the line.

So is it still worth adding?

Here is the genuinely useful decision, not a hedge:

Add FAQ schema if you have one of these specific reasons:

You're feeding AI answer engines and other parsers. AI Overviews, AI Mode, and non-Google assistants read structured data when present. Google's own guidance says no special schema is required for AI features, but clean Q&A markup that matches your page is a tidy way to expose the same facts.
You're standardising schema across the site and the marginal cost of including it is near zero (e.g. your CMS emits it automatically).

Skip it if you were only adding it for the Google dropdown (that reason no longer exists) or if maintaining it costs real effort. Google has confirmed unused FAQ markup doesn't harm Search, so there's no urgency to rip out what you already have. Decide on governance cost, not panic.

What you should not do is keep stuffing FAQPage onto product pages, category pages, and posts that have no genuine FAQ. That over-use is exactly the behaviour that got the feature pruned, and on pages without real Q&A it's a mismatch waiting to be flagged.

Validating what remains

Even with no rich result to preview, validation still catches the structural mistakes that make markup useless:

Build the block with our Schema Generator so the nesting and quoting are correct by construction.
Run the page through the Schema Markup Validator (validator.schema.org) to confirm the JSON-LD parses and the types are recognised. Note that Google's Rich Results Test is dropping FAQ support in 2026, so the generic schema validator is now the right tool for FAQPage.
Confirm the markup is in the rendered HTML; if it's injected client-side and the crawler reads only the initial response, it's invisible. Check via Search Console's URL Inspection.

A note on the on-page FAQ itself

The disappearance of the rich result doesn't change the value of a genuinely good FAQ section on the page. Clear questions and direct answers help readers, reduce support load, and give AI systems clean material to quote. The lesson of 2023 to 2026 is that the markup was never the point; answering real questions well was. Write the FAQ for humans; the schema is now just optional metadata on top.

Frequently Asked Questions

Do FAQ rich results still show in Google?

No. They were narrowed to government and health sites in August 2023 and removed entirely on May 7, 2026. No site earns the FAQ dropdown in Google Search anymore. The FAQPage markup remains valid but produces no visual result.

Should I remove my existing FAQ schema?

There's no need to. Google has confirmed unused FAQ markup doesn't hurt Search. Keep it if it's auto-generated or feeds AI/parsers; remove it if maintaining it costs effort you'd rather spend elsewhere.

Does FAQ schema help with AI Overviews or AI Mode?

It can, but it isn't required. Google says no special schema is needed for AI features. Accurate FAQPage markup that matches your visible content is one clean way to expose Q&A facts to AI and other parsers.

Why did Google remove FAQ rich results?

Over-use. Marketers added FAQ schema to pages with no real FAQs to grab SERP space. Google restricted the feature in 2023 citing quality concerns, then removed it for everyone in 2026 as part of broader pruning of low-value rich result types.

What tool validates FAQ schema now that the Rich Results Test is dropping it?

Use the Schema Markup Validator at validator.schema.org to confirm the JSON-LD parses and the types are correct. It checks structure independent of whether Google renders a rich result.

FAQ Schema Markup Tutorial: Code, Examples, and Common Mistakes