JSON-LD Validator

What this tool is used for

• Checking structured data parses before relying on it for a rich result.
• Finding which required property a schema type is missing.
• Validating markup after a template change that touched the JSON-LD block.
• Comparing two pages' structured data to find why one is eligible and the other is not.
• Checking a block copied from documentation before shipping it.

Frequently Asked Questions

What do @context and @type do?

`@context` maps your property names onto a vocabulary — for structured data that is almost always `https://schema.org`. `@type` says what the thing is: Article, Product, FAQPage. Without both, the block is valid JSON and meaningless as structured data.

Why does Google ignore my valid markup?

Valid is not the same as eligible. Each rich result has its own required properties — a Product needs a name plus an offer, review or rating — and Google also requires the marked-up content to be *visible on the page*. Invisible structured data is a policy violation, not a shortcut.

Should I use JSON-LD, Microdata or RDFa?

JSON-LD, which Google explicitly recommends. It sits in one script block instead of being woven through your HTML, so it survives a template change and can be generated server-side without touching the markup.

What is @graph for?

Expressing several linked entities in one block — an Organization, a WebSite and a WebPage that reference each other by `@id`. It avoids repeating the same organisation object in three places, and it is how most CMS plugins emit their markup.

Does structured data improve rankings?

Not directly — Google has been consistent that it is not a ranking factor. What it can do is win a richer result: stars, prices, FAQs or a recipe card. That changes click-through rate, which is worth more than a ranking nudge anyway.

Does markup have to match the visible page?

Yes, and this is the rule most violations break. Structured data describing content a visitor cannot see — a price, a rating, an author not shown on the page — is a policy violation, and enforcement removes rich results site-wide rather than for one page.

Common errors and gotchas

• Assuming valid markup produces a rich result, when eligibility is necessary but not sufficient.
• Describing content that is not visible on the page, which is a policy violation.
• Using a property that exists in schema.org but is not one Google reads for that result type.
• Nesting objects without `@type`, which leaves the parser unable to interpret them.
• Producing several conflicting blocks on one page, where the parser picks unpredictably.