JSON-LD ratings doesn’t work anymore ….

Unfortunately, it seems that I have the same problem even with Microdata… It doesn’t show up unless I edit the posts once. I have over 3000 posts and I really need a viable solution for this.

Looking forward to your insights.

You can’t just do this automatically. Google has imposed serious restrictions on how rich snippets with ratings work, and they require a lot of information. So, you just setting everything as Product will not fly, because you need to insert all the required Product information for each post you want to be valid. If only one element of the snippet fails, it gets ignored. And, only some snippet types qualify in the first place.

You can set post type to use Product by default through global settings, but you need to modify each post and insert all required product data for the snippet to work. There are no shortcuts here, and that was the point of what Google did: provide very relevant information and to stop exploiting the snippets rating system for promotion.

Milan

I am not doing it automatically! I have built the rating data over the years and now it doesn’t appear on my posts anymore.
The rating data is present but the schema markup (JSON-LD or Microdata) isn’t shown any more unless I update each post manually.
All of my rating data is indexed and shown in google search results and this way all my rating data is going to be removed from google index …
So again I really need a viable solution.

Let me give an example :
Let’s say I have posts for a product that I sell which has 152 ratings and 4.2/5 Stars. After upgrading to the 3.0 version the schema markup is not present in the post and google search console says it can’t see the ratings anymore.
It only shows up if I hit the Update button in the post.
I hope this clarifies my problem.

• This reply was modified 4 years, 10 months ago by metalsoft.

How you could have had data in the rating plugin for rich snippets when that was not an option before this release? The previous version of the plugin had only basic options to set the rich snippets, it had no support for snippet types specific data like Products.

In your example, if you have the product before this version, how did you generate the rich snippet that is valid with Google? It was not with my plugin that is for sure, because it had no ability for that, it was able to generate the snippet with basic information only, and that is no longer enough for Google to validate the snippet. If you have a product, you need to add a lot of information about it in the new plugin version interface for Product in Rich Snippet metabox.

I understand your problem now, and I will investigate why plugin don’t generate snippet (even if it is invalid) before saving the post, but that doesn’t solve the issue – for product type you need to insert a lot of information Google requires now.

I never had to set the snippet type before. The ratings were there and google picked it up.
I just started setting the type to “Product” after upgrading the plugin and never before and only because it stopped showing the AggregareRating for my posts.
I have downgraded temporarily to v2.7.1 and right now I don’t have a problem but I have to upgrade at some point.
Oh and one more thing, I checked right now, and even in 2.7.1 I have the option to set rich snippets Item Scope to Product so I don’t know what do you mean by the option not being there before. it is definitely present in plugin setting, Rich snippets addon.

Here you can see a few pictures showing the options on V2.7.1 :

View post on imgur.com

• This reply was modified 4 years, 10 months ago by metalsoft.

Updated version 3.0.2 is released with the fix. It now includes rating as it should regardless of the snippet type. The problem remains, the snippet will not be valid for Google to use it, and there is no guarantee that they will use it with all the data for it missing (brand, identifiers…).

Regards,
Milan

Thanks a lot. I am going to upgrade in a few hours and then report back.

Thanks again. After the latest update my issue is resolved.