Comma-separated keywords
INGREDIENTS
INSTRUCTIONS
NUTRITION (per serving)
Ready to generate
Fill in the form and click Generate JSON-LD// build recipe json-ld for rich search results
Build Recipe JSON-LD structured data with ingredients, steps, nutrition, and timing fields. Generate schema markup for rich search results instantly.
Ready to generate
Fill in the form and click Generate JSON-LDEnter the recipe name, description, timing, and other metadata in the Basic Info tab.
Switch to the Ingredients and Steps tabs to add each item. Use the + button for more rows.
Click Generate JSON-LD to build the schema, then copy or download the output to paste in your page <head>.
The Recipe Schema Builder generates structured data markup (JSON-LD) following the schema.org Recipe specification. Adding this markup to your pages makes them eligible for Google's rich results — enhanced SERP cards showing ratings, cook time, and calories directly in search.
Recipe schema markup is structured data (JSON-LD format) added to your page's HTML head that tells search engines detailed information about your recipe. It follows the schema.org/Recipe specification and enables Google rich results — enhanced search cards showing star ratings, cook time, and calorie counts.
Schema markup itself is not a direct ranking factor, but it makes your pages eligible for rich results in Google Search. Rich results typically receive significantly higher click-through rates (CTR) than standard blue links, which can drive more organic traffic to your recipe content.
JSON-LD (JavaScript Object Notation for Linked Data) is Google's recommended format for structured data. It's embedded in a <script> tag in your page's <head> and doesn't affect visible page content. It's easier to manage than Microdata or RDFa because it's separate from HTML markup.
Copy the generated embed code and paste it inside the <head> section of your recipe page's HTML. If you use WordPress, you can add it via a plugin like RankMath, Yoast SEO, or by editing your theme's header.php. For static sites, paste it directly before the </head> closing tag.
Google requires at minimum: name, image, author, and either ingredients + instructions. Optional but recommended fields include nutrition, aggregateRating, prepTime, cookTime, and recipeYield. More complete markup increases the likelihood of displaying richer search cards.
After adding the code to your page, use Google's Rich Results Test (search.google.com/test/rich-results) to verify it's valid and eligible for rich results. You can also use our Schema Validator Lite tool to do a quick syntax check before deploying.
A Recipe Schema Builder is a tool that generates valid schema.org/Recipe JSON-LD structured data markup for food content. Instead of manually writing complex JSON, you fill in a form and the tool produces ready-to-embed code that tells search engines everything about your recipe — from ingredients and steps to nutrition facts and aggregate ratings.
When Google or Bing crawls your page and finds properly formatted Recipe schema, your listing becomes eligible for rich results in search: visually enhanced cards that display star ratings, preparation times, calorie counts, and even an image directly in the search results page (SERP). This makes your recipes stand out dramatically from plain blue links.
💡 Looking for premium SEO-optimized themes and templates? MonsterONE offers unlimited downloads of recipe blog themes, food WordPress templates, and UI kits — worth checking out.
Recipe structured data follows the schema.org/Recipe vocabulary. The markup is embedded in a <script type="application/ld+json"> tag inside your page's <head>. Search engines parse this structured data during crawling — it doesn't affect your page's visual appearance but gives crawlers machine-readable signals about your content.
The JSON-LD format is Google's preferred method because it's easy to update, keeps structured data separate from visible HTML, and is less error-prone than Microdata or RDFa alternatives. Our builder generates clean, validated JSON-LD that maps directly to Google's rich result requirements.
Google specifies required and recommended fields for Recipe rich results. Required fields include the recipe name, at least one image, the author, and either a list of recipeIngredients or a recipeInstructions block. Missing any required field will disqualify your recipe from rich results entirely.
Recommended fields that significantly improve rich result appearance include:
Schema.org timing fields require ISO 8601 duration format rather than plain numbers. Our builder handles this automatically — if you enter "30" for cook time, we generate "cookTime": "PT30M". The format follows the pattern: P[n]DT[n]H[n]M[n]S where P is the period designator, T separates date from time, and H/M/S represent hours, minutes, and seconds.
For example: 1 hour 30 minutes becomes PT1H30M. 2 days becomes P2D. Our tool converts your plain minute inputs to this format automatically, eliminating a common source of structured data errors.
The NutritionInformation nested schema lets you specify per-serving nutritional values including calories, fat, carbohydrates, protein, fiber, sodium, and more. While optional, nutrition data is increasingly valuable as users search with health-focused queries like "high protein breakfast recipes" or "low carb dinner ideas." Including this data can surface your recipes in these specialized results.
Each nutrition field accepts a text value with the unit embedded (e.g., "320 calories" or "12 grams"). Our builder formats these correctly and only includes fields where you've provided values, keeping the output clean and avoiding empty placeholder values that could confuse validators.
Beyond generating valid markup, follow these best practices to maximize rich result eligibility. First, ensure your recipe content matches the schema data — Google cross-references your markup against visible page content and will ignore or penalize markup that doesn't reflect the actual content. Second, always include a high-quality image; Google won't display rich results for recipes without images, and recommends images at 1x1, 4x3, and 16x9 aspect ratios for optimal display.
Third, keep instructions granular and step-by-step. Each HowToStep should represent one clear action, making it easier for Google to display step-by-step cards in search. Fourth, validate your markup after adding it — use Google's Rich Results Test and Search Console's Enhancement reports to catch issues before they affect traffic.
Writing Recipe JSON-LD manually is error-prone. Common mistakes include forgetting required @context and @type declarations, using incorrect ISO 8601 duration formats, nesting NutritionInformation incorrectly, or leaving invalid field names. Each error can invalidate your entire schema block. A dedicated builder ensures correct structure every time, with real-time generation so you see the output as you fill in the form.
Our Recipe Schema Builder generates production-ready markup that passes Google's validation checks, handles duration conversion automatically, and provides both standalone JSON and a ready-to-embed <script> tag — everything you need to go from form to deployed structured data in under two minutes.