FAQ Schema: How to Get FAQ Rich Snippets in Google

FAQPage structured data describes visible questions and answers in a machine-readable format. Google now generally limits FAQ rich results to well-known, authoritative government and health sites. Markup does not guarantee a rich result, ranking boost, indexing, or AI citation. Use it only when it accurately matches the visible page content and supports your broader structured-data practice.

Most people get this wrong because they read a 2021 tutorial promising expandable boxes for everyone. That changed. This guide gives you the real rules, copy-paste code that validates, and the workflow that actually moves the needle today.

What FAQ Schema Actually Is

FAQ schema marks up a list of questions your organization asks and answers on a page. It uses the FAQPage type, which contains a mainEntity array of Question entities, each holding one acceptedAnswer of type Answer. The whole thing lives in a single JSON-LD script tag that search engines parse separately from your visible HTML.

The structural hierarchy is simple:

• FAQPage: one wrapper per page

- Question: each FAQ item (the name is the question text) - Answer: the acceptedAnswer with a text field holding the answer

Because the markup sits in its own <script> block, you can add or edit it without touching your layout, CSS, or design. That separation is exactly why Google recommends JSON-LD over inline Microdata or RDFa: it is clean, easy to template, and easy to validate.

One critical distinction: FAQ schema is for content where you supply both the question and the answer. If users ask and other users answer (a forum, a community thread), that is QAPage schema: a completely different type. Mixing them up makes Google ignore your markup.

Why It Still Matters in 2026 (The Honest Version)

Let me be direct about what changed, because most articles on this topic are stale. In mid-2023 Google announced that FAQ rich results would only show for well-known, authoritative government and health websites. For everyone else, the expandable accordion in the blue-link results largely went away.

So why bother? Because the snippet was never the only payoff. Here is what valid FAQ schema still does:

• Does not guarantee AI citations. Google says special structured data is not required for its generative AI features. Follow each other provider’s guidance rather than assuming FAQ markup changes citation eligibility.
• Powers voice and assistant answers. Assistant-style results often read a concise acceptedAnswer aloud.
• Improves entity and topic understanding. Explicit Q&A structure helps search engines map what your page covers.
• May support other implementations. Keep markup only if it accurately describes visible content and a supported consumer uses it; recheck policies as they change.

What it does not do: directly raise your ranking position. Schema is a presentation and parsing signal, not a ranking factor. Anyone promising a ranking boost from FAQ schema alone is selling you something. If you want to confirm whether your pages even have valid markup, run a free SlapMyWeb audit to see which of these issues your site actually has.

How FAQ Schema Connects to the Rest of Your SEO

FAQ schema is one item in a larger structured-data and answer-engine strategy. It rarely works in isolation:

The strongest FAQ pages combine the schema with genuinely useful answers, a logical heading structure, and a page that already earns trust. Schema amplifies a good page; it cannot rescue a thin one.

1. Write the FAQ Content First

Before any code, your questions and answers must exist as visible text on the page. Google requires that FAQ schema mirror visible on-page content. Schema-only FAQs, answers that live in the JSON-LD but appear nowhere on screen, are a guideline violation that can trigger a manual action.

Write 4-8 questions your audience genuinely asks. Mine real demand instead of inventing filler:

• Check the People Also Ask box for your target query
• Pull real questions from Search Console query data
• Read support tickets, sales call notes, and on-site search logs

Keep each answer to 2-4 sentences: direct, specific, and quotable. Lead with the answer in the first sentence, then add the detail: this is the exact format AI engines extract. Do not stuff keywords; FAQ content that reads like keyword soup gets flagged.

2. Build the JSON-LD Markup

