JSON-LD Syntax and Required-Property Checker

Paste JSON-LD, or a whole page, and see syntax errors with line numbers plus missing required and recommended properties for each Google type.

How to use

What it checks and how it works

The checker works in three steps. First it parses strict JSON with the jsonc-parser library and reports each error with line and column, since Google reads JSON-LD as JSON (RFC 8259). Then it checks structure: @context, @type, and the type names against the schema.org vocabulary, release 30.1 of 16 Sep 2026, so a misspelt or wrongly cased type is named. Then it checks each node against the required and recommended properties on the Google Search Central page for its type, opened on 29 Oct 2026, including either-or rules such as Product needing one of review, aggregateRating or offers. For FAQPage and HowTo it states that Google no longer shows the rich result, and for Service and other types with no Google feature it says so and uses schema.org minimums, labelled as Zaher's. It does not fetch your page, run its JavaScript, test eligibility or judge whether the markup matches what readers see, which Google's guidelines require. Use Google's Rich Results Test for the final check.

Does a clean report mean I will get a rich result?

No. Google does not guarantee that structured data produces a result, and the markup must also match the visible page. The report only says the syntax and listed properties pass.

Which formats can I paste?

Plain JSON-LD, an array, an object with @graph, or a full page with one or more script tags of type application/ld+json. Each block is checked.

Why is a retired type shown as a warning, not an error?

The markup is still valid schema.org. The warning tells you that Google no longer shows the rich result, with the dates from its own pages.

Sources

Related tools

Privacy

Runs in your browser; nothing is uploaded. The interactive tool needs JavaScript.