Recipe Schema Generator for Food Bloggers

Recipe schema is the difference between a plain blue search result and a recipe card with a photo, star rating, total time, and calorie count showing right in Google. If you publish recipes and aren't using it, you're invisible in food search. Our free generator builds valid Recipe JSON-LD with every field Google's recipe rich results support — no plugin, no signup.

Why Recipe Schema Is Non-Negotiable for Food Blogs

Google has a dedicated Recipes search vertical, plus a recipes carousel that appears at the top of regular search results for food queries. To appear in either, your page needs valid Recipe schema. Without it, you simply don't exist in food search — Google won't show your page even if your content is the best on the internet.

The food blog space is competitive. Sites with complete Recipe schema (ingredients, instructions, nutrition, ratings, video) get pulled into the recipe carousel. Sites with thin or missing schema get buried. This isn't about ranking nuance — it's a binary inclusion gate.

The good news: Recipe schema is well-documented, has a clear required field list, and the generator does the heavy lifting. Add it once per recipe and you're in.

Required and Recommended Recipe Fields

Google requires the following for Recipe rich results:

• name — recipe title
• image — high-quality photo (1200px minimum)
• recipeIngredient — array of strings, one per ingredient
• recipeInstructions — array of HowToStep objects with text and ideally an image per step

Strongly recommended (and basically required for the carousel):

• aggregateRating — average rating and review count from real users
• nutrition — calories, fat, carbs, protein per serving
• prepTime, cookTime, totalTime — in ISO 8601 format
• recipeYield — servings or quantity
• recipeCategory — appetizer, main, dessert, etc.
• recipeCuisine — Italian, Mexican, Thai, etc.
• video — VideoObject of you making the recipe
• author — Person object with the cook's name

The recipes that win the carousel have all of the recommended fields filled in. The carousel is competitive — fewer than 10 results per query — so completeness wins.

The ISO 8601 Time Format for Recipe Times

All time fields use ISO 8601 duration format. The format starts with "PT" then numbers and unit letters:

• PT15M = 15 minutes
• PT1H = 1 hour
• PT1H30M = 1 hour 30 minutes
• PT45M = 45 minutes

You'll typically have prepTime (chopping, mixing), cookTime (active cooking time), and totalTime (prep + cook + any waiting). totalTime should equal prepTime + cookTime if you're being precise. Don't write "30 minutes" — write "PT30M". The generator does the conversion if you type the number into the minutes field.

Sell Custom Apparel — We Handle Printing & Free Shipping

Adding Nutrition Information (And Why You Should)

Nutrition info is technically optional but critical. Recipes with nutrition data (calories shown in the search snippet) get significantly higher click-through rates than recipes without. Health-conscious searchers filter mentally on calories before they click, so showing the calorie count is a major trust signal.

The NutritionInformation block needs at minimum: calories. Recommended: fatContent, saturatedFatContent, carbohydrateContent, proteinContent, sodiumContent, sugarContent, fiberContent. All values are per serving (so divide your total recipe values by recipeYield).

If you don't calculate nutrition manually, free tools like SparkRecipes Recipe Calculator or VeryWell Fit's recipe nutrition calculator can compute it from ingredients. Add the resulting numbers to the schema. Real numbers — not estimates — are what Google's checkers look for.

Ratings and Reviews — Get Real Ones, Don't Fake

aggregateRating with reviewCount is what unlocks the star display in the search snippet. Star ratings dramatically boost click-through. But Google's spam team is very aggressive about fake ratings — sites caught faking get hit with manual actions that wipe out all rich results.

The honest path: install a free recipe ratings plugin (WP Recipe Maker, Tasty Recipes, Cooked Pro all have free tiers) that lets readers rate recipes. Display the ratings on the page. Pull the average and count into your schema. The schema and the visible ratings must match.

If you're new and have no ratings yet, leave aggregateRating out entirely until you have at least 5 real ratings. An empty rating or a fake one is worse than no rating at all.

Adding Recipe Schema in WordPress (With or Without a Plugin)

With a plugin: WP Recipe Maker, Tasty Recipes, and Cooked are the three most popular. They build a recipe card UI for your readers and automatically generate Recipe schema in the background. Pick one based on the look you want — they all handle schema correctly.

Without a plugin: Use the generator to build the JSON-LD. Open your recipe post in the Gutenberg editor, add a Custom HTML block at the top or bottom of the post, paste the script block (with the script tags). Save. The schema is now in your page. The downside vs. a plugin: you have to update the schema manually if you change ingredients or instructions, and you have no visible recipe card UI for readers.

For most food bloggers, a plugin is worth the slight bloat because of the recipe card UX it provides. For one-off recipes or recipes you only have a few of, hand-coding works fine.

Validating Your Recipe Schema

Run every new recipe through Google's Rich Results Test before publishing. Recipe is one of the schema types Google checks most strictly — errors cause your recipe to be excluded from the recipes carousel entirely.

Common errors:

• Missing image (or image too small)
• recipeInstructions as a single string instead of an array of HowToStep objects
• Times in the wrong format (write "PT30M" not "30 minutes")
• aggregateRating without reviewCount
• Hidden ingredients or instructions in the schema that aren't on the page

Once live, monitor the Recipes report in Search Console (Enhancements section). It shows impressions, clicks, and errors. If errors stay unfixed, Google can stop including your site in the recipes carousel.

Frequently Asked Questions

Can I use Recipe schema on a non-food blog?

Recipe schema is specifically for food and drink recipes — it has fields for ingredients, cooking times, and nutrition. For non-food procedural content like crafts, repairs, or DIY projects, use HowTo schema instead.

Do I need a recipe plugin to add Recipe schema in WordPress?

No. You can paste the JSON-LD directly into a post using a Custom HTML block. Plugins like WP Recipe Maker do it automatically and add a recipe card UI, but they're not required for the schema to work.

Why isn't my recipe showing in the Google recipes carousel?

Most common reasons: incomplete schema (missing nutrition, ratings, or video), low domain authority, recently published (give it 2-6 weeks), or duplicate content (your recipe is too similar to a more authoritative version elsewhere). Run the Rich Results Test first to rule out schema errors.

Do I need to include nutrition information?

Technically no, but recipes with nutrition data get significantly higher click-through rates because the calorie count shows in the snippet. For competitive food categories, leaving nutrition out is leaving traffic on the table.

Can recipe schema include video?

Yes, and you should if you have one. Add a VideoObject inside the Recipe schema with the video URL, thumbnail, and description. Recipes with video frequently outrank recipes without in the carousel.

What's the minimum image size for Recipe schema?

Google recommends 1200 pixels on the longest side, in 16:9, 4:3, or 1:1 aspect ratio. Provide multiple sizes if you can — Google picks the best one for the search result format. Smaller images may cause your recipe to be excluded from the carousel even if everything else is correct.