free tool

Schema.org validator

Validate your JSON-LD structured data against schema.org's required fields — paste the markup or fetch it live from a URL. Pairs with our Schema generator.

Build valid markup → Schema generator

What this tool checks

A JSON-LD validator checks whether your structured data parses correctly and includes the properties schema.org marks as required or recommended for each type — Article, Product, FAQPage, Organization, and the rest. Missing or malformed fields silently disqualify a page from rich results in Google and make your facts harder for AI engines like ChatGPT and Perplexity to parse and cite. Validating before you publish catches the errors that quietly cost you eligibility.

What it looks at

Valid JSON-LD syntax
The markup must be well-formed JSON inside a <script type="application/ld+json"> block; a trailing comma or an unquoted key makes the entire block invisible to parsers.
@type recognition
The @type value must match a real schema.org type such as Product, Recipe, or FAQPage; a typo or invented type stops engines from mapping your data to a known entity.
Required properties
Each type has properties schema.org and Google treat as required — for example name and offers on Product — and a page missing them cannot qualify for the matching rich result.
Recommended properties
Beyond the required set, properties like aggregateRating or image strengthen a snippet and give AI engines more citable facts, even though their absence won't block eligibility.
@context declaration
The block must declare "@context": "https://schema.org" so parsers know which vocabulary the property names belong to.
Value type correctness
Properties expect a specific value shape — a date in ISO 8601, a price as a number, a URL as an absolute link — and the right shape is what lets a machine actually use the value.

How to use it

  1. Paste your JSON-LD markup, or enter a page URL to pull its structured data straight from the live HTML.
  2. Review the flagged errors and warnings — missing required properties, unrecognized types, and syntax faults are listed per block.
  3. Fix each required-field gap in your markup, then re-validate until the block is clean before you publish.

Frequently asked questions

What's the difference between required and recommended schema properties?

Required properties are the minimum a type needs to be eligible for a rich result — omit one and Google won't render the enhanced snippet. Recommended properties are optional extras that improve the snippet and give AI engines more to cite, but their absence won't disqualify the page.

Does valid JSON-LD guarantee a rich result in Google?

No. Valid, complete markup makes a page eligible, but Google decides whether to actually show a rich result based on content quality, page policy, and query context. Validation removes the technical blockers; it doesn't force the enhancement.

Why use JSON-LD instead of Microdata or RDFa?

JSON-LD is the format Google explicitly recommends because it lives in one script block, separate from your visible HTML, making it easier to add, maintain, and validate. Microdata and RDFa are still supported but interleave markup with content, which is more error-prone.

Can I validate structured data on a page that isn't live yet?

Yes — paste the raw JSON-LD directly instead of fetching a URL, and the validator checks the markup on its own. The URL fetch is for auditing pages that are already published.

share the result Useful result? Send it to a teammate: Telegram WhatsApp X
this is just one tool

This audit is 1 of 85 operations in seo·matrix

Free tools show you WHAT to fix. The full audit + the autonomous team of 20 AI agents fix it end-to-end — strategy, content, GEO, internal links, publishing and day-2 upkeep.

All free tools →