Mark up your recipe content with structured data to provide rich cards and host-specific lists for your recipes, such as reviewer ratings, cooking and preparation times, and nutrition information. Rich results can also appear in image search on mobile devices, providing users with useful information about your recipe.


A query such as “mango recipes”

A query such as “grandma's holiday apple pie”

A query such as "great chicken recipes"


In addition to the general guidelines that apply to all Rich Cards, be aware of the following extra guidelines for recipe Rich Cards:

  • Use Accelerated Mobile Pages (AMP) to build your recipe pages and mark up the content with structured data to provide rich cards and instant-loading host-specific lists for your recipes.
  • Use recipe markup for content about preparing a particular dish. For example, "facial scrub" or "party ideas" are not valid names for a dish.
  • Use recipe property markup for a single recipe, not a category of recipes or a list of recipes. For example, “10 apple pie recipes” is not a single recipe. See also policies regarding multiple entities on the same page.
  • If the recipe markup contains a single review, the reviewer’s name must be a valid person or organization. For example, "50% off ingredients" is not a valid name for a reviewer.
  • To enable your recipes to appear in a host-specific list, you must provide ItemList markup to summarize the recipes for your list. You can provide ItemList markup separately or together with Recipe markup. See Mark Up Your Lists for details.
  • For host-specific lists, your site must have a summary page that lists all the recipes in the collection, so that when a user clicks the summary link from Search results, they are properly directed to a page on your site listing the recipes related to their search.

Type Definitions

ItemList Properties

The following table indicates the ItemList properties necessary for host-specific lists. See specific guidelines above and Mark Up Your Listings for implementation details.


ListItem, required

Annotation for a single item page.


Integer, required

Ordinal position of the item page in the list.


URL, required

The canonical URL of the item page. Every item should have a unique URL.

Recipe Properties

Build your recipe pages with AMP, and mark up your recipe content with the following properties of the Recipe type. In addition to the required fields, mark up as many of the recommended fields as possible to drive better engagement in Search.


Text, required

The name of the dish.


Text, recommended

The type of dish. For example: appetizer, entree, or dessert.


URL or ImageObject, recommended*

Image of the completed dish. Must be a minimum of 232px by 130px, with a 16:9 aspect ratio.

*Mark up an image to include it in the rich card. If you don't mark up a specific image, a prominent image from the page will be used in the card. Every page must contain at least one image (whether or not you include markup).


Date, recommended

The date the recipe was published, in ISO 8601 format.


Text, recommended

A short summary describing the dish.


AggregateRating, recommended

Annotation for the average review score assigned to the item.


Review, recommended

A review of the dish. Can include nested review information.


Duration, recommended*

The length of time it takes to prepare the recipe for dish, in ISO 8601 format. Can use min, max as child elements to specify a range of time.

*Always use in combination with cookTime.


Duration, recommended*

The time it takes to actually cook the dish, in ISO 8601 format. Can usemin, max as child elements to specify a range of time.

*Always use in combination with prepTime.


Duration, recommended*

The total time it takes to prepare the cook the dish, in ISO 8601 format. Can use min, max as child elements to specify a range of time.

* Use totalTime or a combination of both cookTime and prepTime.


Energy, recommended

The number of calories in the recipe.


Text, recommended

The steps to make the dish. Can contain the child element instruction, which can be used to annotate each step.


Text, recommended

The quantity produced by the recipe. For example: number of people served, or number of servings.


Text, recommended

An ingredient used in the recipe.


Person, recommended

Creator of the recipe.

Send feedback about...