Plugin’s page markup wrongly identified pages as product rather than review

  • Resolved VA1DER

    (@va1der)


    5 years, 7 months ago

    Google console is showing my a whole bunch of warnings about my review pages. right off the bat, my reviews are incorrectly marked as product pages because the overall @type attribute added by the plugin is “product” and not “review”.

    Secondly, there there isn’t enough markup to make it a proper product page, so I’m getting warnings about missing attributes.

    I would like to know how a) retype my reviews as reviews and not products, or failing that, b) to at least add the missing attributes.

    The missing attributes are:
    “priceValidUntil”
    “aggregateRating”
    “availability”
    “brand”
    “url”
    “sku”
    Missing product ID

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Poonam Namdev

    (@poonam9)

    Hello @va1der

    We are already working on this issue. It should be fixed in the next version of the plugin.

    Sorry for the inconvenience.

    Thread Starter VA1DER

    (@va1der)

    Hi Poonam,

    Don’t apologize. I appreciate the fact you are working on this. It’s a great plugin. If there is any way I can contribute, let me know.

    Thanks

    Thread Starter VA1DER

    (@va1der)

    I see the new review type, and all the schema markings that can be added. This is a great system, but it appears to have some bugs.

    I selected a review of type “product”, started filling in new fields. When I saved it and went back, I now cannot expand the new review type fields. Clicking on the header just causes it to expand to one empty line. It is not parsing what was added correctly.

    Secondly, I notice that no matter what review type you select, the entire schema is of type “product” and not of type “review”. For a review of a product, I believe the hierarchy needs to have review as the base schema type, and product as as a subtype.

    Lastly, even when I do not have a dollar value put in, it is still adding the “offer” schema markings. Is there a way to have it remove offer from the schema markings when there is no offer?

    Thanks

    Thread Starter VA1DER

    (@va1der)

    I have further information on the bug. If there are any single quotes (for example an apostrophe) in and fields stored in wppr_review_custom_fields then the plugin fails to be able to parse it.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin’s page markup wrongly identified pages as product rather than review’ is closed to new replies.