JSON-LD Inspector

Q: Does this tool fix or generate JSON-LD?

No. It is report-only: it extracts JSON-LD, pretty-prints it, and flags parse errors or common schema property gaps without rewriting your data.

Q: Why does URL fetching use a proxy?

getdevtool is a static browser app, and browsers block many cross-origin fetches. The backend proxy fetches public pages so the inspector can analyze their HTML.

Q: Can it inspect localhost or authenticated staging pages?

Use the Paste HTML tab for pages the proxy cannot reach, including localhost, private networks, staging behind auth, or pages requiring cookies.

Q: Will it see JSON-LD rendered by client-side JavaScript?

URL fetches analyze the server-returned pre-JS HTML. JSON-LD injected later by an SPA may not appear until JavaScript rendering support is added.

Inspect JSON-LD structured data from a public URL or pasted HTML/JSON. The report extracts each application/ld+json block it finds, including nested @graph nodes, and flags parse errors plus missing common required or recommended schema properties. It is a syntax and property check, not a full Google rich-result validator.

URL fetches use the DevTools proxy

This static page cannot fetch arbitrary cross-origin URLs directly in the browser, so public URL checks go through the backend proxy. Use Paste HTML for localhost, authenticated, or staging pages.

Report-only structured data review

This inspector reports what it finds and highlights common schema gaps. It does not generate or auto-improve JSON-LD.

URL to inspect

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.

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.

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.

JSON-LD Inspector

JSON-LD inspection examples

Common mistakes

FAQ

Does this tool fix or generate JSON-LD?

Why does URL fetching use a proxy?

Can it inspect localhost or authenticated staging pages?

Will it see JSON-LD rendered by client-side JavaScript?

See also