JSON-LD Validator
Parse JSON-LD and list every @type/@context entity it contains.
Overview
The JSON-LD Validator parses pasted JSON-LD, confirms the document is well-formed JSON, and lists every entity it contains by @type and @id, with a tree view of nested entities. It surfaces invalid @context declarations, missing required properties for common schema.org types, and properties whose values do not match the expected datatype.
Useful for SEO practitioners and developers learning how to debug JSON-LD structured data or how to find the @type of every entity in a JSON-LD block. Reach for it before submitting structured data to Google Search Console or when a page mysteriously stops showing rich results.
How it works
JSON-LD is JSON with a special @context that maps short property names (like name) to full IRIs (https://schema.org/name). The validator parses the JSON, walks every object, identifies entities by the presence of @type or @context, and resolves nested objects into a flat list of entities.
For schema.org types, the validator cross-references the vocabulary's required and recommended properties: a Product without name triggers a warning; an Article with datePublished not in ISO-8601 format is flagged. Custom @context URLs are reported but not deeply validated.
Examples
- A Product entity with nested Offer is reported as two entities, the Offer being inside the Product's
offersproperty. - An Article missing
headlineproduces a warning that Google's Article rich result requires it. - An FAQPage with three Question entities is summarised as one parent and three children.
- A typo (
@typoinstead of@type) is flagged because no entity could be identified.
FAQ
Does the tool fetch the @context URL?
No — only the JSON structure is analysed. The full IRI mapping is not resolved against the live schema.org server, which keeps the tool fast and offline-friendly.
Will it work on JSON-LD embedded in HTML?
Paste only the JSON-LD content (the contents of the <script type="application/ld+json"> block, not the surrounding HTML).
What's the difference between this and the schema validator?
This tool focuses on JSON-LD structure and entity inventory. Google's Rich Results Test additionally simulates whether the structured data would qualify for a specific rich-result feature.
How do I handle @graph?
@graph is a list of entities at the same context. The validator expands the list and reports each entry as its own entity.