Tool
What the Recipe Schema Generator does
Recipe Schema Generator: generates JSON-LD only from Recipe name, Image URL and Ingredients, one per line. Example: recipe name Lemon drizzle cake, image URL https://example.com/cake.jpg and prep time (PT20M) PT20M gives JSON-LD only { "@context": "https://schema.org", "@type": "Recipe", "name": "Lemon drizzle cake", "image": [ "https….
Enter Recipe name, Image URL, Ingredients, one per line and Method, one step per line and the Recipe Schema Generator reports JSON-LD only. The result recalculates on every keystroke without a button press or a page reload.
It is mostly used by people publishing a page. Small on-page details decide whether a listing gets clicked or scrolled past.
Nothing is sent to a server, which means you can safely check drafts and staging content.
The meaning of each field, the formula in use, and a worked example that starts from the default inputs are all further down.
What do the Recipe Schema Generator fields mean?
The Recipe Schema Generator uses 6 inputs. The defaults are there to be replaced. They exist so the tool is never showing an empty result.
| Field | What to enter | Default |
|---|---|---|
| Recipe name | required | Lemon drizzle cake |
| Image URL | required | https://example.com/cake.jpg |
| Ingredients, one per line | paste or type any amount of text | 200g butter 200g caster sugar 4 eggs 200g self-raising flour |
| Method, one step per line | paste or type any amount of text | Cream the butter and sugar. Beat in the eggs. Fold in the flour. Bake at 180C for 45 minutes. |
| Prep time (PT20M) | optional | PT20M |
| Cook time (PT45M) | optional | PT45M |
How does the Recipe Schema Generator work?
Each output is derived from the inputs above in a single pass; there is no hidden state carried between runs, so the same inputs always give the same generated output.
Range checks come first, so the formula only ever sees values it can handle.
Worked example
These are the values the Recipe Schema Generator loads by default, and the result it produces from them. These are the tool’s own default values and the result they produce, not an invented illustration.
| Recipe name | Lemon drizzle cake |
|---|---|
| Image URL | https://example.com/cake.jpg |
| Ingredients, one per line | 200g butter 200g caster sugar 4 eggs 200g self-raising flour |
| Method, one step per line | Cream the butter and sugar. Beat in the eggs. Fold in the… |
| Prep time (PT20M) | PT20M |
| Cook time (PT45M) | PT45M |
| JSON-LD only | { "@context": "https://schema.org", "@type": "Recipe", "name": "Lemon drizzle cake", "image": [ "https… |
|---|
Structured steps and ingredients, not prose blocks
name, image and recipeIngredient are required, but the single most common way this schema gets built wrong is providing what should be structured data as one undifferentiated block of text instead of the discrete list items the format expects.
Worth knowing
- recipeIngredient should be an array of individual ingredient strings ("200g butter", "4 eggs"), not one comma-separated block of text. A validator technically accepting a single string does not mean a recipe rich result parses it usefully.
- recipeInstructions works the same way: individual HowToStep entries, one per step, rather than the entire method as a single paragraph. This is exactly the structure this tool’s own form is built to produce correctly by design.
- prepTime, cookTime and totalTime in ISO 8601 duration format (PT20M for 20 minutes) feed the at-a-glance timing shown in the recipe card. Recipes without any of the three still validate but show a less complete card.
- aggregateRating and nutrition are both optional but commonly shown in the fuller recipe rich-result treatment when present, worth adding once the required fields are in place, provided that data genuinely exists.
How to use it
- Enter Recipe name.
- Set Image URL.
- Paste your content into Ingredients, one per line.
- Paste your content into Method, one step per line.
- Fill in Prep time (PT20M).
- Type Cook time (PT45M).
- Each keystroke triggers a fresh calculation, which is cheap because it happens locally.
- You get JSON-LD only back.
- Both Copy Link and Print capture the current state, so pick whichever suits how you file things.
What this tool does not do
- Search engines weigh hundreds of signals. No single on-page check predicts position.
- This inspects the markup you supply; it cannot see server headers or your live rankings.
- Assumptions built into the method are stated above, but they are still assumptions.
Frequently asked questions
The form asks for Recipe name, Image URL, Ingredients, one per line, Method, one step per line, Prep time (PT20M) and Cook time (PT45M). A starting value is in place for each, letting you treat it as a what-if tool rather than a data-entry form.
With the values loaded when the page opens, JSON-LD only comes out as { "@context": "https://schema.org", "@type": "Recipe", "name": "Lemon drizzle cake", "image": [ "https…. It recalculates the moment an input changes, which makes comparing scenarios quick.
Nothing is stored. The page has no back end to send data to, and holds your input only in memory.
It costs nothing, and there is no limit on repeat use.
Full double precision is used throughout; only the displayed figure is shortened.