🔥 Black Friday is LIVE — 15% off every in-person pass with code BLKFRI2027. Ends Dec 3🔥 15% off all passes · code BLKFRI2027Shop the sale →
Technical SEO

FAQ Schema Guide

FAQ schema is the structured data that marks up a question-and-answer block so search engines understand it as exactly that. For years it earned an expandabl

Terry Samuels Terry Samuels
Founder, SEO Spring Training
·Oct 11, 2026 ·7 min read

FAQ schema is the structured data that marks up a question-and-answer block so search engines understand it as exactly that. For years it earned an expandable FAQ right in the search result — extra real estate under your listing, more reasons to click. Google has since narrowed where those rich results show, which changed the calculus but not the value. Done right, FAQ schema still helps engines and AI models parse your answers, and it’s one of the easiest pieces of structured data to implement correctly.

This is the practitioner’s guide: what FAQ schema is, the current state of the rich result, the exact JSON-LD to use, and Google’s rules — the ones that get markup ignored or, worse, flagged as a violation. It sits under the schema markup hub.

The short version

  • FAQ schema uses the FAQPage type with Question and acceptedAnswer entries
  • Google now shows FAQ rich results mainly for authoritative government and health sites — but the markup still aids understanding and AI citation
  • The markup must match visible content on the page, word for word in intent
  • Use real user questions with genuine answers — not keyword-stuffed fakes
  • Validate with the Rich Results Test and watch the Enhancements report

What FAQ schema is and why it still matters

Structured data is a way of labeling content so machines read it reliably instead of inferring it. FAQ schema specifically wraps a set of questions and their answers in the FAQPage vocabulary from schema.org. When an engine sees it, it knows “this is a list of questions and answers” rather than guessing from your HTML.

Let me be honest about the rich result, because the landscape shifted. Google used to show FAQ rich results widely. In 2023 it restricted them to well-known authoritative sites — mostly government and health domains. So if you’re a typical business or content site, don’t expect the expandable FAQ in your listing anymore. That’s the realistic expectation to set.

Why implement it anyway? Three reasons. It still helps Google understand your page’s structure and the entities in it. AI answer engines parse structured data to extract and cite Q&A content — and getting cited is the new game, as we cover in generative engine optimization. And it costs almost nothing to add. Low effort, durable upside, no downside when done correctly.

The JSON-LD you actually use

Always use JSON-LD — it’s what Google recommends, and it keeps the markup in one clean block instead of tangled through your HTML. Here’s a complete, correct FAQPage:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does FAQ schema still get a rich result?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "For most sites, no. Google now limits FAQ rich results to authoritative government and health sites, but the markup still aids understanding and AI citation."
      }
    },
    {
      "@type": "Question",
      "name": "What format should FAQ schema use?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "JSON-LD, placed in a script tag in the head or body. Google recommends it over microdata or RDFa."
      }
    }
  ]
}
</script>

The structure is always the same: a FAQPage whose mainEntity is an array of Question objects, each with a name (the question) and an acceptedAnswer containing the answer text. The answer text can include basic HTML like links and lists, but keep it to what’s genuinely on the page.

Google’s rules — break these and it backfires

This is where I see implementations go wrong. FAQ schema has guidelines, and violating them doesn’t just lose the rich result — it can earn a manual action for spammy structured data. The rules are common sense once you see them.

FAQ schema: the rules that matter

✓ Do

  • Mark up Q&A that’s visibly on the page
  • Use genuine questions users actually ask
  • Keep answers accurate and self-contained
  • Put the FAQ schema on the page that shows the FAQ

✕ Don’t

  • Mark up content that isn’t visible to users
  • Stuff keywords or promotional copy into answers
  • Use FAQ schema for ads or lead-gen forms
  • Duplicate the same FAQ block across many pages

The single rule under all of these: the markup must match the visible content. Google’s structured data policy is explicit that hidden content you mark up but don’t show users is a violation. So the workflow is always content first, markup second — write the real FAQ onto the page, then describe it in JSON-LD.

How to implement it, step by step

  • Write the real FAQAdd a visible question-and-answer section to the page, using questions your audience genuinely asks.
  • Mirror it in JSON-LDCreate a FAQPage block whose questions and answers match the visible text.
  • Test itRun the URL through Google’s Rich Results Test to confirm valid FAQ markup and no errors.
  • Monitor itWatch the FAQ Enhancements report in Search Console for warnings on live pages.

