The Rich Results Test is a free Google tool that fetches a URL, or accepts pasted code, renders it, and lists the structured data items it found that apply to Google rich results. For each item it shows errors that block eligibility and warnings about missing recommended properties. It replaced the older Structured Data Testing Tool for Google-specific checks.
What it checks and what it ignores
The test only reports on types Google supports as rich results. If a page carries valid Schema.org markup for a type Google does not use, such as DefinedTerm, the test may say no items were detected. That does not mean the markup is broken. Use the Schema Markup Validator to check general Schema.org validity.
Because the tool renders the page with Google's rendering service, it also shows whether JSON-LD injected by JavaScript is visible to Google. You can switch between smartphone and desktop crawlers and view the rendered HTML.
Errors versus warnings
An error, such as a missing required property or an invalid value, makes that item ineligible. A warning means a recommended property is missing; the item is still eligible but may show with fewer details. Fix errors first. Treat warnings as optional improvements where you have real data to add.
Where it fits in a workflow
Use it before launch on a staging URL reachable from the internet, or with pasted code for local work. After launch, rely on the rich result reports in Search Console, which aggregate errors across every page Google has crawled, and use URL Inspection to confirm what Google saw on its last crawl.
Example
Catching a missing price
A form builder, Corvelane, tests its new product page. The test finds a Software App item with an error: offers.price is missing because the plan is free and the template left the field empty. Setting price to 0 clears the error and the item becomes eligible.
Common mistakes
Reading "no items detected" as invalid markup
The tool only shows types tied to Google features. Valid markup for other types will not appear.
Testing once and never again
Template changes break markup silently. Re-test key templates after releases, and watch Search Console reports.
Questions
No. It confirms eligibility. Google still decides whether to show the feature for each query.
Not by URL. Paste the rendered HTML or code snippet instead.
