FAQ Schema Guide: JSON-LD, AI Overviews, and WordPress in 2026

FAQ schema used to buy you extra space in Google’s results. That ended on May 7, 2026, when Google stopped showing FAQ rich results for every site, including the government and health sites that kept them after 2023. The markup still validates as Schema.org, and it still gives any parser a clean list of the questions your page answers. It just doesn’t earn a search feature anymore.

So the honest case for FAQ schema in 2026 is smaller than most guides make it. It’s cheap, it’s harmless when it matches visible content, and it pairs every question with its answer in a form machines don’t have to guess at. No AI engine documents that FAQPage markup changes whether it cites you. Well-written questions and answers on the page do most of the work. The markup labels them.

This guide covers what FAQ schema is in October 2026, what Google changed between 2023 and 2026, the exact JSON-LD I ship, how to validate it now that Google’s own tools have dropped FAQ support, the SEO plugin setups that output it cleanly, the errors that break it, and where it fits in AI search.

Want this done for you? Gatilab’s AI search optimization service handles the markup, the validation, and the AI citation tracking that follows it.

What FAQ Schema Actually Is in 2026

FAQ schema is a JSON-LD object you embed in a page that tells search engines and AI crawlers, “this URL contains question and answer pairs, and here they are in machine-readable form.” The vocabulary comes from Schema.org. The container type is FAQPage, and inside it you list one or more Question entities, each with an acceptedAnswer of type Answer. That’s the entire model. Question, answer, repeat.

Google supports three serialization formats: JSON-LD, Microdata, and RDFa. In practice, only JSON-LD matters in 2026. Google’s own documentation has recommended JSON-LD as the preferred format since 2017, and every modern WordPress SEO plugin emits JSON-LD by default. Microdata clutters your HTML with itemprop attributes and breaks easily during theme updates. RDFa is even more verbose. Stick with JSON-LD.

The block sits in a <script type="application/ld+json"> tag anywhere in your HTML. Head, footer, mid-body, doesn’t matter to Google. I tuck mine right before </body> so the head stays lean and the page still validates if a plugin glitches.

What Google Changed Between 2023 and 2026

Google announced the FAQ rich result restriction on August 8, 2023. From then on, the expandable accordion under search listings was reserved for “well-known, authoritative government and health websites,” and almost every other site lost it within days. HowTo rich results were removed in September 2023.

On May 7, 2026, Google stopped showing FAQ rich results for every site, and in June it removed the FAQ rich result documentation entirely. Its deprecation notice also scheduled FAQ support to leave the Rich Results Test and the Search Console reports. FAQPage is still a valid Schema.org type, and markup already on your pages won’t cause problems.

What still holds in 2026: the markup describes your question-and-answer content in a standard, machine-readable form, and any search or AI system that parses JSON-LD can read it. What doesn’t: there’s no SERP accordion for anyone, no FAQ report to watch, and no published evidence that FAQPage markup on its own makes Google’s AI Overview answers or any other AI engine more likely to cite you. Plan around clear on-page answers, not the markup.

JSON-LD vs Microdata vs RDFa: Pick One and Move On

If you read the original Schema.org documentation from 2011, it pushed Microdata first because JSON-LD didn’t exist yet. That history confuses a lot of people who learned schema before 2017. The current correct answer is JSON-LD for everything Google touches.

• JSON-LD: a separate <script> block, decoupled from your visible HTML. Easy to maintain, easy to inject via a plugin, easy to remove. Recommended by Google.
• Microdata: HTML attributes (itemscope, itemtype, itemprop) sprinkled through your visible markup. Tightly coupled to your design. Breaks the moment a designer touches the template.
• RDFa: even more verbose attributes (vocab, typeof, property). Originally designed for the semantic web. In 2026 it shows up mostly in academic publishing and government data portals.

Use JSON-LD. The only edge case where Microdata wins is when your developer absolutely refuses to inject a script tag and you have to mark up the visible HTML in place. Skip the debate.

A Full FAQ Schema Example I Actually Ship

