Validate JSON-LD structured data.
Paste a <script type="application/ld+json"> block or a raw
JSON-LD document, or fetch a live page. The validator extracts every
@type it can find, walks each object against Schema.org's required
and recommended fields, and surfaces format issues like non-absolute URLs,
bad ISO 8601 dates, or invalid priceCurrency values.
Input
Either a single JSON-LD document or a chunk of HTML that contains
<script type="application/ld+json"> blocks will work. Past
data never leaves the page.
Fetched via the HeaderPilot worker proxy
(headerpilot-csp-checker-proxy.hpb21.workers.dev) so the request
is not blocked by CORS. The validator reads every
application/ld+json block from the response.
Related reading
Where structured data fits in the broader site audit checklist.
Meta Tag & OpenGraph Inspector
Audit the rest of the page's <head> — title, description, canonical, OpenGraph, Twitter card.
sitemap.xml Validator
Confirm the URLs that contain this JSON-LD are reachable, indexable, and listed in your sitemap.
Security Headers Checker
JSON-LD is only useful if the page actually serves — audit the headers at the same time.
robots.txt Generator & Tester
Make sure the crawlers that consume structured data are not blocked at the front gate.
CSP Generator
Strict CSP and rich JSON-LD usually coexist fine — generate the policy here.
What is CSP
Background reading on the broader security baseline this site helps you ship.