Free Schema Markup
Validator
Test JSON-LD, Microdata, and RDFa structured data on any URL. See exactly what schema types Google's crawler detects on your page, in seconds. It reads the same schema.org vocabulary a schema org validator checks against, and reports what Google actually picks up.
See the structured data Google reads on your page.
Paste any URL. In seconds you get every JSON-LD block, the schema types detected, what parses and what is broken, and the raw markup to fix, for JSON-LD, Microdata, and RDFa.
Broken schema fails silently.
Structured data is invisible on the page, so nothing tells you when it breaks. A crawler either reads clean markup and shows you a rich result, or hits a snag and moves on. The gap between those two outcomes is one property you cannot see. This tool makes it visible.
One URL in. A full read out.
Paste a URL
Any live page. A bare domain works too, we add https for you before we fetch.
We fetch and scan it
We pull the page like a browser and read every JSON-LD script block, plus itemscope Microdata and schema.org RDFa vocab.
You get the report
The counts, the list of detected types, valid or broken per block with the exact parse error, and the raw JSON to fix.
What these words mean
Structured data
Extra labels in your page code that state what the content is: this is a product, this is its price, this is a rating. Meaning stated, not guessed.
Also called schema markupJSON-LD
The format Google recommends. A single script block, separate from your visible HTML, so it is easy to add and hard to break.
a <script type="application/ld+json"> blockschema.org type
The vocabulary label for a thing: Article, Product, FAQPage, Organization. The type has to match what the page actually is.
A shop page is a ProductRich result
The enhanced Google listing schema can earn: review stars, price, breadcrumbs, an FAQ drop-down. Valid schema makes you eligible, it does not guarantee it.
Star rating under a resultRequired vs recommended
A required property is mandatory: leave it out and the page is ineligible, an error. A recommended one is optional: skip it and you still qualify, a warning.
Product needs a name; an image is recommendedMicrodata and RDFa
Two older ways to write the same schema, inline in your HTML with attributes instead of a script block. This tool counts those too.
itemscope / itemtype and vocab / typeofSee every type the crawler finds.
The validator reads the whole page, follows nested @graph and arrays, and lists every schema.org type it detects across your JSON-LD, so you can confirm the right ones are present and spot any that should not be there.
- Deep @type extraction through @graph, arrays, and nested nodes
- Each distinct type listed once, drawn from every valid block
- Types written as Microdata or RDFa are surfaced as well
Why it works: Google matches each type to a specific rich result. If the type is not detected, the result it unlocks cannot appear, no matter how good the page is.
Catch the block that silently fails.
Every JSON-LD block is parsed on its own. A valid one is confirmed; a broken one is flagged with the exact JSON error and the raw markup, so you fix the real line instead of guessing where it went wrong.
- Each JSON-LD script block parsed independently
- Invalid blocks flagged with the exact JSON error message
- Raw, pretty-printed markup shown for every block
Pro tip: one invalid block warns you nowhere, Google just drops it. A quick re-check after any deploy catches it in seconds.
Know what blocks a result vs what just trims it.
For the common rich-result types, the validator checks each block against schema.org required and recommended properties, so a missing required field, an error, is never buried next to a merely recommended one, a warning.
- Required properties checked per type, a miss is an error
- Recommended properties flagged as warnings, not errors
- Covers Product, Article, LocalBusiness, FAQPage, and more
Rule of thumb: fix every error first, they are what make a page ineligible. Then fill the recommended fields to give Google more to show.
Everything the report puts in front of you.
All three formats
JSON-LD, Microdata itemscope tags, and schema.org RDFa vocab, all counted in one pass.
Raw JSON per block
The full, pretty-printed markup of each block, so you can read and copy the exact structured data.
Exact parse errors
When a block is invalid, the real JSON error message, not a vague note that something is wrong.
Deep type extraction
Follows @graph, arrays, and nested nodes, so a type buried three levels down still shows.
Honest fetch reporting
If the page blocks bots or renders schema in JavaScript, it says so, instead of pretending there is none.
No signup, unlimited
Test as many URLs as you want, free, with no account and no rate limit on this page.
How to turn a report into a fix.
A pile of counts is only useful if you know which one to act on. Here is the exact read on our example page, the product page at yourstore.com, the way an experienced SEO would think it through.
From a hidden field to a confident ship.
Confirm you qualify
See in seconds whether your key pages carry the schema that earns rich results, with no code to read and nothing to set up.
Verify the markup shipped
Paste the live URL after a build and confirm the JSON-LD renders with every required property, so a template change did not quietly break it.
Audit before it costs you
Check schema across templates and catch a missing or mistyped property before it drops a page out of rich results and the traffic they bring.
Ship articles that qualify
Confirm each new post carries Article schema with a headline, date, and author before it goes live, not after the listing looks plain.
Questions, answered.
A live fetch of the URL you enter, read like a browser. You are checking the real HTML Google's crawler sees, not a saved copy. It uses a normal browser user agent, and falls back to a Googlebot one if a site blocks it.
Both. It confirms each block is valid JSON, then validates the common rich-result types, Product, Article, LocalBusiness, FAQPage, and more, against their required and recommended properties, so you see a real gap, not just a syntax pass.
No, and any tool that promises that is wrong. Valid schema makes you eligible; Google decides what to show. It has also narrowed some results: FAQ rich results now appear mainly for authoritative government and health sites, and HowTo results were retired for everyone. Product, Article, Breadcrumb, and Review remain widely shown.
It reads the HTML as returned by the server. If your schema is injected client-side by React or Next, the tool flags the page as likely JavaScript-rendered rather than reporting no schema, so you know to test the rendered output instead.
Yes, 100% free. No signup, no credit card, and no rate limit on this page. Paste as many URLs as you like. A free Metric Vault account adds nine more SEO tools and a handful of premium reports each month, but this validator needs none of that.
Google's test only checks the handful of types it can render and hides the rest. This shows everything on the page, every type, valid or broken, with the raw JSON, so you get the full map at a glance. Use both: this for the whole picture, Google's for its specific eligibility.
Paste a URL and see what Google reads.
In seconds you will have every schema block on the page, the types detected, what is valid, what is broken, and the raw markup to fix. It takes one URL.
See if AI actually recommends you
The checker tells you if AI can read your site. Metric Vault tracks whether ChatGPT, Gemini, Perplexity and Claude actually mention you, how you stack up against competitors, and how it trends over time, plus the rest of the platform's 60+ SEO and AI tools.