Why it matters
Structured data is how search engines and AI assistants understand what a page is: a product with a price, an event with a date, a business with opening hours. Mistakes don't show on the page, so they go unnoticed until rich results disappear.
This validator checks your JSON-LD offline against Schema.org and Google's documented requirements, including the details that often break: ISO dates, absolute URLs, currency codes and enumeration values. The Schema Generator writes JSON-LD; this one checks what you already have.
How it works
- InputA page's HTML or JSON-LD
- In your browserChecked against Google's required fields
- OutputErrors, recommendations and eligibility
Where it fits in a designer's workflow
- Plan
- Design
- Build
- Test
- Launch
By the numbers
Show the numbers as a table
| Type | Errors | Recommended missing | Rich result | Eligible |
|---|---|---|---|---|
| Organization | 1 | 2 | Organization logo | no |
| Product | 2 | 8 | Product snippet | no |
| BreadcrumbList | 1 | 0 | Breadcrumb | no |
| Event | 0 | 9 | Event | yes |
How to use it
- Paste a page's HTML or a JSON-LD object.
- Read the list of items and their problems.
- Fix errors first, then recommended properties.
- Re-check, then confirm with Google's Rich Results Test after publishing.
FAQ
Is this the same as Google's Rich Results Test?
It checks the same documented rules for the common types, without needing a public URL. Google's test is the final word for eligibility.
Does it read Microdata or RDFa?
No, JSON-LD only, which is the format Google recommends.
What's the difference between errors and warnings?
Errors are missing required properties or invalid values that stop a rich result. Warnings are recommended properties that make one more likely or richer.
Is anything fetched?
No. It reads only what you paste.
