Google Tightens Review Schema Rules Has Anyone Faced Plugin Conflicts After the Update?

[RMX]

Google has officially updated its Review Schema guidelines, and a lot of sites may be unknowingly breaking the rules. The key change:
If your Review or AggregateRating schema is nested under another schema type, you must NOT use itemReviewed.
Google now expects the parent entity to define what’s being reviewed no more repeating it in nested objects.

This update comes after years of duplicated data, mixed signals, and messy rich snippets caused by themes and plugins injecting redundant itemReviewed fields.

What needs to be fixed:

• Remove itemReviewed from nested Review/AggregateRating schema
• Validate again via Rich Results Test
• Check if your SEO plugin or theme is still injecting it
• Monitor Search Console for cleaner markup

It’s a quick fix for most setups, but plugins not updated to the new rules are already causing warnings.

Is anyone experiencing conflicts or warnings from SEO plugins after this schema rule change?

 

[NimbusTheOwl]

Yes, many website owners are experiencing conflicts or warnings from SEO plugins due to the new Review Schema guidelines update, especially if their plugins haven't been updated to remove the nested itemReviewed fields.

 

[RMX]

Yes, many website owners are experiencing conflicts or warnings from SEO plugins due to the new Review Schema guidelines update, especially if their plugins haven't been updated to remove the nested itemReviewed fields.

Totally makes sense a lot of plugins haven’t caught up yet, and schema updates always expose the slow movers.

Here’s a probing question you can add to keep the discussion flowing:

Have you found a plugin or setup that handles the new schema rules correctly out of the box, or are you manually fixing the markup for now?

 

[tommshardy]

Great insight! This update definitely changes how plugins handle review schema — curious to see how others are dealing with these conflicts.

 

[nukuta]

I had to manually strip it out using a custom schema block until the plugin devs release a fix. If anyone’s using Rank Math or older Yoast versions double-check your structured data output.

 

[RMX]

Great insight! This update definitely changes how plugins handle review schema — curious to see how others are dealing with these conflicts.

Looks like quite a few plugins havenot adapted to the new review schema rules yet, so the itemReviewed conflicts are popping up everywhere. I’ve had a couple of sites throw warnings the moment Google pushed this update.

Has anyone checked whether the issue is coming from the theme markup or the SEO plugin output?

Quick fix for now is to remove itemReviewed from nested Review/AggregateRating and re-validate cleans everything up straight away.