How do I validate FAQ schema markup?

To validate FAQ schema markup: (1) enter your page URL into an FAQ schema validator like SEO-Snap, (2) the tool fetches your page and extracts the JSON-LD block, (3) it checks required fields and syntax, (4) you get a pass/fail result with specific error details. You can also use Google's Rich Results Test for a secondary check.

What are the required fields for FAQ schema?

Required fields for valid FAQPage schema are: @context (must be https://schema.org), @type (must be FAQPage), mainEntity (array of Question objects), each Question must have @type: Question and name (the question text), each acceptedAnswer must have @type: Answer and text (the answer text). Missing any of these makes the schema invalid — AI platforms like ChatGPT and Perplexity rely on correct FAQPage structure to identify and surface your Q&A content.

Why is my FAQ schema not showing in Google search results?

Google ended support for FAQ rich snippets in 2026 and no longer displays them in search results. However, valid FAQ schema is still important: AI platforms like ChatGPT, Perplexity, and AI Overviews use structured data to understand and surface your Q&A content. If your schema is not working in AI search, common causes are: (1) syntax errors in the JSON-LD block, (2) missing required fields like acceptedAnswer.text, (3) answers that are too short or thin. Validate your schema to rule out structural errors.

FAQ Schema Validator & Tester: Check, Test & Fix FAQPage JSON-LD

What is FAQ schema?

FAQ schema (formally FAQPage structured data) is a type of JSON-LD markup you add to a web page to tell search engines and AI platforms that specific content is a list of questions and answers. You add it as a <script type="application/ld+json"> block in your page HTML.

Google used to show FAQ schema as expandable rich snippets in search results, but ended support for FAQ rich results in 2026. However, FAQ schema is still worth implementing because AI search platforms — ChatGPT, Perplexity, Google AI Overviews, and Bing Copilot — actively use structured data to identify and surface question-and-answer content when users ask related queries.

Google no longer shows FAQ rich snippets (2026)

Google deprecated FAQPage rich results in 2026. Adding FAQ schema will not produce expandable question rows in Google search. However, valid FAQ schema still helps AI platforms like ChatGPT, Perplexity, and AI Overviews understand and cite your content — making it worth validating and fixing.

What does valid FAQ schema look like?

FAQ schema must be placed in a <script type="application/ld+json"> block in your page's HTML. Here is the minimal valid structure:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is FAQ schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "FAQ schema is JSON-LD structured data that tells
Google which content on a page is a question-and-answer pair."
      }
    },
    {
      "@type": "Question",
      "name": "How do I add FAQ schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add a <script type='application/ld+json'> block
to your page's <head> or <body> containing the FAQPage JSON-LD."
      }
    }
  ]
}

Every field in this example is required. Skip any one of them and your schema is invalid — Google will ignore it entirely for rich results.

Field	Required	What it must contain
@context	✅ Yes	"https://schema.org" — exactly this string
@type	✅ Yes	"FAQPage" — exactly this value
mainEntity	✅ Yes	Array of Question objects (at least one)
Question @type	✅ Yes	"Question" — each item in mainEntity
Question name	✅ Yes	The question text as a string
acceptedAnswer @type	✅ Yes	"Answer"
acceptedAnswer text	✅ Yes	The answer text — cannot be empty

How to test and validate your FAQ schema — 3 free methods

There are three ways to test FAQ schema code. Use all three for confidence before expecting rich results — each FAQ schema checker catches different classes of errors.

SEO-Snap FAQ Schema Validator (fastest)

Enter your page URL. SEO-Snap fetches the page, extracts your JSON-LD, and validates all required fields against Google's FAQPage specification. Get specific error messages — not just "invalid schema".

Validate FAQ Schema →

Google Rich Results Test (structure check)

Google's tool at search.google.com/test/rich-results confirms whether Google's crawler can parse your schema structure. Note: Google ended FAQ rich results in 2026, so you won't get rich snippets — but this still validates your JSON-LD is syntactically correct.

JSON validator (for syntax errors)

If the tools above show a parsing error, paste your JSON-LD into jsonlint.com to find exact syntax errors — missing commas, unclosed brackets, incorrect quote types. Fix syntax first, then revalidate schema structure.

Most common FAQ schema errors (and how to fix them)

Missing acceptedAnswer.text

Very common

The text property inside acceptedAnswer cannot be empty or absent. Every question must have an answer with actual text content. Even a one-sentence answer is fine — just not an empty string.

// ❌ Bad
{"@type":"Answer"}  // missing text property

// ✅ Good
{"@type":"Answer","text":"Your answer here."}

Incorrect @type casing

Common

Schema.org type names are case-sensitive. "faqpage", "FAQ Page", and "Faqpage" are all wrong. Use exactly "FAQPage", "Question", and "Answer".

// ❌ Bad
"@type": "Faqpage"  // wrong casing

// ✅ Good
"@type": "FAQPage"  // correct

JSON syntax error (trailing comma, wrong quotes)

Common

JSON does not allow trailing commas after the last item in an array or object. Use straight double quotes (") not curly/smart quotes ("). Validate with jsonlint.com if the schema validator cannot parse your block.

// ❌ Bad
{"name": "Q?",}  // trailing comma

