Free Recipe Schema Generator

Why many recipe pages underperform

How SwiftSchema helps

How it works

What is Recipe structured data?

Recipe structured data describes ingredients, step‑by‑step instructions, and timing details so search engines can better understand and present your recipe. Accurate markup helps your pages qualify for recipe‑rich experiences when eligible.

Essential properties to include

• name and description matching the on-page recipe.
• image[] with at least one high-quality photo (≥1200px width).
• recipeIngredient: clear, measured ingredients as strings.
• recipeInstructions: ordered HowToStep items with concise text.
• prepTime, cookTime, totalTime: ISO 8601 durations.
• recipeYield: servings or output quantity.
• recipeCategory and recipeCuisine: classification context.
• Optional: nutrition (calories and macros), video, aggregateRating, keywords.

Preparing recipe content before generating schema

1. Write ingredients with exact units and prep notes (e.g., “1 cup onions, diced”).
2. Create clear steps; keep one action per HowToStep and note temperatures/timings.
3. Capture prep/cook/total times and yields; convert them to ISO 8601.
4. Gather hero and step images; ensure alt text is descriptive.
5. Collect nutrition facts and author attribution; ensure they match on-page copy.
6. If you have video, confirm stable URLs, duration, and thumbnails.

Additional modeling tips

• Use HowToSection when grouping steps (e.g., Dough, Filling, Assembly).
• Add suitableForDiet if your recipe fits a dietary pattern (e.g., VeganDiet).
• Include supply/tool only when they add clarity; keep lists concise.
• If you support variations (gluten-free swap), mention them in instructions or notes.

On-page parity checklist

• Title, description, and hero image on-page match name, description, and image.
• Ingredient list and steps match recipeIngredient and recipeInstructions order.
• Times and yields shown on-page match prepTime/cookTime/totalTime and recipeYield.
• Ratings/reviews displayed match aggregateRating values and counts.
• Nutrition values on-page align with nutrition entries; units are clear.
• Video player (if present) matches video.contentUrl/thumbnailUrl.

Common Errors & Fixes

• Images too small: aim for ≥1200px width; use WebP/JPEG.
• Unstructured instructions: use HowToStep with text for each step.
• Missing durations: use ISO 8601 times (e.g., PT15M, PT1H).
• Missing yield: include servings or output quantity.
• Hidden ratings: only include AggregateRating if ratings appear on the page.
• Mixed units: keep ingredient units consistent; avoid vague quantities.

Maintenance and QA

• Revalidate after redesigns, image swaps, or ingredient changes.
• Keep datePublished/dateModified current when updating recipes.
• Run image checks to ensure all referenced assets are accessible to crawlers.
• Audit quarterly for times/ingredients consistency and remove stale ratings if reviews change.

Images and video best practices

• Provide multiple image URLs (hero, plated dish, process shots) with alt text.
• If you include video, add VideoObject with contentUrl, thumbnailUrl, duration, and uploadDate; keep the player visible on the page.
• Ensure CDNs don’t block crawlers; test assets with URL Inspection.

Dietary, allergy, and variation notes

• Add dietary labels (vegan, gluten-free) in copy and consider suitableForDiet when accurate.
• Include allergy callouts (contains nuts/soy) and safe substitutions.
• Provide variation notes (spicy/low-sodium options) and keep them near the relevant steps.

Testing and governance

• Create a pre-publish checklist: validate ISO times, ingredient counts, and that every step is structured.
• When editors change ingredients or steps, update schema, nutrition, and times together.
• Centralize recipe data in your CMS so schema, UI, and feeds stay in sync.
• Keep sourcing notes (local, organic) and storage/leftover guidance in copy to increase usefulness.
• Add author bios or test-kitchen notes to reinforce expertise; align author data with Person schema on the page.
• Link to related recipes (sides, toppings) and build collections so each page has substantial internal context.
• Include equipment notes (pan size, thermometer use) and substitutions for common dietary needs to avoid thin, generic steps.
• For multi-language sites, add inLanguage and ensure translations keep measurements and temperatures accurate (convert units when needed).
• Provide serving suggestions and make-ahead/freezer guidance in copy; align with any timing notes in schema.
• Add allergy disclaimers or cross-contact notes when relevant to increase trust and utility.
• Offer troubleshooting tips (too dry, not browned) to improve usefulness and on-page depth.
• Keep lastReviewed updated after each recipe retest or photo refresh.