SEO

Rich Results Test

Also called RRT

Google's checker for whether a page's structured data qualifies for a search feature such as breadcrumbs, products or events.

Quick facts: Rich Results Test

Category
SEO
Also called
RRT
Level
Intermediate
Affects
Rich result eligibility, click-through rate, structured data quality
Where to see it
Rich Results Test, Search Console enhancement reports, Schema Markup Validator
In this article4
  1. How the Rich Results Test works
  2. Why the Rich Results Test matters
  3. Common mistakes with the Rich Results Test
  4. How to act on it

How the Rich Results Test works

You give it either a live URL or a block of pasted code. It fetches the page as Googlebot, runs the rendering step so that markup injected by JavaScript is included, and compares what it finds against Google’s published requirements for each search feature.

Results are grouped by feature type rather than by tag. For each type it lists the items it detected and flags what is missing. Errors are required properties that are absent, and they disqualify the item. Warnings are recommended properties that are absent — the item still qualifies, but with less available to display. You can switch between the smartphone and desktop crawler, and open the rendered HTML to see exactly what was parsed.

Why the Rich Results Test matters

Structured data is invisible. Nothing on the page looks different when it breaks, so without a validator you discover the problem weeks later, when a rich result quietly disappears from search. This test shortens that feedback loop to a few seconds.

It also settles a recurring argument about JavaScript. A plugin or a tag manager that writes structured data after the page has loaded may or may not survive Google’s rendering step. Testing the live URL rather than reading the page source is the only dependable way to find out.

Common mistakes with the Rich Results Test

The biggest is reading “eligible” as “will appear”. The test judges the markup, not the page’s chance of being chosen. Google decides feature by feature and query by query, and it has retired whole feature types before. Promising a client a rich result on the strength of a green tick is a promise you cannot keep.

Two smaller mistakes follow. Testing pasted code instead of the live URL hides everything that caching, rendering or the live template could break at publication. And driving every warning to zero is rarely worth the effort — required properties are not negotiable, optional ones are a judgement about how much detail you want available.

How to act on it

Test a template once rather than every page built from it, then spot-check a few live URLs after each release. Most structured data faults are template faults repeated at scale, so fixing the template fixes the site. Clear all errors first, then decide which warnings earn the extra fields.

After that, hand continuous monitoring to Search Console. Its enhancement reports watch the whole site over time, while this test examines one page on demand, and the two answer different questions. Keep the markup and the visible content in step: if a price, a stock status or an opening time changes on the page, the schema markup has to change with it, or you are describing a page that no longer exists.

Do and do not

Do

  • Test the live URL, not only pasted code
  • Clear every error before weighing up the warnings
  • Re-test a template after each release or plugin update

Do not

  • Treat eligible as a promise the feature will appear
  • Mark up content a visitor cannot see
  • Chase warnings to zero for their own sake

Questions people ask about this

Why does my page pass the test but show no rich result?

Eligibility and display are separate decisions. The test only confirms that the markup meets Google's requirements. Whether the feature actually appears is decided per query, per device and per result, and Google can withdraw a feature type entirely. Content quality, the searcher's intent and the competing results all play a part. Valid markup is a condition, never a guarantee.

How is this different from the Schema Markup Validator?

The Rich Results Test is Google's, and it reports only on markup that maps to a Google search feature. The Schema Markup Validator comes from schema.org and checks any structured data against the vocabulary, including types Google makes no use of. Use the first for search eligibility, and the second when you want a plain syntax check.

Should I mark up content that is not visible on the page?

No. Google's guidelines expect structured data to describe what a visitor can actually see. Hidden or invented markup risks a manual action for spammy structured data, which removes the rich results you were chasing and can take a long time to reverse. If a detail is worth marking up, it is worth putting on the page.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.