What is Recipe schema?
Recipe schema describes a cooking recipe with name, image, ingredients, instructions, total time, yield and nutrition information. It is one of the oldest and most successful structured data types in Google search, powering recipe rich results, image carousels, Google Discover and the dedicated recipes filter on mobile. Sites that publish recipes without valid markup are effectively invisible in the most important food-search experiences regardless of how good the actual recipe is.
Which fields does Google need for recipe rich results?
Google requires name, image, recipeIngredient and recipeInstructions. Strongly recommended fields include author, datePublished, description, prepTime, cookTime, totalTime, recipeYield, recipeCategory, recipeCuisine, nutrition and aggregateRating. Times must be in ISO 8601 duration format such as PT30M. Each instruction step should be a HowToStep with a name and text, and ingredient lines should be plain strings that include quantity and unit, for example two tablespoons olive oil.
How does aggregateRating affect recipe rankings?
Recipes with valid first-party aggregateRating tend to win larger, more visual rich-result treatments, and the rating star itself attracts clicks. Use ratingValue between 1 and 5, plus reviewCount. As with all rich-result reviews, the ratings must be collected on your own site and visible to users. Pulling ratings from third-party sources or showing inflated counts is against Google's structured data policy and is a common cause of manual actions in the recipe vertical.
Can I add video to a recipe?
Yes. Embed a VideoObject inside the recipe with name, description, thumbnailUrl, contentUrl or embedUrl, uploadDate and duration. Recipes with video typically earn larger SERP treatments and better Discover placement because video is a high-engagement format. The generator can emit the VideoObject inline so you only manage one block of structured data per recipe instead of juggling separate recipe and video schemas that risk falling out of sync.
How do I validate Recipe structured data?
Run the URL through Google's Rich Results Test, which has a dedicated Recipe section that lists every property it detected and any required fields that are missing. The Schema Markup Validator catches general schema.org issues. Once live, the Recipe enhancement report in Search Console aggregates errors and warnings across the site, and the Performance report filtered by Recipe appearance confirms how many impressions and clicks the new markup is generating.
How can I avoid common recipe schema mistakes?
Keep one Recipe block per page, ensure the visible content matches the schema exactly, do not stuff keywords into the recipe name, and never emit Recipe markup on listing pages or category archives. Time fields must be ISO 8601 durations, not human strings. Images should be high resolution and represent the finished dish. The generator handles formatting correctly, but reviewing each value before publishing prevents subtle policy and validation issues from slipping through.
