The Rich Results Test is Google’s free tool for checking whether a page’s structured data qualifies it for enhanced search features like star ratings, FAQ dropdowns, or event listings. Most people find it after noticing something’s missing, not proactively, and the error messages it returns can look more alarming than they actually are. If you haven’t already run your schema through our step-by-step schema markup checker guide, it’s worth doing that first, since the two tools catch different types of problems.

Key Takeaways

• It checks Google-specific eligibility, not general schema.org compliance, so a page can pass one and fail the other.
• Errors block rich results entirely. Warnings flag optional fields worth adding but won’t prevent eligibility on their own.
• The single most common error is a missing required field, like a business name, price, or image, not broken syntax.
• Re-running the test after every fix is necessary, since resolving one error sometimes reveals a second one hidden underneath it.
• You can test both a live URL and raw code directly, which is useful for checking changes before they go live.

Table of Contents

1. What It Actually Checks
2. How to Use the Tool Step-by-Step
3. What Do Rich Results Actually Display?
4. How to Read What It Flags
5. Common Errors and How to Fix Each One
6. Other Ways to Check Rich Snippets Beyond the Official Tool
7. Decision Framework: How Urgent Is This Error?
8. Mistakes People Make Reading Their Results
9. How Lorphic Helps With Structured Data Health Checks
10. FAQs
11. Implementation Best Practices

What Is a Rich Results Test?

This tool is Google’s own free tool that scans a specific page and reports which rich result types, if any, that page currently qualifies for based on its structured data. It’s built and maintained by Google directly, not a third-party SEO tool, which makes its results the closest thing to ground truth available.

Running it takes seconds: paste in a URL or raw code, and the tool returns a pass or fail status for each schema type it detects, along with specific errors or warnings tied to individual fields.

• It only evaluates rich result eligibility, not overall SEO health or ranking potential.
• It replaced Google’s older Structured Data Testing Tool, which was deprecated in 2021 for anything beyond generic validation.
• It works on both live, publicly accessible URLs and code you haven’t published yet.

How to Use Google’s Rich Results Test

Using the tool correctly the first time saves a lot of confused re-checking later. Here’s the process.

1. Go to Google’s official test tool and choose between testing a live URL or pasting in code directly.
2. Enter your page’s URL if it’s already published, since this reflects exactly what Google’s crawler currently sees.
3. Wait for the scan to complete, usually a few seconds, longer for pages with heavier scripts.
4. Review the summary at the top, which lists each schema type found and whether it’s valid.
5. Click into each result to see the specific fields Google detected, along with any errors or warnings attached to them.
6. Fix errors first, then warnings, then re-run the test on the same URL to confirm the fix worked.
7. Repeat for every key page, not just your homepage, since service pages and blog posts often carry their own separate schema.

If you manage a business with multiple locations, run this test on each location’s page separately. A local business’s address and hours schema is easy to accidentally duplicate or mismatch across pages during a site update.

What Do Rich Results Actually Display?

This is a common source of confusion because a rich result isn’t one single thing, it’s a category covering several different visual formats in search results. Understanding what you’re actually working toward makes the errors easier to interpret.

Rich results can include star ratings pulled from review schema, expandable FAQ sections, event dates and locations, recipe cook times, and product pricing and availability. Not every business qualifies for every type, and that’s expected, not a sign something’s broken.

• Review or AggregateRating schema can produce visible star ratings next to your listing.
• FAQPage schema can produce an expandable question and answer dropdown directly in search results.
• LocalBusiness schema contributes to knowledge panel accuracy, though it doesn’t produce its own distinct visual rich result the way FAQ or Review schema does.

How to Read the Errors the Rich Results Test Flags

This is where most confusion actually happens, not in running the test, but in understanding what the output means. The tool separates its findings into two categories that behave very differently.

Errors mean something is broken or missing that’s required for that rich result type to be eligible at all. A page with even one unresolved error for a given schema type won’t be eligible for that rich result, regardless of everything else being correct.

Warnings flag optional fields that Google recommends but doesn’t require. A warning won’t block eligibility, but addressing it can make your rich result more detailed or visually complete once it does appear.

• Click directly on the flagged field name to see Google’s specific explanation for that error, rather than guessing from the general message alone.
• A single missing field often triggers what looks like multiple errors, since other fields sometimes depend on it being present first.
• Test the same page again immediately after each fix. Errors sometimes cascade, meaning fixing one reveals a second one Google couldn’t previously evaluate.

Common Errors and How to Fix Each One

A handful of specific errors account for most of what businesses actually encounter.

Error Message	What It Means	How to Fix It
Missing field “name”	The schema is missing a required title or business name field	Add the field with the exact name matching your visible page content
Missing field “image”	No valid image URL was found in the structured data	Add a direct, publicly accessible image URL, not a placeholder
Invalid value type	A field contains text where a number was expected, or vice versa	Correct the format to match the field’s required data type
Missing field “aggregateRating”	Review schema is present but lacks a summarized rating value	Add both the average rating and total review count as separate fields
Duplicate schema detected	The same schema type appears more than once on the page	Remove the duplicate, keeping only the accurate, current version

Most of these take a few minutes to resolve once you know exactly which field triggered the error, which is why reading the specific message matters more than the general error count.

Decision Framework: How Urgent Is This Error?

Not every flagged issue needs to be fixed today. Use this to prioritize.

What the Test Flagged	Urgency
An error blocking your main rich result type (Review, FAQ, etc.)	High, fix immediately, this is actively costing you visibility
A warning on an optional field you don’t currently use	Low, fix when convenient, no visibility impact
Errors appearing after a recent site redesign or plugin update	High, this usually means schema broke during the change
Warnings suggesting additional optional fields for richer display	Medium, worth adding for a more complete rich result over time
No schema detected on the page at all	High if you intended to add it, otherwise not applicable

Other Ways to Check Rich Snippets Beyond the Official Tool

The Rich Results Test isn’t the only way to verify your structured data, but it’s the only one built and maintained directly by Google, which is why it should always be your final word on eligibility. Still, knowing how to check rich snippets through other methods gives you a fuller picture, especially when you’re troubleshooting something the main tool doesn’t fully explain.

• Schema.org’s own validator lets you check rich snippets against the general schema.org standard rather than Google-specific rules, which is useful when your code needs to work across multiple search engines, not just Google. See Google Search Central’s structured data documentation for how the two standards relate.
• Browser extensions built for structured data let you check rich snippets on any page you’re viewing without copying a URL into a separate tab, which speeds up spot-checking competitor pages too.
• Search Console’s Enhancements report lets you check rich snippets sitewide automatically instead of one page at a time, catching new errors the moment they appear rather than waiting for you to notice a rich result disappeared.

If you’ve already read our guide on how AI systems measure structured content, you’ll recognize why running this check across more than one tool matters: each one surfaces slightly different gaps, and no single check rich snippets method catches everything on its own. For a second official reference point, Schema.org’s validator is worth bookmarking alongside Google’s own tool, as noted on Lorphic’s homepage resource list for technical SEO tools.

Mistakes People Make Reading Their Results

A few habits lead people to either overreact or under-react to what the tool actually found.

• Treating every warning like an error. Warnings are recommendations, not blockers, and don’t need the same urgency.
• Only testing the homepage. Service pages, product pages, and blog posts often carry their own schema that never gets checked.
• Not re-testing after a fix. A single correction sometimes exposes a second, previously hidden error underneath it.
• Ignoring the specific field name. The general error summary is less useful than clicking into the exact field Google flagged.
• Assuming a failed test means the page will drop in rankings. Rich result eligibility affects visual display, not core ranking position.

How Lorphic Helps With Structured Data Health Checks

Reading this kind of report correctly is one small piece of a broader technical SEO picture that also includes page speed, mobile usability, and overall crawlability. When we run a technical audit for a client, checking every key page’s rich result eligibility is a standard step, since it directly affects both visual search presence and how clearly AI tools can describe the business.

If your test results are showing errors you’re not sure how to interpret, a short review usually clarifies what’s actually urgent versus what can wait.

FAQs

Implementation Best Practices

The Rich Results Test is a sensitive diagnostic area where accuracy is paramount, as Google’s eligibility requirements and the underlying structured data standards evolve frequently. Because of this, you should always consult Google Search Central’s Rich Results Test documentation and Google’s official Search Console Help directly to verify current requirements before making technical changes. For ongoing reference, please continue to utilize the internal documentation links and established markup standards we have previously reviewed for your site’s technical SEO health.

Curated by Lorphic
Digital intelligence. Clarity. Truth.