-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid object type for field "itemReviewed" #141
Comments
Same here! |
There is nothing I can do actually. I would recommend disable Rich Text Snippet. You can read more details here https://webmasters.googleblog.com/2019/09/making-review-rich-results-more-helpful.html or discussion here which took place few months back https://wordpress.org/support/topic/new-google-requirements-for-structured-data/ |
Ok. |
Under WP-Admin -> Ratings -> Rating Options. |
@lesterchan Wouldn't it be a solution to add a select field in the setting where you can globally select the type of the articles on this page, or a additional setting in the article page? For example I need the type "Recipe" for a food blog. This would be a great solution. |
@rogervanwile in an ideal world yes, but it is too much work for me right now. Feel free to help and send back a pull request if you did. Having said that, it still does not solve the problem. If you are not doing a site on Recipe, but still choose to use Recipe so that the ratings can display in Google. If Google found out, your site might be blacklisted or some sort. |
Is there anything we can do to avoid disabling Rich Text Snippets (RTS)? Be able to show the ratings in Google is one of the main reasons on using this kind of rates... In my case, half of my posts are book reviews (that uses Book schema) that works fine with rich snippets (data is correct), but the other half that use Article schema give this error. So... Is there a way to disable RTS only in "article" schema posts? Something I can insert in the PHP that assigns the proper schema to each post. |
@CabalTC Good point, I added a new |
Tested on a live web. It works fine for the non-disabled ones (books as https://cabaltc.com/el-misterio-de-salems-lot) and I think half work for the Articles (https://cabaltc.com/pedir-que-te-hagan-una-resena) where rich snippets are disabled via code. Problem is that, if you disable Rich Snippets from the customizer (old way), all Schema is removed (checked in Google's Schema Validator), but if you do so using the new filter, Schema is defined BUT all data is empty, so there are several warnings and errors displayed in the schema validator. Do you need more info? PS: code that use the new filter is in place, so you can check the URL's schemas if you want. |
I am not sure how do u disable via customizer? I don't remember supporting it |
I mean via wp-admin: ratings > options > Rich Snippets (Y/N)
El El mar, 18 feb 2020 a las 15:31, Lester Chan <[email protected]>
escribió:
I am not sure how do u disable via customizer? I don't remember supporting
it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#141?email_source=notifications&email_token=AGYRXHIHBAW3VDBT2ETHM3DRDPWMBA5CNFSM4KS3D5KKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMCFV6Y#issuecomment-587487995>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGYRXHK5QJKGDQNKTJY6JQLRDPWMBANCNFSM4KS3D5KA>
.
--
David Olier
Escritor y consultor Worpdress
https://DavidOlier.com
|
Oh that is the options page. Okie I missed out one place, you can try downloading the file again. |
Works fine! Now it has the same result to remove GRS with the options page and the new filter. Thank you! |
Hola. Alguien pudo solucionarlo? Sigue arrojando error estado deshabilitado: https://irrigadorbucalone.com/cual-es-el-mejor-irrigador-dental |
Google Search Console gives this error: Invalid object type for field "itemReviewed"
You can see it here: https://search.google.com/test/rich-results?utm_campaign=devsite&utm_medium=microdata&utm_source=review-snippet&id=V_vyTdviz0t83nIrXJQN3Q
The text was updated successfully, but these errors were encountered: