Schema Validator
Validate JSON-LD markup against Schema.org and Google’s structured-data expectations. Paste your markup, get a pass / warn / error report — entirely in your browser.
Validator
Idle
Paste the contents of a script type=”application/ld+json” block. Runs locally.
Runs locally · nothing sent to a server
How it works
Paste a block of JSON-LD and the validator parses it, walks every node (including @graph arrays), and checks each one against the required and recommended properties for its @type.
Every result is graded on three levels:
- Error — a required property is missing or malformed. Google is unlikely to treat the block as a valid rich result.
- Warning — a recommended property is missing. The markup is valid but leaves rich-result coverage on the table.
- Pass — the property is present and non-empty.
It covers Article, Product, FAQPage, BreadcrumbList, Organization, Person, WebSite, and LocalBusiness, with deeper checks on nested shapes like FAQ questions, breadcrumb items, publisher logos, and product offers. Nothing you paste leaves your machine.
Frequently asked
No — think of it as a fast first pass. It catches the structural gaps (missing required and recommended fields) before you paste into Google’s tester or deploy. Google’s test additionally checks live rendering and eligibility, which needs their crawler.
No. Parsing and validation run entirely in your browser. You can validate markup for unpublished or confidential pages without anything leaving your machine.
Article / BlogPosting / NewsArticle, Product, FAQPage, BreadcrumbList, Organization, Person, WebSite, and LocalBusiness. Unrecognised types are reported but only checked for a valid @type. More types are on the roadmap.
Warnings flag recommended-but-optional properties (like dateModified or publisher.logo). Your markup can be valid without them — the warning just tells you where you could earn richer results.