Where do the questions come from? The best source is real demand: People Also Ask boxes on your target query, the questions customers email you, the searches inside your own site. A good FAQ earns its place by answering things people actually wonder — which is also why it’s the natural companion to strong on-page content. If your answers are solid and self-contained, they’re exactly what AI engines like to lift and cite.

JSON-LDThe only format worth using
100%Of marked-up Q&A must be visible on the page
2Tools to validate: Rich Results Test + Search Console

Validating and troubleshooting

Two tools do the job. Google’s Rich Results Test tells you whether the page is eligible for the FAQ rich result and flags errors and warnings in the markup. The schema.org validator checks general syntax if you want a second opinion. After you deploy, the Enhancements section of Search Console reports FAQ markup across your live pages, so you catch errors at scale rather than one URL at a time.

Common issues and fixes: a missing acceptedAnswer on a question (every question needs one), answer text that doesn’t match the page (align them), and FAQ schema placed on a page with no visible FAQ (add the content or remove the markup). If the Rich Results Test says “valid” but you still see no rich result, that’s expected for most sites now — remember the eligibility limits. Validity earns eligibility, not a guaranteed feature. That distinction trips up a lot of people, and it’s the same logic across all of structured data.

Want to build structured data that actually gets used?We implement and validate schema on real pages at SEO Spring Training — April 7–11, 2027, Chandler, Arizona.

Get your pass →

FAQPage vs QAPage — pick the right one

A quick clarification, because the two get confused. FAQPage is for a page where you publish both the questions and the official answers — a product FAQ, a service page’s common questions. QAPage is for a page with a single user-submitted question and community answers, like a forum thread. If you’re writing the answers yourself, you want FAQPage. Using the wrong type sends a confusing signal about what the page is.

Where FAQ schema fits in your structured-data stack

FAQ schema is rarely the only markup on a page, and it shouldn’t be. It layers alongside the other types that describe your page — Article or BlogPosting for content, BreadcrumbList for navigation, Organization and Person for your entity. The clean way to handle this is a single JSON-LD @graph that holds every type for the page in one script block, each node cross-referenced by @id. That’s exactly how the hubs on this site are built, and it keeps your markup maintainable instead of scattering five script tags across the template.

The practical rule: add FAQ schema only where a genuine FAQ lives, and let the sitewide types (Organization, Person, breadcrumbs) ride along on every page from your template. Don’t force an FAQ onto a page just to use the markup — a thin, invented FAQ bolted on for schema’s sake is the kind of low-value content that hurts more than it helps. The best FAQ schema describes an FAQ that earned its place answering real questions, and the same discipline runs through everything in the schema markup hub.

Frequently asked questions

Is FAQ schema worth adding in 2027?

Yes, with realistic expectations. You probably won’t get the expandable rich result unless you’re an authoritative government or health site, but the markup still helps search engines and AI models understand and cite your Q&A content. It’s low effort with durable upside.

Can FAQ schema hurt my site?

Only if you misuse it — marking up hidden content, stuffing keywords, or using it for ads and forms can trigger a structured-data manual action. Mark up genuine, visible Q&A and there’s no risk.

How many questions should I include?

As many as you genuinely answer on the page — there’s no magic number. Three to six focused, real questions beats a dozen padded ones. Quality and relevance matter more than count, and every question must have a visible answer.

Do I need a plugin for FAQ schema?

No, but plugins help. On WordPress, Rank Math and Yoast can output FAQ schema from a block, which keeps markup and visible content in sync automatically. Hand-coded JSON-LD works fine too — just remember to update the markup whenever you edit the visible FAQ.

FAQ schema is the friendliest piece of structured data to start with: a clear vocabulary, an easy-to-template JSON-LD block, and real value even without the rich result. Write genuine questions, answer them visibly, mirror them in clean markup, and validate. Do that and you’ve made your answers unmistakable to every engine that reads your page.

Want to go deeper than a guide?Learn this live at SEO Spring Training — Apr 7–11, 2027 · Chandler, AZ.
Get Your Pass →
Terry Samuels

About the author

Terry Samuels

Founder and host of SEO Spring Training — a practitioner-taught digital marketing conference in Chandler, Arizona. Terry writes from real campaigns, not theory.

Last updated October 2026 · Reviewed by the SEOST team
Learn this live at SEOSTApr 7–11, 2027 · Chandler, AZ · Passes from $897
Get Your Pass →