cochiloco

Well, I’m not sure why this is turning into an academic discussion as I’m talking from experience.

This has also happened to a commenter in the following thread: https://andrewhansen.name/seo/spammy-structured-data-manual-action-penalty/

My only guess is that as google says in the link you provided:
https://developers.google.com/search/docs/data-types/product

“Using markup to enable rich product results lets you attract potential buyers while they are searching for items to buy on Google or images that include products you sell.”

It implies that users need to be able to buy the product directly from you in order to label the item as Product, perhaps because it will appear in Google Shopping results as well.

If it’s a 3rd party critic review of the product labeled as “Product” then Google doesn’t like that. I followed this guy’s advice and changed the label to Review (via another plugin), then submitted a reconsideration request in google search console and the manual penalty was lifted.

I also noticed that all of my competitors doing 3rd party reviews also only had “Review” as the only label and not “Product”.

Incidentally, there is also another bug in YASR because it allows values less than 1 star, which google flags as an error (you can see it in their structured markup testing tool) because if it’s less than 1 then it then requires a min and max value.

Yes there is.

The problem is when pages contain product reviews. It turns out that google doesn’t like having Product as a top level item with a nested review as this implies that this is the main product page that happens to contain reviews as well, and not a 3rd party critic review page.

The Review type should be the top level item for posts that are critic reviews. Otherwise, it results in a spammy structured markup manual penalty.

I did add it at frontend/class-opengraph.php but doesn’t seem to have any effect.

Has anyone gotten this to work?

Thanks! Where should I add that? In YoastSEO’s code?

Anybody?

Will do, thanks!