GrowthPedia

Google Rich Results

Google Rich Results Test is a free tool that checks if a page or code snippet has structured data eligible for Google's rich results.

Level: IntermediateRead: 4 minUpdated: 27 Jul 2026By Vera Lindqvist

Key facts

  • It is an official Google tool for testing structured data and rich result eligibility.
  • It can test a live, publicly accessible URL or a pasted code snippet.
  • It previews how rich results may look in Google Search.
  • It replaced the older Structured Data Testing Tool, which was shut down in December 2020.
  • Only pages that Google can access publicly can be tested by URL.

Also called

Rich Results Test, Google Rich Results Test

Use it for

Testing structured data for rich results eligibility.

Applies to

Google

How the Rich Results Test Works

The Google Rich Results Test is a free tool at search.google.com/test/rich-results. You can enter a publicly accessible URL or paste a code snippet. The tool fetches the page or parses the snippet, then evaluates the structured data against Google's supported rich result schemas.

After analysis, it shows which rich result types are detected, along with any errors or warnings. It also provides a preview of how the result might appear in Google Search. This preview is not guaranteed but gives a helpful visual.

The tool is specifically designed for rich results, not for all structured data. It focuses on schemas that can generate enhanced search features. Use it in conjunction with how schema markup works for best practices.

What the Tool Can and Cannot Do

The tool validates structured data for rich result eligibility. It is not a ranking checker or a full SEO audit. The tool tests for eligibility for rich snippets, not for general structured data. Understanding its capabilities and limitations is essential. The tool is specifically designed to validate schemas that Google supports for rich snippets, such as Article, Product, Recipe, and Review. It does not validate all schemas from Schema.org, only those that can produce rich results. This focus makes it a targeted tool for SEO practitioners aiming for enhanced search features. The tool can only evaluate the initial HTML; it does not execute JavaScript for rendering, so rich results that rely on JavaScript may not be detected. Regularly testing after updates helps maintain eligibility.

  • Can test live URLs and pasted code snippets.
  • Can detect multiple rich result types on a single page.
  • Can preview how rich results may look in Google Search.
  • Cannot guarantee that rich results will appear in search.
  • Cannot test non-public pages or pages blocked from crawling.
  • Cannot replace Search Console enhancement reports or a comprehensive SEO audit.

Common Errors and Warnings

The Rich Results Test surfaces errors and warnings. Errors indicate invalid or missing required properties. Warnings suggest missing optional properties that could affect eligibility. Fix both. Even though warnings are not errors, they indicate missing information that could help Google understand your content better. For example, adding a 'description' property to a Product schema is optional but recommended. Ignoring warnings may result in missed opportunities for rich results. Common errors include missing required fields, unrecognized properties, and missing values. The table below shows typical examples. For instance, if you use a 'review' property but forget to include 'itemReviewed', the tool will flag an error. Similarly, using a property that is not part of the schema, like 'priceCurrency' in a Recipe schema, will be flagged as unrecognized. Whenever you update your structured data, run the test again to ensure no new errors have been introduced.

  • Missing required field
  • Unrecognized property
  • Missing value

Differences from the Structured Data Testing Tool

The Rich Results Test replaced the older Structured Data Testing Tool in December 2020. The old tool checked all structured data on a page, regardless of rich result potential. The new tool is focused only on schemas that Google supports for rich results.

This focus makes the Rich Results Test more relevant for SEO practitioners aiming for enhanced search features. The old tool could validate non-Google schemas; the new one does not. Understanding semantic markup helps in using both tools effectively.

Limitations and Caveats

A passing test result does not guarantee that Google will display rich results. Google's systems consider many factors, including the query, page quality, and user context. The tool only checks structured data eligibility. Actual appearance in Search Results depends on Google's algorithms.

The tool can only test pages that are publicly accessible and not blocked by robots.txt or noindex. If your page is behind a login or firewall, the tool cannot fetch it. Also, the test is a snapshot; changes to the page or to Google's schemas can affect eligibility later.

Rich results are not the same as ranking. They are visual enhancements. Use the tool alongside Organic Results analysis to understand your search presence.

How to Integrate with Search Console

The Rich Results Test complements Google Search Console's enhancement reports. While the test checks individual pages, Search Console provides a sitewide view of rich result issues over time. Use Search Console to monitor trends and the Rich Results Test to debug specific pages. You can use the Rich Results Test to validate a single page, then cross-reference with Search Console's enhancement report to see if the same errors appear across multiple pages. If Search Console shows a high number of errors, use the test to drill down into individual pages. Additionally, you can use the test to verify fixes after implementing changes suggested by Search Console. Regularly testing with both tools ensures that your structured data remains valid over time, especially after site updates or Google schema changes. For a comprehensive strategy, implement rich content seo techniques. This includes using valid structured data, creating high-quality content, and ensuring technical SEO fundamentals. The combination of individual testing and sitewide monitoring ensures your structured data is effective. Advanced users can use the Rich Results Test API to automate testing.

Common Errors and Warnings in the Rich Results Test
Error TypeMeaningRecommended Action
Missing required fieldA required property like 'name' is missingAdd the required property from the schema documentation
Unrecognized propertyA property that is not part of the schemaRemove or correct the property
Missing valueA property exists but has no valueProvide a valid value

Common mistakes

  • Assuming a valid test result guarantees the page will receive rich results in Google Search. You may be disappointed when rich results don't appear due to other ranking factors.
  • Testing pages that are not publicly accessible or blocked from crawling. The tool cannot fetch the page, giving false negatives.
  • Ignoring warnings and only fixing hard errors. Warnings may indicate missing optional properties that affect eligibility.
  • Confusing the Rich Results Test with a general SEO audit or a ranking checker. You may waste time on irrelevant metrics.

Questions

What is the difference between the Rich Results Test and the Structured Data Testing Tool?

The Rich Results Test is focused on schemas that generate rich results in Google Search. The older Structured Data Testing Tool validated all structured data, including non-Google schemas. Google shut down the old tool in December 2020 and recommends using the Rich Results Test for rich result eligibility.

Can I test a page that is not yet live?

You can paste a code snippet of the page's structured data. The tool will analyze the snippet without needing the page to be publicly accessible. However, if you want to test a live URL, the page must be public and crawlable by Google.

Does passing the test guarantee rich results?

No. A passing test only indicates that the structured data is valid and eligible for rich results. Whether Google actually displays the rich result depends on many factors, including the search query, page quality, and Google's algorithms. The tool is a validation step, not a guarantee.

How often should I test my structured data?

Test whenever you add or modify structured data on a page. Also test after major site updates or changes to your CMS. It is good practice to retest periodically, especially after Google announces changes to rich result types.

See also

Sources

  1. Google Rich Results Test search.google.com
  2. Google Search Central: Structured data developers.google.com

Outbound links are unpaid and nofollow. If one has gone stale, tell me.