New Recipes issues detected for site

Hi @hehafner,

We will investigate, and get back to you on this.

Rogier

Hi @hehafner,

I think I have found a possible solution for this. Google seems to interpret the image only if it’s an object, not when it’s a URL.
https://stackoverflow.com/questions/34595924/google-complains-image-missing-or-invalid-itemtype#comment56948869_34599404

I’ve also come across some info that suggests only to use the json-ld microdata. The article above suggests that removing the html microdata and leaving only the json-ld will also resolve this.

I’m releasing a new version this week, I’ll then do some tests with the above.

Is this something that I need to do to my website, or just wait for the update?

Thank you for helping with this problem.

Heidi

Hi @hehafner,

You can just wait for the next update. I’ve started on some schema.org related improvements, and will include this in the update as well. Hope to finish this in two weeks.

Hi @hehafner,

I just dived deeper into this issue, and see that Zip Recipes works fine with images in Google. I did a double check on your site, and see that you have another recipe reference on the page, which is not coming from Zip Recipes.

So now there are two: one from Zip Recipes, and one custom Recipe declaration. This causes the recipe data not to be understandable.

I think if you remove the one in the <article> element the issue will be resolved.

Thank you, @rogierlankhorst for looking into this deeper for me.

I went back into the post and found that there is a Markup Scheme under the editor that WP supplies and the skin that I use, Agility, also supplies one. Both of these were set on “Recipe.” Perhaps this is the problem? Other than that, there is only one recipe in the post.

I have turned off the skin schema for now and will see if that helps.

Thanks

When I now run your site in the schema.org tester, I get a valid image:
https://search.google.com/structured-data/testing-tool/u/0/?hl=nl#url=https%3A%2F%2Fchefeliana.com%2Fpastalaya

Thanks again @rogierlankhorst! I’m still getting email from google saying:

Top new issues found, ordered by number of affected pages:

Invalid value type for field “prepTime”

Invalid value type for field “cookTime”

But I think if I shut those off I’ll stop getting the alerts.

It looks like you haven’t filled those values out that, is that correct?

Correct. My client hasn’t. I opened them up so she would see them to fill in. So, I’m sure that she would fill them in when she sees them. However, if having blanks cause Google to choke, I may need to hide them. Please correct me if I’m wrong.

Thank you

When I open the tester, it says “warning: field … is recommended. Supply a value if available”

This means there is no error, only that Google recommends to use this value. No harm done if you don’t.

Thanks, @rogierlankhorst! You’ve helped a great deal. I’ll close this ticket now! Thank you for all your hard work!