Schema markup validator
Paste JSON-LD or a page's HTML. Every problem gets a numbered proof mark in the margin, a plain-English fix and the Google or schema.org rule behind it.
Paste JSON-LD or a page's HTML, or load a sample. Results appear as you type; nothing is sent anywhere.
Checking a live page? Test a URL. Only need to know why JSON won't parse? JSON-LD syntax check.
What this schema checker looks for
Structured data fails in layers. A syntax slip makes Google discard the whole block ("Unparsable structured data"). Past that, a misspelt property is silently ignored, a price written as "$89.00" is rejected, and a Product with no offers, review or aggregateRating is simply not eligible for a product snippet.
The validator runs those layers in order and sorts findings by severity:
- error breaks parsing or a documented requirement. The item can't get that rich result until it's fixed.
- warning a recommended property is missing, a name looks misspelt, or a value is ambiguous. Worth fixing, not fatal.
- note context: a retired feature, a short-form enumeration, markup Google ignores.
Rules come from Google's structured data search gallery and each feature's documentation page, with types and properties checked against schema.org. The requirements table lists them all.
What a validator does, in five passes
Step through the passes. Each one can only catch the mistakes that survive the one before it.
1. Find
Locate every <script type="application/ld+json"> in the HTML. Markup injected later by JavaScript only exists in the rendered page.
Catches: No markup at all; markup only in the rendered DOM; wrong script type.
Validated examples by type
Each example passes this validator, with the required properties marked and the mistakes people make most often.
- Articlearticle schema example
- Productproduct schema example
- FAQPagefaq schema example
- Reciperecipe schema example
- Eventevent schema example
- LocalBusinesslocal business schema example
- Organizationorganization schema example
- BreadcrumbListbreadcrumb schema example
- VideoObjectvideo schema example
- JobPostingjob posting schema example
- Reviewreview snippet schema
Questions
Is this the same as Google's Rich Results Test?
No. StructuredValidator is an independent checker. It applies the required and recommended properties from Google Search Central's structured-data docs plus schema.org vocabulary checks, and explains each problem. Google's Rich Results Test renders your page with Googlebot and is the final word on what Google can read; use both.
Does valid markup guarantee rich results?
No. Valid markup only makes a page eligible. Google says it decides whether to show a rich result based on many factors, including content quality and the search itself.
What does it check?
JSON syntax (with line and column), @context, types and property names against schema.org, value formats (ISO 8601 dates and durations, prices, currencies, URLs, enumerations), @id references, and per-feature required and recommended properties for Article, Product, Review, Recipe, Event, LocalBusiness, Organization, Breadcrumb, Video, JobPosting, SoftwareApplication and more. It also flags retired features such as FAQ and How-to.
Is my markup uploaded?
Not by the validator: it runs entirely in your browser. Only two optional actions contact our server: testing a URL (we fetch that page for you) and "Explain and fix with AI" (the markup and findings are sent to an AI model to write the explanation).
Does it check microdata or RDFa?
It detects them in pasted HTML and tells you they are there, but it validates JSON-LD only, the format Google recommends.
What is the difference from validator.schema.org?
The Schema Markup Validator checks your markup against the full schema.org vocabulary but says nothing about search features. This tool checks a curated slice of the vocabulary and adds the rich-result requirements and plain-English fixes.