Tutorial

Recipe schema markup: a complete example and how to check yours

A complete recipe schema markup example in JSON-LD, the two fields Google actually requires, and a five-minute check to see whether your recipe pages get it right.

By Crumb EditorsUpdated 5 min read

You've seen them in Google: recipe results with a photo, a cook time, sometimes a row of stars. That extra detail comes from recipe schema markup, a small block of code that describes your recipe in a format Google can read without guessing.

Whether you ever touch that code depends on where your recipes live:

  • WordPress with a recipe card plugin, or a recipe platform like Crumb: the markup is built from the fields you fill in. Your job is checking it.
  • Squarespace: its automatic structured data covers blog posts, products and events, not recipes. Without a third-party recipe tool, you add it by hand. Our Squarespace recipe card guide covers the options.
  • Wix: it depends on the recipe app you use. Run the check below and see.
  • A hand-built website: you add it yourself, using the example below as a template.

Either way, here's what good markup looks like, which parts Google cares about, and the five-minute check that catches the mistakes Google's own test misses.

What recipe schema markup actually is

Schema.org is a shared vocabulary for describing things on web pages, and Recipe is one of its types. Google's recipe structured data documentation says which of those labels its search features use, and it's the page to trust over any blog post, this one included.

The markup usually sits in the page's code as JSON-LD: a list of labels (Google calls them properties) and their values. "recipeYield": "4" means "this recipe serves four." Readers never see it. Google reads it to understand the recipe and, if the page qualifies, to build an enhanced listing called a rich result.

A complete recipe schema example

Here's a recipe as a reader sees it on the page:

Lemon chickpea soup. Bright, lemony chickpea soup made in one pot. Serves 4. Prep 10 minutes, cook 30 minutes.

2 tablespoons olive oil · 1 onion, finely chopped · 3 garlic cloves, sliced · 2 cans (400 g each) chickpeas, drained · 1 liter vegetable stock · 100 g baby spinach · 1 lemon, zested and juiced · 1/2 teaspoon salt

  1. Warm the oil in a large pot over medium heat. Cook the onion until soft, about 8 minutes, then add the garlic for 1 minute.
  2. Add the chickpeas and stock. Bring to a boil, then simmer until the chickpeas crush easily against the side of the pot, about 15 minutes.
  3. Mash about a third of the chickpeas to thicken the soup. Stir in the spinach until wilted, then the lemon zest, lemon juice and salt.

And here's the matching markup, following the structure of Google's own examples:

{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "Lemon chickpea soup",
  "image": [
    "https://example.com/photos/1x1/lemon-chickpea-soup.jpg",
    "https://example.com/photos/4x3/lemon-chickpea-soup.jpg",
    "https://example.com/photos/16x9/lemon-chickpea-soup.jpg"
  ],
  "author": {
    "@type": "Person",
    "name": "Ana Example"
  },
  "datePublished": "2026-09-23",
  "description": "Bright, lemony chickpea soup made in one pot.",
  "recipeCategory": "Soup",
  "recipeCuisine": "Mediterranean",
  "keywords": "one-pot, weeknight, vegan",
  "prepTime": "PT10M",
  "cookTime": "PT30M",
  "totalTime": "PT40M",
  "recipeYield": "4",
  "recipeIngredient": [
    "2 tablespoons olive oil",
    "1 onion, finely chopped",
    "3 garlic cloves, sliced",
    "2 cans (400 g each) chickpeas, drained",
    "1 liter vegetable stock",
    "100 g baby spinach",
    "1 lemon, zested and juiced",
    "1/2 teaspoon salt"
  ],
  "recipeInstructions": [
    {
      "@type": "HowToStep",
      "name": "Soften the onion",
      "text": "Warm the oil in a large pot over medium heat. Cook the onion until soft, about 8 minutes, then add the garlic for 1 minute."
    },
    {
      "@type": "HowToStep",
      "name": "Simmer",
      "text": "Add the chickpeas and stock. Bring to a boil, then simmer until the chickpeas crush easily against the side of the pot, about 15 minutes."
    },
    {
      "@type": "HowToStep",
      "name": "Finish",
      "text": "Mash about a third of the chickpeas to thicken the soup. Stir in the spinach until wilted, then the lemon zest, lemon juice and salt."
    }
  ]
}

On a real page it sits inside <script type="application/ld+json"> tags. A few details worth copying:

  • Times use ISO 8601 durations. PT10M is 10 minutes; an hour and a half is PT1H30M.
  • Every ingredient is one line of text, quantity included, exactly as the reader sees it.
  • Steps are HowToStep objects with only the instruction itself. Google asks you to leave out labels like "Step 1".
  • There's no aggregateRating, because this soup has no reviews. Add ratings only when real readers have left them on the page.

Which fields Google requires, and which it recommends

FieldGoogle saysWhat to know
nameRequiredThe name of the dish.
imageRequiredA photo of the finished dish. The URL must be crawlable and indexable. Google suggests several high-resolution versions at 16:9, 4:3 and 1:1.
recipeIngredient, recipeInstructionsRecommended"Recommended" for search, essential for cooks. Always include them.
prepTime + cookTime, or totalTimeRecommendedUse prepTime and cookTime together, or totalTime.
recipeYieldRecommendedGive servings as a plain number. You can add an item count too, like ["6", "24 cookies"].
nutrition.caloriesRecommendedPer serving. If you include it, recipeYield with the number of servings is required.
keywordsRecommendedExtra descriptors like "one-pot". Categories and cuisines have their own fields.
aggregateRatingRecommendedOnly from real reviews, following Google's review snippet rules.

Missing a required field makes the page ineligible for a recipe rich result. A missing recommended field may be flagged as a non-critical issue in the testing tool; Google says fixing those can improve your structured data, but they aren't needed for eligibility.

Check your own recipe schema in five minutes

  1. Open Google's Rich Results Test and enter the full address of a published recipe. Use the URL option instead of pasting code, so you test what your website actually serves.
  2. Look for Recipe under the detected items and expand it. If the tool can't fetch the page, fix access first. It can't log in, so private and members-only pages won't work.
  3. Put the page and the results side by side and compare: name, photo, every ingredient, every step, yield and times.

That third step is the one people skip, and it's where the real problems hide. The test checks format. It has no idea what your recipe says. If the page says 1 tablespoon of lemon juice and the markup says 1 teaspoon, the test passes happily. If the soup serves four on the page and six in the markup, it passes too.

Mismatches like that usually mean the markup is coming from an old field, a plugin setting or a second copy of the recipe. Correct the recipe in your editor first, then publish and test again.

When your editor is right and the markup isn't

On Crumb, the markup is built from the recipe fields you fill in: title, cover image, ingredients, instructions, yield and times. Fix the field and the markup follows when you save. On WordPress, the recipe card plugin does the same job, with its own settings. If you wrote the markup by hand, the fix is in your code, and every correction to the recipe means editing it twice.

If the saved fields are right and the test still shows the wrong value, send whoever maintains your website or plugin a report they can act on:

My soup page says "Serves 4," and the recipe editor says four. Google's Rich Results Test still shows recipeYield as 6 after publishing. Here's the recipe address and a screenshot of the test. Can you check where the old value comes from?

If you're still choosing where to publish, compare recipe website builders on how they generate recipe markup and where you'd fix it.

Markup matches and the test is clean, but still no rich result? Google doesn't guarantee one, and the cause is usually bigger than the code: access, indexing or a name nobody searches for. The recipe SEO guide walks through those checks in order, starting with URL Inspection.

recipe SEOrecipe schemastructured data
← Back to the blog