FAQ Schema Validator
Check FAQ structured data against the rules Google documents for FAQPage. The validator reads the JSON-LD on a page – or code you paste – finds every FAQPage, and checks that each item is a Question with a name and an acceptedAnswer of type Answer with text. It flags HTML tags Google ignores in answers, repeated questions, more than one FAQPage per page, a missing schema.org context, invalid JSON, and questions that do not appear in the visible text of the page.
- Encrypted connection
- No sign-up
- Free to use
How to use FAQ Schema Validator
- Enter the page URL, or paste HTML or JSON-LD.
- Click “Validate FAQ schema”.
- Fix the errors first, then the warnings.
- Re-test after publishing.
FAQ Schema Validator features
Structure checks
Question, acceptedAnswer and Answer.
Allowed HTML
Tags Google ignores flagged.
Visibility
Questions found in page text.
JSON errors
Syntax errors with the message.
Question table
All questions and answers listed.
Paste JSON-LD
Validate code before it goes live.
When to use FAQ Schema Validator
- Checking FAQ blocks added by a CMS plugin.
- Reviewing hand-written JSON-LD.
- Debugging Search Console FAQ errors.
- Auditing help-centre pages.
FAQ Schema Validator FAQ
Will my FAQ show as a rich result?
Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites. Valid markup still describes your content accurately.
Which HTML can answers contain?
Google reads h1–h6, br, ol, ul, li, a, p, div, b, strong, i and em. Other tags are ignored, which can change how the answer reads.
Must the questions be visible?
Yes. Google requires the FAQ content to be visible on the page; markup for hidden content can be ignored.
Is microdata supported?
The tool validates JSON-LD, the recommended format. It notes when FAQ microdata is present.
Why does my FAQ not show in Google?
Google limited FAQ rich results to a small set of authoritative sites in 2023. The markup can be valid without a visible result.
Valid FAQ markup
An FAQPage contains a mainEntity list of Question items. Each question has a name (the question itself) and one acceptedAnswer whose text holds the answer. The page should contain one FAQPage with all questions, written by the site owner – user-submitted questions belong in QAPage markup.
Errors stop the markup from being understood; warnings point at things that are allowed but often unintended, such as unsupported HTML. Fix errors first, then look at the warnings.
Google’s Rich Results Test remains the final word for Google features; this validator explains the most common problems in plain words.
FAQPage markup must follow Google’s structure: each item is a Question with a name and an acceptedAnswer of type Answer with text. The validator finds every FAQPage in the page’s JSON-LD – or in code you paste – and checks each question and answer.
It flags HTML tags Google ignores in answers, repeated questions and answers, and markup used for content that is not a real FAQ, such as advertising. The questions and answers must also be visible on the page.
Google now shows FAQ rich results mainly for authoritative government and health sites, so most sites will not see FAQ snippets. Valid markup still helps machines understand the content.