Format Recipes Using Rich Snippets and Microformats
Recipes need to be formatted to generate rich snippets. For recipes, using hRecipe microformat is a good way to go especially if you are using WordPress as your blog software since there is a plugin. For those of you who aren't web designers or programmers, I should explain that rich snippets are generated by using specific tags within HTML code that allow Google to recognize data as a recipe along with the various components that comprise a recipe. Here are some good resources to understand the process:

Google's Webmaster Tools documentation of the process for recipes, Rich Snippets Testing Tool, Rich snippets general info (microdata, microformats, RDFa)
Google's Recipe Search and Rich Snippets Elise Bauer (simplyrecipes.com) at Food Blog Alliance. Simply Recipes recipes are showing up in the Google Recipe search so she clearly knows the scoop.
Making Microformats Manageable: The New RecipeSEO Plugin Allison Day (recipeseo.com) at Food Blogger Forum. Here is the direct link to her WordPress plug.
Food Bloggers: How Google's New Recipe Search Works Meathead Goldwyn at Huffington Post
New Google Recipe Search Means Extra Coding for Food Bloggers Dianne Jacob at Will Write for Food
How I adapted my blog to Google’s recipe search at Café Liz
Amanda Hesser at food52: Google's New Recipe Search

Basically, you should know that recipe data now has to be marked with specific tags so Google's search engine can recognize the information as a specific content type namely, a recipe. Right now, doing this takes time and some coding knowledge, which is a pain, but doable. Hopefully, this process will get easier as more editing tools become available to bloggers.

Submit a Form to Google about Including Your Site
Google suggests you fill out this Interested in Rich Snippets? form to alert them that your site is now using the required markup code and should be indexed by Google Search. You are required to submit four examples of pages that incorporate rich snippet code and have been validated using the Rich Snippets Testing Tool but it is not clear how much of your site needs to be compliant or how long it will take in order for Google to start displaying your results.

Follow the Procedure, Validate your Recipes, No Guarantee
Once your page validates there is this message:

"Note that there is no guarantee that a Rich Snippet will be shown for this page on actual search results. For more details, see the FAQ."

This FAQ seems like an earlier version of the information displayed on the page "Rich snippets not appearing" since the FAQ page does not mention including recipe sites being eligible for rich snippets.

"Note that there is no guarantee that a Rich Snippet will be shown for this page on actual search results. For more details, see the FAQ."

So, even if you go through the process of tagging and validating your recipes you are not guaranteed that your posts will display as Rich Snippets which I am guessing means that they may or may not show up in the Google Recipe Search. So, you are left to wait and see.

Maybe I'm suspicious, but what seemed like a cool idea -- a search tool that enables readers to quickly find recipes -- now appears to be a tool catering to larger company sites and I'm concerned about what this means for food bloggers. It seems that many established recipe sites started incorporating the markup to generate rich snippets once they were aware of Google's plan to develop the Recipe Search but the urgency to start using microformats did not appear to reach the blogger community. The lack of integrated and easy to use plugins for the various blogging platforms speaks to the absence of this necessity. Elise Bauer points out the irony that Blogger, Google's blogging platform does not have tools developed for recipe markup that would help bloggers generate rich snippets.

Okay. Whine whine, gripe gripe. Poor bloggers. But what about readers and cooks? How does Recipe View change their experience? The average recipe seeker may be unaware of the filtering that is currently going on and miss out on much of the user-generated food content that has accumulated on the web over the years. On the other hand, it will provide a faster and more efficient system to access information they are seeking without having to manipulate their queries or apply advanced search techniques.

Regardless of the effect on my posts, as a reader I'm a bit frustrated that I may lose out on seeing an innovative recipe with a great story, which is why I read blogs in the first place. I love reading about David Lebovitz's various forays into Paris bakeries that end with a lovely tart recipe, or getting inspired to try making a Death in the Afternoon cocktail after giggling over one of Michael Procopio's pieces.

I should note that many major sites with extensive recipe collections (but are not exclusively recipe sites) are also not yet displaying in Google Recipe View. For instance, I haven't seen any New York Times recipes listed (by them) and I am curious about how large sites that have food as a topic area and a wealth of recipes are approaching the situation.

Maybe this will all work itself out soon. The problem, however, is that bloggers and readers alike have now come to expect immediacy. When I post a recipe it shows up without any delays and people can read it. You can twitter about it and the information is distributed without a waiting process. Perhaps we all need to just learn (or relearn) to be patient again and this post is the equivalent of Chicken Little yelling that the sky is falling on food bloggers everywhere. So although I'm finding the new Google Recipe View a bit frustrating, it may not be elitist. I'm keeping my fingers crossed that it ends up being inclusive and helpful in the end.

What do you think?

recipe searchrecipe search

Google’s New Recipe Search: A Food Blogger's Dilemma