Is Google really replacing the Structured Data Testing Tool with the Rich Results Test?

What sets these two tools apart?

The Structured Data Testing Tool validated all types of schema.org markup present on a page, regardless of whether they were used by Google to enhance search results. An Article, Person, Organization, Event schema.org — anything was put through the wringer, and the tool returned a technical compliance report.

The Rich Results Test, on the other hand, adopts a radically different approach: it only tests schemas that can trigger enriched displays in the SERPs. If your markup does not generate a rich snippet, star ratings, breadcrumb, or enriched card, the tool won't even acknowledge it. It's a pragmatic filter focused on observable user impact.

Why the shift in direction now?

Because many sites were throwing schema.org all over the place without considering its actual utility. We saw Author, Publisher, SameAs tags on pages that had no chance of achieving an enriched display. The Structured Data Testing Tool gave a false impression of compliance.

Google is refocusing attention on what really matters: structured data that truly enhances results display. If a schema has no visible effect, why waste time validating it? It’s a clear signal that Google wants to avoid unnecessary efforts from webmasters — and perhaps also reduce noise in its own analysis systems.

What does this change mean for an SEO practitioner?

It forces a prioritization of schemas based on their SEO ROI. Gone are the days of mechanically validating all types of markup just to check a box. Now, you must ask yourself: will this schema trigger a rich snippet? A carousel? Stars? If the answer is no, Google itself is telling you not to bother.

It also simplifies diagnostics: if the Rich Results Test returns nothing for a marked-up page, either the schema is not eligible for enriched results, or there is an error preventing its utilization. In both cases, the signal is clearer than with the old tool.

• The Rich Results Test only validates schemas with a visible impact in the SERPs
• Non-eligible schemas for enriched results are no longer tested or reported by the tool
• This compels you to focus your efforts on tags that provide measurable SEO benefits
• Google sends a clear message: technical compliance alone is not enough, there needs to be a user effect

Has this distinction always existed in practice?

Let’s be honest: Google has never used all types of schema.org. From the start, only a handful of tags triggered enriched displays — Product, Recipe, Event, Article, FAQ, HowTo, Review. The rest? Stored, maybe analyzed for the Knowledge Graph, but with no direct effect in the SERPs.

What Mueller is formalizing here is already an established practice. The change is that Google is now publicly acknowledging it and adapting its tools accordingly. Before, we could deceive ourselves by seeing all our schemas validated. Now, the tool confronts you with reality: if it doesn't generate an enriched result, it doesn't exist for Google.

Do all valid schemas really trigger an enriched display?

[To be verified] — and that's where it gets tricky. Even with perfectly compliant markup tested positively in the Rich Results Test, nothing guarantees an enriched display in production. Google reserves the right not to display a rich snippet even if the schema is technically correct.

Factors play a role: perceived quality of the site, relevance of the query, competition on the SERP, Google’s A/B testing. We frequently see pages with impeccable markup that don't achieve any enriched results, while others with minor errors still show up. The Rich Results Test says 'eligible', not 'guaranteed'. A crucial nuance.

Should we remove all schemas not tested by the Rich Results Test?

Not necessarily. Some schemas like Organization, Person, SameAs don't trigger enriched results but likely feed the Knowledge Graph. If you're targeting an entity in the knowledge panel, these tags still hold value — even if the tool no longer validates them.

The problem is that we are navigating somewhat blind. Google does not clearly document which non-eligible schemas for rich snippets still have utility. My position: keep those that structure your main entity (Organization, Person on an author page), but avoid decorative markup that serves no purpose. If you must decide where to invest development time, focus on what the Rich Results Test validates.

Which schemas should be prioritized above all?

Focus your efforts on schemas eligible for enriched results documented by Google: Product (with Review/AggregateRating), Recipe, Article, Event, FAQ, HowTo, BreadcrumbList, VideoObject, JobPosting. These are the ones that the Rich Results Test validates and can trigger enhanced displays.

For an e-commerce site, Product + Review is the absolute foundation. For a media outlet, Article with structured image. For a local service site, LocalBusiness. Each type of site has its winning combo — identify it and implement it properly before spreading thin on secondary schemas.

How to quickly audit a site with this new approach?

Run all your strategic pages through the Rich Results Test via the API or manually. If a page supposed to have enriched results returns nothing, either the markup is absent, contains errors, or is not eligible. In any case, it's a signal for action.

Also use the Search Console, Enhancements section, which reports errors and warnings on schemas eligible for enriched results. Prioritize fixing errors that prevent display, then warnings that degrade quality. Ignore schemas not documented by Google — they won't yield anything in the SERP.

What errors should be avoided with this tool migration?

The first error: continuing to validate with the old tool out of habit and believing everything is fine just because the markup is technically correct. If the Rich Results Test detects nothing, your schema is useless for the SERPs, period.

The second error: brutally removing all untested schemas without thinking. Some may contribute to the Knowledge Graph or be used by third-party tools. Analyze the real use before getting rid of everything. The third error: thinking that markup validated by the Rich Results Test guarantees an enriched display in production — it's a necessary condition, not sufficient.

• Audit all strategic pages with the Rich Results Test, not the old tool
• Prioritize implementing Product, Article, FAQ, Recipe, Event schemas according to your sector
• Monitor the Enhancements section of the Search Console for production errors
• Correct blocking errors first, then warnings
• Do not remove Organization/Person schemas if they structure your main entity
• Test real display in the SERPs after each markup modification