Recipe Schema Tips and Common Mistakes to Avoid

The most common reason recipe rich results fail is a mismatch between the markup and the page: invented star ratings, times that don't parse as ISO 8601 durations, or ingredients and steps that aren't visible on the page itself. Recipe schema is powerful, but Google is strict — get the details right and your dishes earn eye-catching cards; get them wrong and you risk warnings or a manual action.

Below are the best practices that keep your markup valid and the mistakes worth checking before you hit publish.

Best practices that earn richer cards

• Mark up only what's visible. Every ingredient and instruction in your JSON-LD must also appear in the page's visible content. Structured data is a description of the page, not a substitute for it.
• Use one Recipe block per recipe page. Multiple Recipe objects on a single URL confuse the parser. Split roundup posts carefully or use a single primary recipe per page.
• Break instructions into individual steps. One step per line becomes a separate HowToStep, which unlocks step-by-step display and, on some assistants, guided cooking.
• Provide multiple image aspect ratios. Google prefers high-resolution photos at least 1200px wide in 16x9, 4x3 and 1x1 crops of the finished dish.
• Only add ratings that are real. An aggregateRating should reflect genuine user reviews shown on the page.

Common mistakes and how to fix them

Settings and fields worth double-checking

When you use the generator, pay attention to how durations combine. If you enter a prep time of 20 minutes and a cook time of 90 minutes, the tool produces prepTime of PT20M, cookTime of PT1H30M, and calculates totalTime as PT1H50M automatically — so you never hand-write durations. Leave the calories and rating fields blank until you have real numbers; the generator omits empty fields to keep the output valid rather than shipping placeholders that trigger warnings.

Troubleshooting when the rich result won't appear

If validation passes but no card shows, the usual causes are recrawl lag, a page that doesn't meet Google's content quality bar, or a policy issue elsewhere on the page. Run the live URL through the Rich Results Test, confirm the Recipe item is detected with zero errors, then check the Enhancements report in Search Console for the Recipe status. Rich results are always eligibility, never a guarantee — clean markup plus genuinely useful content is the combination that wins.

Try the Recipe Schema Generator — free and 100% in your browser.

FAQ

Will fake reviews really get my site penalized?

Yes. Marking up ratings that aren't backed by real, on-page user reviews breaks Google's structured data guidelines and can trigger a manual action that removes all your rich results, not just the recipe card.

Why does my totalTime look wrong?

The tool derives totalTime by summing prep and cook time. If it looks off, check that you entered minutes as plain numbers and didn't include text like "mins" in the field.

Can I mark up a recipe that has no photo yet?

You can generate the markup, but recipe rich results depend heavily on a crawlable image. Add a high-resolution photo of the finished dish before expecting a card.

Do I need nutrition data for rich results?

No. Calories are optional. Adding a genuine calorie figure can enrich the card, but leaving it out won't disqualify you.

Related free tools

• JSON-LD Generator — general structured data for any type.
• HowTo Schema Generator — for non-recipe step guides.
• Article Schema Generator — Article markup for posts.
• Video Schema Generator — describe your recipe videos.

Built by ByteVancer

ByteTools is a free product of ByteVancer, a software and web development studio building web apps, SaaS and custom software. If you want SEO baked into a site from the ground up, explore how ByteVancer can help.