Schema Markup Checker
Or check the page you are on and scan whole sites with the Every type at a glance
One card per entity: Product, Article, Recipe, Organization. Green when it is clean, red when it is broken. Details open only when you need them.
Free · JSON-LD & Microdata · No signup
Schema markup checker for pages that should earn rich results
Paste a URL. We extract the structured data, validate every type and property against schema.org, apply Google's rich result rules, and show you the exact line to fix.
Or check the page you are on and scan whole sites with the Chrome extension.
Why use this structured data validator?
Google's own testing tools tell you whether a page passes. This one tells you what is on the page, what is wrong, where, and how to fix it.
The exact line to fix
Syntax errors come with line and column. Wrong values are marked right inside the JSON. Every issue has a plain-language hint.
Google rich result rules
Required and recommended properties for Article, Breadcrumb, FAQ, Product, Review snippet and 11 more, straight from Google's documentation.
Full schema.org vocabulary
Unknown types, misspelled properties, wrong case, values of the wrong kind, properties that do not apply to the type, unresolved @id references.
JSON-LD and Microdata
Both formats are extracted from the same page and shown the same way, so a Microdata product and a JSON-LD breadcrumb sit side by side.
Share, export, automate
Every report has a link you can send to a developer or client, a CSV export for audits, and a JSON API for CI checks and monitoring.
How the schema checker works
- 1
Enter a page address
We fetch the page like a search engine crawler and pull out every application/ld+json script and every Microdata item.
- 2
Three layers of validation
JSON syntax, schema.org vocabulary and Google's rich result requirements, each with stable issue codes you can filter and export.
- 3
Fix with the line in front of you
Open a type, see its issues with the path to the property, show the JSON with the offending line marked, copy it, share the report.
One page or the whole site
The web checker is the quickest way to test a URL. The Chrome extension goes further.
Check a page here
- Any public URL, no account
- Report link to share with your team
- CSV export and JSON API
- Whole-site scan up to {max} pages, report by link
Chrome extension
- Checks the page as your browser renders it, JavaScript-injected markup included
- Highlights Microdata items right on the page
- Scans a whole website from its sitemap and links, with a CSV of every issue and the pages it is on
Rich Results Test vs Schema Markup Validator vs this checker
Google split its old Structured Data Testing Tool into two. Here is what each one shows.
| Google Rich Results Test | Schema.org Markup Validator | Schema Markup Checker | |
|---|---|---|---|
| Lists every type on the page | Only rich-result types | Yes | Yes |
| Google required and recommended properties | Yes | No | Yes |
| Unknown or misspelled schema.org terms | No | Yes | Yes |
| Value formats: dates, URLs, durations, enumerations | Partly | Partly | Yes |
| Shows the offending line in the JSON | No | Highlights the block | Line marked, with a hint |
| Shareable report link, CSV, JSON API | No | No | Yes |
| Whole-site scan | No | No | Chrome extension |
| JavaScript-rendered markup | Yes | No | Chrome extension |
Built for the people who ship structured data
SEO specialists
Audit a landing page or a client's whole site, and hand over a CSV that says exactly what to change.
Developers
Validate JSON-LD in staging before release, and wire the JSON API into CI so a broken schema never reaches production.
Content teams
Check that every recipe, article and product page keeps its rich result after an edit or a template change.
Agencies
Run the same check across every client site and report with shareable links instead of screenshots.
Frequently asked questions
What does the schema markup checker validate?
Three layers. Syntax: the JSON-LD parses and every Microdata item is well-formed. Vocabulary: every type and property exists in schema.org, is spelled with the right case, applies to that type, and has a value of the right kind (dates, URLs, durations, enumerations). Google: the required and recommended properties for rich results such as Product, Article, Recipe, Event, FAQ, Breadcrumb, Job posting, Video and Local business.
Is this a replacement for Google’s Structured Data Testing Tool?
Yes, for the day-to-day job that tool did: paste a URL, see every entity on the page and what is wrong with it. Google retired the Structured Data Testing Tool and split it into the Rich Results Test and the Schema Markup Validator. This checker combines both views in one report and adds the exact line of each problem.
How is it different from the Rich Results Test?
The Rich Results Test only reports types Google shows as rich results and says little about other schema.org markup. Our report lists every type on the page, marks which are eligible for Google rich results, and shows vocabulary mistakes the Rich Results Test ignores, such as a property that does not exist or a misspelled type. It also shows the JSON with the offending line marked, and you can share the report link or download a CSV.
Which formats are supported: JSON-LD, Microdata, RDFa?
JSON-LD and Microdata are fully extracted and validated. RDFa is detected and reported, but not validated yet.
Does the checker see structured data added by JavaScript?
The web checker fetches the raw HTML, like a crawler would, so markup injected by scripts or tag managers is not seen. The Chrome extension runs inside your browser after the page renders and sees everything, including JavaScript-generated JSON-LD.
Can I check a whole website instead of one page?
Yes, with the Chrome extension. It discovers pages through the sitemap and internal links, checks each one, and builds a report of every type and issue across the site with the pages they occur on. Results export to CSV.
Is there an API?
Yes. GET /api/check?url=... returns the full report as JSON: entities, statuses, issues with codes, locations and hints. It is free, rate-limited to 30 requests per minute, and needs no key.
Do you store the pages I check?
A report is cached in memory for five minutes so repeated checks and shared links are fast. Nothing is written to a database, and there is no account.
JSON API for CI and monitoring
The same report as JSON. Fail a build when a required property goes missing, or poll your key pages daily.
GET /api/check?url=https://example.com/page
{
"report": {
"summary": { "errors": 1, "warnings": 3, "items": [ { "type": "Product", "status": "errors" } ] },
"issues": [ { "severity": "error", "code": "google/missing-required", "property": "image", "hint": "…" } ]
}
}30 requests per minute per IP. Add &fresh=1 to bypass the five-minute cache.