Skip to toolbar

Find answers, ask questions, and connect with our
community around the world.

Forums Forums Bug Reports Schema.org is a quite messy

Tagged: , ,

  • Schema.org is a quite messy

     Mickael updated 1 month, 1 week ago 2 Members · 5 Posts
  • Mickael

    Member
    August 5, 2020 at 4:47 pm

    Hello,

    First, we really like your plugin.

    But, for the review block, there are 2 things we don’t understand.

    1. The schema generated by the Review block has a “reviewRating” and an “aggregatedRating” field. It appears that Google displays the “aggregatedRating” showing the number of advices, but we’d like to display the reviewRating instead (showing only 1 advice from 1 author)

    2. We have two products, same fields, same structure, but one leads to a correct Rich Result and the other one, no. They are both valid in the Google online tester, but one is missing the yellow magnificent shinning stars one google search page. Here is the two links : https://pxlbbq.com/test-western-digital-wd_black-d10-8to/ https://pxlbbq.com/test-clavier-razer-huntsman-mini/

    3. Is it possible to add a dropdown menu with all the possible item reviewed types. Generic “Product” by default, but also videogames, books, creativework, mobile app, movie, etc. A text field if it’s there is too much valid possibilities on schema.org ?

    Thanks a lot

    M01n34u

  • Alexis

    Member
    August 6, 2020 at 1:09 am

    Hi @M01n34u ! We’re glad you like our plugin.

    1. We’re trying to reduce the number of warning messages Google generates when using the review block’s JSON-LD code. Unfortunately, this means not showing the author’s name in Google’s entry for the page when the aggregate rating is specified. We’ll be adding an option to display the author name for those who don’t mind getting a warning for omitting the aggregate rating.
    2. I have no idea why Google treats those two pages differently even if the JSON-LD codes for those two pages are structurally identical. I noticed that the page where the JSON-LD code used USD as the offer currency worked, while the page where the code used EUR didn’t. Perhaps that could be the reason. You could check if switching from EUR to USD in the page where it didn’t work would fix it.
    3. We don’t have the option to do that yet. After specifying the item type, inputs for attributes specific to the selected item type would be also needed. We’ll be able to provide these options in a future version of our plugin.

    If you have other concerns about the plugin, please let us know.

    Regards.

    • Mickael

      Member
      August 7, 2020 at 2:25 pm

      Thanks a lot for the complete answer.

      For the point 2, we’ll try. For the third, we are thrilled by that.

      For the first, I think you misunderstood our problem. The issue is in the presence of the “aggregatedRating” which correspond with a aggrecation of client response. And it doesn’t fit the structure of the block where it feel like it’s only a website author review.

      • Alexis

        Member
        August 8, 2020 at 4:03 am

        Point taken regarding aggregateRating. The next version of the plugin will no longer include it.

        • Mickael

          Member
          August 9, 2020 at 4:18 pm

          Thanks a LOT !

          And confirmed, USD is good instead of EUR 😉
          Great team !

Log in to reply.

Original Post
0 of 0 posts June 2018
Now