The Rich Results Test is a free Google tool that checks a page, or a snippet of code, for structured data that can produce rich results in Google Search. It shows which rich result types Google detects, whether each one is valid, and which errors or warnings need attention.
How the Rich Results Test works
You give the tool either a URL or a block of code. With a URL, Google fetches the live page with its own crawler, renders it as Googlebot would (you can choose a smartphone or desktop agent) and reads every piece of structured data it finds, whether written as JSON-LD, Microdata or RDFa. With code, it tests exactly what you paste, which is useful for checking markup before it goes live.
Results are grouped by rich result type, such as Product snippets, Merchant listings, Review snippets, Breadcrumbs or Event. Each detected item is marked valid, valid with warnings, or invalid.
- Errors mean a required property is missing or malformed, and that item cannot produce a rich result.
- Warnings flag recommended properties that are missing. The item can still qualify, but adding true values may make the listing fuller.
Because the tool renders the page, you can also view the rendered HTML and a screenshot. That is a quick way to confirm that markup injected by JavaScript is actually seen, which makes the tool handy for rendering problems as well.
It reports only the types Google supports for rich results. For general schema.org checks on any type, the Schema Markup Validator run by Schema.org is the companion tool; it replaced Google’s old Structured Data Testing Tool.
Why it matters
Structured data breaks quietly. A theme update drops a property, a review app starts outputting a second product block, a price field comes through empty, and nothing on the visible page looks different. For a UK online shop that relies on price and stock details in search, listings can lose their extras for weeks before anyone notices. The Rich Results Test is the quickest way to check a page in a minute, before and after a change.
Common mistakes
- Reading “valid” as “will show”. The tool confirms eligibility only; Google still decides whether to display the rich result.
- Testing one page and assuming the template is fine. Products with no reviews, with variants or out of stock often produce different markup from the page you tested.
- Misreading “no items detected”. Markup for a type that is not a supported rich result for your site may simply not be listed. That says nothing either way about whether the code is correct.
- Testing a staging site Google cannot reach. Pages behind a password or blocked to crawlers need the code option instead.
- Clearing warnings with invented values. Fill recommended properties that are true and useful; never make up a review count or brand to turn a warning green.
How to act on it
Test one example of each template that carries markup: a product, a category, a blog post, an event page. Save the results or screenshots as a baseline. Fix errors first, then the warnings that matter. After any theme, plugin or platform update, retest the same URLs.
For ongoing checks across the whole site, use the Enhancements and Shopping reports in Google Search Console, which group problems by type and list affected pages. When markup errors are widespread or spread across several plugins, untangling them is part of my schema markup implementation work.