Google has updated its review snippet documentation to make it absolutely clear that when a review or an aggregate rating sits inside another schema type, the itemReviewed field should be left out so Search can correctly understand what is being reviewed.
Google has revised its review snippet guidelines, explaining how site owners should mark up reviews and ratings when they are placed inside another schema type.
The update appears in Google’s review documentation and affects anyone who uses structured data to help search engines identify what a page is reviewing.
Google wants sites to avoid sending mixed signals about which item is being reviewed so search features can work more accurately.
The updated rule says that when a review or an aggregate rating is nested under a parent item, the itemReviewed field should be removed because the parent already provides that context.
Why Google Made the Update
Before this update, developers relied on wording that left room for uncertainty. The documentation mentioned itemReviewed, but did not fully explain how nested reviews should be handled.
Many sites ended up including itemReviewed inside nested objects even though the parent already identified the item. That often resulted in duplicated references and unnecessary noise that could complicate how Google interpreted the data.
By rewriting the documentation, Google removes the ambiguity.
The new guidance tells developers exactly where itemReviewed belongs and where it does not. This helps Search extract cleaner, more consistent information.
A Clear Breakdown of Before and After
Before the Update:
- The documentation referenced itemReviewed but did not specify its correct use for nested reviews.
- Developers often included itemReviewed inside nested review or aggregateRating objects because the rules were not explicit.
- Duplicate identifiers sometimes led to inconsistent review snippets or warnings in Search Console.
- Nested implementations varied across websites and plugins, creating uneven results.
After the Update:
- Google now states directly that itemReviewed should be omitted when a review or aggregate rating is nested under a parent item.
- A nested review should rely entirely on the parent schema type to identify what is being reviewed.
- References such as itemReviewed.name are now clarified to point to either the standalone item name or the parent item name, depending on the structure.
- The documentation now guides developers toward a cleaner, more predictable markup style.
What This Means for Websites Using Review Schema
Many product pages, business profiles, service listings, and recipe sites use nested reviews. Under the updated guidance, these pages may need small changes.
If itemReviewed exists inside a nested review, it should be removed to prevent mixed signals. Google already knows the review belongs to the parent, so repeating the field only adds clutter.
Plugins and CMS tools that automatically insert itemReviewed within nested objects may require updates as well. Developers should test their output to make sure it aligns with the new expectations.
Many businesses rely on expert support to keep their structured data aligned with new search standards. Stan Ventures’ professional SEO service team regularly handles schema cleanups and review snippet optimization for brands that want to stay compliant without technical headaches.
If you need help updating your review schema or improving visibility in Search, Stan Ventures can guide you through the process.
What Developers and SEO Teams Should Do Next
Here are the steps that help bridge the updated guidance with practical implementation.
- Review the existing schema to see where nested reviews or ratings appear.
- Remove itemReviewed from any nested object, and let the parent item define what is being reviewed.
- Test updated markup using Google’s Rich Results Test or Schema Markup Validator.
- Check review- and rating-related plugins to ensure they do not insert the field in nested locations.
- Monitor Search Console after publishing changes to confirm that structured data is being read correctly.
What This Means Moving Forward
This update does not overhaul how reviews work in search, but it makes the rules clearer and the expectations easier to follow.
Sites that clean up their structured data should see fewer warnings, more consistent parsing, and a smoother experience when rich snippets appear. It also encourages cleaner schemas in general, reducing the chance of misalignment between user-facing content and structured data.
Key Takeaways
- Google now confirms that itemReviewed should be omitted inside nested reviews and nested aggregate ratings.
- The parent schema item provides the information Google needs about what is being reviewed.
- Redundant fields create confusion and may affect how review snippets appear.
- A quick audit of templates, plugins, and CMS outputs can prevent errors.
- Always test markup updates and monitor Search Console for indexing feedback.
Zulekha
AuthorZulekha is an emerging leader in the content marketing industry from India. She began her career in 2019 as a freelancer and, with over five years of experience, has made a significant impact in content writing. Recognized for her innovative approaches, deep knowledge of SEO, and exceptional storytelling skills, she continues to set new standards in the field. Her keen interest in news and current events, which started during an internship with The New Indian Express, further enriches her content. As an author and continuous learner, she has transformed numerous websites and digital marketing companies with customized content writing and marketing strategies.
