Check JSON-LD schema markup
Validate Schema.org JSON-LD before it goes into a page template, CMS field, or ecommerce theme. Paste a JSON-LD object, an array, a graph document, or the HTML that contains the structured data script.
The report separates syntax errors from structured-data warnings. Invalid JSON stops parsing. Valid JSON-LD is then checked for detected types, missing @context, missing @type, required fields for common schema types, relative URLs, duplicate root @id values, and supported rich result rules.
JSON-LD vs rich result eligibility
JSON-LD can be valid and still fail a search feature. A Product node with @type and name is parseable, but it may still be missing image, offers, price, or priceCurrency fields expected by product result guidelines.
Use the error count for blocking fixes first. Then read warnings for fields that can change search understanding or rich result eligibility.
Pasted HTML
Auto mode handles two common inputs. If the text starts with { or [, it is parsed as JSON. Otherwise the validator looks for <script type="application/ld+json"> blocks inside the pasted HTML.
This is useful when copying from a rendered page source, CMS preview, or tag manager output. Each script block is counted separately so broken markup in one block does not hide problems in another.
Common schema mistakes
Structured data failures often come from small mismatches: http://schema.org mixed with custom contexts, a graph node without @type, a FAQPage question without acceptedAnswer.text, a BreadcrumbList without positions, or a relative image URL where an absolute URL is expected.
The validator reports the path and field names where it can. For graph documents, check the detected types list first, then move through the errors from top to bottom.