Free Recipe Schema Generator

Generate valid Recipe JSON-LD structured data for your food posts. Add ingredients, steps, times, and nutrition, then copy the markup. Free, no sign-up required.

Build Your Recipe Schema

Recipe basicsThe core details of the recipe you are marking up.

The name of the dish. This must match the visible title on the page.

Who created the recipe. Left out of the markup if empty.

ImagesUse high-resolution images (at least 1200px wide). Multiple aspect ratios help rich results.

DetailsTimes, yield, category, and cuisine. Times are entered in minutes and converted for you.

IngredientsList each ingredient with its quantity on its own line. Empty rows are skipped.

InstructionsOne step per row, in order. Each becomes a HowToStep in the markup. Empty rows are skipped.

Nutrition (optional)Basic nutrition information. Google can show calories in the recipe rich result.

Rating (optional)An aggregate rating can earn star ratings in search results.

Enter your recipe name above and your JSON-LD will build here automatically.

Generated JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Recipe"
}
</script>

How to add it to your site

  1. Copy the code above.
  2. Paste it inside the <head> section of the recipe page (or your recipe post template).
  3. Validate it with the Google Rich Results Test or the Schema.org Validator.
  4. Deploy, then request indexing in Google Search Console to speed things up.

Build better recipe pages around your schema

Structured data tells search engines what your recipe is. These free widgets make the page better for readers.

Explore More Free Tools

Other free tools to help you optimize and grow.

How It Works

How to use this free recipe schema generator

No account needed, no sign-up, completely free. Fill in your recipe details, and valid JSON-LD structured data builds live, ready to copy into your page.

1

Enter your recipe details

Add the recipe name, a short description, and a high-resolution image. Then fill in the prep and cook times in minutes, the yield, category, and cuisine. Everything you type builds the markup live.

2

Add ingredients and steps

List each ingredient with its quantity and write out the method one step at a time. Optionally add calories and, only if you show real reviews on the page, an aggregate rating. Empty rows are left out automatically.

3

Copy and validate

Copy the generated JSON-LD, paste it into the head of your recipe page, and confirm it with the Google Rich Results Test. No sign-up, completely free.

The Basics

What is recipe schema, and why does it matter?

Search engines read your recipe, but structured data tells them exactly what they are looking at: the dish, its ingredients, the steps, the times, and the rating.

The idea

Your recipe details → schema.org vocabulary → JSON-LD in your <head>

Result: search engines understand your recipe as data, not just text

Recipe schema is structured data that describes a single dish using the shared schema.org vocabulary. Instead of hoping Google infers the ingredients, steps, and cook time from your HTML, you state them explicitly in a format built for machines to read.

The recommended format is JSON-LD: a small block of JSON placed in the head of the page. It lives separately from your visible content, so it is easy to add without touching your design. This generator covers the fields Google uses for recipe rich results, from ingredients and instructions to times, nutrition, and ratings.

Structured data does not guarantee rankings or rich results, but it makes your recipe unambiguous to search engines and to the AI assistants that increasingly summarize the web. Clear data means your recipe is easier to represent, and cite, correctly.

Recipe Fields

The fields Google wants for recipe rich results

The properties that carry the most weight for recipe rich results. Here is what each one does and when to use it.

FieldWhat it doesWhen to useRole
nameThe name of the dish. Required, and it must match the visible title on the page.Every recipe you mark up.Required
recipeIngredientOne entry per ingredient, including the quantity. Google expects a complete list.Every recipe. Aim for one line per ingredient.Recommended
recipeInstructionsThe ordered method, written as HowToStep items so each step is machine-readable.Every recipe. List steps in the order you cook them.Recommended
aggregateRatingAn average rating and review count. Can earn star ratings in search results.Only when real reviews are shown on the page.Optional

Based on the schema.org Recipe type as supported by Google Search, 2026.

What It Can Unlock

What recipe schema can do for you

Structured data makes your recipe eligible for search features and helps machines understand your content. Eligibility is never guaranteed, but the groundwork matters.

🍽️

Recipe rich card

Valid Recipe markup makes your page eligible for an enhanced listing with an image, times, and rating that stand out in search.

Star ratings

An honest aggregate rating from real reviews on the page can show star ratings next to your result, which helps it earn attention.

⏱️

Cook time and calories in results

Prep time, cook time, and calorie data can appear right in the search listing, so cooks see the key details before they click.

🎠

Recipe carousel eligibility

Complete recipe data helps your dish qualify for host-specific recipe carousels and the recipe filters on Google.

🖼️

Image in results

A high-resolution image in your markup gives Google a clear candidate to show alongside your listing.

🤖

AI answer clarity

Structured recipe data makes your ingredients and steps easier for AI answer engines to attribute and cite accurately.

Avoid These

Six recipe schema mistakes that cause problems

Structured data helps only when it is accurate and valid. Steer clear of these common errors.

🚫

