Why does my valid schema produce no rich result?

Because schema.org validity and Google's requirements are different things. A Product with only a name is valid and shows nothing without offers, review or aggregateRating.

What date and duration formats are required?

ISO 8601 for both: 2026-09-10 for dates, PT30M for thirty minutes. Readable alternatives like "30 mins" are ignored entirely.

Does it check that the markup matches the page?

No, and nothing static can. Structured data describing content a visitor cannot see risks a manual action, and that judgement is yours.

JSON-LD Validator

Check JSON-LD structured data against the properties search engines actually require.

Runs in your browserNo account neededFree

Processing: This tool runs entirely in your browser. Your input and any file you open stay on your device — nothing is uploaded to a server.

How to use the json-ld validator

Paste JSON-LD, or paste the whole page and extract it.
Fix the errors: those are properties without which nothing appears.
Treat the warnings as the difference between a result and a good one.

About this tool

This checks against Google's documented requirements for rich results rather than schema.org's vocabulary, and the difference is the whole point. schema.org accepts almost anything: a `Product` with nothing but a name is perfectly valid structured data. Google requires `offers`, `review` or `aggregateRating` before it will show anything, so that valid markup produces no rich result, no error and no explanation.

The types covered are the ones that actually produce results — Article, Product, FAQPage, BreadcrumbList, Organization, LocalBusiness, Recipe, Event, VideoObject, HowTo, JobPosting and a few others — with required properties reported as errors and recommended ones as warnings.

Two formats catch people repeatedly. Dates must be ISO 8601, so `2026-09-10` rather than `10/09/2026`. Durations must be ISO 8601 too: `PT30M`, not "30 mins" — and a recipe with a human-readable cooking time has no cooking time at all as far as a search engine is concerned.

`@graph` is followed, nested objects are checked, and JSON-LD can be pulled straight out of a pasted page, since that is usually how people have it rather than as a bare document. What no static check can tell you is whether the markup matches what the page actually shows — structured data that describes content a visitor cannot see is a manual-action risk, and that judgement stays with you.

Common uses

Checking structured data before a page goes live.
Finding why a rich result never appeared.
Auditing markup generated by a plugin or CMS.

Frequently asked questions

Why does my valid schema produce no rich result?: Because schema.org validity and Google's requirements are different things. A Product with only a name is valid and shows nothing without offers, review or aggregateRating.
What date and duration formats are required?: ISO 8601 for both: 2026-09-10 for dates, PT30M for thirty minutes. Readable alternatives like "30 mins" are ignored entirely.
Does it check that the markup matches the page?: No, and nothing static can. Structured data describing content a visitor cannot see risks a manual action, and that judgement is yours.

Related tools

FAQ Schema Generator

Build FAQPage JSON-LD from your questions and answers, ready to paste into a page.

Article Schema Generator

Generate Article or BlogPosting JSON-LD with author, dates and image.

Product Schema Generator

Generate Product JSON-LD with price, availability, brand and rating.

JSON Formatter

Format, validate and minify JSON with clear error messages that point at the exact position.