Hi there,
I’m having some trouble with the information displayed in Reviews on the Google testing tool when using reviews. To address this I’d need to move the closing </article> tag to immediately after the article content, ignoring any sidebar or related/author articles box which also include article markup. Is there a way to do this without affecting the layout? Is this being addressed for future updates?
Thanks!
Hi,
Could you please also specify what type of problems google testing tool indicates you have and also provide your site’s url so we can have a look at this.
Also let us know what post template you use.
You can try to move the article closing tag if you need to do it but it would be best to let us about the problem you have, we’ll test this and fix as soon as possible.
Thanks
Thanks for replying,
The problem I’m having is that I’m able to create a review but it includes elements of other posts. An example is at http://www.xposy.com/technology/ori-and-the-blind-forest-review I’ve managed to select the name using schema markup but the elements are still included when testing. It’s using post style 2. I think this is because article tags are included before the original one containing the schema markup is closed
Hi,
I’ve added it on our list, we’ll fix it as soon as we find the solution, thanks for reporting this.
Thank you, Emil G.
Thanks very much for looking into this. For now I’ll try closing the article tag after the content and see if I have any luck.
Hi,
It seems that you’ve managed to solve this as I’ve tested this using google’s structured data testing tool and your reviews aren’t returning any error: http://screencast.com/t/izbRmZkT
We’ll do further testing regarding this and add it in the next update if all it’s ok.
Thanks for reporting it!
Hi,
I have same problem.
In the testing tool, it said “The review has no reviewed item specified.”
http://www.screencast.com/t/K2TAnkLws
The testing URL is https://www.enterpr1se.info/2015/03/bang-bang-modern-chinese-cuisine-review/
Hi,
As I said above we have this on our todo list for further testing and we’ll fix in the next update.
Thanks