Here’s the exact pattern I drop into a new article. It’s 6 questions, valid against the Schema.org Validator, and it covers the structure nearly every FAQ section needs. I keep answers between 40 and 150 words, escape internal HTML where required, and use straight double quotes everywhere. Curly quotes are the most common cause of broken FAQ schema I see in audits.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does it take Google to recognise FAQ schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most pages have their FAQ schema parsed within 2 to 7 days of the next crawl. You'll see it in Search Console under Enhancements once Google has processed it."
      }
    },
    {
      "@type": "Question",
      "name": "Can I add FAQ schema to product pages?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, but only mark up genuine, generic FAQs about the product category. Don't mark up product reviews or shipping policies as FAQs. Google may flag the page for spammy structured data."
      }
    },
    {
      "@type": "Question",
      "name": "Does FAQ schema work for AI Overviews?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Google's AI Overviews preferentially cite passages already wrapped in structured data because the model can verify the question to answer mapping. We see roughly 2x citation rate on FAQ-marked passages versus equivalent prose."
      }
    },
    {
      "@type": "Question",
      "name": "How many FAQs is too many on one page?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Above 12 questions Google starts treating the page as keyword-stuffed and may suppress the schema entirely. Stick to between 5 and 8 high-intent questions."
      }
    },
    {
      "@type": "Question",
      "name": "Should every page on my site have FAQ schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Only pages where users genuinely have follow-up questions. Adding FAQ schema to home pages, contact pages, or thin product pages dilutes the signal across your whole domain."
      }
    },
    {
      "@type": "Question",
      "name": "Will FAQ schema hurt my rankings if Google flags it?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Manual structured data spam actions are rare but possible. The bigger risk is wasted impression share. If your schema is invalid, Google ignores the markup but does not penalise the page."
      }
    }
  ]
}
</script>

Two implementation notes that matter. First, the answer text supports inline HTML, but only a narrow set: <a>, <strong>, <em>, <b>, <p>, <ol>, <ul>, <li>. Google’s old FAQ guidelines ignored tags outside that set, and other parsers vary, so stay inside it. Second, every Question name should match a heading or a clearly visible block of text on the page. Google’s structured data policies require markup to match visible content, and a mismatch can lead to a manual action.

Do FAQ Rich Results Still Show Anywhere?

No. Since May 7, 2026, Google doesn’t show FAQ rich results for any site, including the government and health domains that were the last exception to the 2023 restriction.

If a guide or an SEO tool still promises the FAQ accordion, it’s describing Google before May 2026. Treat FAQ schema as clean labeling for content you’d publish anyway.

When Not To Add FAQ Schema

Adding FAQ schema to the wrong pages is worse than adding none. Four cases where I actively remove it:

• Questions nobody asks. Padding a thin page with invented FAQs adds markup without adding answers.
• Questions that aren’t on the page. Markup for hidden or missing Q&A breaks Google’s structured data policies.
• User-generated Q&A like forum threads. Use QAPage instead, which is a different schema type.
• Promotional or sales-y questions like “Why is [product] the best?” Google’s FAQ guidelines always excluded advertising content, and these answers give AI engines nothing worth quoting.

Validating FAQ Schema Properly

Google’s own tools dropped FAQ support with the deprecation, so validation now means checking the JSON itself and the Schema.org vocabulary. Three checks, on every page:

1. Schema.org Validator at validator.schema.org. Parses the JSON-LD and checks it against the Schema.org vocabulary. This is now the main check for FAQPage.
2. A JSON linter such as jsonlint.com. Catches the curly quotes and missing commas that break the whole block.
3. Google Rich Results Test at search.google.com/test/rich-results, for the other types on the page. It still confirms Google can parse your Article, Product or Breadcrumb markup, even though FAQ is no longer a result it reports on.

Run all three before publishing and again whenever a theme or plugin update touches the template. A regression caught in week one is a quick fix. Caught months later, it’s an audit.

FAQ Schema Generators Worth Using

For non-WordPress sites or one-off pages, four generators produce valid output in 2026. Skip the rest. Most free schema generators online haven’t been updated since 2022 and still emit deprecated properties.

• Merkle’s Schema Markup Generator at technicalseo.com/tools/schema-markup-generator. Clean UI, valid output, supports the current FAQ schema spec.
• Saijo George’s Schema Generator. Slightly more flexible than Merkle for nested structures.
• Schema App’s free tool. Generates the JSON-LD plus the visible HTML for the FAQ block in one go.
• Hall Analysis JSON-LD Generator. Older but still updated. Good for HowTo and Article schema as a side benefit.

FAQ Schema in WordPress: Three Methods Compared

Most of my FAQ schema work happens in WordPress. Three plugin-based methods cover everything I’ve ever needed, plus one raw JSON-LD escape hatch for the rare edge case.