Keyword Combiner
Cross three lists of words into every combination.
Check JSON-LD for syntax errors and missing required fields.
The Schema Markup Validator extracts every JSON-LD block from what you paste — a bare script or a whole page of HTML — and checks it. Syntax errors are reported with the position they occur at, and each item is measured against the properties its type requires and the ones Google recommends. It never fetches anything, so staging and unpublished pages work.
Paste a JSON-LD block, or the whole HTML of a page, and the validator pulls out every structured data script and checks it. It reports JSON syntax errors with the position they occur at, then checks each item for the properties its type requires and the ones Google recommends but does not demand.
This runs entirely in your browser, which is both its advantage and its limit. It never fetches your page, so you can validate markup on a staging site, behind a login, or on a page that is not published yet — all of which Google's own Rich Results Test cannot reach. What it cannot do is tell you whether Google will actually award a rich result, because that depends on quality signals beyond the markup. Use this to get the structure right first, then confirm eligibility with the Rich Results Test once the page is live.
Paste an entire page and each application/ld+json block is pulled out and checked separately.
A trailing comma or a smart quote is reported at the character it appears, not as a bare failure.
Required and recommended properties are checked for the common Google-supported types.
No fetch means staging sites, password-protected pages and local drafts all validate fine.
Graphs, arrays and nested objects are walked, so an error deep inside an item is still found.
A JSON-LD block on its own, or the full HTML of the page — script tags are found and extracted.
Any JSON error is reported with the character position, which is usually a trailing comma or a smart quote.
Each item is measured against what its type requires and what Google recommends on top of that.
Correct the flagged fields and paste again. Nothing is uploaded, so it is safe to test unpublished pages.
No, and it is deliberately different. Google's test fetches a live URL and tells you about eligibility for its own rich results. This one checks markup you paste, without a network request, so it works on staging, on password-protected pages and on markup that is not published yet.
Validity is the entry requirement, not the decision. Google also weighs page quality, whether the marked-up content is genuinely visible, whether the site has a history of accurate markup, and whether the query warrants a rich result at all. Valid markup makes you eligible; it does not make you chosen.
It reads JSON-LD, which is the format Google recommends and the one this site's generators produce. Microdata attributes spread through the HTML are not extracted. If you are still on Microdata, moving to JSON-LD is worth doing for its own sake.
schema.org itself marks very little as required; the requirements that matter come from Google's structured data documentation for each feature. This validator checks against those — the fields that make an item eligible — and lists the recommended ones separately.
What people who use the Schema Markup Validator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Schema Markup Validator. It takes half a minute and no account.
Write the first reviewCross three lists of words into every combination.
Split a page's links into internal, external, nofollow and broken shapes.
Steps, tools and materials as HowTo structured data.
Score a headline on length, structure, and the words that pull.
Build the short link that opens your review box directly.
Price, stock, rating and reviews as product rich snippet markup.
Build robots and X-Robots-Tag directives without guessing the syntax.
See your listing the way most people actually see it.