// SEO plans from €35/hour or €395/month// from €35/hr · €395/mo Free SEO checker[email protected]+31 6 4555 9353
Free SEO audit
technical seo

Rich Results Test: How to Validate Structured Data

The Rich Results Test is Google’s tool for validating structured data and, in some cases, previewing how a feature might look in Search. This guide shows where it fits in a development workflow, how to use it alongside the URL Inspection tool and Search Console reports, and what it cannot tell you.

  • Validate markup
  • Preview some features
  • Test, deploy, monitor
  • Know the limits
workflow3 stages
develop -> Rich Results Test
deploy  -> URL Inspection
live    -> Rich result reports
// quick answer
Use the Rich Results Test during development to validate structured data; it can also preview how a feature may look. After deployment, monitor with the Rich result status reports in Search Console, because templating or serving problems can break markup that was valid at launch. Use the URL Inspection tool to confirm Google found the markup on a page. Valid markup does not guarantee a rich result.

What the Rich Results Test is

Google describes it as a tool for validating structured data that can, in some cases, also preview how a feature might look in Google Search. Google’s policies page says it can test compliance with technical guidelines and catches most technical errors. Structured data basics are in the schema markup guide.

Where it fits in the workflow

1
development

Check markup as you build

Google says to check structured data with the Rich Results Test during development.

Rich Results Test
2
deployment

Confirm Google found it

The URL Inspection tool confirms your markup is valid and that Google has found the structured data on the page.

URL Inspection
3
live

Monitor reports

Use the Rich result status reports, since templating or serving issues can break previously valid markup.

status reports

Which tool for which job

ToolUse it for
Rich Results TestValidating markup and previewing features during development
URL InspectionConfirming Google found valid structured data on a specific page. See URL Inspection
Rich result status reportsOngoing monitoring after deployment
Performance reportComparing pages with and without structured data. See Performance report

Test your markup step by step

Google’s pages I used do not describe the tool’s screens in detail, so the exact clicks below are my own general routine, not Google’s instructions.

1
choose

Pick the page and its type

Decide which feature the page should qualify for (my own step).

feature
2
add

Add the markup

Use JSON-LD in the page or via a plugin.

JSON-LD
3
test

Run the Rich Results Test

Check for errors before publishing.

validate
4
fix

Fix problems and retest

Repeat until clean.

retest
5
inspect

Inspect the live URL

Confirm Google sees the markup.

URL Inspection
6
monitor

Watch the reports

Catch template regressions.

Search Console

Reading the results

The Google pages I used do not explain how errors and warnings are presented, so I will not state that here. My own cautious guidance: treat errors as things to fix before publishing, and check each warning against the feature’s documentation before deciding.

After launch: why you keep monitoring

Google warns that templating or serving issues can break structured data that was valid at launch. Check the Rich result status reports regularly, especially after theme, plugin or template changes (the last part is my own advice).

Measuring the effect

Google suggests tracking results in the Search Console Performance report and filtering by URL, so you can compare pages with and without structured data.

Notes for WordPress sites

  • Plugins output markup. Yoast and similar plugins add schema automatically; test a sample page after any change (my own note). See Yoast settings.
  • Avoid duplicate markup from a plugin and a theme at once (my own advice).
  • Page builders can alter output; retest after edits.

Troubleshooting

SymptomLikely cause (my own diagnosis)Action
Valid markup, no rich resultValidity does not guarantee displayReview feature guidelines
Markup disappeared after updateTemplate or plugin changeRetest and check reports
Two schema blocksPlugin plus themeDisable one
Not seen by GooglePage not crawled yetUse URL Inspection

Checklist

Before launch

  • Choose target feature
  • Add JSON-LD
  • Run the test
  • Fix errors

At launch

  • Inspect the live URL
  • Confirm markup found
  • Check one sample page
  • Note the date

After launch

  • Watch status reports
  • Retest after updates
  • Compare in Performance
  • Fix regressions

Hygiene

  • No duplicate schema
  • Markup matches page
  • Follow guidelines
  • Keep it current

What Google’s pages do not say

The pages I fetched do not say whether the tool accepts a URL or pasted code, what the results screen looks like, how errors differ from warnings, or what rendering it uses. They also do not mention requesting indexing as a step. Check Google’s own Rich Results Test documentation for those details.

Key terms

Structured data
Machine-readable markup describing page content.
Rich result
An enhanced search listing based on markup.
JSON-LD
A common structured data format.
Status report
Search Console report on markup health.

Common mistakes

mistake 1

Testing only once

Templates change.

Monitor reports.
mistake 2

Assuming valid means shown

No guarantee.

Follow guidelines.
mistake 3

Skipping URL Inspection

You do not know Google found it.

Inspect live pages.
mistake 4

Duplicate schema

Plugin plus theme.

Keep one source.
mistake 5

Markup not matching content

Breaks guidelines.

Mark up visible content.
mistake 6

No measurement

Cannot prove value.

Compare in Performance.

Related guides

faq

Rich Results Test questions

What is the Rich Results Test?

A Google tool for validating structured data that can sometimes preview a feature in Search.

When should I use it?

During development, before deploying markup.

What do I use after deployment?

The Rich result status reports and the URL Inspection tool.

Does valid markup guarantee a rich result?

No. Google does not promise display for valid markup.

Why monitor after launch?

Templating or serving issues can break markup that was valid.

How do I measure impact?

Filter the Performance report by URL and compare pages with and without markup.

Can JavaScript add markup?

Yes, JSON-LD can be generated with JavaScript; test it.

Does it catch every error?

Google says it catches most technical errors, not all.

sources

The tool’s purpose, the development-then-monitoring workflow, URL Inspection use and Performance comparison come from Google’s pages. The step routine, WordPress notes, troubleshooting and checklists are my own.

Scroll to Top