Why is Google retiring the Structured Data Testing Tool, and what could you potentially lose?

Why is Google removing a tool that worked perfectly?

The Structured Data Testing Tool validated any type of structured data — Schema.org, Open Graph, custom vocabulary — without distinguishing their usefulness for Search. This functionality created an unrealistic expectation: a technically validated markup does not guarantee a rich display in the SERPs.

Google has observed that many webmasters were implementing types of schema that are unnecessary for their industry, simply because the tool validated them without error. The Rich Results Test, on the other hand, focuses exclusively on the types of structured data that Google actively uses to generate rich snippets, knowledge panels, or other enriched elements. This decision represents a strategic clarification: prioritizing business relevance over technical compliance.

What is the concrete difference between the two tools?

The Structured Data Testing Tool scanned all types of structured markup present on a page, whether or not they were utilized by Google. It detected errors in JSON-LD, Microdata, or RDFa syntax and provided a comprehensive report.

The Rich Results Test, however, filters drastically: it only returns types of schema eligible for rich results in Google Search. If your markup is technically perfect but pertains to a type of unsupported content (for example, a MedicalEntity schema without being a certified health page), the tool won’t even report it. This approach forces you to ask the right question: does my markup actually serve my SEO, or is it just unnecessary decoration?

Which types of structured data remain relevant after this change?

Google maintains a limited catalog of schema types that it actively uses: Product, Recipe, Event, Article, FAQ, HowTo, Job Posting, Local Business, Review, Video, Breadcrumb, Course. These are the structures that the Rich Results Test will diagnose. Everything else — even if perfectly implemented — generates no visible benefit in search results.

This distinction is crucial for prioritizing your technical resources. If you have implemented dozens of schema types

Is this decision consistent with observed practices in the field?

Absolutely. For years there has been a massive gap between technical validation and actual display. Sites with perfect JSON-LD markup do not trigger any rich snippets, while others with minor errors appear in rich results without an issue. Google has always been selective about what it displays, but the tools did not reflect this reality.

The withdrawal of the Structured Data Testing Tool is an implicit admission: the tool created more confusion than it resolved. By forcing SEOs to focus on the Rich Results Test, Google is promoting a healthy discipline — to stop treating structured data as a checklist and begin seeing it as a conditional lever. [To verify]: Google has never released statistics on the actual usage rate of rich snippets by type of schema, which would clarify which implementations are truly prioritized.

What nuances should be added to this announcement from Mueller?

First point: the timing. This deprecation comes at a time when Google is multiplying the types of rich results (videos, FAQs, products, recipes). Paradoxically, structured data has never been more important — but only if it targets the right goals. Mueller is not saying 'structured data is less important', he is saying 'stop wasting time on what is pointless.'

Second nuance: some types of schema not displayed in rich snippets can still have an indirect impact. For example, Organization and WebSite help Google understand the site architecture and the sitelinks searchbox, even though these elements do not always appear. The Rich Results Test will not detect them, but they remain useful. This is where the tool change creates a blind spot: you will need to use third-party validators for these edge cases.

Third point, and this is crucial: Google does not always release new types of rich results it is testing in advance. If you wait for the Rich Results Test to detect a schema type, you are already lagging behind early adopters who implemented it at the announcement. Let's be honest — this tool change favors the reactive at the expense of the proactive.

In what cases does this rule not apply?

If you work in regulated sectors where structured data serves other systems than Google Search (health data aggregators, product feeds for marketplaces, social networks that use Open Graph), the general Structured Data Testing Tool remains relevant. Google will deprecate it, but you will need to continue using alternative validators like schema.org's validator or third-party tools.

Another case: if you implement markup for vertical engines (Google Jobs, Google Travel, Google Shopping feed), these systems have their own validation criteria, often stricter than the Rich Results Test. The tool change does not affect these workflows — you will continue to test using dedicated tools (Merchant Center diagnostics, Job Posting validator, etc.).

What concrete actions should be taken in the coming weeks?

First step: audit your current implementations with the Rich Results Test instead of the Structured Data Testing Tool. Review all your critical pages — categories, product sheets, articles, landing pages — and identify what actually triggers a rich result versus what is simply validated without display.

Document precisely the gaps between present markup and utilized markup. If you have 12 types of schema implemented but only 3 generate rich snippets, you have a prioritization problem — or a potential goldmine of missed opportunities. This diagnostic phase is critical for streamlining your future efforts.

What mistakes should be avoided when migrating to the Rich Results Test?

Do not make the mistake of removing technically validated markup just because the Rich Results Test does not detect it. Some types of schema (Organization, WebSite, BreadcrumbList) remain useful even without direct rich snippet display. They contribute to Google’s overall understanding of your site.

Another pitfall: do not blindly rely on the Rich Results Test as the only validator. The tool is limited to the types of rich results Google publicly displays, but there are markup signals that Google employs without exposing them visually. Use the schema.org validator or third-party tools for complete syntax validation, then the Rich Results Test to confirm eligibility for rich displays.

And this is where it gets tricky: many webmasters will interpret this deprecation as a green light to slack off on structured data. Mistake. Google simplifies the tooling, but the eligibility criteria for rich snippets are becoming increasingly strict (content quality, guideline compliance, absence of spam). A technically perfect markup is no longer enough — content also needs to merit the rich display.

How can I ensure my site remains compliant after this change?

Establish a continuous monitoring process in Search Console, under the Enhancements section. Google reports structured data errors by type (Product, Recipe, FAQ, etc.) with examples of affected URLs. Pay particular attention to warnings — they often signal content problems rather than syntax issues.

Supplement this tracking with regular tests using the Rich Results Test on your critical templates, especially after CMS updates or changes in page structure. If a rich result type suddenly disappears, you will immediately know whether it's a technical bug or an algorithmic decision by Google not to display that snippet type anymore.

Keep in mind that these optimizations can quickly become complex, especially if your site manages multiple content types or if you need to coordinate dev and editorial teams. In such cases, bringing in a specialized SEO agency can significantly speed up diagnosis and implementation while avoiding costly missteps on such strategic elements as structured data.

• Systematically replace the Structured Data Testing Tool with the Rich Results Test in your QA processes
• Audit the schema types currently implemented and identify those that do not generate any rich displays
• Prioritize implementations like Product, Recipe, FAQ, HowTo based on your content type
• Set up Search Console alerts for structured data errors to quickly detect regressions
• Maintain up-to-date documentation of the schema types used and their measurable ROI (CTR, impressions, conversions)
• Test each new template or page modification with the Rich Results Test before going live