Rich Results Test: How to Use It and Read the Results

This guide supports our SEO services.

A technical structured-data pass is shown separately from an unanswered question about search-result display.

To run Google’s Rich Results Test, open search.google.com/test/rich-results, paste a live URL or a code snippet, keep the smartphone crawler and select Test URL or Test code. The tool lists each structured data item it finds as valid, valid with warnings or invalid. A valid item is eligible for a rich result, but Google does not promise to show one.

This guide covers running the test, reading the result, how it differs from the Schema Markup Validator, which rich results Google has retired and what to check when a page passes but no rich result appears. For which schema types to add and how to set them up, see schema markup types and setup.

How to use the Rich Results Test

  • Choose URL or Code. Use URL for a published page that anyone on the internet can reach. Use Code to paste JSON-LD, Microdata or RDFa and check it before it goes live; you can edit the snippet and rerun it.
  • Keep the smartphone crawler. Smartphone is the default user agent. Switch to desktop only when you need to compare. The tool fetches the page as Google-InspectionTool, not with your login, so pages behind a login or firewall cannot be tested by URL.
  • Run the test and wait for the page to load and render, JavaScript included.
  • Read the detected items. Each supported rich result type found on the page is listed with its status. Expand an item to see its properties and open the code explorer at the issue.
  • Fix errors first, then warnings. An error makes that item ineligible. A warning flags a missing recommended property; the item can still be eligible.
  • Check the rendered page. View the tested page to see the rendered HTML and a screenshot, which shows whether scripts or blocked resources hid your markup.
  • Retest, then ask Google to recrawl. After a fix, run the test again, then use URL Inspection in Search Console to request indexing for that URL.

You can share a results link with anyone, without granting permissions. Google keeps test history and result links for about 90 days.

What the result means: valid, warnings and errors

Each detected item gets a status. Open an item to see the exact properties Google read and where the issue sits in the rendered code.

ResultWhat it meansWhat to do
Valid item detectedThe markup meets the technical requirements for that rich result type.Confirm the markup matches the visible content and that the feature is still supported.
Valid with warningsRequired properties are present, but recommended ones are missing.Add the recommended properties where the information is real and shown on the page.
Invalid itemA required property is missing or malformed, so the item is not eligible.Fix the error in the template or plugin that prints the markup, then retest.
No items detectedGoogle found no structured data it can use for rich results on this URL.Check that the markup is in the rendered HTML and that the type is one Google supports.
Page not fetchedGoogle could not crawl the URL (blocked, redirected, login or server error).Check robots.txt, redirects and server responses, then test again.
Want this handled for your business?

Our SEO team plans, fixes and reports on the work in this guide every month for Canadian businesses.

The tool can also report syntax errors, which usually mean broken JSON such as a missing comma or bracket. Comments inside JSON-LD are not valid JSON; the test ignores them, but remove them before publishing.

Rich Results Test vs Schema Markup Validator

Google’s tool tests only the structured data that can produce a Google rich result. The Schema Markup Validator checks any Schema.org markup against the full vocabulary, with no Google eligibility checks. Use both: the validator to confirm the markup is well formed and complete, and the Rich Results Test to see what Google can use.

Rich Results TestSchema Markup Validator
ChecksGoogle-supported rich result types onlyAll Schema.org types and properties
InputLive URL or code snippetLive URL or code snippet
Shows eligibility for Google featuresYesNo
Best forBefore and after a fix for a Google featureAuditing every entity on a page

Why a pass does not mean a rich snippet

The Rich Results Test checks the structured data relevant to Google-supported search features on the one URL or snippet you test. It is not a complete Schema.org validator, a website-wide audit or a promise that an enhanced result will appear.

A single-page test reviews one submitted page, unlike a broader website audit.
Figure 1. A single-page test is not a website audit. The Rich Results Test checks the submitted URL or code. That limited scope is different from reviewing the wider website, its content and its various page templates.

A valid result means the tested markup meets the tool’s technical checks. The page still has to meet Google’s quality requirements, and the markup must describe what visitors can see. Google states in its structured data guidelines that correct markup does not ensure display, and even its own preview in the test notes that the page may not appear exactly as shown.

Check whether the search feature still exists

Google’s Search documentation update log records that FAQ rich results stopped appearing in Google Search on May 7, 2026. Google retired HowTo rich results in September 2023. Several other types were phased out in 2025, including course info, estimated salary, learning video, special announcement and vehicle listing, and practice problems followed in January 2026. An old screenshot or tutorial is not evidence that a feature is available now.

Useful questions and answers can stay on your page for readers. Accurate FAQPage markup is not the same as a Google FAQ search feature, and adding more of it will not bring a retired feature back. Check current support before investing in a search appearance that no longer exists.

