Rich Results Test

How it works

The Rich Results Test accepts either a live, publicly accessible URL or a pasted HTML code snippet. When you submit a URL, Google fetches the page as Googlebot would, parsing the HTML for structured data in JSON-LD, Microdata, or RDFa formats. For a code snippet, the tool parses the pasted markup directly without fetching external resources.

The tool then evaluates the structured data against Google's supported rich result types, such as recipes, reviews, products, events, and FAQs. It checks for required properties, recommended properties, and correct syntax. If the data is valid for one or more rich result types, the tool displays a preview of how that result might appear in Google Search, including enhancements like star ratings, images, or breadcrumbs.

Results are presented as a list of detected rich result types, each with a status of valid, with errors, or with warnings. Errors indicate missing required properties or syntax problems that prevent eligibility. Warnings flag missing recommended properties that may reduce the chance of appearing as a rich result. The tool also shows the specific lines of code where issues occur, making debugging straightforward. Google recommends fixing all errors and warnings, then retesting until the page passes cleanly.

Why it matters

For SEO practitioners, the Rich Results Test is the fastest way to validate structured data before or after deployment. Catching syntax issues, missing required properties, or eligibility problems early prevents wasted crawl budget and missed opportunities for enhanced search appearance. A page with invalid structured data will not generate rich results, potentially losing click-through rate advantages over competitors who appear with star ratings, images, or other enhancements.

The tool also helps avoid common pitfalls. For example, testing a page that is not publicly accessible or is blocked by robots.txt will fail, alerting the practitioner to access issues before they affect indexing. Similarly, the tool distinguishes between valid structured data and actual rich result appearance in Search, preventing the misconception that a clean test guarantees visibility. Search Console enhancement reports complement the tool by showing sitewide rich result status over time, but the Rich Results Test provides immediate, page-level feedback.

Using the tool regularly during development and after content updates reduces the risk of deploying broken schema markup. It also supports iterative testing when implementing complex structured data, such as for events with multiple dates or products with variants. The tool's preview feature allows stakeholders to see how the result might look before it goes live, aiding alignment between SEO, development, and content teams.

Where it changes your decision

• Before deploying a new page with structured data: Test the URL or snippet to catch errors before the page goes live, avoiding a period where invalid markup is crawled and indexed.
• When troubleshooting a drop in rich result impressions in Search Console: Test the affected page to see if the structured data has become invalid due to a CMS update, plugin change, or manual edit.
• When evaluating a third-party plugin or schema implementation: Paste the generated code snippet into the tool to verify it produces valid markup for the intended rich result type, rather than trusting the plugin's output blindly.

What it is not

• A guarantee that rich results will appear in Google Search: A valid test result only confirms eligibility. Actual appearance depends on query relevance, page quality, crawling, indexing, and Google's evolving systems.
• A general SEO audit tool: The Rich Results Test checks only structured data for rich result types. It does not evaluate page speed, content quality, backlinks, or other ranking factors.
• A replacement for Search Console enhancement reports: The tool gives a snapshot of one page at one moment. Search Console shows sitewide rich result status over time, including impressions and clicks.
• A tool for testing non-public pages: Only pages that Google can access publicly can be tested by URL. Testing staging sites or pages behind login walls requires pasting the code snippet instead.