How to Test and Validate Schema Markup

By Amit Patel

There are two main tools for checking structured data — Google’s Rich Results Test and the Schema.org validator — and they answer different questions: whether your markup is eligible for a Google rich result, versus whether it is syntactically valid Schema.org. Knowing which to use, and how to read errors versus warnings, is the difference between shipping working markup and chasing phantom problems. This reference covers both tools plus the Search Console reports that monitor markup over time.

The Two Validators

The Rich Results Test tells you whether your markup qualifies for a specific Google rich result and previews it; the Schema.org validator checks that your markup is syntactically valid Schema.org regardless of Google features.

Use the Rich Results Test when your goal is a Google feature (Product stars, Event listings). Use the Schema.org validator to confirm general correctness, including types Google does not render. They are complementary — markup can be valid Schema.org yet not eligible for any Google rich result, which is exactly the situation for retired types like HowTo.

Errors vs Warnings

Errors mean the markup is invalid or ineligible and must be fixed; warnings flag missing recommended fields that limit richness but do not disqualify — fix errors first, then close warnings on high-value pages.

A missing required field (a price on a Product, a startDate on an Event) is an error. A missing recommended field (a brand, a review) is a warning — the result still qualifies but could be richer. Do not panic over warnings; prioritize by whether the page matters, the same triage the merchant listings and enhancement reports use.

The Search Console Enhancement Reports

Beyond one-off testing, Search Console’s enhancement reports (Product, Merchant listings, Video indexing, Breadcrumbs, and more) monitor your live markup at scale, showing errors and warnings across all indexed pages over time.

The testing tools check one URL; the Search Console enhancement reports watch your whole site and let you “validate fix” after corrections. That is where you catch a template regression that broke markup across thousands of pages — something no single-URL test would surface.

A Validation Workflow

Draft the markup, run it through the Schema.org validator for syntax, then the Rich Results Test for Google eligibility and a preview, deploy, and finally watch the Search Console enhancement report for site-wide issues.

For live pages, always test the rendered URL (not just pasted code), because JavaScript and templating can change what Google actually sees. After a fix, use “Validate fix” in the relevant report. Our free schema validator gives you a quick first check before the official tools.

Frequently Asked Questions

The Bottom Line

Validation is a two-tool, two-stage habit: check syntax and Google eligibility before you ship, then monitor the enhancement reports after. Fix errors first, treat warnings as polish, and always test the rendered URL — the verification discipline that keeps every type in the schema cluster actually working in the wild.