Schema.org Structured Data Checker
Paste a URL and this tool fetches that page’s HTML and reports the Schema.org structured data inside it — in JSON-LD, Microdata and RDFa. It shows the entities it found and where each one sits in the document, how their terms compare with a pinned release of the Schema.org vocabulary, and what the check could not see. It works for any business — construction, automatic doors, office equipment, telecoms, professional services or anything else.
This reads one URL’s fetched HTML and the JSON-LD, Microdata and RDFa in it. It does not crawl the site or run the page’s JavaScript, and it checks terms against one pinned Schema.org release, named with the results.
Frequently asked questions
What is Schema.org structured data?
Schema.org is a shared vocabulary for describing things on a web page — a business, a product, a job, an event — in a format software can read without guessing from the prose. It can be published in several syntaxes: JSON-LD in a script tag, Microdata as HTML attributes, or RDFa, also as attributes.
What exactly does this tool inspect?
It fetches the HTML for the one URL you enter and reads the JSON-LD, Microdata and RDFa inside it. It reports the entities it found and where in the document each one sits, which JSON-LD blocks parsed and which did not, and how each term compares with a specific pinned release of the Schema.org vocabulary. It does not crawl the rest of the site and does not run the page’s JavaScript.
Which Schema.org version do you check against?
One pinned release, named in every result. Schema.org publishes versioned releases, and a conclusion drawn from one is not a conclusion drawn from another — so the version travels with the findings rather than being implied. A term this release does not contain is reported for review, not as an error: it may be newer than the pinned release, part of an extension, or a mistake, and the check cannot tell those apart.
Which types should my business publish?
That depends on what your business does and which search features you want, so this tool does not prescribe a list. A door installation company, an office equipment supplier, a telecoms provider and a solicitor all describe themselves with different types, and all of them can be correct. What this tool does is show you what is actually on the page.
I have several JSON-LD blocks. Is that a problem?
No. Splitting markup across several blocks is normal and valid — many content management systems and plugins add their own. This tool reports the count and flags a contradiction only where two entities claim the same @id and disagree about a property. Two different entities having different names is not a contradiction, and a single entity carrying several types is not either.
Does this tool tell me my markup is valid?
In the respects it checks, and it says which. It reports whether each JSON-LD block is valid JSON, whether a block’s @context resolves to Schema.org, and whether each resolved term appears in the pinned release. It does not check the requirements of any particular search feature — those are set by each search provider and change over time — and it reads Microdata and RDFa as declared subsets, listed with every result.
It found nothing. Does that mean my site has no structured data?
It means no JSON-LD, Microdata or RDFa was found in the HTML returned for that one URL. Other pages may differ, and markup injected by JavaScript after load is not visible to this check. If the fetch itself failed, the tool tells you that separately rather than reporting an empty result.