Should you really implement all the new types of structured data supported by Google?

Why is Google adding these types of structured data now?

Google never communicates about the timing of these additions, but the expansion of the rich results test to Article, Review, and EmployerAggregateRating is significant. These three types meet massive user needs: consuming editorial content, making purchase decisions based on reviews, and job searching.

The inclusion of these formats in the testing tool means that Google can now validate and display this enriched data in the SERPs more systematically. It's not a guarantee of display — it never has been — but it's a strong signal that these markups are becoming eligible for advanced search features.

What's the difference between 'supported' and 'displayed in results'?

This is the classic trap. Google can understand a type of structured data without necessarily visually leveraging it in search results. Technical support does not guarantee the display of a rich snippet.

In this case, Mueller states that these types are integrated into the rich results test — which means that the tool can validate your markup and signal errors. But the actual display depends on other criteria: query relevance, content quality, competition on the SERP, and likely internal trust thresholds at Google.

Which sites are affected by these new types?

Online media, blogs, and news sites benefit from marking up Article to signal their editorial content. E-commerce sites, comparison sites, and review platforms utilize the Review markup to display stars and aggregated ratings. Career sites, job boards, and 'Join Us' pages can leverage EmployerAggregateRating to enhance their employer brand.

If your site publishes structured content in any of these formats, you have every reason to audit and validate your Schema.org implementation right now. Google won't warn you a second time.

• Article: editorial sites, blogs, online magazines, news portals
• Review: e-commerce, comparison sites, customer review platforms, buying guides
• EmployerAggregateRating: corporate sites, career pages, job boards, HR platforms
• The rich results test allows you to technically validate your markup, but does not guarantee display
• Inclusion in Google's official test is a signal of intent: these formats are becoming a priority

Is this announcement consistent with practices observed in the field?

Yes and no. The markups Article and Review have existed for years in the Schema.org spec and are already widely deployed. What changes is their official integration into Google's testing tool — a signal that the engine wants to standardize their validation.

On the other hand, the EmployerAggregateRating markup is much less mature in terms of display. Very few rich snippets related to employer ratings appear in the classic SERPs, even for queries like 'company reviews' or 'working at'. Google still favors its own sources (Google for Jobs, Knowledge Graph). [To be verified] whether this addition foreshadows a broader deployment or remains limited to specific use cases.

What nuances should be added to this statement?

Mueller does not say that these markups are new, he states that the rich results test now supports them. There's a nuance. You could already implement Article, Review, or EmployerAggregateRating before this announcement — it's just that the official validation tool did not support them, or validated them via generic formats.

Another point: Google publishes no data on the actual impact of these markups on click-through rates or rankings. It is known that stars in SERPs can boost CTR, but the effect on ranking remains unclear. Don't count on these structured data to compensate for weak content or a poor link profile.

In what cases does this development change nothing for you?

If you are not in the affected sectors — no structured editorial content, no customer reviews, no career page — this announcement brings you nothing concrete. It is useless to force a Review markup on pages that do not contain it.

Even in the affected sectors, the impact depends on the maturity of your implementation. If you already have clean markup validated via other tools (schema.org validator, Chrome extensions), you are not late. What matters is the quality of the implementation, not the validation tool.

What should you do if you publish editorial content or reviews?

First step: audit your existing markup. If you already use Article or Review, run your pages through Google's rich results test to ensure no errors come up. Partial or poorly formed implementations are useless — worse, they can be harmful.

Second step: complete the recommended properties. Google distinguishes between mandatory properties (without which the markup is invalid) and recommended properties (which enhance the display). Adding author, datePublished, image for Article, or reviewRating, reviewBody for Review can make the difference between a generic rich result and a standout snippet.

What mistakes should you avoid when implementing these markups?

Classic mistake: duplicating markups in JSON-LD and Microdata on the same page. This creates conflicts, and Google may ignore both. Choose one format and stick to it — JSON-LD remains the most recommended by Google.

Another pitfall: marking up automatically generated content without human validation. If you aggregate third-party reviews, ensure that the data reflected in the markup perfectly matches what is displayed on the page. Google detects inconsistencies and may remove your eligibility for rich snippets.

How can you ensure your site is compliant and optimized for these new types?

Use the Google rich results test as a priority, as it determines whether your markup will be utilized. Complement with the Schema.org validator for stricter technical verification.

Also, monitor the Search Console, Improvements section. Google highlights errors detected in your markups (missing properties, invalid values, conflicts). If you see warnings about Article, Review, or EmployerAggregateRating, resolve them before Google stops displaying your rich results.

• Audit key pages with Google's rich results test
• Complete the recommended properties (author, image, datePublished, reviewRating)
• Avoid markup duplication (JSON-LD + Microdata on the same page)
• Check for consistency between structured data and visible content
• Monitor the Search Console for errors reported by Google
• Test display under real conditions through targeted queries