SEO & web Structured data

Recipe schema generator

Recipe name Description Author Image URL Prep time Cook time Servings Ingredients, one per line Steps, one per line Wrap in a <script type="application/ld+json"> tag Generated code

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

Built in your browser · nothing is uploaded

Local · PT20M, not “20 minutes”

Builds Recipe JSON-LD with ingredients and steps. Times use ISO 8601 duration format — `PT20M` is twenty minutes, `PT1H30M` is an hour and a half.

How to use the recipe schema generator

1 Fill in the fields. Empty ones are left out rather than emitted blank.

2 Keep the script-tag wrapper on unless you are inserting the JSON somewhere that adds it.

3 Paste it into your page and check it with Google’s Rich Results Test before relying on it.

The duration format is the only genuinely awkward part and it is worth learning: `P` opens the period, `T` separates the date part from the time part, then `H`, `M` and `S`. So twenty minutes is `PT20M`, not `20 minutes` or `PT20`. Recipe is one of the richer result types with real visible payoff — it can produce an image carousel with times and ratings — which is why recipe sites invest in it heavily. The ingredient list should match the page exactly, including quantities, since the markup is what a voice assistant reads aloud and a mismatch there is worse than an inconsistency in a search snippet.

Questions

What is PT20M? −

ISO 8601 duration: P opens the period, T starts the time part, so PT20M is twenty minutes and PT1H30M is ninety.

Do ingredients need quantities? +

Is recipe markup worth doing? +

Does structured data improve my rankings? +

How do I check it works? +

Sources

Schema.org — the vocabulary Google Search Central — structured data general guidelines

Was this tool any good?

INTERNAL SIGNAL ONLY · WE USE IT TO FIND TOOLS WORTH REBUILDING