Paste JSON-LD to identify JSON syntax errors and review selected structured-data fields. The checker supports JSON objects, arrays, and graph entries, helping you inspect generated markup before it is added to a page.
How to Use JSON-LD Syntax Checker
- Copy JSON-LD without its surrounding script element.
- Paste the JSON and run the check.
- Fix parsing errors, then review missing fields and unsupported type notices.
- Check factual accuracy and feature-specific requirements before publishing.
Separate JSON syntax from schema requirements
A JSON document can be syntactically valid while still lacking useful schema information. This tool first parses the supplied JSON, then checks context, type, and selected fields for Article, LocalBusiness, Product, FAQPage, and BreadcrumbList entries. It flags unsupported field checks rather than pretending to validate every vocabulary type.
Example: valid JSON with missing information
An Article object containing only a type can parse correctly but receive a missing-headline prompt. A malformed comma or quotation mark can prevent parsing entirely. For a graph, a context on the root can apply to its contained entries; the table lets you review each detected node.
Check the published page separately
Paste JSON without surrounding script tags. Once syntax is correct, confirm that the values match the visible content and that your website actually outputs the intended JSON-LD. Use a schema-aware validator for broader vocabulary checks and the appropriate search-engine tool for any currently supported search feature.
The Schema Markup Generator provides supported starting structures. The On-Page SEO Checker can help with a separate review of the page metadata and source HTML.
Key Features
- Browser-based processing
- Example inputs
- Copy and download results
- No paid API or signup
Common Use Cases
- Website publishing
- Content review
- SEO maintenance
Privacy
Your supplied content is processed in your browser and is not uploaded by this tool.
Limitations
This checks syntax and selected fields, not the full Schema.org vocabulary or Google eligibility.