Get your recipes on Google

Help users find your recipe content by telling Google about your recipe with structured data. When you provide information such as reviewer ratings, cooking and preparation times, and nutrition information, Google can better understand your recipe and present it to users in interesting ways. Recipes can appear in Google Search results and Google Images.

Recipes in Google Search and Google Images

Based on how you mark up your content, your recipes can be eligible for the following enhancements:

Recipe enhancements
Guided Recipes: Enable the Google Assistant to guide users through your recipes on Google Home and smart displays by adding Recipe structured data. There are a few additional properties that are required for Guided Recipes, but only recommended for Google Search. Make sure you add recipeIngredient and recipeInstructions.

For more information about recipes on the Google Assistant, learn how you can build Actions from web content.

Recipe on the Assistant
Recipe host carousel: Enable users to explore your recipe gallery pages by adding ItemList structured data. Recipe carousel in Google Search


Here are some examples of recipes using JSON-LD code.

Guided Recipes

Here's an example of a page that's eligible for display on Google Search and as a Guided Recipe on the Assistant.

Recipe on Search only

Here's an example of a page that's eligible to be displayed on Search. It's not eligible for display as a Guided Recipe on the Assistant.

Here's an example of a recipe summary page (a page with a list of recipes) with itemList structured data. This content may be eligible to be displayed in a grid in Search results.

Enhance your recipes on Google

