ToolsHub
SEO Tools

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
Analyse pasted HTML or JSON-LD instead

How to use FAQ Schema Validator

  1. Enter the page URL, or paste HTML or JSON-LD.
  2. Click “Validate FAQ schema”.
  3. Fix the errors first, then the warnings.
  4. 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.

Product Schema Validator Make sure your product pages describe products the way search engines expect. The… Schema Markup Generator Fill in a form and get valid JSON-LD structured data for your page. Choose from… Breadcrumb Schema Generator Breadcrumb markup lets Google show your site’s structure – Home › Bikes › Road… JSON Validator Find out whether your JSON is valid and, if it is not, exactly where and why.…

FAQPage markup in short

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.

Privacy: the address you enter is fetched by our server only to run this check. The downloaded HTML is passed to your browser for analysis and is not stored, and the results are not saved on our side. Requests are rate-limited to keep the service fair for everyone, so if you check many pages in a row you may need to wait a few minutes.

Limits: pages are read up to 2 MB of HTML, redirects are followed up to eight hops and each request has a short timeout. Pages behind a login, servers that block automated requests and content added only by JavaScript cannot be analysed this way; for those, copy the page source from your browser and use the paste option where it is available.

Tip: fix the problems marked red first, because they matter most. Yellow warnings are worth reviewing but are often harmless in context, and blue notes are information. After a change, run the check again to confirm the result – search engines pick up the change on their next visit to the page.

Other useful tools