Schema Validator

A schema validator is a tool that reads the structured-data markup on a web page and checks it for errors before a search engine has to. Structured data is code — usually JSON-LD following the Schema.org vocabulary — that labels a page's content so machines can understand it: this is a recipe, that is its cook time, this is a product and its price, that is a review and its rating. A validator parses that markup, confirms it is syntactically correct, checks that required properties are present, and reports what it finds. The two most common are Google's Rich Results Test, which shows whether a page qualifies for specific search features, and the Schema Markup Validator hosted by Schema.org, which checks conformance to the vocabulary itself. Both turn invisible markup into a readable pass-or-fail report.

The reason a validator matters is that structured data is easy to get subtly wrong and hard to eyeball. A missing required field, a mistyped property name, a price without a currency, a date in the wrong format — any of these can make markup invalid or make a page ineligible for the rich result it was meant to earn, and none of it shows up on the rendered page. A schema validator surfaces these problems while you can still fix them, ideally before the code ships. It is the structured-data equivalent of a spell-checker. It will not tell you whether your content is good, but it will tell you whether the machines can read the labels you put on it, which is the precondition for any rich result at all.

The two common validators answer related but different questions, and knowing which to reach for saves confusion. Google's Rich Results Test is eligibility-focused: it tells you whether a page's markup qualifies for Google's supported rich result types — review stars, FAQ accordions, product snippets, and the like — and previews how they might appear. It only reports on features Google actually supports, so valid Schema.org markup for a type Google does not render will simply not show up as a rich result there. The Schema Markup Validator, hosted at Schema.org, is vocabulary-focused: it checks whether your markup conforms to the Schema.org standard in general, regardless of whether any particular search engine renders it, which makes it broader but less tied to specific search features.

Use them together rather than treating either as the whole truth. Start with the Schema Markup Validator to confirm your markup is well-formed and conformant to the vocabulary, then run the Rich Results Test to see whether Google considers the page eligible for a specific rich result. A page can be perfectly valid Schema.org yet ineligible for a Google rich result because Google requires extra properties or does not support that type. Conversely, passing the Rich Results Test means Google can read it, not that the content deserves to rank. Neither tool judges content quality or guarantees the feature will appear — eligibility is necessary, not sufficient. Reading both, in order, tells you the markup is correct and whether search is likely to act on it.

Use a schema validator as a gate, not an afterthought — validate structured data before it ships, and re-validate whenever the page template or the markup changes. Paste the code or the live URL into the tool, read every error and warning rather than only the top line, and fix the required-property failures first, since those are what break eligibility. Test with real page data, not placeholder values, because a validator can pass a template that fails on the messy content of a live page. When you are chasing a specific rich result, run the Rich Results Test and match your markup to that feature's documented requirements. Keeping a validation step in the publishing workflow is what stops broken markup from reaching production unnoticed.

The failure modes are trusting valid markup to mean guaranteed rich results, ignoring warnings because the page still passes, and validating a template once while live pages quietly generate invalid data. A validator confirms the markup is correct and, in Google's case, that a page is eligible. It does not promise the feature will appear, since eligibility, quality, and Google's own discretion all sit between valid markup and a visible result. It also cannot tell you the labels are true — mark a three-star product as five stars and the validator will happily pass it, but the mismatch risks a manual penalty. Treat the validator as the tool that proves machines can read your structured data correctly, then rely on honest, complete markup to earn the result.

A schema validator checks markup written in the Schema.org vocabulary, the shared structured-data standard backed by major search engines, using tools like Google's Rich Results Test.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where schema validator is a core concern: