Structured Data Testing Tool: An Overview
The Google Rich Results Test is a diagnostic tool used to check whether a web page’s structured data is eligible to generate rich results in Google Search, such as FAQs schema, reviews schema, products schema, events schema, or breadcrumbs schema. It does not validate all schema types, and it does not guarantee rankings. It only confirms eligibility and detects errors that may prevent enhanced search appearances.
OR
The Structured Data Testing Tool was one of the most trusted tools SEOs used for years. It allowed you to test almost any type of schema markup and quickly see if something was broken or missing. You could paste a URL or code, make edits, and re-test instantly. For technical SEO work, especially during development, this tool was simple and very effective. Its biggest strength was flexibility, not rich result validation.
Introducing the Schema Markup Validator
After the Structured Data Testing Tool was deprecated, Google moved its core validation features to schema.org as the Schema Markup Validator. This tool focuses purely on checking whether your schema follows schema.org standards. It doesn’t tell you if your markup will generate rich results in Google Search, but it’s still extremely useful for debugging structure, nesting, and syntax issues before testing eligibility elsewhere.
Understanding Google’s Rich Results Test
The Google Rich Results Test is designed to check whether a page’s structured data is eligible for enhanced search features like FAQs, products, or reviews. Unlike older tools, it only supports schema types that Google actually uses in search results. The test shows errors, warnings, and a preview of how your page may appear in Google Search, making it useful for final validation before publishing.
Recent Updates to the Rich Results Test
Over time, Google has quietly improved the Rich Results Test. Support for additional schema types has been added, error messages are now more detailed, and rendering of JavaScript-based markup has improved. While the tool still has limitations, these updates have made it more reliable for modern websites using dynamic content and CMS-based schema generation.
Why the Rich Results Test Exists (and how we got here)
Before the Rich Results Test, SEOs relied heavily on the Structured Data Testing Tool (SDTT). That tool could validate any schema type, even ones that never showed in search results. It was flexible, fast, and honestly, very SEO-friendly.
Around 2019–2020, Google shifted direction.
Their focus moved from:
“Is your schema technically valid?”
to
“Does this markup qualify for enhanced search features?”
That shift resulted in:
-
The Rich Results Test (RRT) for Google-facing features
-
The Schema Markup Validator (moved to schema.org) for pure syntax checking
This split confused a lot of SEOs at first, and even today, many people still misuse the Rich Results Test because they expect it to behave like the old SDTT. It doesn’t.
What the Google Rich Results Test actually evaluates
The Rich Results Test checks three things only:
-
Whether Google supports the structured data type
-
Whether the required properties are present
-
Whether the markup qualifies for rich result enhancements
It does not:
-
Validate all schema types
-
Confirm indexing
-
Improve rankings
-
Replace Search Console data
This distinction is critical and often misunderstood.
Rich Results Test vs Other Structured Data Tools (practical comparison)
| Tool | What it’s good at | What it’s not good at | Real-world implication |
|---|---|---|---|
| Rich Results Test | Google rich result eligibility | Full schema validation | Best used after markup is final |
| Schema Markup Validator | Syntax + schema.org compliance | Google SERP eligibility | Best for development and debugging |
| Google Search Console | Site-wide enhancement tracking | Single-page testing | Best for monitoring long-term issues |
| Bing Markup Validator | Broader schema support | Google-specific features | Useful for cross-engine validation |
Practical takeaway: If you only use the Rich Results Test, you’re missing half the picture.
When the Rich Results Test is the right tool (real use cases)
1. Before publishing a page
If you’re about to push:
-
FAQ schema
-
Product schema
-
Review schema
-
Article enhancements
The RRT helps catch missing required fields that would silently fail in search.
2. When rich results disappear
A common real-world scenario:
“Our FAQs were showing last month, now they’re gone.”
The RRT helps identify:
-
Invalid properties
-
Deprecated fields
-
Mobile vs desktop differences
It won’t tell you why Google stopped showing them, but it helps rule out markup errors.
3. Testing JavaScript-rendered schema
The RRT handles rendered DOM, which makes it useful for:
-
React
-
Vue
-
Next.js
This is one area where it performs better than older tools.
Common mistakes SEOs make with the Rich Results Test
Mistake 1: Treating “valid” as “will rank”
A valid rich result only means eligibility, not visibility.
Google still applies:
-
Quality thresholds
-
Spam policies
-
Site trust signals
Mistake 2: Ignoring warnings completely
Warnings don’t always block eligibility, but they often:
-
Reduce enhancement richness
-
Affect future eligibility
-
Indicate weak data quality
In audits, a warning-heavy schema almost always underperforms.
Mistake 3: Testing the wrong URL version
The RRT often defaults to:
-
Mobile version
-
Canonical version
-
AMP version (if present)
Testing the wrong version leads to false conclusions.
Mistake 4: Using unsupported schema types
Many schema types are valid, but not supported by Google rich results.
The RRT will simply ignore them.
This doesn’t mean the schema is useless. It just won’t enhance SERPs.
Limitations you should be aware of (honest ones)
From hands-on SEO work, these are the real limitations:
-
No bulk testing
-
No historical comparison
-
No explanation for why Google may suppress a rich result
-
Limited editing capability
-
Focused only on Google, not schema quality overall
This is why professionals never rely on this tool alone.
A practical step-by-step workflow (how professionals actually use it)
Step 1: Validate schema structure
- Use Schema Markup Validator first.
- Fix syntax, nesting, and type errors.
Step 2: Refine required properties
Ensure:
-
Required fields are present
-
Values are specific, not generic
-
Content matches visible page content
Step 3: Test with Rich Results Test
Confirm:
-
Eligibility
-
Errors vs warnings
-
Device differences
Step 4: Deploy and monitor in Search Console
Check:
-
Enhancements report
-
Error trends
-
Sudden drops
Step 5: Re-test after major updates
Especially after:
-
CMS changes
-
Theme updates
-
Content rewrites
Schema breaks more often than people realise.
Alternative Tools to the Rich Results Test
Sometimes the Rich Results Test alone isn’t enough. In real SEO workflows, it’s often combined with other tools to get a complete picture of structured data quality.
1. Schema Markup Validator
The Schema Markup Validator allows you to validate all schema types, not just the ones supported by Google rich results. It’s especially helpful when working with custom or advanced schema and during the early stages of implementation.
2. Bing Markup Validator
Bing’s Markup Validator supports a wide range of structured data types and is useful for checking compatibility beyond Google. It’s quick to use, although it requires a sign-in, and works well as a secondary validation tool.
3. Structured Data Viewer
The Structured Data Viewer from classyschema.org presents structured data in a visual, easy-to-understand format. It’s helpful for seeing how entities are connected and for reviewing complex schema relationships that are harder to read in raw code.
4. Screaming Frog
Screaming Frog’s SEO Spider is useful for testing structured data at scale. For larger sites, it helps identify missing, invalid, or inconsistent schema across hundreds or thousands of URLs, making it a strong complement to Google Search Console.
Decision guidance: when to rely on the Rich Results Test
Use the Rich Results Test when your goal is visibility, not validation.
If your question is:
-
“Is my schema correct?” → Use Schema Markup Validator
-
“Will Google show this as a rich result?” → Use Rich Results Test
-
“Is this working at scale?” → Use Search Console
Each tool answers a different professional question.
Frequently asked questions (SEO-optimised)
- Does the Rich Results Test affect rankings?
No. It does not influence rankings directly. It only checks eligibility for enhanced SERP features.
- Can a page rank without passing the Rich Results Test?
Yes. Rich results are optional enhancements, not ranking requirements.
- Why does Search Console show errors that RRT doesn’t?
Search Console works at scale and over time. RRT is a point-in-time snapshot.
- Should warnings always be fixed?
Not always, but in competitive SERPs, fixing warnings usually improves consistency.
- Is structured data required for SEO?
No, but for certain features (FAQs, products, reviews), it’s effectively mandatory.
Final thoughts from an SEO Business
The Google Rich Results Test is not a magic SEO tool, and that’s exactly why it’s misunderstood.
Used correctly, it’s a confirmation tool, not a strategy.
It tells you whether Google can show enhancements, not whether it will.
The SEOs who get consistent results treat schema as:
-
A quality signal
-
A clarity layer
-
A trust reinforcement
Not as a shortcut.
If you approach the Rich Results Test with that mindset, it becomes useful.
If you expect it to boost rankings on its own, it will always disappoint.
That’s the difference between testing markup and understanding it.
