Free recipe schema checker
Check Recipe structured data on a specific recipe page
Enter the actual public recipe page URL to inspect the Recipe JSON-LD on that page, including Google-required name and image plus selected recommended fields.
The result separates Google’s documented Recipe rich-result requirements from OpenForBots heuristics. It also applies Google’s conditional recipeYield requirement when per-serving nutrition calories are declared. Recommended-field coverage is intentionally focused rather than a replacement for Google’s Rich Results Test.
Observed website result
Check result
More free checks
Try the other free AI discovery checks
Each check looks at a different layer of AI discovery readiness. Run them together for a fuller picture, or open the complete audit for all of it at once.
Enter a public hostname to test whether its deployed robots.txt policy allows, blocks, or has no matching restriction for documented AI crawler tokens at the root path.
Check the live /llms.txt file on a public website, or paste a draft to validate it before deployment. Both modes use the same rules for title, introduction, sections, links, malformed Markdown, duplicate destinations, and insecure URLs.
Compare visible homepage identity with structured entities, graph identifiers, sameAs identity references, and trust signals.
Fill in a title, short context, and the resource links you want to list, and this page builds a valid llms.txt file for you to review, edit, and publish.
Choose a declared policy goal and this page builds robots.txt groups for the documented AI crawler tokens that goal has an explicit preference for, which you can review, edit, and publish.
Build Organization JSON-LD with a reusable #organization @id and optional identity-reference URLs.
Paste a prompt and the source an AI answer cited. See which public evidence differs from your site, what is worth testing, and what no external audit can prove.
Compare the business name, phone, email, address, and official profiles stated on your homepage, About page, Contact page, and JSON-LD, and see where any value differs.
Compare the new version of a site or page with the current live one under the same audit rules, and see regressions in crawler access, content, and identity before you launch.
What this check looks for
See the public evidence behind the result
OpenForBots examines the relevant public page or resource, shows what it found, and explains what to review next.
- 1
Retrieves the exact same-site HTTPS recipe page you submit and parses its server-delivered JSON-LD for Recipe entities.
- 2
Checks Google’s documented required Recipe properties: name and image.
- 3
Requires recipeYield when the Recipe declares per-serving nutrition calories, matching Google’s conditional guidance.
- 4
Surfaces a focused set of recommended opportunities including ingredients, instructions, author, publication date, timing, and yield.
- 5
Flags malformed JSON-LD and unconfirmed Schema.org context while preserving valid entities from other blocks.
Example evidence result
A recipe page has the required fields but could expose more useful details
The live result uses the deployed page or resource and exact check time. This example shows the evidence structure, not a claim about a real domain.
- Observed source: https://example.com/recipes/apple-pie
- Recipe entity: found (name and image observed)
- Missing required properties: none
- Selected recommendation: add prepTime, cookTime, and recipeYield when accurate
Add only accurate recipe facts that match the visible page, validate with Google’s Rich Results Test, then re-run this exact page after deployment.
Understand the result
What the check confirms—and what it cannot tell you
What it can confirm
- Whether a Recipe entity was declared in the checked recipe page’s server-delivered JSON-LD at check time.
- Whether the Google-required Recipe properties covered by this check were present, including the conditional recipeYield rule when applicable.
- Which selected recommended fields were observed or missing and whether the JSON-LD was syntactically parseable.
What remains unknown
- This focused checker does not reproduce every Google recommended property or replace Google’s Rich Results Test.
- Complete Recipe structured data does not guarantee Google rich-result eligibility, ranking, AI Mode inclusion, AI citation, traffic, or revenue.
- Google documentation is the source of truth for current Recipe rich-result requirements and can change independently of this checker.
- The result covers the submitted recipe page only; other recipe URLs on the same site may differ.
Learn and take action
Related guides and methodology
Place Recipe structured data in the wider access, content, structure, identity, and verification workflow.
Read more AI Structure and Identity CheckerReview broader JSON-LD entity and identity signals beyond Recipe-specific properties.
Read more How the audit worksReview evidence labels, heuristics, structured-data limits, and retrieval boundaries.
Read moreCommon questions
Questions about this check
Does valid Recipe schema guarantee a rich result in Google Search?
No. Google evaluates eligibility and presentation beyond structured-data syntax. This checker confirms selected page-level evidence against documented requirements; it cannot guarantee rich-result inclusion, ranking, AI Mode inclusion, or citation.
What are the required properties for Recipe rich results?
Current Google documentation requires name and image. If you declare per-serving nutritional information such as nutrition.calories, recipeYield is also required. Google documents many additional recommended properties; this focused checker surfaces a selected practical subset rather than pretending to replace the Rich Results Test.
Does this check every recipe on my site?
No. It checks the exact public recipe page URL you submit. Different recipe pages can have different markup, so test representative or important pages individually.