Here's an overview of how to enhance your recipes on Google:

  1. Ensure that Googlebot can crawl your recipe pages (meaning, your pages aren't protected by a robots.txt file or robots meta tag).
  2. Make sure you follow our guidelines.
  3. Add structured data to your recipe pages.
  4. Test and preview your structured data.
  5. Check the index status of your URLs and request for your URL to be crawled with the URL inspection tool in Search Console. To confirm if crawlers are able to access structured data on your page, use the Live Test feature.
  6. Keep Google informed of new recipe pages or changes to existing recipe pages.

Monitor performance in Search

To understand how users interact with your recipes, use the following Google tools:

  • Use the Performance Report in Search Console to see how your recipes appear in Search results. You can automatically pull these results with the Search Console API.
  • Use the Rich result status report in Search Console to understand what Google could or could not read from your site, and troubleshoot rich result errors.

If you're experiencing unexpected fluctuations or inconsistencies in your traffic, use the troubleshooter to identify and resolve the issues.


You must follow the general structured data guidelines for your recipe to be eligible to appear in Search results. If you want your recipe to display as a Guided Recipe on the Assistant, make sure your content follows the content restrictions policy for the Assistant.

The following guidelines apply to recipe structured data.

  • Use recipe structured data for content about preparing a particular dish. For example, "facial scrub" or "party ideas" are not valid names for a dish.
  • To enable your recipes to appear in a carousel or grid, you must follow these guidelines:
    • Provide ItemList structured data to summarize the recipes for your list. You can provide ItemList structured data separately or together with recipe structured data.
    • Your site must have a summary page that lists all the recipes in the collection. For example, 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.

Structured data type definitions

You must include the required properties for your content to be eligible for display as a rich result in Google Search. You can also include the recommended properties to add more information about your content, which could provide a better user experience.


Mark up your recipe content with the following properties of the Recipe type. The full definition of Recipe is available at

Required properties

URL or ImageObject

Image of the completed dish.

Additional image guidelines:

  • Every page must contain at least one image (whether or not you include markup). Google will pick the best image to display in Search results based on the aspect ratio and resolution.
  • Image URLs must be crawlable and indexable.
  • Images must represent the marked up content.
  • Images must be in .jpg, .png, or. gif format.
  • For best results, provide multiple high-resolution images (minimum of 50K pixels when multiplying width and height) with the following aspect ratios: 16x9, 4x3, and 1x1.

For example:

"image": [


The name of the dish.

Recommended properties


Annotation for the average review score assigned to the item. Follow the Review snippet guidelines and list of required and recommended AggregateRating properties.

If the recipe structured data 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.


Person or Organization

The name of the person or organization that wrote the recipe.



The time it takes to actually cook the dish in ISO 8601 format. You can use min and max as child elements to specify a range of time.

Always use in combination with prepTime.



The date the recipe was published in ISO 8601 format.



A short summary describing the dish.



Other terms for your recipe such as the season ("summer"), the holiday ("Halloween"), or other descriptors ("quick", "easy", "authentic").

Additional guidelines

  • Separate multiple entries in a keywords list with commas.
  • Don't use a tag that should be in recipeCategory or recipeCuisine.

    Not recommended

    "keywords": "dessert, American"


    "keywords": "winter apple pie, nutmeg crust"


The number of calories in each serving produced with this recipe. If nutrition.calories is defined, recipeYield must be defined with the number of servings.



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

Always use in combination with cookTime.



The type of meal or course your recipe is about. For example: "dinner", "main course", or "dessert, snack".



The region associated with your recipe. For example, "French", Mediterranean", or "American".



An ingredient used in the recipe.

For example:

"recipeIngredient": [
  "1 (15 ounce) package double crust ready-to-use pie crust",
  "6 cups thinly sliced, peeled apples (6 medium)",
  "3/4 cup sugar",
  "2 tablespoons all-purpose flour",
  "3/4 teaspoon ground cinnamon",
  "1/4 teaspoon salt",
  "1/8 teaspoon ground nutmeg",
  "1 tablespoon lemon juice"

Additional guidelines:

  • Include only the ingredient text that is necessary for making the recipe.
  • Don't include unnecessary information, such as a definition of the ingredient.

HowToStep, HowToSection, or Text

The steps to make the dish.

There are several options for setting the value of recipeInstructions. We recommend using HowToStep. HowToSection can also be used to group HowToSteps when the recipe has sections.

  • HowToStep: Specify this recipe’s steps with HowToStep.
  • HowToSection (only if a recipe has multiple sections): Use to group steps into multiple sections. See HowToSection for an example.
  • Single or repeated property of text: A block of text that includes one or more steps. Google treats all steps as being in a single section. Repeated property values are concatenated into a single block of text. Google then attempts to automatically split the single block of text into individual steps. Google tries to find and remove any section names, step numbers, keywords, and anything else that can incorrectly appear in recipe step text. For best results, we recommend you unambiguously specify steps with HowToStep.

Additional guidelines

  • Don't include metadata that belongs elsewhere. In particular, use the author property to specify the author, recipeCuisine for cuisine, recipeCategory for category, and keywords for other keywords.
  • Include only text on how to make the dish and don't include other text such as "Directions", "Watch the video", "Step 1". Those phrases should be specified outside of the structured data.

    Not recommended

    "recipeInstructions": [{
      "@type": "HowToStep",
      "text": "Step 1. Heat oven to 425°F."


    "recipeInstructions": [{
      "@type": "HowToStep",
      "text": "Heat oven to 425°F."


The quantity produced by the recipe. Specify the number of servings produced from this recipe with just a number. If you wish to use a different unit (for example, number of items), you may include additional yields. This is required if you specify any nutritional information per serving (such as nutrition.calories).


"recipeYield": [
  "24 cookies"


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

Use totalTime or a combination of both cookTime and prepTime.

video VideoObject

A video depicting the steps to make the dish. Follow the list of required and recommended Video properties.

  • Video without clips
  • Video with clips: A video with clips that correspond to segments of the video. Other parts of the recipe (such as steps) can refer to these clips, which are defined in video.hasPart.


A video clip that is part of the entire video.



The end time of the clip expressed as the number of seconds from the beginning of the video.


The name of the clip. For example, "Arrange pie crust" could be the name of the clip that shows how to arrange and press the pie crust into the pie plate.



The start time of the clip expressed as the number of seconds from the beginning of the video.



A link to the start of the clip. The start of the clip must match the value set in video.hasPart.startOffset. For example:

"startOffset": 20,
"endOffset": 29,
"url": ""


Use HowToSection to group a sequence of steps (or sub-sections) that make up part of the instructions for a recipe. Specify HowToSection directly within the definition of recipeInstructions property, or as an itemListElement of another HowToSection.

The HowToSection type defines a section of a single recipe and contains one or multiple steps. Don't use HowToSection to define different recipes for the same dish; instead, use HowToSection as part of a single recipe. For listing multiple recipes for a dish, use multiple Recipe objects. For example, multiple ways to make an apple pie should be listed as multiple Recipe objects, not HowToSection objects.

The full definition of HowToSection is available at

Required properties
itemListElement HowToStep

A list of detailed steps for the section, and/or sub-sections. For example, a pizza recipe may have one section of steps for making the crust, one for preparing the toppings, and one for combining and baking. If a recipe has sections, but they aren’t defined with HowToSections, the Assistant may mistakenly present the section name as just another step (for example, a "Make the crust" step followed by a "Combine the flour and yeast" step).


  "@type": "HowToSection",
  "name": "Assemble the pie",
  "itemListElement": [
      "@type": "HowToStep",
      "text": "In large bowl, gently mix filling ingredients; spoon into crust-lined pie plate."
    }, {
      "@type": "HowToStep",
      "text": "Top with second crust. Cut slits or shapes in several places in top crust."
name Text

The name of the section.


Use HowToStep to group one or more sentences that explain how to do part of the recipe. Define the text property with the sentences or, alternately, define itemListElement with a HowToDirection or HowToTip for each sentence.

Mark up your recipe steps with the following properties of the HowToStep type. Specify a HowToStep directly within the definition of recipeInstructions property, or as an itemListElement of a HowToSection.

The full definition of HowToStep is available at

Required properties
itemListElement HowToDirection or HowToTip

A list of detailed substeps, including directions or tips.

Optional if text is used.

text Text

The full instruction text of this step.

Optional if itemListElement is used. Additional guidelines:

  • Include only instructional text and don't include other text such as "Directions", "Watch the video", "Step 1". Specify those phrases outside of the marked up property.
Recommended properties
image ImageObject or URL

An image for the step. Additional image guidelines:

  • Image URLs must be crawlable and indexable.
  • Images must represent the marked up content.
  • Images must be in .jpg, .png, or. gif format.
name Text

The word or short phrase summarizing the step (for example, "Arrange pie crust"). Don't use non-descriptive text (for example, "Step 1: [text]") or other form of step number (for example, "1. [text]").

url URL

A URL that directly links to the step (if one is available). For example, an anchor link fragment.

video VideoObject or Clip

A video for this step or a clip of the video.

For VideoObject, follow the list of required and recommended Video or Clip properties.

HowToDirection and HowToTip

Use HowToDirection and HowToTip to describe directions or tips. They have the same required and recommended properties.

The full definitions of HowToDirection and HowToTip are available at and

Required properties
text Text

The text of the direction or tip.


In addition to Recipe properties, add the following properties for host-specific lists. While ItemList isn't required, you must add the following properties if you want your recipe to be eligible for a host carousel. For more information about host carousel, see Carousel.

The full definition of ItemList is available at

Required properties


Annotation for a single item page.



Ordinal position of the item page in the list. For example:

"itemListElement": [
    "@type": "ListItem",
    "position": 1,
  }, {
    "@type": "ListItem",
    "position": 2,


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