Free recipe schema checker

Check Recipe structured data on a food publisher page

Enter a public hostname to inspect Recipe entities declared in its homepage JSON-LD and see which of Google’s documented required and recommended Recipe properties were observed.

The result separates Google’s documented Recipe rich-result requirements from OpenForBots heuristics such as duplicate-identity and visible-name review. It reports structured-data evidence only; it does not claim rich-result inclusion, ranking, AI Mode inclusion, AI citation, traffic, or revenue.

Public website check Inspectable evidence Clear limitations

Methodology reviewed 2026-08-08

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.

Check robots.txt rules for documented AI crawlers

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 AI crawler rules

Inspect a deployed llms.txt file and its linked resources

Enter a public hostname to inspect its root-level llms.txt response, title, introduction, sections, links, malformed Markdown, duplicate destinations, and insecure URLs.

Inspect llms.txt

Check how clearly your website identifies the business and its entities

Enter a public hostname to compare the visible business name and opening copy with the Organization, WebSite, Person, or SoftwareApplication entities declared in the homepage JSON-LD.

Check structure and identity

Build a starting llms.txt file

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.

Build llms.txt

Build a starting robots.txt from a declared policy goal

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 robots.txt

Build a starting Organization JSON-LD block

Fill in your business name, canonical URL, logo, and official profile links, and this page builds a valid Organization JSON-LD block for you to review, edit, and publish.

Build JSON-LD

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 deployed homepage and parses its JSON-LD for Recipe entities.
2
Compares each Recipe entity against Google’s documented required properties (name, image).
3
Reports recommended-property opportunities such as ingredients, instructions, author, and timing fields.
4
Flags malformed JSON-LD blocks and unconfirmed Schema.org context without suppressing valid entities.
5
Keeps documented provider requirements separate from OpenForBots heuristics.

Example evidence result

A Recipe entity is present but missing recommended timing properties

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 evidence

Observed source: https://example.com/
Recipe entity: found (name, image observed)
Missing required properties: none
Recommended opportunity: add prepTime, cookTime, and totalTime

Recommended next action

Add only accurate, visible recipe facts, then run a fresh check after the deployed page changes.

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 page’s JSON-LD at check time.
Which Google-documented required and recommended Recipe properties were observed or missing.
Whether the declared JSON-LD was syntactically valid and used a recognized Schema.org context.

What remains unknown

Complete Recipe structured data does not guarantee Google rich-result eligibility, ranking, AI Mode inclusion, AI citation, traffic, or revenue.
This focused check inspects the submitted page’s homepage response only; other recipe pages on the same site may differ.
Google documentation is the source of truth for current Recipe rich-result requirements and can change independently of this checker.
A missing Recipe entity on the checked page is not proof that no page on the website has Recipe structured data.

Learn and take action

Related guides and methodology

AI discovery readiness checklist

Place Recipe structured data in the wider access, content, structure, identity, and verification workflow.

Review broader JSON-LD entity and identity signals beyond Recipe-specific properties.

Questions about this check

Does valid Recipe schema guarantee a rich result in Google Search?

No. Google evaluates many factors beyond structured-data validity. This checker confirms what the deployed page declares against documented requirements; it cannot prove rich-result inclusion, ranking, AI Mode inclusion, or citation.

What are the required properties for Recipe rich results?

Per current Google documentation, name and image are required. Ingredients, instructions, author, and timing fields are recommended and materially improve how useful the recipe is to search and AI systems, but their absence does not fail Google’s minimum requirement.

Does this check every recipe on my site?

No. This focused result inspects the submitted page’s homepage response. Use the evidence and methodology to review individual recipe pages separately when their markup may differ.