How to Use Google’s Rich Results Test to Check Schema

Google's Rich Results Test checks whether a page's structured data is eligible for rich results in Google Search — such as product details, breadcrumbs or review stars. It is the quickest way to find schema errors before they cost you features in search.

Step 1: Choose URL or code

• URL — tests the live page as Googlebot sees it, including markup added by JavaScript.
• Code — paste HTML or JSON-LD to test before publishing.

You can choose the smartphone or desktop crawler; smartphone is the default and usually the right choice.

Step 2: Read the results

• Valid items detected — the rich result types found, such as Product, Breadcrumbs or Article.
• Errors (red) — required properties are missing or invalid. Items with errors are not eligible.
• Warnings (orange) — recommended properties are missing. Items are still eligible, but adding them can improve the result.

Click any item to see exactly which property has a problem and where it is in your code.

Common problems and fixes

• "No items detected" — the page has no supported markup, or it failed to load. Check the page loaded and the markup is in the HTML.
• Missing field "price" or "availability" on products — add offers with price, currency and availability.
• Invalid date format — use ISO 8601, such as 2026-11-20 or 2026-11-20T09:30:00+05:30.
• Page could not be loaded — robots.txt blocking, server errors or firewalls. See server error 5xx fix.
• Parsing error — a missing comma or bracket in JSON-LD. Regenerate the markup with the schema generator.

Rich Results Test vs Schema Markup Validator

• Rich Results Test — checks only the types Google supports for rich results, against Google's rules.
• Schema Markup Validator — checks all schema.org markup, whether Google uses it or not.

Use both: the validator for general correctness, the Rich Results Test for Google eligibility.

After fixing

Retest the URL, then check Search Console's enhancement reports (such as Products or Breadcrumbs) for site-wide problems. Use "Validate fix" there once templates are corrected.

Remember

Valid markup makes a page eligible, but Google decides whether to show a rich result. Markup must also match visible content. Read what schema markup is, product schema for ecommerce and whether FAQ schema is still useful.

A worked example

A shop's product pages lost price information in search results after a theme update. The Rich Results Test showed "Missing field 'offers'" — the new theme placed price markup inside a section that loaded only after a click. Moving the offers markup into the main product JSON-LD fixed the error, and the Products report in Search Console returned to valid within a few weeks.

What to test after changes

• Theme or template updates: one page of each type.
• New plugins or apps: pages where they add markup.
• New page types: before launch, using the code tab.
• Price or review display changes: product pages.
• Site migration: a sample of every template on the new site.

Testing a handful of pages takes minutes and catches errors before Search Console reports them weeks later.

Related guides

• Organization Schema Markup: Example and Properties to Use
• Breadcrumb Schema Markup: Example and How to Add It
• Article Schema Markup for Blog Posts: What to Include

More free tools: browse all our free SEO tools, no sign-up needed.

Frequently asked questions