Recipe markup should separate information about the dish from preparation instructions: use Recipe to describe the dish’s name, images of the finished dish, ingredients, and timing, then use recipeInstructions with HowToStep to mark up the steps. Use HowToSection to group steps only when a single recipe has multiple preparation sections. The following explains which properties to use for each type of information, based on Google’s developer documentation. Even complete markup does not guarantee how a recipe will appear in search results.
Put information about the dish in the appropriate properties
The documentation lists name and image as required properties for the dish’s name and images of the finished dish. Images must match the marked-up content, be crawlable and indexable, and use a supported format. A photo of a preparation step should not simply be used as an image of the finished dish.
- recipeIngredient: List the ingredients needed for the recipe as text, without unnecessary information such as ingredient definitions.
- author: Provide the recipe’s author; description: Provide a brief introduction to the dish.
- recipeCategory: Provide a category such as “main course” or “dessert”; recipeCuisine: Provide the region associated with the cuisine.
- keywords: Provide seasons, holidays, or other descriptive terms, separating multiple entries with commas. Do not repeat the recipe category or cuisine information here.
Distinguish preparation from cooking time and specify the yield for nutrition information
Use totalTime for the combined preparation and actual cooking time, or provide both prepTime and cookTime. prepTime covers preparing ingredients and the workspace, while cookTime is the actual cooking time. According to the documentation, prepTime and cookTime should be used together, with durations expressed in ISO 8601 format.
If you provide nutrition information per serving, you must specify the yield using recipeYield. If you specify nutrition.calories, recipeYield must state the quantity the recipe produces. The documentation’s example lists both six servings and twenty-four cookies, showing that serving count and the number of finished items can be provided together.
Describe actions in the step text and summarize them in the step name
The recommended approach is to use a separate HowToStep for each step in recipeInstructions. For a simple step, use text to provide the complete instructions. To break down instructions or tips further, use itemListElement instead, with HowToDirection or HowToTip entries that each have their own text. Once either text or itemListElement is provided, the other is optional.
For example, name could be “Arrange the pie crust,” while text provides the specific actions. Do not include phrases such as “Step 1,” “Instructions,” or “Watch the video” in the action text, or insert the author, recipe category, or keywords into the steps. Step names should describe the content, rather than consist only of a number.
The documentation also allows instructions in a block of text. Google will attempt to combine the text, automatically split it into steps, and remove inappropriate content, but correct interpretation is not guaranteed. The documentation therefore still recommends explicitly marking up each step.
Use sections for parts of one recipe, not different versions
A recipe with a straightforward sequence of steps does not need additional sections. If a pizza recipe includes making the crust, preparing the toppings, assembling the pizza, and baking it, you can group these using HowToSection. Give each section a name and list its steps in itemListElement.
Different ways of making the same dish should be marked up separately. For example, multiple apple pie recipes should each use a separate Recipe object, rather than being placed in HowToSection entries within a single recipe.
Recipe markup: perspectives from across the web
Can Recipe image markup determine which image appears in text search results?
No. Google’s documentation states that the Recipe image property does not affect image selection in text search results. To optimize images for those results, follow image SEO best practices separately. For the best image results, the documentation recommends providing high-resolution images in 16:9, 4:3, and 1:1 aspect ratios, each containing at least 50,000 pixels, but this does not guarantee that a particular image will appear in search results.
What requirements apply when adding images to individual cooking steps?
If you provide an image for a HowToStep, its URL must be crawlable and indexable, the image must represent the marked-up content of that step, and it must use the .jpg, .png, or .gif format. These requirements apply when a step image is provided. If you also provide a step name, use a descriptive summary rather than a step number as the name.
How can ratings or a single review be marked up for a recipe?
If you use aggregateRating to represent an average rating, follow the review snippet guidelines and the list of required and recommended AggregateRating properties. If a Recipe includes a single review, the reviewer’s name must identify a valid person or organization; promotional wording or similar text cannot be used as the reviewer’s name. Rating markup should reflect actual data, and reviews should not be fabricated to obtain a star-rating display.
References
- 食譜結構定義標記 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Can Recipe image markup determine which image appears in text search results?; What requirements apply when adding images to individual cooking steps?
