# Recipe 结构化数据

> 来源：Google Search Central (https://developers.google.com/search/docs/appearance-structured-data-recipe.txt)

---

* Ranking and search appearance
  ** Visual Elements gallery  **
  ** Title links  **
  ** Snippets  **
  ** Images  **
  ** Videos  **
  ** Structured data  **
  ** Favicons  **

  * Site-specific guides
  ** Ecommerce  **
  ** International and multilingual sites  **

  * Data analysis
  ** Get started with Search Console  **
  ** Debug traffic drops  **
  ** Using Search Console and Google Analytics data for SEO  **
  ** Get started with Google Trends  **

[ Support ](https://developers.google.com/search/help) [ Blog ](https://developers.google.com/search/blog) [ What's new ](https://developers.google.com/search/news)

  ** All updates  **
  ** Documentation updates  **
  ** Ranking updates  **
  ** New YouTube videos  **
  ** Recent podcast episodes  **

[ Events ](https://developers.google.com/search/events) [ Case studies ](https://developers.google.com/search/case-studies)

`/`

  * English
  * Deutsch
  * Español
  * Español – América Latina
  * Français
  * Indonesia
  * Italiano
  * Polski
  * Português – Brasil
  * Tiếng Việt
  * Türkçe
  * Русский
  * العربيّة
  * हिंदी
  * ภาษาไทย
  * 中文 – 简体
  * 中文 – 繁體
  * 日本語
  * 한국어

Sign in

  ** Documentation **

[Search Console](https://goo.gle/searchconsole)

[ ](https://developers.google.com/search)

  ** Google Search Central **

  ** Documentation  **
    * More 
  ** Support  **
  ** Blog  **
  ** What's new  **
    * More 
  ** Events  **
  ** Case studies  **

  **Introduction**
  * Search Essentials

    **Overview**
    **Technical requirements**
    **Spam policies**

  * SEO fundamentals

    **SEO Starter Guide**
    **How Google Search works**
    **Creating helpful, reliable, people-first content**
    **Do you need an SEO?**
    **Maintaining your site's SEO**
    **Developer's guide to Search**
    **Get your website on Google**
    **Guidance on using generative AI**

  * Crawling and indexing

    **Overview**
    **File types Google can index**
    **URL structure**
    **Links**
    * Sitemaps

      **Learn about sitemaps**
      **Build and submit a sitemap**
      **Manage sitemaps with sitemap index file**
      * Sitemap extensions

        **Image sitemaps**
        **News sitemaps**
        **Video sitemaps and alternatives**
        **Combining sitemap extensions**

    * Crawler management

      **Ask Google to recrawl your URLs**
      **Troubleshoot crawl errors**
      * Google crawlers

        **List of Google crawlers**
        **Googlebot**
        **Reduce the Google crawl rate**
        **Verifying Googlebot and other Google crawlers**

    * robots.txt

      **Introduction to robots.txt**
      **How Google interprets the robots.txt specification**

    * Canonicalization

      **What is URL canonicalization**
      **How to specify a canonical URL with rel="canonical" and other methods**
      **Fix canonicalization issues**

    **Mobile site and mobile-first indexing**
    * AMP

      **AMP on Google Search guidelines**
      **Understand how AMP works in search results**
      **Enhance AMP content**
      **Validate AMP content**
      **Remove AMP content**

    * JavaScript

      **Understand the JavaScript SEO basics**
      **Fix search-related JavaScript problems**
      **Fix lazy-loaded content**
      **Dynamic rendering as a workaround**

    * Page and content metadata

      **Page metadata**
      * Meta tags

        **Meta tags and HTML attributes that Google supports**
        **Robots meta tag, data-nosnippet, and X-Robots-Tag**
        **noindex**

      **rel attributes**

    * Removals

      **Control what you share with Google**
      **Page removals**
      **Image removals**
      **Redacted information**

    * Site moves and changes

      **Redirects and Google Search**
      * Site moves

        **Changing your hosting**
        **Move a site with URL changes**

      **A/B testing**
      **Temporarily pause or disable a website**

  * Ranking and search appearance

    **Overview**
    **AI features**
    **Byline dates**
    **Favicons**
    **Featured snippets**
    **Flexible Sampling**
    **Google Discover**
    **Images**
    * Local features

      **Business details**
      **Top Places List**
      **Opting out of local search results**

    * Page experience

      **Understanding page experience**
      **Core Web Vitals**
      **Interstitials and dialogs**
      **Get started with signed exchanges on Google Search**

    **Preferred sources**
    * Ranking systems

      **A guide to Google Search ranking systems**
      **Reviews system**

    * Ranking updates

      **List of ranking updates**
      **Core updates**
      **Spam updates**

    **Site names**
    **Sitelinks**
    **Snippets**
    * Structured data

      **Understand how structured data works**
      **Structured data general guidelines**
      **Enriched search results**
      **Generate structured data with JavaScript**
      * Feature guides

        **All structured data features**
        **Article**
        **Book actions**
        **Breadcrumb**
        **Carousel**
        **Course list**
        **Dataset**
        **Discussion forum**
        **Education Q&A**
        **Employer aggregate rating**
        **Fact check**
        **Event**
        **FAQ**
        **Image metadata**
        **Job posting**
        **Local business**
        **Math solver**
        **Movie carousel**
        **Organization**
        * Shopping

          **Overview**
          **Product snippet**
          **Merchant listing**
          **Variants**
          **Loyalty program**
          **Merchant return policy**
          **Merchant shipping policy**

        **Profile page**
        **Q&A**
        **Recipe**
        **Review snippet**
        **Software app**
        **Speakable**
        **Subscription and paywalled content**
        **Vacation rental**
        **Video**

    **Title links**
    * Translated features

      **Translated results**
      **Ad networks and translation-related Google Search features**

    **Videos**
    **Visual Elements gallery**
    * Web Stories

      **Enable Web Stories on Google**
      **Best practices for creating Web Stories**
      **Web Story content policy**

    * Early Adopters Program

      **Package tracking**
      **Structured data carousels (beta)**

  * Monitoring and debugging

    **Debug drops in Search traffic**
    * Monitor with Search Console

      **Get started with Search Console**
      **Improve SEO with a bubble chart**
      **Using Search Console and Google Analytics data for SEO**

    * Debug with search operators

      **Overview**
      **site: search operator**
      **Google Images search operators**

    * Preventing and monitoring abuse

      **Overview**
      **Prevent user-generated spam**
      **Malware and unwanted software**
      **Prevent a malware infection**
      **Social engineering (phishing and deceptive sites)**
      **Google Safe Browsing Repeat Offenders Policy**

    **Get started with Google Trends**

  * Site-specific guides

    * Ecommerce

      **Overview**
      **Where content can appear**
      **Share product data**
      **Include structured data**
      **Launch a new website**
      **Write high quality reviews**
      **Design a URL structure**
      **Ecommerce site structure**
      **Pagination, incremental page loading, and Search**

    * International and multilingual

      **Overview**
      **Managing multi-regional and multilingual sites**
      **Tell Google about localized versions of your page**
      **How Google crawls locale-adaptive pages**

    * Explicit content

      **Guidelines for sites with explicit content**
      **What to do if your site is incorrectly flagged as explicit**

  * SEO fundamentals 
  ** Introduction  **
  ** Search Essentials  **
  ** SEO Starter Guide  **
  ** How Google Search Works  **
  ** Do you need an SEO?  **
  * Crawling and indexing 
  ** Sitemaps  **
  ** robots.txt  **
  ** Meta tags  **
  ** Crawler management  **
  ** Removals  **
  ** Canonicalization  **
  ** Redirects  **
  ** JavaScript SEO  **
  * Ranking and search appearance 
  ** Visual Elements gallery  **
  ** Title links  **
  ** Snippets  **
  ** Images  **
  ** Videos  **
  ** Structured data  **
  ** Favicons  **
  * Site-specific guides 
  ** Ecommerce  **
  ** International and multilingual sites  **
  * Data analysis 
  ** Get started with Search Console  **
  ** Debug traffic drops  **
  ** Using Search Console and Google Analytics data for SEO  **
  ** Get started with Google Trends  **

  ** All updates  **
  ** Documentation updates  **
  ** Ranking updates  **
  ** New YouTube videos  **
  ** Recent podcast episodes  **

  ** Home **
  ** Search Central **
  ** Documentation **

Send feedback 

# Recipe (`Recipe`, `HowTo`, `ItemList`) structured data

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.

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

Recipe enhancements | Recipe host carousel: Enable users to explore your recipe gallery pages by adding `ItemList` structured data.  |   
---|---  
  
##  How to add structured data 

Structured data is a standardized format for providing information about a page and classifying the page content. If you're new to structured data, you can learn more about [how structured data works](/search/docs/appearance/structured-data/intro-structured-data). 

Here's an overview of how to build, test, and release structured data.

  1. Add the required properties. Based on the format you're using, learn where to [insert structured data on the page](/search/docs/appearance/structured-data/intro-structured-data#format-placement).  Using a CMS? It may be easier to use a plugin that's integrated into your CMS.   
Using JavaScript? Learn how to [generate structured data with JavaScript](/search/docs/appearance/structured-data/generate-structured-data-with-javascript).
  2. Follow the guidelines.
  3. Validate your code using the [Rich Results Test](https://search.google.com/test/rich-results) and fix any critical errors. Consider also fixing any non-critical issues that may be flagged in the tool, as they can help improve the quality of your structured data (however, this isn't necessary to be eligible for rich results). 
  4. Deploy a few pages that include your structured data and use the [URL Inspection tool](https://support.google.com/webmasters/answer/9012289) to test how Google sees the page. Be sure that your page is accessible to Google and not blocked by a robots.txt file, the `noindex` tag, or login requirements. If the page looks okay, you can [ask Google to recrawl your URLs](/search/docs/crawling-indexing/ask-google-to-recrawl). Note: Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it.
  5. To keep Google informed of future changes, we recommend that you [submit a sitemap](/search/docs/crawling-indexing/sitemaps/build-sitemap). You can automate this with the [Search Console Sitemap API](/webmaster-tools/v1/sitemaps).

## Examples

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

Note: The actual appearance in Search results might be different. Preview the structured data in the Rich Results Test for the most up-to-date layout.

### Recipe on Search

Here's an example of a page that's eligible to be displayed on Search.

<html> <head> <title>Non-Alcoholic Piña Colada</title> <script type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Recipe", "name": "Non-Alcoholic Piña Colada", "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "author": { "@type": "Person", "name": "Mary Stone" }, "datePublished": "2024-03-10", "description": "This non-alcoholic pina colada is everyone's favorite!", "recipeCuisine": "American", "prepTime": "PT1M", "cookTime": "PT2M", "totalTime": "PT3M", "keywords": "non-alcoholic", "recipeYield": "4 servings", "recipeCategory": "Drink", "nutrition": { "@type": "NutritionInformation", "calories": "120 calories" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": 5, "ratingCount": 18 }, "recipeIngredient": [ "400ml of pineapple juice", "100ml cream of coconut", "ice" ], "recipeInstructions": [ { "@type": "HowToStep", "name": "Blend", "text": "Blend 400ml of pineapple juice and 100ml cream of coconut until smooth.", "url": "https://example.com/non-alcoholic-pina-colada#step1", "image": "https://example.com/photos/non-alcoholic-pina-colada/step1.jpg" }, { "@type": "HowToStep", "name": "Fill", "text": "Fill a glass with ice.", "url": "https://example.com/non-alcoholic-pina-colada#step2", "image": "https://example.com/photos/non-alcoholic-pina-colada/step2.jpg" }, { "@type": "HowToStep", "name": "Pour", "text": "Pour the pineapple juice and coconut mixture over ice.", "url": "https://example.com/non-alcoholic-pina-colada#step3", "image": "https://example.com/photos/non-alcoholic-pina-colada/step3.jpg" } ], "video": { "@type": "VideoObject", "name": "How to Make a Non-Alcoholic Piña Colada", "description": "This is how you make a non-alcoholic piña colada.", "thumbnailUrl": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ], "contentUrl": "https://www.example.com/video123.mp4", "embedUrl": "https://www.example.com/videoplayer?video=123", "uploadDate": "2024-02-05T08:00:00+08:00", "duration": "PT1M33S", "interactionStatistic": { "@type": "InteractionCounter", "interactionType": { "@type": "WatchAction" }, "userInteractionCount": 2347 }, "expires": "2024-02-05T08:00:00+08:00" } } </script> </head> <body> </body> </html>
    
    
    <html>
      <head>
        <title>Non-Alcoholic Piña Colada</title>
        <script type="application/ld+json">
        {
          "@context": "https://schema.org/",
          "@type": "Recipe",
          "name": "Non-Alcoholic Piña Colada",
          "image": [
          "https://example.com/photos/1x1/photo.jpg",
          "https://example.com/photos/4x3/photo.jpg",
          "https://example.com/photos/16x9/photo.jpg"
          ],
          "author": {
            "@type": "Person",
            "name": "Mary Stone"
          },
          "datePublished": "2024-03-10",
          "description": "This non-alcoholic pina colada is everyone's favorite!",
          "recipeCuisine": "American",
          "prepTime": "PT1M",
          "cookTime": "PT2M",
          "totalTime": "PT3M",
          "keywords": "non-alcoholic",
          "recipeYield": "4 servings",
          "recipeCategory": "Drink",
          "nutrition": {
            "@type": "NutritionInformation",
            "calories": "120 calories"
          },
          "aggregateRating": {
            "@type": "AggregateRating",
            "ratingValue": 5,
            "ratingCount": 18
          },
          "recipeIngredient": [
            "400ml of pineapple juice",
            "100ml cream of coconut",
            "ice"
          ],
          "recipeInstructions": [
            {
              "@type": "HowToStep",
              "name": "Blend",
              "text": "Blend 400ml of pineapple juice and 100ml cream of coconut until smooth.",
              "url": "https://example.com/non-alcoholic-pina-colada#step1",
              "image": "https://example.com/photos/non-alcoholic-pina-colada/step1.jpg"
            },
            {
              "@type": "HowToStep",
              "name": "Fill",
              "text": "Fill a glass with ice.",
              "url": "https://example.com/non-alcoholic-pina-colada#step2",
              "image": "https://example.com/photos/non-alcoholic-pina-colada/step2.jpg"
            },
            {
              "@type": "HowToStep",
              "name": "Pour",
              "text": "Pour the pineapple juice and coconut mixture over ice.",
              "url": "https://example.com/non-alcoholic-pina-colada#step3",
              "image": "https://example.com/photos/non-alcoholic-pina-colada/step3.jpg"
            }
          ],
          "video": {
            "@type": "VideoObject",
            "name": "How to Make a Non-Alcoholic Piña Colada",
            "description": "This is how you make a non-alcoholic piña colada.",
            "thumbnailUrl": [
              "https://example.com/photos/1x1/photo.jpg",
              "https://example.com/photos/4x3/photo.jpg",
              "https://example.com/photos/16x9/photo.jpg"
             ],
            "contentUrl": "https://www.example.com/video123.mp4",
            "embedUrl": "https://www.example.com/videoplayer?video=123",
            "uploadDate": "2024-02-05T08:00:00+08:00",
            "duration": "PT1M33S",
            "interactionStatistic": {
              "@type": "InteractionCounter",
              "interactionType": { "@type": "WatchAction" },
              "userInteractionCount": 2347
            },
            "expires": "2024-02-05T08:00:00+08:00"
           }
        }
        </script>
      </head>
      <body>
      </body>
    </html>

### Carousel

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.

<html> <head> <title>Grandma's Best Pie Recipes</title> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "ItemList", "itemListElement": [ { "@type": "ListItem", "position": 1, "url": "https://example.com/apple-pie.html" }, { "@type": "ListItem", "position": 2, "url": "https://example.com/blueberry-pie.html" }, { "@type": "ListItem", "position": 3, "url": "https://example.com/cherry-pie.html" }] } </script> </head> <body> </body> </html>
    
    
    <html>
      <head>
        <title>Grandma's Best Pie Recipes</title>
        <script type="application/ld+json">
        {
          "@context": "https://schema.org",
          "@type": "ItemList",
          "itemListElement": [
            {
              "@type": "ListItem",
              "position": 1,
              "url": "https://example.com/apple-pie.html"
            },
            {
              "@type": "ListItem",
              "position": 2,
              "url": "https://example.com/blueberry-pie.html"
            },
            {
              "@type": "ListItem",
              "position": 3,
              "url": "https://example.com/cherry-pie.html"
            }]
        }
        </script>
      </head>
      <body>
      </body>
    </html>

## Guidelines

You must follow the [general structured data guidelines](/search/docs/appearance/structured-data/sd-policies) for your markup to be eligible to appear in Search results. If you violate these policies, your recipe might not show up as a rich result, but your content will still appear in Search results. Read about [Spammy Structured Markup](https://support.google.com/webmasters/answer/3498001).

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](/search/docs/appearance/structured-data/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.

### `Recipe`

Mark up your recipe content with the following properties of the schema.org [`Recipe`](https://schema.org/Recipe) type. The full definition of `Recipe` is available at [schema.org/Recipe](https://schema.org/Recipe). The Google-supported properties are the following: 

Required properties  
---  
`image` | `[URL](https://schema.org/URL)` or `[ImageObject](https://schema.org/ImageObject)` Image of the completed dish. Additional image guidelines: 

  * Image URLs must be crawlable and indexable. To check if Google can access your URLs, use the [URL Inspection tool](https://support.google.com/webmasters/answer/9012289).
  * Images must represent the marked up content.
  * Images must be in a file format that's [supported by Google Images](/search/docs/appearance/google-images#supported-image-formats).
  * For best results, we recommend providing 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": [
      "https://example.com/photos/1x1/photo.jpg",
      "https://example.com/photos/4x3/photo.jpg",
      "https://example.com/photos/16x9/photo.jpg"
    ]

Specifying the `image` property in `Recipe` markup has no impact on the image chosen for a [text result image](/search/docs/appearance/visual-elements-gallery#text-result-image). To optimize for a text result image, follow the [image SEO best practices](/search/docs/appearance/google-images).  
`name` | `[Text](https://schema.org/Text)` The name of the dish.  
Recommended properties  
---  
`aggregateRating` | `[AggregateRating](https://schema.org/AggregateRating)` Annotation for the average review score assigned to the item. Follow the [Review snippet guidelines](/search/docs/appearance/structured-data/review-snippet#guidelines) and list of required and recommended [`AggregateRating` properties](/search/docs/appearance/structured-data/review-snippet#aggregated-rating-type-definition). 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.  
`author` | `[Person](https://schema.org/Person)` or `[Organization](https://schema.org/Organization)` The name of the person or organization that wrote the recipe. To help Google best understand authors across various features, consider following the [author markup best practices](/search/docs/appearance/structured-data/article#author-bp).  
`cookTime` | `[Duration](https://schema.org/Duration)` The time it takes to actually cook the dish in [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), if applicable.  Always use in combination with `prepTime`.   
`datePublished` | `[Date](https://schema.org/Date)` The date the recipe was published in [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), if applicable.  
`description` | `[Text](https://schema.org/Text)` A short summary describing the dish.  
`keywords` | `[Text](https://schema.org/Text)` 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's actually a `recipeCategory` or `recipeCuisine`.   
Not recommended:
    
        "keywords": "dessert, American"

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

  
`nutrition.calories` | `[Energy](https://schema.org/Energy)` 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.  
`prepTime` |  `[Duration](https://schema.org/Duration)` The length of time it takes to prepare ingredients and workspace for the dish, in [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), if applicable.  Always use in combination with `cookTime`.  
`recipeCategory` | `[Text](https://schema.org/Text)` The type of meal or course your recipe is about. For example: "dinner", "main course", or "dessert, snack".  
`recipeCuisine` | `[Text](https://schema.org/Text)` The region associated with your recipe. For example, "French", Mediterranean", or "American".  
`recipeIngredient` | `[Text](https://schema.org/Text)` 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. 

  
`recipeInstructions` | `[HowToStep](https://schema.org/HowToStep)`, `[HowToSection](https://schema.org/HowToSection)`, or `[Text](https://schema.org/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`. 
    
        "recipeInstructions": [
      {
        "@type": "HowToStep",
        "name": "Preheat",
        "text": "Heat oven to 425°F.",
        "url": "https://example.com/recipe#step1",
        "image": "https://example.com/photos/recipe/step1.jpg"
      }, {
        "@type": "HowToStep",
        "name": "Prepare crust",
        "text": "Place 1 pie crust in ungreased 9-inch glass pie plate, pressing firmly against side and bottom.",
        "url": "https://example.com/recipe#step2",
        "image": "https://example.com/photos/recipe/step2.jpg"
      }, {
        "@type": "HowToStep",
        "name": "Make filling",
        "text": "In large bowl, gently mix filling ingredients; spoon into crust-lined pie plate.",
        "url": "https://example.com/recipe#step3",
        "image": "https://example.com/photos/recipe/step3.jpg"
      }, {
        "@type": "HowToStep",
        "name": "Cover",
        "text": "Top with second crust. Cut slits or shapes in several places in top crust.",
        "url": "https://example.com/recipe#step4",
        "image": "https://example.com/photos/recipe/step4.jpg"
      }, {
        "@type": "HowToStep",
        "name": "Bake",
        "text": "Bake 40 to 45 minutes. The pie is ready when the apples are tender and the crust is golden brown.",
        "url": "https://example.com/recipe#step5",
        "image": "https://example.com/photos/recipe/step5.jpg"
      }, {
        "@type": "HowToStep",
        "name": "Cool",
        "text": "Cool on cooling rack at least 2 hours before serving.",
        "url": "https://example.com/recipe#step6",
        "image": "https://example.com/photos/recipe/step6.jpg"
      }
    ]

  * `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`. 
    
        "recipeInstructions": [
      "In large bowl, gently mix filling ingredients; spoon into crust-lined pie
    plate. Top with second crust. Cut slits or shapes in several places in top
    crust. Bake 40 to 45 minutes. The pie is ready when the or until apples are
    tender and the crust is golden brown. Cool on cooling rack at least 2 hours
    before serving."
    ]

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". Specify those phrases outside of structured data. Not recommended:
    
        "recipeInstructions": [{
      "@type": "HowToStep",
      "text": "Step 1. Heat oven to 425°F."
    }]

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

  
`recipeYield` | `[Text](https://schema.org/Text)` or `[Integer](https://schema.org/Integer)` The quantity produced by the recipe, if applicable. 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`). Example
    
    
    "recipeYield": [
      "6",
      "24 cookies"
    ]  
  
`totalTime` | `[Duration](https://schema.org/Duration)` The total time it takes to prepare the cook the dish, in [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), if applicable.  Use `totalTime` or a combination of both `cookTime` and `prepTime`.   
`video` | `[VideoObject](https://schema.org/VideoObject)` A video depicting the steps to make the dish. Follow the list of required and recommended [Video properties](/search/docs/appearance/structured-data/video#video-object).   
  
### `HowToSection`

Most recipes don't have sections. Start by splitting the recipe instructions into `HowToStep` properties, and only add `HowToSection` if you need to additionally specify sections of steps.

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, for multiple ways to make an apple pie, list them as multiple `Recipe` objects, not `HowToSection` objects.

The full definition of `HowToSection` is available at [schema.org/HowToSection](https://schema.org/HowToSection). 

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. Example:
    
    
    {
      "@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](https://schema.org/Text)` The name of the section.  
  
### `HowToStep`

Use `HowToStep` to group one or more sentences that explain how to do part of the recipe, if this makes sense for your content. 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](https://schema.org/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 [schema.org/HowToStep](https://schema.org/HowToStep). 

Required properties  
---  
`itemListElement` | `[HowToDirection](https://schema.org/HowToDirection)` or `[HowToTip](https://schema.org/HowToTip)` A list of detailed substeps, including directions or tips. Optional if `text` is used.  
`text` | `[Text](https://schema.org/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.   
Not recommended:
    
        {
      "@type": "HowToStep",
      "text": "Step 1. Heat oven to 425°F."
    }

Recommended:
    
        {
      "@type": "HowToStep",
      "text": "Heat oven to 425°F."
    }

  
Recommended properties  
---  
`image` | `[ImageObject](https://schema.org/ImageObject)` or `[URL](https://schema.org/URL)` An image for the step. Additional image guidelines: 

  * Image URLs must be [crawlable and indexable](/search/docs/crawling-indexing/sitemaps/image-sitemaps).
  * Images must represent the marked up content.
  * Images must be in .jpg, .png, or. gif format.

  
`name` | `[Text](https://schema.org/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](https://schema.org/URL)` A `URL` that directly links to the step (if one is available). For example, an anchor link fragment.   
`video` | `[VideoObject](https://schema.org/VideoObject)` or `[Clip](https://schema.org/Clip)` A video for this step or a clip of the video.  For `[VideoObject](https://schema.org/VideoObject)`, follow the list of required and recommended [Video](/search/docs/appearance/structured-data/video#type-definitions) or [Clip](/search/docs/appearance/structured-data/video#clip) properties.   
  
### `HowToDirection` and `HowToTip`

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

The full definitions of `HowToDirection` and `HowToTip` are available at [schema.org/HowToDirection](https://schema.org/HowToDirection) and [schema.org/HowToTip](https://schema.org/HowToTip). 

Required properties  
---  
`text` | `[Text](https://schema.org/Text)` The text of the direction or tip.  
  
### `ItemList`

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](/search/docs/appearance/structured-data/carousel).

The full definition of `ItemList` is available at [schema.org/ItemList](https://schema.org/ItemList).

Required properties  
---  
`itemListElement` | `[ListItem](https://schema.org/ListItem)` Annotation for a single item page.  
`ListItem.position` | `[Integer](https://schema.org/Integer)` Ordinal position of the item page in the list. For example:
    
    
    "itemListElement": [
      {
        "@type": "ListItem",
        "position": 1,
      }, {
        "@type": "ListItem",
        "position": 2,
      }
    ]
      
  
`ListItem.url` | `[URL](https://schema.org/URL)` The canonical URL of the item page. Every item must have a unique URL.  
  
## Monitor rich results with Search Console

Search Console is a tool that helps you monitor how your pages perform in Google Search. You don't have to sign up for Search Console to be included in Google Search results, but it can help you understand and improve how Google sees your site. We recommend checking Search Console in the following cases: 

  1. After deploying structured data for the first time
  2. After releasing new templates or updating your code
  3. Analyzing traffic periodically

###  After deploying structured data for the first time 

After Google has indexed your pages, look for issues using the relevant [Rich result status report](https://support.google.com/webmasters/answer/7552505). Ideally, there will be an increase of valid items, and no increase in invalid items. If you find issues in your structured data:

  1. Fix the invalid items.
  2. [Inspect a live URL](https://support.google.com/webmasters/answer/9012289#test_live_page) to check if the issue persists.
  3. [Request validation](https://support.google.com/webmasters/answer/13300208) using the status report.

###  After releasing new templates or updating your code 

When you make significant changes to your website, monitor for increases in structured data invalid items. 

  * If you see an increase in invalid items, perhaps you rolled out a new template that doesn't work, or your site interacts with the existing template in a new and bad way.
  * If you see a decrease in valid items (not matched by an increase in invalid items), perhaps you are no longer embedding structured data in your pages. Use the [ URL Inspection tool](https://support.google.com/webmasters/answer/9012289) to learn what is causing the issue.

###  Analyzing traffic periodically 

Analyze your Google Search traffic using the [Performance Report](https://support.google.com/webmasters/answer/7576553). The data will show you how often your page appears as a rich result in Search, how often users click on it and what is the average position you appear on search results. You can also automatically pull these results with the [Search Console API](/webmaster-tools/search-console-api-original/v3/how-tos/search_analytics). 

## Troubleshooting

If you're having trouble implementing or debugging structured data, here are some resources that may help you. 

  * If you're using a content management system (CMS) or someone else is taking care of your site, ask them to help you. Make sure to forward any Search Console message that details the issue to them.
  * Google does not guarantee that features that consume structured data will show up in search results. For a list of common reasons why Google may not show your content in a rich result, see the [General Structured Data Guidelines](/search/docs/appearance/structured-data/sd-policies).
  * You might have an error in your structured data. Check the [list of structured data errors](https://support.google.com/webmasters/answer/13300873) and the [Unparsable structured data report](https://support.google.com/webmasters/answer/9166415).
  * If you received a structured data manual action against your page, the structured data on the page will be ignored (although the page can still appear in Google Search results). To fix [structured data issues](https://support.google.com/webmasters/answer/9044175#zippy=%2Cstructured-data-issue), use the [Manual Actions report](https://support.google.com/webmasters/answer/9044175). 
  * Review the guidelines again to identify if your content isn't compliant with the guidelines. The problem can be caused by either spammy content or spammy markup usage. However, the issue may not be a syntax issue, and so the Rich Results Test won't be able to identify these issues. 
  **Troubleshoot missing rich results / drop in total rich results**.
  * Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it. For general questions about crawling and indexing, check the [Google Search crawling and indexing FAQ](/search/help/crawling-index-faq). 
  * Post a question in the [Google Search Central forum](https://support.google.com/webmasters/community).

Send feedback 

Except as otherwise noted, the content of this page is licensed under the [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/), and code samples are licensed under the [Apache 2.0 License](https://www.apache.org/licenses/LICENSE-2.0). For details, see the [Google Developers Site Policies](https://developers.google.com/site-policies). Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-10 UTC.

Need to tell us more?  [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-12-10 UTC."],[],["To enhance recipe visibility on Google, implement `Recipe` structured data with required properties like `name` and `image`. Follow guidelines and include recommended properties such as `cookTime`, `recipeIngredient`, and `recipeInstructions`. Validate using the Rich Results Test and deploy on a few pages initially. Use `ItemList` for recipe carousels and `HowToStep` or `HowToSection` to format recipe steps. Submit a sitemap to keep Google updated. Ensure images are accessible, and use the Search Console to monitor changes.\n"]] 

  ** LinkedIn  **

Join us on LinkedIn

  ** YouTube  **

Watch our videos

  ** Blog  **

Subscribe to our RSS feed

  ** Podcast  **

Listen to Search Off the Record

  ** X (Twitter)  **

Join us on X (Twitter)

  * ### Get support

    ** Go to the help forum **
    ** Submit a question for office hours **
    ** Report spam, phishing, or malware **
    ** More support resources **
  * ### Resources

    ** Do you need an SEO? **
    ** SEO Starter Guide **
    ** Status of Search systems **
    ** Search Console documentation **
    ** Case Studies **
  * ### Tools

    ** Search Console **
    ** Rich Results Test **
    ** PageSpeed Insights **
    ** AMP Test **

[ ](https://developers.google.com/)

  ** Android **
  ** Chrome **
  ** Firebase **
  ** Google Cloud Platform **
  ** Google AI **
  ** All products **

  ** Terms **
  ** Privacy **
  * Manage cookies 

  * English
  * Deutsch
  * Español
  * Español – América Latina
  * Français
  * Indonesia
  * Italiano
  * Polski
  * Português – Brasil
  * Tiếng Việt
  * Türkçe
  * Русский
  * العربيّة
  * हिंदी
  * ภาษาไทย
  * 中文 – 简体
  * 中文 – 繁體
  * 日本語
  * 한국어
