Product block
{"@context":"https://schema.org","@type":"Product","name":"Acme Backpack"}The Product type is detected and the report flags recommended fields such as image, description, brand, sku, or offers.
JSON-LD Inspector
Report only
Extract JSON-LD blocks, inspect Schema.org types, and flag syntax or common-property gaps from a URL, HTML, or raw JSON.
URL fetches use the DevTools proxy
Report-only structured data review
Fetch a public URL or paste HTML/JSON-LD to see parsed blocks, schema types, property-check issues, and pretty JSON.
How to interpret this report
Errors mean invalid JSON or missing properties the built-in checklist treats as required for a recognized schema type. Warnings are commonly recommended properties or useful optional signals. Info messages mean the type was detected but there is no built-in property checklist for that schema type.
JSON-LD inspection examples
Inspect each application/ld+json block independently, then review the detected Schema.org types and property checklist findings.
Graph block
{"@graph":[{"@type":"WebSite"},{"@type":"Organization"}]}Nested typed nodes are extracted so each @graph entry can be reviewed.
Common mistakes
- Pasting JavaScript object literals instead of valid JSON.
- Forgetting @context on otherwise typed structured data.
- Assuming an info message means the schema type is invalid; it may only lack a built-in checklist.
Examples and guidance reviewed .
