IZN Tools

JSON-LD Validator

Parse structured data and list what Google will reject.

A whole script tag can be pasted
INPUT
FINDINGS

Waiting for input

Structural checks only — this is not Google's rich results test
Computed on this device
Related
Schema Markup GeneratorJSON FormatterMeta Tag AnalyzerOpen Graph GeneratorRobots.txt GeneratorUTM Link Builder

Three ways structured data fails silently

None of these produce an error. All of them mean the markup does nothing:

  1. The JSON does not parse. A trailing comma, a smart quote pasted from a document. The whole block is skipped.
  2. A required property is missing. An Article without a headline, a Product without a name. The type is recognised and then discarded.
  3. A date is not ISO 8601. 27/08/2026 instead of 2026-08-27. The property is ignored and everything else carries on.

The third is the one that survives review, because the value looks like a date to a person reading the file.

The rule that gets sites penalised

Markup must describe what a visitor actually sees. FAQ entries that appear nowhere on the page, review aggregates with no reviews, a price different from the displayed one — all are grounds for a manual action, and the recovery takes far longer than the rich result was worth.

If the FAQ block is rendered by JavaScript that does not run for crawlers, the markup is describing content that, as far as the crawler is concerned, is not there.

Where it goes

One <script type="application/ld+json"> in the served HTML. Position does not matter; being in the initial response does. Structured data injected after hydration is unreliable.

Questions

Is this Google's rich results test?+

No, and it cannot be. This checks structure — valid JSON, a @context, a @type, the properties each type requires, ISO dates. Whether Google grants a rich result depends on its own policies and on the page around the markup, which no offline tool can know.

Why does a wrong date format matter so much?+

Because Schema.org accepts only ISO 8601, and anything else is not parsed as a date — it is simply ignored. `27/08/2026` does not produce an error anywhere; the property just does not exist as far as a consumer is concerned, and the rich result quietly does not appear.

Can I paste the whole script tag?+

Yes. The wrapping `<script type="application/ld+json">` is stripped before parsing, because copying the tag along with its contents is what everyone actually does.

What does 'no rich result exists for this type' mean?+

That the type is valid Schema.org but Google has no enhanced display for it. The markup is not wrong — it may help other consumers understand the page — but it will not change how the result looks.