• Resolved Andrew

    (@lifesabargain)


    I’m curious if this plugin contains rich snippet markup for google? I’ve been using the plugin and received this message from google:

    “Google systems show that your site is affected by 2728 instances of Recipes markup issues. This means that your Recipes pages might not appear as rich results in Google Search.

    Search Console has created a new report just for this rich result type. The new report enables you to identify, fix, and resubmit affected pages to Google so they can start appearing in Search Results with rich result features. ”

    Does this plugin create rich markup? Or do you suggest a good way to do this?

    Thanks!

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Meal Planner Pro

    (@mealplannerpro)

    Hello,

    Our plugin does markup your recipes with the latest schema for Google and Pinterest. Can you please send a link to your site so that we can test why you’re receiving the markup issue notifications? info(at)mealplannerpro(dot)com

    Thanks

    Plugin Author Meal Planner Pro

    (@mealplannerpro)

    We received the same email message from Google for our site Meal Planner Pro. This tells us Google is really pushing recipe authors to include all the recipe info possible. Missing info such as cook time, keywords, recipe ratings etc. will show as markup issues or errors which could affect your recipe view search ranking.

    Our plugin will markup all the recipe info with JSON-LD schema which Google wants. If a recipe doesn’t include info then we can’t mark it up. It’s important that you include as much info as possible with each recipe. Also, you should consider enabling recipe ratings from our plugin settings.

    We will also be only using JSON schema from now on. At one time Pinterest could not work with JSON for rich pins so we had to include schema . org for them. Pinterest rich pins are now compatible with JSON so we can remove schema .org. This will reduce the number of potential errors in half.

    I hope this makes sense. Bottom line is that Google wants as much info included in your recipes as possible. Any info you enter will be marked up correctly by our plugin for both Goolgle recipe view and Pinterest Rich Pins. If you’ve entered all the info then you won’t see any errors.

    Thread Starter Andrew

    (@lifesabargain)

    Yes, here is a page on my site with a recipe: https://scrappygeek.com/four-bean-salad/

    Thanks!

    Plugin Author Meal Planner Pro

    (@mealplannerpro)

    Thanks. There’s nothing to worry about with the notification from Google. It’s their way of saying please add more info to your recipes. They want as much info as possible. i.e. – cook times, summary, keywords, nutrition, ratings etc.

    As you add missing recipe details the errors will be removed. Our plugin will markup the info to Google’s requirements but if there’s no info to markup then you’ll receive an error for each missing item.

    Google is just pushing food bloggers to include more recipe details. Our plugin has you covered.

    I can send you an email mail newsletter we just sent out with more details if you like.
    Just need your email address.

    Thanks

    Plugin Author Meal Planner Pro

    (@mealplannerpro)

    FYI – we now only use JSON-LD recipe schema markup. This is what Google requires and is compatible with Pinterest rich pins as well.

    You simply need to start adding as much recipe info as possible so that Google doesn’t count missing info as an error. It’s important to use our “Nutrition Analyzer” and “Tag Manager” features as well. They will automatically fill in much of this info Google wants for accurate nutrition and tags/keywords.

    Bottom line is the more info you include the higher your recipes will rank in Google recipe view search results. Our plugin automatically marks up the info you enter.

    Thanks

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Recipe Rich Reaults Markup?’ is closed to new replies.