What is the Rich Results Test?

Running a test

1. Open search.google.com/test/rich-results.
2. Choose URL for a live page or Code to paste HTML or a JSON-LD block.
3. Pick the crawler, smartphone or desktop. Smartphone is the default and matches how Google indexes.
4. Run the test and wait for the page to be fetched and rendered.

The code option is the useful one before publishing. Paste a snippet like this and you get a verdict without touching the live site:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "Lentil ragu",
  "image": "https://example.com/img/ragu.jpg"
}
</script>

For that snippet the tool finds a Recipe item and warns about recommended properties that are absent, such as author and recipeIngredient.

Reading the result

Each detected item falls into one of three states:

Click an item to see the parsed properties and the line that caused each message. View tested page shows the rendered HTML, a screenshot and any resources that failed to load, which helps when markup is injected by JavaScript and did not appear.

What the tool does not check

• Types without a Google rich result. Markup that Google has no feature for is not reported at all. A page can carry correct schema.org markup and still show "No items detected". For full vocabulary checking use the Schema Markup Validator at validator.schema.org, or our JSON-LD validator for syntax and required properties.
• Whether the markup is truthful. Google's guidelines require structured data to match content visible on the page. The tool cannot judge that, and markup that breaks the rule can lead to a structured data manual action.
• Whether a rich result will be shown. Eligibility is a precondition. Google decides per query whether to display one.
• Retired features. FAQ and HowTo markup no longer produce rich results in Google, whatever a validator says about the syntax.

Rich Results Test, URL Inspection and Search Console reports

The three overlap. The Rich Results Test works on any URL and on code that is not live yet. The URL Inspection tool shows what Google found on its last crawl of your own page, which is the real state of the index. The enhancement reports in Search Console, such as Products or Breadcrumbs, summarise valid and invalid items across the site and are the place to watch for regressions after a theme or plugin update.

Testing a WordPress page

Test one URL of each template: a post, a page, a product, a category archive. Problems tend to be template-wide, so one sample of each catches most of them. Two things to look for in particular are the same type detected twice, a sign that a theme and a plugin both output markup, and a type you did not expect.

Hydrogen SEO outputs JSON-LD for the schema types you configure, and the steps for checking it are in validate rich results. To build markup by hand first, use the schema markup generator.