Which validation tool are you using? Google rich results test shows only warnings (not errors) about missing ratings and reviews:
https://search.google.com/test/rich-results/result?id=Rmwa_XpWJK28KzSopduMBQ
Which ratings and reviews plugin are you using?
Which plugin is creating the “_ts_MPN” custom field for your products, and where did you enter the “_ts_MPN” custom field name in the WPSSO settings?
js.
Thread Starter
Sandra
(@spoodes)
Hello, thank you for your reply! 🙂
I am just looking into the Google Search Console alsmost every day for a quick glimpse. Today the above named warnings appeared newly for more than 2.000 products at once. – So this seems to be a new general error.
Indeed those are all “yellow warnings” (not “red errors”).
I am not using a special rating plugin, except WordPress/Woocommerce itself. And additionally your “WPSSO Add Five Stars”.
The field “_ts_MPN” is created by the Plugin “Germanized”. This plugin offers a field for the MPN int the product editing page.
I entered it at WPSSO > Advanced > Attributes and Meta > MPN Attribute.
And also under Custom Fields > Product MPN Custom Field.
Thank you. (No hurry needed!)
Sandra
FYI, looking at your Schema markup, it looks like the ProductGroup has an MPN (ie. the WooCommerce product), but not the individual products (ie. the WooComerce variations). If your WooCommerce variations do not have an MPN custom field, then WPSSO cannot add that custom field to the markup for variations. If you’re using a plugin to manage that MPN custom field, make sure it allows variations to inherit that custom field as well.
js.
Thread Starter
Sandra
(@spoodes)
Thank you! I see!
Indeed I am never entering an MPN for the variations, just one for the whole product.
I guess thats not a big thing in the end, if it stays this way now.
Each product in a product group should have a unique MPN, GTIN, UPC, ISBN, etc., so if your variations do not have a unique MPN, the products in the product group should not have an MPN (as duplicate MPN numbers would be an incorrect).
In the past, WPSSO Core would create a single product with multiple offers, but Google Merchant does not understand multiple offers very well, so Google has created a new Schema ProductGroup type specifically to deal with product variations. Unfortunately, the real world applications of this are still being ironed-out. For example, WooCommerce allows you to rate/review a product, not a variation, so WPSSO Core can add ratings/reviews to the product group, not the individual products (ie. the variations) in the product group as variations do not have any ratings/reviews.
There’s nothing to change for the MPN issue – variations either have unique MPNs, or they don’t, but I should be able to add WooCommerce ratings/reviews to products within the same product group using @ids to minimize duplication.
js.
No problem.
Product inheritance of ratings and reviews for variations has been added in WPSSO Core v15.1.0-dev.3. See here for more info: https://wordpress.org/plugins/wpsso/#developers
js.
Thread Starter
Sandra
(@spoodes)
Thanks and all my best from Germany!
Thread Starter
Sandra
(@spoodes)
Hello js, thank you for the update!
It seems, Google is now happy again with the previous missing “aggregate Rating”, the “review field” and the “description”. 🌹
But unfortunately there plopped up something new today:
“The review has multiple aggregate ratings (in “review”)”
Example URLs:
https://spoo-design.de/produkt/68322/
https://spoo-design.de/produkt/62402/
Sorry, for bothering you again….
Sandra
Yes, that is because two products in the product group have the same review and aggregate rating. It seems that Google cannot make up its mind as to whether the product group should have the reviews and aggregate ratings, or they must be duplicated for each variant (ie. each product in the product group). It’s a bit of a catch 22 situation as WooCommerce does not offer ratings and reviews for each variation, only the main product. When using the Google rich snippet tool, you can use the “?” feedback option to report errors/warnings that should not be errors/warnings.
If I were to choose, I would prefer leaving the ratings and reviews in the product group, but Google does not support this, as we saw earlier.
js.
FYI, the reviews use an @id value to connect reviews with products, but because the markup of the aggregate rating is so small, we haven’t used an @id. I’m thinking Google might prefer an @id for the agreggate rating block as a signal that the same block is connected to several products. I’ll add an @id to the aggregate rating markup in the next version of WPSSO Core.
js.
FYI, an @id for the aggregate rating markup has been added in WPSSO Core v15.2.0-dev.5.
See here for more info: https://wordpress.org/plugins/wpsso/#developers
And here to download the current development version: https://wordpress.org/plugins/wpsso/advanced/
js.
Thread Starter
Sandra
(@spoodes)
Thank you very much for taking your time into this!
Honestly, I am not so much in it – and that is why I bought your plugin, which I am generally very happy with. 🙂
I know that Google is constantly changing their requirements.
Just, before the last update of WPSSO (before 15.0 or 15.1 and further back) – their were no complaints in the Search Console.
But in the end I do not know, if it was a Plugin – or Google itself, who has changed something once more….
WPSSO Core v15 has switched to the new ProductGroup markup for WooCommerce variations, and Google is still ironing out its requirements for this new markup. See here https://surniaulula.com/2023/apps/wordpress/plugins/wpsso/whats-new-in-wpsso-core-v15/ for more info.
js.
Thread Starter
Sandra
(@spoodes)
Thank you! I understand the issue better now! So you really have to maneuver through….
