Fixing Recipe Schema Errors

What Recipe markup does in Google today

Recipe is a schema.org type for a single dish: its name, a photo, the ingredients, the method, how long it takes and how many it serves. Google reads it to build recipe rich results, the listing with a picture, star rating, total time and calories, and to place the page in recipe carousels and in the recipe filters on image and mobile search.

Unlike FAQ and HowTo, which Google cut back in 2023, Recipe rich results are still shown to all sites. That is why Recipe has its own report in Search Console, under Enhancements, and why the Rich Results Test still checks it in full. A Recipe error is not just an audit warning: it can be the difference between a listing with a photo and stars and a plain blue link.

Google splits Recipe problems into two kinds, and it helps to know which is which before starting:

• Errors (red, "critical"): the page cannot get a recipe rich result at all until they are fixed. A missing name or image, and JSON that cannot be read, are errors.
• Warnings (orange, "non-critical"): the page can still get a rich result, but with less in it. Missing recipeIngredient, totalTime, nutrition or aggregateRating are warnings, and each one removes something from the listing.

When Recipe is the wrong type

• A round-up of recipes ("20 summer salads") is a list, not a recipe. Mark up each recipe on its own page, and use an ItemList on the round-up page that points to them.
• Non-food instructions such as mixing paint or making soap are not recipes. Use HowTo or a plain article.
• A product page for a sauce or a meal kit is a Product, even if it lists ingredients.

The fields Recipe needs

Only two fields are strictly required, but a recipe rich result without the recommended fields is thin. This table lists what Google reads, and what each one adds.

A correct block you can copy

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "Lemon drizzle cake",
  "description": "A light sponge soaked in a sharp lemon syrup, ready in under an hour.",
  "image": [
    "https://example.com/images/lemon-drizzle-16x9.jpg",
    "https://example.com/images/lemon-drizzle-4x3.jpg",
    "https://example.com/images/lemon-drizzle-1x1.jpg"
  ],
  "author": { "@type": "Person", "name": "Sam Baker" },
  "datePublished": "2026-03-14",
  "prepTime": "PT15M",
  "cookTime": "PT40M",
  "totalTime": "PT55M",
  "recipeYield": "8",
  "recipeCategory": "Dessert",
  "recipeCuisine": "British",
  "keywords": "lemon cake, afternoon tea, traybake",
  "nutrition": { "@type": "NutritionInformation", "calories": "320 calories" },
  "recipeIngredient": [
    "225g unsalted butter, softened",
    "225g caster sugar",
    "4 large eggs",
    "225g self-raising flour",
    "2 lemons, zested and juiced",
    "85g icing sugar"
  ],
  "recipeInstructions": [
    { "@type": "HowToStep", "name": "Make the batter", "text": "Beat the butter and caster sugar until pale, then beat in the eggs one at a time and fold in the flour and lemon zest.", "url": "https://example.com/lemon-drizzle#step-1" },
    { "@type": "HowToStep", "name": "Bake", "text": "Spoon into a lined 2lb loaf tin and bake at 180C (160C fan) for 40 minutes until a skewer comes out clean.", "url": "https://example.com/lemon-drizzle#step-2" },
    { "@type": "HowToStep", "name": "Drizzle", "text": "Mix the lemon juice with the icing sugar, prick the warm cake all over and pour the syrup over it.", "url": "https://example.com/lemon-drizzle#step-3" }
  ],
  "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.7", "ratingCount": "38" }
}
</script>

The errors you will see, and what each one means

These are the messages the Rich Results Test, the Search Console Recipes report, the Schema Markup Validator and the Schema Debugger give for Recipe, with the cause behind each one.

Images: the most common critical error

A recipe without a usable image cannot get a rich result, and image problems are the most frequent critical Recipe error we see in audits. Google asks for more than one image in different shapes so it can crop for each place the recipe appears.

• Use full https addresses. A relative path such as /images/cake.jpg is not a valid URL in structured data.
• Give three crops. Google recommends the same photo in 16x9, 4x3 and 1x1 ratios, each at least 50,000 pixels in area (for example 1200 x 675, 1200 x 900 and 1200 x 1200).
• Let Google crawl them. An image folder blocked in robots.txt, a hotlink-protection rule, or an image served only after a script runs, all count as missing.
• Show the finished dish. The image must be of this recipe. A site logo, a stock photo or an image of the author is not a valid recipe image.
• Keep it on the page. The marked-up image should be one the reader can see on the page.

Times, yield, nutrition and ratings

Times

prepTime, cookTime and totalTime are ISO 8601 durations. They start with P, and a T comes before hours, minutes and seconds.

If you give all three, totalTime should equal prepTime plus cookTime, or be longer when there is resting or chilling time. A totalTime shorter than the cooking time is flagged as a mismatch.

Yield

recipeYield takes a number of servings ("8") or a quantity with its unit ("12 cookies", "1 loaf"). Google uses the number to work out calories per serving, so give the servings count when you can.

Nutrition

Nutrition sits inside its own object. calories is text with the unit: "320 calories". Other values such as fatContent, proteinContent and sugarContent also take text with a unit: "12 g". Give values per serving, to match recipeYield.

Ratings

aggregateRating needs a ratingValue and a ratingCount or reviewCount above zero. The rating must come from real readers and be shown on the page. A rating written by the site owner, or copied from another site, breaks Google's review snippet rules and can lead to a manual action.

Fixing JSON that cannot be read

An unparsable block is ignored completely, including every other type in the same script. Recipe blocks are long and full of text typed by people, so they break often. Four mistakes cause almost all of them.

1. A comma after the last ingredient or step

    "85g icing sugar",
  ],      <-- the comma before ] breaks the JSON

2. Curly quotes

Recipe text pasted from a word processor often carries “ and ”. They are fine inside a value, but the quotes that open and close each name and value must be straight: ".

3. A double quote inside a value

"recipeIngredient": ["1 8" cake tin"]           <-- broken: inch mark ends the string
"recipeIngredient": ["1 8\" cake tin"]         <-- fixed

Inch marks in tin sizes are the most common cause of a broken Recipe block. Escape them with a backslash, or write "20cm" or "8 inch".

4. A line break inside the text

A raw line break inside a value ends the string. Split long methods into separate HowToStep items rather than one long value with line breaks.

Making the markup match the recipe on the page

Google's structured data rules apply in full to recipes: the markup must describe the recipe the reader sees. Mismatches are common because recipes get edited after publishing.

• Same ingredients. Every ingredient in the markup must be in the visible ingredient list, with the same amounts.
• Same method. Steps in the markup should match the visible steps in number and order.
• Same times and servings. If the recipe card says 45 minutes and serves 6, the markup should say PT45M and 6.
• One recipe per block. A page with two recipes (a cake and its icing) can mark up both, each in its own Recipe, only if both are full recipes on the page.
• Ratings visible. If the markup has an aggregateRating, the page must show the rating and let readers leave one.

The fix, step by step

Stopping it from coming back

• One recipe source. Let the recipe card plugin output Recipe, and switch off Recipe output in the theme and any SEO plugin.
• Make the image compulsory. Do not publish a recipe post without a featured image.
• Store times as numbers. Keep minutes as numbers in the recipe card and let it write the ISO 8601 durations, so no one types "about an hour" into the markup.
• Watch the Recipes report. Search Console emails you when new Recipe errors appear. Treat those emails as a to-do list.
• Test after updates. Re-run the Schema Debugger on one recipe after every plugin or theme update.