Recipe Schema Generator

Generate Recipe JSON-LD for Google rich results and recipe cards.

Total Time: 45 minServings: 4Calories: 350 kcalIngredients: 5Steps: 6

Basic Information

Recipe Name

Description

Author Name

Image URL

Time & Servings

Prep Time (min)

Cook Time (min)

Total Time (min)

Servings

Category & Details

About Recipe Schema Generator

The Recipe Schema Generator creates valid JSON-LD structured data for your recipes following Schema.org standards. Adding Recipe markup helps Google display rich results including recipe cards, cooking times, calorie counts, and star ratings directly in search results — increasing click-through rates and driving more qualified traffic to your food blog or website. Simply fill in your recipe details and copy the generated JSON-LD into your page's <head> section inside a <script type="application/ld+json"> tag.

Built and maintained by Meet Shah · Last updated 19 July 2026

What this tool is used for

Producing structured data for a recipe page so it can qualify for rich results.
Filling in ingredient and instruction fields consistently across a site's recipes.
Checking which properties a rich result actually requires before writing them by hand.
Generating a starting block you then extend with nutrition or video fields.
Comparing your existing markup against a freshly generated version to find omissions.

Frequently Asked Questions

What does Recipe markup produce in search?: A rich card with the image, rating, cook time and calories, and eligibility for the recipe carousel and voice guidance. It is one of the most visually distinctive rich results, which is why food sites invest in it more than most.
How are durations written?: As ISO 8601 durations — PT30M for thirty minutes, PT1H15M for an hour and a quarter. The leading PT is required and is the part most often omitted, which silently invalidates the field rather than being interpreted leniently.
Which properties are required?: name and image at minimum, with recipeIngredient, recipeInstructions, cookTime, prepTime and recipeYield strongly recommended. Instructions as an array of HowToStep objects rather than one blob is what enables step-by-step voice guidance.
Can I include nutrition information?: Yes, through nutrition with calories and the rest as a NutritionInformation object. Calories is the field Google surfaces; the others are read but rarely displayed, and all of them should reflect the stated yield rather than the whole batch.
Do the ratings have to be real?: Yes, genuinely collected and visible on the page. aggregateRating invented or imported from elsewhere is a documented policy violation, and the penalty removes rich results across the whole site rather than for the one recipe.

Common errors and gotchas

Marking up content that is not on the page. Structured data must describe what a visitor can actually see.
Writing durations in plain text. The format expects an ISO 8601 duration, and prose is ignored.
Adding aggregate ratings with no real reviews behind them, which is a policy violation rather than an optimisation.
Splitting instructions into one step per sentence, which loses the structure the format is for.
Assuming valid markup guarantees a rich result. It makes eligibility possible, nothing more.