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 | |
|---|---|
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 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.
Here's an overview of how to build, test, and release structured data. For a step-by-step guide on how to add structured data to a web page, check out the structured data codelab.
- Add the required properties. For information about where to put structured data on the page, watch JSON-LD structured data: Where to insert on the page.
- Follow the guidelines.
- Validate your code using the Rich Results Test.
- Deploy a few pages that include your structured data and use the URL Inspection tool 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
noindextag, or login requirements. If the page looks okay, you can ask Google to recrawl your URLs. - To keep Google informed of future changes, we recommend that you submit a sitemap. You can automate this with the Search Console Sitemap API.
Examples
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.
<html>
<head>
<title>Party Coffee Cake</title>
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "Recipe",
"name": "Party Coffee Cake",
"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": "2018-03-10",
"description": "This coffee cake is awesome and perfect for parties.",
"prepTime": "PT20M",
"cookTime": "PT30M",
"totalTime": "PT50M",
"keywords": "cake for a party, coffee",
"recipeYield": "10",
"recipeCategory": "Dessert",
"recipeCuisine": "American",
"nutrition": {
"@type": "NutritionInformation",
"calories": "270 calories"
},
"recipeIngredient": [
"2 cups of flour",
"3/4 cup white sugar",
"2 teaspoons baking powder",
"1/2 teaspoon salt",
"1/2 cup butter",
"2 eggs",
"3/4 cup milk"
],
"recipeInstructions": [
{
"@type": "HowToStep",
"name": "Preheat",
"text": "Preheat the oven to 350 degrees F. Grease and flour a 9x9 inch pan.",
"url": "https://example.com/party-coffee-cake#step1",
"image": "https://example.com/photos/party-coffee-cake/step1.jpg"
},
{
"@type": "HowToStep",
"name": "Mix dry ingredients",
"text": "In a large bowl, combine flour, sugar, baking powder, and salt.",
"url": "https://example.com/party-coffee-cake#step2",
"image": "https://example.com/photos/party-coffee-cake/step2.jpg"
},
{
"@type": "HowToStep",
"name": "Add wet ingredients",
"text": "Mix in the butter, eggs, and milk.",
"url": "https://example.com/party-coffee-cake#step3",
"image": "https://example.com/photos/party-coffee-cake/step3.jpg"
},
{
"@type": "HowToStep",
"name": "Spread into pan",
"text": "Spread into the prepared pan.",
"url": "https://example.com/party-coffee-cake#step4",
"image": "https://example.com/photos/party-coffee-cake/step4.jpg"
},
{
"@type": "HowToStep",
"name": "Bake",
"text": "Bake for 30 to 35 minutes, or until firm.",
"url": "https://example.com/party-coffee-cake#step5",
"image": "https://example.com/photos/party-coffee-cake/step5.jpg"
},
{
"@type": "HowToStep",
"name": "Enjoy",
"text": "Allow to cool and enjoy.",
"url": "https://example.com/party-coffee-cake#step6",
"image": "https://example.com/photos/party-coffee-cake/step6.jpg"
}
],
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "5",
"ratingCount": "18"
},
"video": {
"@type": "VideoObject",
"name": "How to make a Party Coffee Cake",
"description": "This is how you make a Party Coffee Cake.",
"thumbnailUrl": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"contentUrl": "http://www.example.com/video123.mp4",
"embedUrl": "http://www.example.com/videoplayer?video=123",
"uploadDate": "2018-02-05T08:00:00+08:00",
"duration": "PT1M33S",
"interactionStatistic": {
"@type": "InteractionCounter",
"interactionType": { "@type": "http://schema.org/WatchAction" },
"userInteractionCount": 2347
},
"expires": "2019-02-05T08:00:00+08:00"
}
}
</script>
</head>
<body>
</body>
</html>
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.
<html>
<head>
<title>Non-alcoholic Pina Colada</title>
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "Recipe",
"name": "Non-alcoholic Pina 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": "2018-03-10",
"description": "This non-alcoholic pina colada is everyone's favorite!",
"recipeCuisine": "American",
"prepTime": "PT1M",
"cookTime": "PT2M",
"totalTime": "PT3M",
"keywords": "non-alcoholic",
"recipeYield": "1 serving",
"recipeCategory": "Drink",
"nutrition": {
"@type": "NutritionInformation",
"calories": "120 calories"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "5",
"ratingCount": "18"
},
"recipeIngredient": [
"2 cups of pineapple juice",
"5/8 cup cream of coconut",
"ice"
],
"recipeInstructions": [
{
"@type": "HowToStep",
"text": "Blend 2 cups of pineapple juice and 5/8 cup cream of coconut until smooth."
},
{
"@type": "HowToStep",
"text": "Fill a glass with ice."
},
{
"@type": "HowToStep",
"text": "Pour the pineapple juice and coconut mixture over ice."
}
],
"video": {
"@type": "VideoObject",
"name": "How to make a Party Coffee Cake",
"description": "This is how you make a Party Coffee Cake.",
"thumbnailUrl": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"contentUrl": "http://www.example.com/video123.mp4",
"embedUrl": "http://www.example.com/videoplayer?video=123",
"uploadDate": "2018-02-05T08:00:00+08:00",
"duration": "PT1M33S",
"interactionStatistic": {
"@type": "InteractionCounter",
"interactionType": { "@type": "http://schema.org/WatchAction" },
"userInteractionCount": 2347
},
"expires": "2019-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>
Guidelines
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
Recipestructured 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
ItemListstructured data to summarize the recipes for your list. You can provideItemListstructured 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.
- Provide
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 type. The full definition of
Recipe is available at
schema.org/Recipe.
| Required properties | |
|---|---|
|
Image of the completed dish. Additional image guidelines:
For example: "image": [ "https://example.com/photos/1x1/photo.jpg", "https://example.com/photos/4x3/photo.jpg", "https://example.com/photos/16x9/photo.jpg" ] |
|
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 If the |
|
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 |
|
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
|
|
The number of calories in each serving produced with this
recipe. If |
|
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 |
|
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:
|
|
The steps to make the dish. There are several options for setting the value of
Additional guidelines
|
|
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 Example "recipeYield": [ "6", "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 |
|
VideoObject
A video depicting the steps to make the dish. Follow the list of required and recommended Video properties.
|
|
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
"startOffset": 20, "endOffset": 29, "url": "https://www.example.com/example?t=20" |
HowToSection
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
schema.org/HowToSection.
| Required properties | |
|---|---|
|
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 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."
}
]
}
|
|
Text
The name of the section. |
HowToStep
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
schema.org/HowToStep.
| Required properties | |
|---|---|
|
HowToDirection or HowToTip
A list of detailed substeps, including directions or tips. Optional if |
|
Text
The full instruction text of this step. Optional if
|
| Recommended properties | |
|---|---|
|
ImageObject or URL
An image for the step. Additional image guidelines:
|
|
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
A |
|
VideoObject or Clip
A video for this step or a clip of the video. For |
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
schema.org/HowToDirection and
schema.org/HowToTip.
| Required properties | |
|---|---|
|
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.
The full definition of ItemList is
available at schema.org/ItemList.
| 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. |
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:
- After deploying structured data for the first time
- After releasing new templates or updating your code
- 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. Ideally you should see an increase of valid pages, and no increase in errors or warnings. If you find issues in your structured data:
- Fix the errors.
- Inspect a live URL to check if the issue persists.
- Request validation 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 errors and warnings.- If you see an increase in errors, 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 errors), perhaps you are no longer embedding structured data in your pages. Use the URL Inspection tool to learn what is causing the issue.
Analyzing traffic periodically
Analyze your Google Search traffic using the Performance Report. 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.Troubleshooting
If you're having trouble implementing structured data, here are some resources that may help you.
- You might have an error in your structured data. Check the list of structured data errors.
- Troubleshoot missing rich results / drop in total rich results.
- For general questions about crawling and indexing, check the Webmaster FAQ.
- Ask a question in the Webmaster Office Hours.
- Post a question in the Webmaster forum.