Marking up pages that are not recipes

Recipe schema is for actual recipes with ingredients and steps. Do not add it to a roundup, a category page, or a story with no method.

Only mark up real recipes

Inventing or borrowing ratings

Only add an aggregate rating that comes from real reviews visible on the same page. Fake or imported ratings violate Google guidelines and risk a penalty.

Real ratings only
📋

Incomplete ingredient or step lists

Leaving out ingredients or condensing several actions into one vague step weakens the markup. List every ingredient and every step.

List every item and step
⏱️

Wrong or missing times

Prep and cook times must reflect the real recipe. Do not pad or drop them, since Google shows these values directly to cooks.

Use accurate times

Never validating

Always run your markup through the Rich Results Test and Schema.org Validator. A single syntax slip can invalidate the whole block.

Validate before you ship
🖼️

Low-resolution or missing image

Google recommends images at least 1200px wide. A tiny image, or none at all, weakens your eligibility for the recipe rich card.

Use images 1200px+ wide

Get More From It

6 tips for effective recipe markup

Practical ways to make your schema work harder. All CommonNinja widgets mentioned are free to start.

01

Put the markup on the recipe page

Recipe schema belongs in the head of the individual recipe post, not your homepage. Add it to your recipe template so every dish gets it automatically.

02

Pair it with site-wide schema

Recipe markup describes one dish. Your Organization and WebSite schema describes the whole brand. Use both. Our free Website Schema Generator builds the site-wide part.

Try the Website Schema Generator
03

Write times and yield the way cooks read them

Enter prep and cook times in real minutes and a clear yield like "12 cookies" or "4 servings". Accurate details are what Google surfaces in the rich card.

04

Show every stage with images

Schema describes your content; make the on-page version just as clear. An image carousel walks readers through each stage of the dish and keeps them on the page.

Try the Image Carousel widget
05

Only add ratings you actually display

An aggregate rating is powerful, but it must come from real reviews shown on the page. If you do not display reviews, leave the rating out entirely.

06

Validate after every change

Re-run the Rich Results Test whenever you edit your markup or redesign the recipe template. It catches errors before Google does.

Glossary

Key recipe schema fields

A quick reference for the properties behind recipe markup.

FieldDefinitionExampleWhen It Matters
nameThe name of the dish. It must match the visible page title and is required for recipe rich results.Classic Chocolate Chip CookiesEvery recipe you mark up
recipeIngredientA list where each entry is one ingredient with its quantity. Google expects the full list.2 cups all-purpose flourEvery recipe
recipeInstructionsThe ordered method, written as HowToStep items so each step is machine-readable.HowToStep per stepEvery recipe
prepTime / cookTimeHow long the recipe takes, in ISO 8601 duration format. Entered here in minutes and converted for you.PT25MRecipes with a time commitment
aggregateRatingThe average rating and review count from real reviews shown on the page. Can earn star ratings.4.8 from 126 reviewsOnly when real reviews are on the page

FAQ

Recipe schema markup is structured data that describes a single dish, its ingredients, steps, times, and more, to search engines using the schema.org vocabulary. Instead of leaving search engines to guess the ingredients and cook time from the page, you state them explicitly in a machine-readable format. This generator creates Recipe JSON-LD you can copy straight into your page.
The recipe name is required and must match the visible title. Beyond that, Google looks for a high-resolution image, a complete recipeIngredient list, ordered recipeInstructions written as HowToStep items, and the prep and cook times. Adding recipeYield, recipeCategory, recipeCuisine, nutrition, and an honest aggregateRating strengthens the markup further and unlocks more of the rich card.
Google uses ISO 8601 duration format for prepTime, cookTime, and totalTime, which looks like PT25M for 25 minutes. You do not need to write that yourself: enter the time in plain minutes and this tool converts it. If you fill in both prep and cook time, the total time is calculated for you.
List each ingredient with its quantity on its own line, for example "2 cups all-purpose flour". Write the method one step at a time, in the order you cook. Each step becomes a HowToStep in the markup, which is the format Google reads best. Empty rows are skipped, so you only ever ship the lines you filled in.
Only if the rating comes from real reviews shown on the same page. An aggregate rating can earn star ratings in search results, but inventing, borrowing, or importing ratings you do not display violates Google guidelines and can trigger a manual penalty. If you do not show reviews on the page, leave the rating out.
JSON-LD is the format Google recommends for structured data: a small block of JSON inside a script tag. Copy the generated code and paste it into the section of the individual recipe page, or into your recipe template so every dish gets it automatically. It lives separately from your visible HTML, so it will not change how your page looks.
No. Structured data makes your page eligible for the recipe rich card and helps search engines understand your content, but Google decides when to show rich results, and schema is not a direct ranking factor. To check your markup, paste your page URL or the generated code into the Google Rich Results Test or the Schema.org Validator. Both are free and flag errors and warnings. Always validate after adding or editing your markup.

Trusted by