Google Updated Recipe Structured Data Guidelines

A recent change by Google has affected the way that recipe structured data is displayed in the SERPs, especially on mobile devices.

This means that all recipes must be updated to the new requirements before they can be displayed correctly in the SERPs. This guide explains what the changes are and how you can update your recipes so they are displayed correctly in Google’s results.

What is Recipe Structured Data?

Recipe structured data is not a new development, but one of several markup schemes Google supports that are used to markup web pages to help serve rich snippets in search results. Basically, a structured data recipe (often referred to as Rich Snippets) helps give users more information about products and services when they search for them online.

Why is recipe structured data important?

Recipe structured data allows you to not only show Google what’s in your recipe but also helps them determine when and how it should appear on SERPs. With more than one billion monthly searches for recipes, including holiday-specific terms like Thanksgiving recipes or vegetarian Thanksgiving recipes, is an opportunity to drive traffic to your site.

The following are examples of typical recipe enhancements:

  • Recipes with Directions
  • Carousel of recipe hosts

It is critical to use properly structured data. Failure to use the right structured data may result in a site’s eligibility for Recipe Enhancements being revoked, as well as a loss of search engine traffic to sites that do use correct structured data.

Three Recipe Structured Data Properties Changed

According to Google’s documentation, the suggestion for defining a time range for the cooking time and prep time parameters has been removed.

The cook time property recommendation has the following wording removed:

“Use the min and max child components to establish a time range.”

The following text no longer appears in the prepTime property:

“Use the min and max child components to establish a time range.”

For both the cooking time and prep time attributes, Google now only supports precise time, as well as one additional feature that Google did not document.

The time range can no longer be used.

According to the update’s changelog:

“At this time, the only approach that is supported is an exact time; time ranges are not supported.” We recommend altering that value in your structured data to a single value (for example, “cook Time”: “PT30M”) if you’re currently supplying a time range and want Google to better comprehend your time values for cook time and prep time.

A Third Structured Data Property Changed

According to Google’s changelog documentation, only the cook Time and prepTime properties have changed.

However, there is a third property that has changed as well.

The following is taken from the changelog:

“In the Recipe documentation, information on selecting a range for the cooking time and prep time parameters has been removed.”

Despite Google’s changelog documentation not mentioning it, the total time attribute has changed.

According to the previous total time Recipe documentation:

“Use the min and max child components to establish a time range.”

Here’s a screenshot of the January 4, 2022 documentation:

Previous total time Recommendation

Previous total time Recommendation for recipe structures data.

The above-mentioned time range guideline is completely absent from the new documentation.

New total time Recommendation

New total time Recommendation

Although the change in the total time property is not mentioned in Google’s documentation, it’s definitely a good idea to point out that it has changed as well, and to avoid using a time range for the total time property in the future because Google no longer advises it.

Recipe Structured Data:

Many recipe sites rely on plugins for structured data. It’s a good idea to upgrade to the most recent version if you’re using a recipe structured data plugin that also uses the time range to ensure that your structured data is up to date. This change to the structured data occurred on January 18, 2022, making it extremely recent.

Rishabh Kolhe
Rishabh Kolhe

I am the founder of WealthyWork, I started my digital marketing journey in 2017. First, I started my career with SEO in Culturelligence, then after some time, I learned more about Digital Marketing. I worked as a Digital Marketer with Agile PeopleOps, a US-based HR organization. Now I am working in WealthyWork, We all specializing in Digital Marketing Services.

Articles: 101