Review the content and the schema together

Structured data should describe what a visitor can find on the page. Review the service, author, business details and any stated prices alongside the markup. An obsolete offer or unsupported claim does not become reliable because the JSON is valid. If an answer is vague or written to fit a format rather than help a reader, rewrite it before assuming a schema fix will solve a display problem.

Which Search Console reports to use after the test

Search Console rich result reports show detected structured data, valid and invalid items and issues to address across your site. They are not a full inventory of every piece of markup on every page.

For clicks, impressions and search appearance breakdowns, use the Performance report and filter by date range, page, device and appearance. A search you run yourself is a snapshot for one query, location, device and moment, so compare it with Search Console data rather than treating it as proof.

A short checklist before you trust a pass

  • Confirm that the Google search feature you want is currently supported.
  • Test representative live URLs from each template, not just one page.
  • Check the wider Schema.org vocabulary in the validator and confirm the markup matches visible content.
  • Look for duplicate or contradictory entities printed by the theme, plugins and page-level code, and keep one authoritative version.
  • Use Search Console’s rich result and Performance reports for their different purposes.

Common mistakes with rich results testing

A technical pass is not proof that the whole website is error free. A single-page test can miss differences across templates, and correct markup cannot make up for misleading business information or an unrelated offer. Review the actual page and its rendered output rather than adding another schema block by default.

When an answer, price or business detail changes, update its structured data too. Where several tools describe the same service differently, choose one implementation and remove the conflict instead of maintaining parallel copies.

How this plays out across schema types

Choose types that describe the actual page. A service page and an informational article need different primary descriptions. Product markup should not be used to make an agency service look eligible for review stars.

Google’s review snippet guidelines exclude self-serving reviews of an Organization or LocalBusiness from review stars. A business showing reviews about itself does not become eligible because its review count is genuine or the reviews sit in a third-party widget.

What a pass tells you

The Rich Results Test is one useful check, not a verdict on content quality, every Schema.org type or future search performance. The practical order is: check current feature support, validate the markup, inspect the visible content and review real search data in Search Console.

A passed test satisfies its checks but does not guarantee enhanced search appearance.
Figure 2. A passed test does not guarantee search appearance. Passing the applicable checks does not guarantee that Google will display an enhanced search result. Treat the test result and observed search appearance as separate evidence.

For help connecting structured data with useful content and internal links, see our technical and on-page SEO services.

Frequently asked questions

What is the Rich Results Test?

It is Google's free tool at search.google.com/test/rich-results that checks whether a live URL or a pasted snippet contains structured data eligible for Google rich results. It reads JSON-LD, Microdata and RDFa. Each detected item is listed as valid, valid with warnings or invalid.

How do I run Google's Rich Results Test?

Open the tool, choose URL or Code, keep the smartphone crawler and run the test. Read each detected item, fix errors first and warnings second. After a fix, retest and request indexing through URL Inspection in Search Console.

What do warnings mean in the Rich Results Test?

A warning means a recommended property is missing while the required ones are present, so the item can still be eligible. Add the recommended property only when the information is real and shown on the page.

Why does my page pass but show no rich result?

A pass means the markup is eligible, not that Google will display it. The page must also meet Google's quality requirements, and the markup must match what visitors see. Check that the feature you want is still supported.

Is the Rich Results Test the same as the Schema Markup Validator?

No. Google's test checks only the types that can produce a Google rich result. The Schema Markup Validator checks any Schema.org markup against the full vocabulary, without Google's eligibility checks.

Do FAQ and HowTo rich results still show in Google?

No. HowTo results were retired in September 2023, and Google stopped showing FAQ results in Search from May 7, 2026. Keep useful questions and answers on the page for readers, but extra FAQ markup will not bring the feature back.

Can I test structured data before a page goes live?

Yes. Choose Code, paste the markup and run it; you can edit and rerun the snippet. Once the page is live and public, test the URL as well, since rendering can change what Google sees.

Why does the Rich Results Test say the URL cannot be crawled?

Google could not fetch the page, often because of robots.txt rules, a login or firewall, a redirect or a server error. The tool crawls as Google-InspectionTool without your credentials, so the page must be reachable by an anonymous visitor.

How do I check rich snippets across my whole site?

Use the rich result reports in Search Console, which show valid and invalid items across the pages Google found. Then test a representative URL from each template, because one page's result does not cover the rest.

Can a business get review stars by marking up its own reviews?

Google's review snippet guidelines exclude self-serving reviews of an Organization or LocalBusiness from review stars. A genuine review count or a third-party widget does not change that.