You can use the Recipe schema Markup for letting Google know about your recipes. When you use the Recipe structured data, you provide valuable information like review ratings, preparation and cooking time, nutrition information, etc. helping Google to understand your content better and also display it in unique ways for the users.
Recipes appear in Google Search and Google Images.
You can enhance your recipes display over Google in two ways:
- Guided Recipes :
The Recipe structured data allows Google Assistant to guide users through various Recipes on Google Home and helps in a smart display. Make sure to add the RecipeIngridient and RecipeInstruction properties.
- Recipe Host Carousel :
You can enable users to explore recipe gallery pages by adding ItemList Structured Data.
PRO TIP: Please refer to the previous posts in the Series, to know in detail about How To Add Structured Data.
WHAT ARE THE GUIDELINES TO FOLLOW?
- It is mandatory for you to follow the General Structured Data Guidelines for making your Recipe eligible on Search Results.
- To display your Recipe as a Guided Recipe on the Google Assistant, ensure that your content follows the content restrictions policy for the assistant.
- Only use Recipe structured data for content containing information about preparing a particular dish and not for any other type of content.
- For ensuring that your Recipes are displayed as a carousel or grid, follow the below-listed guidelines:
- Ensure to provide ItemList structured data for summarising the recipes for your lists.
- Ensure to add ItemList structured data together or separately with the Recipe structured data.
- Your website must include a summary page listing all the recipes in the collection.
WHAT ARE THE VARIOUS PROPERTIES OF THE STRUCTURED DATA?
1.Recipe: The item holds a particular recipe.
2.Image: The entity contains the image of the completed dish.
- a.All images must be crawlable and indexable.
- All images must represent the marked-up content.
- All Image formats must be Google Images Supported.
- Each page must contain one image, and e.Google picks the best image that is displayed in search results considering the aspect ratio and resolution.
- Always provide high-resolution images with the said aspect ratios: 16×9, 4×3, 1×1.
3. Name: The name of the said dish.
4.Aggregate Rating: The property denotes the average review score for the said item. Follow the Review guidelines and the Required and Recommended AggeregateRating property.
5. Author: The name of the person or organisation who has created the recipe.
6. CookTime: the entity denotes the cooking time of the dish in ISO-8601. Ensure to use the entity in combination with preptime
7. DatePublished: the date of recipe publication in ISO-8601.
8. Description: The entity denotes the summary of the Dish.
9. Keywords: The entity contains various other keywords related to the recipe such as the said season, the holiday and other descriptions.
- Ensure to separate all multiple entries is a keywords list separated by commas.
- Avoid using a tag which should be in RecipeCategory or RecipeCusine.
10. Nutrition.Calories: The said number of calories per serving of the recipe.
11.PrepTime: The entity denotes the length of time taken for preparing the dish in ISO-8601. Ensure to use it in combination with CookingTime.
12.RecipeCategory: The entity denotes the type of the said recipe. Example: Dinner, Breakfast, etc.
13.RecipeCusine: The entity denotes the region of the recipe. Example: Meditrenian, French.
14. RecipeIngridient: A mandatory property for Guided Recipe. The ingredients used in the said recipe.Ensure to include the only ingredient which is essential for making the recipe.Avoid including unnecessary information like the definition of the ingredient, etc.
15.RecipeInstructions: The Entity is a mandatory property for Guided Recipes.The instructions needed to follow for making the dish.
You can denote the value in two ways:
a.HowToStep: You have to specify each step of the recipe via the entity.
b.HowToSection: Only use if the recipe has multiple sections. The entity groups the steps of multiple recipe sections.
- Single or Repeated Text Property :
A chunk of text indicating one or more steps. Google treats all the steps as part of a single section. Repeated property values are sequenced into a single chunk of text. Google then tries splitting the block of text into several individual steps. It tries to find and remove section names, numbers, keywords, any item which can incorrectly appear in the recipe step txt. It is recommended that you unambiguously specify steps using the HowTo step property.
Do not include unneeded metadata.
Only include texts containing how to make the dish. Avoid including texts like Directions, etc.
The steps should be specified outside the structured data.
16. RecipeYeild: The entity must be an integer type for guided recipes. Ensure to specify the number of savings the recipe produces with only a number. Use additional yields if you wish to include different units. It is required for specifying nutritional information preservation.
17. TotalTime: The entity holds the total time taken for making the entire dish in ISO-8601. You are free to use min and max as child elements for specifying a range of time
Use the entity in combination with CookTime and PrepTime.
18. Video: The video contains the steps to make the dish. Ensure to follow the list of Required and Recommended properties video properties.
- VideoWithClips: Video clips corresponding to segments of the video. Other various parts of the recipe might refer to the clips defined in the Video.hasPart
19. Video.hasPart: The video clip which is the part of the entire video.
20. Video.hasPart.endOffset: The entity holds the end time of the clip represented as several seconds from the starting of the video.
21. Video.hasPart.name: The name of the said clip.
22. Video.hasPart.startOffset: The beginning time of the clip represented via the number of seconds from the starting of the video.
23. Video.hasPart.URL: The link to the start of the clip. It must match the values set in Video.hasPart.start
How To Section :
PRO TIP: Many Recipes do not have sections. For Recipes having sections, start by splitting the recipe instructions into HowToStep properties and add the HowToSection only for specifying sections of steps.
- Ensure to use the said section for groping a sequence of steps that make up the recipe instructions.
- Always specify the HowToSection directly within the RecipeInstructions property or an ItemListElement of another HowToSection.
- It is used for defining a single recipe containing multiple steps
- Do not use the section to define different recipes for the same dish
- Use Recipe property for stating multiple recipes for a dish.
The various properties of the HowToSection:
a.ItemListElement: The entity holds the detailed steps of the section or subsections. If a recipe sub-section is not defined properly, then it might be presented as another step.
b.Name: The entity holds the name of the said section.
Use the entity for holding the various steps of a recipe.
- ItemListElement: The entity holds a detailed list of sub-steps that includes directions and tips.
- Text: The entity holds the full instructional text of the said step.
It is an optional entity, used only when ItemListElement is used.
Only include instructional text and not other texts such as Directions, etc.
- Image: An image for the said step.
All image URLs must be Crawlable and Indexable
Images should represent the marked-up content
Images should be in .jpg , .png , or .gif format.
4. Name: The entity holds the word or a short phrase summarizing the step. Avoid using non-descriptive text.
- URL: The entity holds the said URL linking directly to the said step.
- Video: The entity holds a video for the said step or a clip of the video.
- HowToDirection and HowToTip:
Use the said entity for describing directions or tips.
- Text: The said text of the direction or tip.
The property must be added if you want your recipe eligible to appear as a carousel.
- ItemListElement: The said item contains annotation for a single page item.
- ListItem.position: The item contains the ordinal position of the item page in the list.
- ListItem.Url: The URL of the said item page. Each item must have a unique URL.
PRO TIP: For knowing in-detail about problems related to Troubleshooting and Monitoring Rich Results with Search Console, please refer to the previous posts of the Series.