// ✅ Good
{"name": "Q?"}   // correct

FAQ content not visible on page

Less obvious

Google requires that FAQ schema questions and answers are visible to users on the page — not hidden behind JavaScript that doesn't render server-side, or collapsed by default with no way to expand. The content must be in the HTML that Googlebot fetches.

Using FAQ schema on product/homepage without real FAQ content

Policy violation

Google's guidelines state FAQ schema should only be used when the page's primary purpose is answering questions. Using it on homepages or product pages as a trick to get more SERP space can lead to manual actions. Only add FAQ schema to pages with genuine FAQ content.

How to add FAQ schema to your page

Add a <script> block anywhere in your page (inside <head> or <body>):

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

WordPress

Use a plugin like Rank Math or Yoast SEO — both have built-in FAQ block support. Add FAQ content using the FAQ block in the editor, and the plugin generates valid JSON-LD automatically.

Webflow

Add a Custom Code component (Embed element) to your page. Paste the JSON-LD script block directly. Webflow does not inject structured data automatically.

Shopify

Edit your theme's Liquid template. Add the JSON-LD script in the product or page template, using Liquid to dynamically output FAQ questions if they're stored as metafields.

Next.js / React

Use dangerouslySetInnerHTML in a <script type="application/ld+json"> tag in your page component or layout. SSR ensures Googlebot sees the structured data on first fetch.

FAQ schema validator vs Google Rich Results Test

Both tools test FAQ schema, but they serve different purposes. Use both for full confidence.

Capability	SEO-Snap Validator	Google Rich Results Test
Specific field-level errors	✅	⚠️ Sometimes
Confirms Google crawler parses schema	❌	✅
Tests JavaScript-rendered schema	❌	✅
Checks full SEO alongside schema	✅	❌
Instant, no login needed	✅	✅
Explains how to fix errors	✅	❌
Note: neither shows FAQ rich results — Google ended these in 2026	—	—

Why FAQ schema still matters in 2026: AI search

Google ended FAQ rich snippets in 2026, but FAQ schema has a new purpose: AI-powered search platforms use structured data as a key signal when generating answers.

When a user asks ChatGPT, Perplexity, or Google AI Overviews a question, these systems scan the web for pages with relevant Q&A content. FAQPage schema explicitly marks your questions and answers as structured data — making it easier for AI models to identify, parse, and cite your content in responses.

ChatGPT

Uses web browsing to pull content for answers. Structured Q&A is easier to extract than prose paragraphs.

Perplexity

Indexes and cites web sources. FAQPage schema helps it identify authoritative Q&A content on your page.

AI Overviews

Google's AI summaries at the top of search results. Structured FAQ data improves how your answers are understood.

The bottom line

Valid FAQ schema = AI platforms can correctly read your Q&A content. Invalid or missing FAQ schema = AI platforms treat your FAQ as generic prose and may miss it entirely. The value of validating is now about AI visibility, not Google rich snippets.

Frequently asked questions

What is an FAQ schema validator?▼

An FAQ schema validator checks your FAQPage JSON-LD structured data for errors and confirms whether it is correctly structured per the schema.org FAQPage specification. It verifies required fields (Question name, Answer acceptedAnswer.text), JSON syntax, and @type declarations. Correct FAQ schema helps AI platforms like ChatGPT, Perplexity, and Google AI Overviews identify and surface your Q&A content.

How many FAQ questions should I include in my schema?▼

Google recommends 2–5 questions for best rich result display — too many and they won't all show. Prioritise the questions your users actually search for. Every question must have a meaningful answer (not just a sentence fragment).

Does FAQ schema still matter after Google ended rich snippets?▼

Yes — FAQ schema still has value in 2026, but for different reasons than before. Google ended FAQ rich results, so adding FAQ schema will not create expandable rows in Google search. However, AI platforms like ChatGPT, Perplexity, Bing Copilot, and Google AI Overviews use FAQPage structured data to identify Q&A content and surface it in AI-generated answers. If your FAQ schema is invalid, these platforms may not correctly understand your content.

How do I test FAQ schema for free?▼

To test FAQ schema for free: (1) use SEO-Snap's FAQ schema checker — enter your URL and get field-level validation errors instantly. (2) Use Google's Rich Results Test at search.google.com/test/rich-results — this confirms whether Google's crawler can parse your schema. (3) Use jsonlint.com to check JSON syntax if either tool reports a parsing error. Run all three tests before expecting FAQ rich results in Google search.

How do I get my FAQ content into ChatGPT or Perplexity answers?▼

Valid FAQ schema increases the likelihood that AI platforms correctly identify and cite your Q&A content. Ensure your FAQPage JSON-LD has no errors (use SEO-Snap's validator), your answers are substantive (at least 2-3 sentences), and the questions match what users actually ask. AI platforms also rely on overall page quality, so ensure your page loads quickly and has clear, crawlable HTML. There is no direct submission — AI platforms index the web and use schema as a signal.

Check your FAQ schema now — free

Validate your FAQPage structured data in seconds. Get specific error messages, not just pass/fail. Fix issues so AI platforms can correctly read your content.

Validate FAQ Schema Free →

Free Tool

FAQ Schema Validator — Instant Check

Article

Schema Markup Validator: Full Guide