Invalid object type for field "itemReviewed"

[Gabriel Torres]

Hi,

After the improvement in Review microdata added in version 4.6.8, Google is now complaining about this:

Invalid object type for field "itemReviewed"

Sample URL: https://www.clubedohardware.com.br/livro-redes-de-computadores

Where:

"aggregateRating": {
        "@type": "AggregateRating",
        "reviewCount": 5,
        "ratingValue": 4.8,
        "bestRating": "5"
    }

If you run this URL at https://search.google.com/test/rich-results, you will see the same error being pointed out.

Please advise.

Cheers.

[Adlago]

I confirm links to all my articles have been reported by Google with this issue.

[Marc Stridgen]

Thank you for reporting. I have added a bug report for this so that it can be looked into

[Stuart Silvester]

The problem as far as I can see is with Google. Schema.org supports the aggregateRating property in an Article schema type - https://schema.org/Article (and many others).

However, Google is picky and they only support it in a certain types. - https://developers.google.com/search/docs/advanced/structured-data/review-snippet. You'll notice that they don't have support for reviewing 'Articles'.

It comes down to whether to leave it in place for any other search engine or platform that uses the data, or remove it to appease Google.

[Gabriel Torres]

@Stuart Silvester In our case,the reviews are only enabled in two databases in Pages: books (which lists our books) and courses (which lists our online courses). Maybe an option in Pages to select the kind of property, i.e. a setting that we can select the proper property (e.g., Book https://schema.org/Book or Product https://schema.org/Product), depending on the kind of database we have. I believe this would fix the issue. Just an idea. Because right now the platform lists everything as Article.

[Hisashi]

@Gabriel Torres The articles on my website have been having the same issue after the upgrade 4.6.8. Did you manage to solve the problem?

Edited November 30, 2021 by Hisashi

[Gabriel Torres]

@Hisashi No. This is an issue that IPS is already aware of (see previous posts).

[Marc Stridgen]

This has now been resolved in the 4.6.9 version which has just been released. Please feel free to let us know if you are seeing any issues after upgrading