✦ tomai
Free · SEO Tools

JSON-LD Validator

Paste your structured data and check it against Schema.org — valid JSON-LD, missing required fields, and the issues Google cares about.

0
Validation runs live as you type.
Paste some JSON-LD above to validate it.

Validate before Google rejects it

Syntax check plus required/recommended property auditing against schema.org expectations — errors explained plainly, not parser dumps.

📏

Line-precise syntax errors

Broken JSON reports the exact line and column of the problem, so you can jump straight to the fix instead of hunting through a minified block.

🧠

Google-minimum requirements

The built-in vocabulary covers ~35 rich-result types and enforces what Google requires for each — missing required fields are surfaced as errors, not silent failures.

🔒

Catches rich-result errors

Everything runs in your browser. Your markup is never uploaded, stored or shared — the validator works even with your internet connection off.

Validation layers

Frequently asked questions

Why does Google show "not eligible for rich results" for my page?

Usually one of these: a required field is missing (for example datePublished on an Article), the @context is missing or wrong, or a property has the wrong value shape — a date that is not ISO 8601, a URL without http(s), or a priceCurrency that is not a 3-letter code. Paste your JSON-LD here and the validator lists every problem it can find.

Are unknown types or properties always errors?

No. Schema.org explicitly allows extension, so the validator reports unknown types and properties as warnings. Only errors — broken JSON, missing @context, missing required fields — mean Google will not read your markup. Warnings tell you what a validator with a larger vocabulary would flag.

Does it support @graph and full schema.org URLs?

Yes. @graph arrays are validated element by element, and type or property names written as full URLs (https://schema.org/Article) are normalized automatically. Dates must be ISO 8601 (2026-08-01 or 2026-08-01T12:30:00Z); currencies must be 3-letter ISO codes.

Related tools

What is a JSON-LD Validator?

JSON-LD is the script block search engines parse when deciding whether a page earns a rich result: the headline and author of an article, the price of a product, the steps of a recipe, the questions of an FAQ. One misplaced comma or a date in the wrong shape can make Google silently skip the whole block. This validator reads pasted markup in three layers: whether the JSON parses, with exact line and column of any break, whether the shape is sound with a valid context plus well-formed type and graph nodes, and whether types, properties and values match the vocabulary, down to dates, URLs, prices, currencies, ratings and integers.

Checks inside the verdict engine

  • 🧾 JSON syntax pass pinpointing line and column instead of failing silently
  • 🧩 Shape pass over context, type and graph structure, including nested and multi-node documents
  • 📚 Vocabulary pass against a built-in subset of about seventy schema types, flagging missing required fields per type
  • 🏷️ Unknown types and properties marked as warnings, never hard errors, since extensions are legal
  • 🔢 Value-shape tests for ISO dates, addresses, prices, three-letter currencies, ratings, integers and arrays
  • 🏷️ Detected-type chips plus error and warning counts, with a one-click sample Article for learning

Moments when validation pays for itself

  • 📰 Before publishing an article, recipe or event page whose rich result you count on
  • 🔧 After hand-editing generator output, when one renamed field can void the block

What the verdict cannot promise

  • 📖 The built-in vocabulary is a practical subset of the full tree, so rare types surface as warnings to confirm elsewhere
  • ✅ Green means well-formed and eligible, while Google alone decides whether a rich result shows

Your markup is checked on the spot in this browser tab and never transmitted anywhere, so drafts and client copy stay private by construction, which is the entire privacy story of this page.

Last updated · 2026-09-01

Related tools