Skip to the indexed answers
Digital Marketing Index

usdigitalmarketingindex.com SEO

Which fields are required for eligible Recipe structured data?

Two: image and name. Those are the only properties Google’s documentation lists as required for Recipe markup, checked on November 11, 2026 (Google’s recipe structured data documentation). Ingredients, instructions, cooking times, ratings, and the rest are recommended. They add information about the recipe, and a page can be eligible without them. Google’s lists change, so the documentation, not this guide, is the reference at the time of implementation. And eligibility is a condition for a rich result, not a promise of one.

Recipe eligibility

Before any field matters, the page has to be a recipe. The documentation says: “Use Recipe structured data for content about preparing a particular dish”. Its examples of what does not qualify are a facial scrub and party ideas, which it calls not valid names for a dish.

Page Recipe markup?
Instructions for making one dish Yes
A roundup linking to ten recipes Not as a single Recipe; each recipe page carries its own
A restaurant menu item with no method No
A craft, cosmetic, or cleaning preparation No
An article about an ingredient No

The general structured data guidelines also apply. In the documentation’s words, a page that violates them “might not show up as a rich result”.

Required and recommended fields

The required properties, with the conditions the documentation attaches:

Property What it holds Conditions stated
image An image of the completed dish The image URL must be crawlable and indexable; "Images must represent the marked up content"; a file format supported by Google Images
name The name of the dish A real dish name

Recommended properties named in the documentation:

  • aggregateRating
  • author
  • cookTime
  • datePublished
  • description
  • keywords
  • nutrition.calories
  • prepTime
  • recipeCategory
  • recipeCuisine
  • recipeIngredient
  • recipeInstructions
  • recipeYield
  • totalTime
  • video

Some of these carry rules of their own. The documentation says of prepTime: “Always use in combination with cookTime”. Of calories it says that if nutrition.calories is defined, recipeYield must be defined as well. For recipeInstructions it recommends the HowToStep form, one step per entry. For recipeIngredient it asks for “only the ingredient text that is necessary for making the recipe”.

A small example. The dish and all values are invented, and the address is a placeholder.

{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "Lemon Barley Soup",
  "image": [
    "https://www.example.com/images/lemon-barley-soup-1x1.jpg",
    "https://www.example.com/images/lemon-barley-soup-4x3.jpg"
  ],
  "author": {
    "@type": "Person",
    "name": "Jordan Ellis"
  },
  "datePublished": "2026-09-20",
  "description": "A light soup of pearl barley, lemon, and herbs.",
  "prepTime": "PT15M",
  "cookTime": "PT40M",
  "recipeYield": "4 servings",
  "recipeIngredient": [
    "1 cup pearl barley",
    "6 cups vegetable stock",
    "1 lemon, juiced"
  ],
  "recipeInstructions": [
    {
      "@type": "HowToStep",
      "text": "Simmer the barley in the stock until tender."
    },
    {
      "@type": "HowToStep",
      "text": "Stir in the lemon juice and serve."
    }
  ]
}

Only the name and image lines are required. Everything else in the block is there because the page shows it.

Visible recipe content

Every value in the markup has to be on the page. Google’s structured data guidelines say “Don’t mark up content that is not visible to readers of the page” (Google’s structured data general guidelines).

Markup Page
name The recipe's title
image A photograph of the finished dish that appears on the page
recipeIngredient The ingredient list, same items and quantities
recipeInstructions The method, same steps
prepTime, cookTime The times stated on the page
recipeYield The servings stated
aggregateRating Ratings that visitors gave and that the page displays
nutrition Figures the page publishes

What this rules out:

  • a stock photograph of a different dish;
  • times in the markup that are shorter than the method allows;
  • a rating with no reviews behind it;
  • calories added to the markup that the page does not give;
  • ingredients in the markup that the visible list omits.

Recommended fields should be added when the information is real and shown. Leaving one out is better than inventing a value to fill it.

Validation

Check Method Pass condition
Required fields Rich Results Test Recipe detected; no errors
Recommended fields Same test Warnings read and judged; each is a field you could add if the page has the information
Image Open each image URL; test with URL Inspection Loads; not blocked from crawling
Correspondence Compare markup with the visible recipe, field by field Identical
Dependent fields Inspect the markup prepTime accompanied by cookTime; calories accompanied by yield
Site-wide Search Console recipe report No rise in invalid items
After changes Retest when the recipe plugin or template updates Still valid

Reading the test output correctly matters. An error means a required property is missing or malformed, and the page is not eligible. A warning means a recommended property is absent, and the page remains eligible.

Two further points about scope. The documentation describes additional recipe presentations with their own requirements, such as a host carousel, which needs a summary page listing the recipes in the collection. And passing the test establishes eligibility only. Google’s guidelines state that it “does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test”.

Recipe is not the only type with a short required list. Article markup has no required properties at all, as explained in the guide to when a publisher should add Article structured data.

The answer in one line: image and name are required, everything else is recommended, and all of it must match the recipe a visitor sees.

Link trail

Reader comments on this answer

Add your comment to this answer

Your email address will not be published. Required fields are marked *