DEV Community

Byte Vancer
Byte Vancer

Posted on

FAQ Schema in 2026: How to Add FAQPage JSON-LD (and Is It Still Worth It?)

#webdev #seo #html #tutorial

If you've ever added an FAQ section to a page, you've probably wondered whether you
should also mark it up with FAQ schema. The short answer: yes — but for different
reasons than you might expect in 2026. Let's walk through what FAQPage structured data
is, how to generate it correctly, what changed with Google, and why it still earns its
place in your <head>.

What FAQ schema actually is

FAQ schema is a small block of schema.org FAQPage structured
data, written as JSON-LD and dropped into your page. It tells machines: "this page
contains a list of questions and their answers." Here's the minimal shape:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is FAQ schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "FAQ schema is FAQPage JSON-LD that describes a page's questions and answers so search engines and AI tools can understand them."
      }
    },
    {
      "@type": "Question",
      "name": "Is FAQ schema free to add?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. It's just a script tag you paste into your HTML — no cost, no library required."
      }
    }
  ]
}
</script>
Enter fullscreen mode Exit fullscreen mode

That's it. Each Question has a name (the question) and an acceptedAnswer with
text (the answer). You can have as many as you like.

The honest part: what changed with Google

For years, FAQ schema could earn you an FAQ rich result — those expandable Q&A
accordions right in the Google search listing. That was a big real-estate win.

In August 2023, Google rolled that back. FAQ rich results are now shown only for
"well-known, authoritative government and health websites." For everyone else, the
accordion is gone.

So if the only reason you were adding FAQ schema was the Google rich result — that
reason is mostly gone. Be clear-eyed about it. But that's not the whole story.

Why it's still worth doing in 2026

  1. AI / LLM answers. ChatGPT Search, Perplexity, Copilot and Google's AI Overviews increasingly answer questions by pulling from structured, clearly-labeled content. A clean Question/Answer pair is about the most machine-extractable format there is. FAQ schema makes your answers easy for an LLM to lift and cite.
  2. Bing still uses it. Bing (which also feeds Copilot) continues to support FAQ structured data. Bing traffic is small next to Google, but it's free upside.
  3. It's a forcing function for good content. Writing real questions your users ask — and answering them concisely — is good SEO regardless of markup. The schema just formalizes it.
  4. Valid markup, zero downside. As long as you follow the rules below, there's no penalty risk. It's cheap insurance for a future where AI-driven search keeps growing.

The takeaway: don't add FAQ schema expecting a Google rich snippet. Add it because
it makes your Q&A content legible to the machines that increasingly decide what gets
surfaced.

How to do it correctly

Google's (still-published) FAQPage guidelines are worth following even without the rich
result, because Bing and validators use the same rules:

  • The Q&A must be visible on the page. Don't mark up content that isn't there for users. Schema should describe real, on-page content.
  • Genuine FAQs only. Not a way to stuff keywords, product prompts, or ads. Each answer should actually answer the question.
  • One FAQPage per page. Don't add multiple FAQPage blocks.
  • Escape properly. Answers can contain basic HTML, but you must escape characters that break JSON (quotes, <, &). This is the #1 source of "my schema is invalid" bugs.
  • No duplicate questions, and keep answers reasonably concise.

Validate before you ship

Two quick checks:

If your JSON has a stray unescaped quote or a trailing comma, these will catch it.

The fast way to generate it

Hand-writing JSON-LD is fine for two questions. For a real FAQ — and to avoid the
escaping bugs above — it's faster to generate it. I maintain a free, browser-based
FAQ Schema Generator: you
add question/answer rows, and it outputs a valid, ready-to-paste FAQPage script block.
It runs entirely client-side (nothing you type is uploaded), handles the escaping for
you, and there's no signup. It's part of ByteTools,
a set of free tools that includes generators and validators for the other common schema
types too (Article, Product, Organization, Breadcrumb, HowTo).

Paste the output into your page's HTML (anywhere in <head> or <body>), run it
through the Rich Results Test once, and you're done.

TL;DR

  • FAQ schema = FAQPage JSON-LD describing on-page questions and answers.
  • Google removed FAQ rich results for most sites in 2023 — don't add it for that.
  • It's still worth it for AI/LLM answers, Bing, and clean content structure.
  • Follow the rules (visible content, genuine FAQs, one block per page, proper escaping).
  • Validate with the Schema Validator + Rich Results Test.
  • Generate it in seconds with a free FAQ schema generator instead of hand-escaping JSON.

Got a favorite structured-data workflow, or a question about a specific schema type?
Drop it in the comments.

Top comments (0)