Recipe Schema Generator - Free JSON-LD Builder

A recipe schema generator turns your recipe details into Recipe JSON-LD, the structured data Google reads to understand ingredients, cooking times, calories and ratings. Fill in the form, click Generate Schema, and copy a ready-to-paste script block for your recipe page. It is free, needs no sign-in, and suits food bloggers and site owners.

What Is Recipe Schema Markup?

Recipe schema markup is structured data, written in the schema.org vocabulary, that labels the parts of a recipe so search engines can read them without guessing. Instead of scanning your page for something that looks like a cook time, Google reads a field that says exactly that.

The most common format is JSON-LD, a block of data placed in a script tag on the page. It sits apart from your visible content, so you can add it without touching your design. The block describes a single item of type Recipe, with properties such as name, author, description, image, prepTime, cookTime, recipeYield, recipeIngredient and recipeInstructions.

Google's Search Central documentation describes how this data can power recipe rich results, such as cards with a photo, a star rating, a cooking time and a calorie count. Rich results are not guaranteed for any page, but accurate markup is the starting point for being eligible. The same data also helps other systems that read the web understand what your page is about.

Which properties matter most?

Google's documentation treats the recipe name and image as required, and lists many others as recommended. These include author, date published, description, prep time, cook time, yield, category, cuisine, calories, ingredients, instructions and ratings. This generator covers all of those fields except total time, keywords and video.

How to Use the Recipe Schema Generator

You can build a complete block of Recipe JSON-LD in about five minutes by filling in the form from top to bottom. Only the recipe name is mandatory, but the more fields you complete accurately, the more useful the markup is.

1. Enter the Recipe Name, for example Classic Chocolate Chip Cookies. The tool asks you to fill this in before it will generate anything.
2. Add the Author Name, a Description, an Image URL (a full address starting with http or https) and the Date Published from the date picker.
3. Type the Prep Time and Cook Time in ISO 8601 format, such as PT15M for 15 minutes or PT1H20M for 1 hour 20 minutes. Then fill in Yield / Servings, Cuisine, Category and Calories (per serving).
4. Paste your ingredients into the Ingredients box, one per line, and your steps into the Instructions box, one step per line.
5. If your page really shows reviews, enter a Rating (1-5) and a Rating Count. Otherwise leave both empty.
6. Click Generate Schema, then press Copy and paste the result into your recipe page's HTML.

If you change any field after generating, the old result clears, so click Generate Schema again to get fresh code.

Worked Example: Chocolate Chip Cookies

Here is what a realistic input produces and how to read it. Say you publish a cookie recipe and enter the following values.

• Recipe Name: Classic Chocolate Chip Cookies
• Author Name: Jane Smith
• Prep Time: PT15M, Cook Time: PT30M
• Yield / Servings: 24 cookies
• Cuisine: American, Category: Dessert
• Calories: 250 calories
• Rating: 4.8, Rating Count: 128

The tool returns a script tag of type application/ld+json. Inside, the context points to schema.org and the type is Recipe. Jane Smith becomes a Person author. The calories value sits inside a nutrition object, the rating and count sit inside an aggregate rating object, and each line you typed in Instructions becomes its own step.

Each ingredient line becomes one entry in the ingredient list, so 2 cups all-purpose flour stays exactly as you wrote it. That is why the order and wording of your lines matter: Google and other readers see them the same way your visitors do.

Notice that the prep and cook times add up to 45 minutes of work, but this generator does not create a total time property. If your page shows a total time to readers, you can add that property by hand, or use the general schema markup generator as a reference for other types.

How Do You Read and Act on the Results?

The result is a single block of code with a Copy button, and a good result is one that matches your visible page line for line. Check the output against what readers see before you publish it.

If a field is wrong, the tool shows a message instead of code. Here is what each one means and how to fix it.

• Please enter a recipe name: the name field is empty. Add the title and click Generate Schema again.
• Duration message: your time is not in ISO 8601 form. Replace 30 minutes with PT30M, and 1 hour 20 minutes with PT1H20M.
• URL message: the image address is not absolute. Use the full address, including https://, not a relative path like /images/cookies.jpg.
• Rating and count message: you filled in only one of the two. Provide both, with a positive whole number for the count, or clear both fields.
• Rating range message: the rating must fall between 1 and 5.

What to do after copying

Paste the block into the HTML of your recipe page, usually in the head section, though Google also reads it in the body. Then run the live page through the schema markup validator to confirm the syntax and key properties are read correctly. Google's own Rich Results Test is also worth running to see whether the page is eligible for recipe features.

Who Is This Tool For?

The tool is for anyone who publishes a recipe and wants search engines to understand it without learning schema syntax. It is a good fit in several common situations.

• Food bloggers who write recipes in a plain editor and have no plugin that outputs structured data.
• Small business owners, such as bakeries, meal-kit shops and caterers, who publish a few recipes on a custom site.
• SEO consultants who need a quick, correct block to hand to a client or developer.
• Developers who want a clean starting template to adapt for a recipe template in a CMS.
• Site owners fixing errors after a structured data report flags missing recipe fields.

Best Practices and Common Mistakes

Accurate, complete markup that mirrors the page is what Google asks for, and most problems come from a mismatch between the data and what readers see. These habits prevent the common ones.

Match the markup to the page

Every ingredient, step, time and calorie value in your JSON-LD should also appear on the page. Google's guidelines say structured data must describe visible content. If you change a recipe, regenerate the block so the two stay in sync.

Only add ratings you actually collect

Do not invent a 4.8 rating to look better in results. Add rating data only if your site genuinely collects reviews and shows them to visitors. A made-up rating can break Google's structured data guidelines, and the tool will not let you add a lone rating without a count anyway.

Write one step per line

Each line in the Instructions box becomes a separate step. Pasting a long paragraph into one line creates a single huge step. Break it up at natural pauses, such as Preheat oven to 375°F on one line and Mix dry ingredients in a bowl on the next.

Keep calories as a per-serving number

The calories field is labeled per serving, so write something like 250 calories rather than the total for the whole batch. Make sure the yield and the calorie value describe the same portion.

Use a real, crawlable image

Point the Image URL at a photo of the finished dish that visitors can actually see on the page. A broken link or a placeholder defeats the purpose of a recipe card.

One recipe per block

Generate a separate block for each recipe page. If you also have a question section on the page, build it with the FAQ schema generator and add it as its own block.

Limitations and Accuracy Notes

This tool builds the core Recipe properties, and it cannot guarantee a rich result. Google decides what to show based on quality, relevance and eligibility, and markup alone does not promise a recipe card.

The form accepts one image URL and one set of nutrition data, which is calories only. It does not output total time, keywords, video or individual review entries. Fields you leave empty are simply left out, so a sparse form gives you a sparse block.

For rating details beyond the summary, the review schema generator can help with Review markup. If your recipe page is really a tutorial with steps and tools, the HowTo schema generator may suit that content better. You can also browse the On-Page SEO and Meta Tags tools for other markup and metadata helpers.

Use the form above to fill in your recipe, click Generate Schema, copy the result into your page, and test it before you publish. Accurate markup takes a few minutes and gives search engines a clear picture of your dish.