You can hand-write JSON-LD, but a generator is faster and avoids syntax slips. Here is a complete, valid FAQPage block you can adapt directly:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is FAQ schema markup?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "FAQ schema markup is structured data in JSON-LD format that tells search engines a page contains a set of questions and answers. Search engines and AI assistants use it to understand, quote, and present that Q&A content."
      }
    },
    {
      "@type": "Question",
      "name": "How many FAQs should a page include?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Aim for four to eight focused, high-quality questions per page. Cramming twenty or more generic questions onto one page signals low-quality content and provides no extra benefit."
      }
    },
    {
      "@type": "Question",
      "name": "Does FAQ schema improve rankings?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. FAQ markup is not a ranking factor. Keep it accurate and aligned with visible answers; it does not guarantee search visibility or citations."
      }
    }
  ]
}

Notice the answer text contains no HTML, no smart quotes, and no line breaks that could break the JSON. Keep answers as plain strings. If you must include a link inside an answer, schema.org permits a limited set of HTML tags (<a>, <p>, <br>, lists): but plain text is safest.

The HTML you actually paste

Wrap the JSON in a script tag. It works in the <head> or right before </body>; Google processes both identically.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Your question here?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Your answer here."
      }
    }
  ]
}
</script>

WordPress: paste into a Custom HTML block, or use your SEO plugin's schema/FAQ block (Yoast, Rank Math, and others ship FAQPage blocks that generate this for you). Next.js / React: render it server-side in your page component: a dedicated <JsonLd> component using dangerouslySetInnerHTML with JSON.stringify is the cleanest pattern, and it guarantees the markup is in the initial HTML rather than injected after hydration.

3. Validate Before You Ship

A single missing comma silently kills the entire block: Google does not partially parse broken JSON. Validate every time:

1. 1Schema.org validator: confirms your structure matches the vocabulary.
2. 2Google Rich Results Test: paste the live URL (or code) to confirm Google can read the FAQPage and see whether it is eligible for any enhancement.

Validation catches syntax errors (unescaped quotes, trailing commas, unclosed brackets) and structural issues (wrong type names, missing acceptedAnswer) before they reach production.

4. Deploy, Recrawl, and Monitor

After publishing, request indexing in Google Search Console to speed up the recrawl (typically a few days). Then watch two places:

• Search Console → Enhancements → FAQ (when present) shows whether Google detected valid FAQ items and lists any errors.
• Search Console → Performance → Search Appearance reveals whether any FAQ enhancement is being served for your qualifying pages.

Google generally limits FAQ rich results to well-known, authoritative government and health sites. Other publishers can validate markup for correctness but should not treat validation or AI appearances as guaranteed outcomes.

Common Mistakes That Break FAQ Schema

Invalid JSON syntax

The number-one failure. A missing comma, an extra bracket, or an unescaped quote inside answer text breaks the whole FAQPage. Always run it through a validator. Copy-paste from a word processor (which inserts curly quotes) is the usual culprit.

Content not visible on the page

Every question and answer in the schema must appear in the rendered page. JavaScript-driven accordions are fine because Google renders JS: but content that exists only in the JSON-LD is a violation that can cost you all enhancements site-wide.

Schema/visible-text mismatch

The answer text in your markup should match the on-page answer. Heavily paraphrased or different content between the two is treated as misleading markup.

Too many or off-topic FAQs

Twenty-plus questions on one page signals low quality. Keep it to a focused 4-8 that genuinely relate to the page topic. And do not bolt FAQ schema onto pages with no real Q&A just to "have schema."

Using FAQPage for user-generated Q&A

If your community asks and answers, that is QAPage, not FAQPage. Using the wrong type makes Google discard the markup.

A Reusable Workflow for Many Pages

For a site with dozens of FAQ pages, manual JSON editing does not scale. Build a template instead:

1. 1Audit: find every page that has Q&A content but no schema. A complete SEO audit surfaces these quickly.
2. 2Template: store questions and answers as structured CMS fields, then render the FAQPage JSON-LD automatically from those fields.
3. 3Validate in CI: lint the generated JSON on build so a broken page never ships.
4. 4Monitor: track Enhancement reports and AI citations over time.

This way every new FAQ page gets correct, validated markup with zero hand-editing: and you stay aligned with the broader schema markup fundamentals.

Frequently Asked Questions