Recipe schema
Free Recipe schema generator
21 October 2026 · CiteScore Team · 7 min read
Free AI Answer Snapshot
When customers ask ChatGPT or Perplexity for your trade in your city, who do they name?
We email the Fix Pack within a few business days after payment, once we have the business name, city, service, and public site URL. The re-check in the pack is the same prompts, run again 14 days later. Full refund within 14 days of delivery if the Fix Pack is not useful. Refund policy.
Opens Payhip in a new tab. The shop name on that page is DeskOps Templates (opens in a new tab). Payhip lists a text file with the order. We email the Fix Pack. What happens after you buy.
The free AI Answer Snapshot asks logged-out ChatGPT and Perplexity and records the answer. The Fix Pack is $49. This generator copies facts the page already shows. It does not make an assistant name the business.
AI answers vary run to run. This is a snapshot, not a ranking, and not a promise that any assistant will name the business.
See an example snapshot · See what's in the Fix Pack. Example pages use illustrative numbers. Not a customer result.
Prepared by the CiteScore Team.
Request a free AI Answer Snapshot
Same request as the free snapshot page. AI answers vary run to run. This is a snapshot, not a ranking, and not a promise that any assistant will name the business.
Prepared by the CiteScore Team.
Free, no-signup Recipe JSON-LD generator. Add the dish name, description, image, author, prep, cook, and total time, yield, ingredients, steps, calories, and an optional rating already on the page. Copy the script. Nothing is uploaded.
Why the recipe is labeled
A recipe page says what the dish is, who wrote it, how long it takes, what goes in it, and how to cook it. An answer engine that quotes that page still has to decide which string is the dish, which line is an ingredient, and which number is the calories. schema.org Recipe is that decision written down. It defines name, image, description, author, prepTime, cookTime, totalTime, recipeYield, recipeIngredient, recipeInstructions, nutrition, and aggregateRating. A parser can read those labels without guessing which line is the yield. The script does not create a citation, and it does not rank the page. The same point, for Comet’s browser assistant, is on how to get cited by Perplexity Comet. DuckDuckGo’s Search Assist answers are on how to get cited by DuckDuckGo.
Google’s recipe documentation, read on 21 October 2026, says the markup helps Google understand the recipe and present it in Google Search and Google Images. Eligibility is not a placement. The required properties on that page are image and name. The image has to be a crawlable, indexable picture of the completed dish, in a format Google Images supports. For best results, that page recommends several high-resolution images, at least 50,000 pixels when width is multiplied by height, at 16:9, 4:3, and 1:1. This form cannot measure the file. It writes the URLs you enter. One URL is a string. More than one is an array. The same page says the image property does not choose the image used in an ordinary text result. A restaurant menu is a different page. The location and the menu URL are on AI search visibility for restaurants. Use this script on a page that is a recipe, with ingredients and steps. Do not mark the whole menu up as one Recipe.
The recommended properties are the ones a rich result can show when they are true. author is a Person or an Organization. It is included only when you enter a name. A URL without a name is omitted, so the script does not invent a byline. prepTime, cookTime, and totalTime are ISO 8601 durations. Forty-five minutes is PT45M. One day and two hours is P1DT2H. Google’s page says to use cookTime together with prepTime, and to use totalTime or that pair. The example on that page includes all three. This form writes prep and cook only as a pair, and writes totalTime whenever it is valid on its own. It does not add the two clocks together. Resting time that the page states belongs in the total you type.
recipeYield is the amount the recipe makes. Google’s page says a number of servings can be the number alone, and that another unit, such as a count of cookies, can be added. The text you type is kept, so “4 servings” is not rewritten as a bare integer. nutrition.calories is the calories in each serving. That page says a calorie count requires recipeYield. A number you type as 120 is written as 120 calories, which is the shape of Google’s example. 120 kcal is kept when you type the unit. The calories are left out until the yield is present.
recipeIngredient is one line per ingredient, the text required to make the dish. Google’s page says not to add a definition of the ingredient. recipeInstructions is the steps. That page recommends HowToStep, and says a single block of text is harder for Google to split. Each step in this form is a HowToStep with text, and name when you enter a short label such as “Simmer”. Google’s page says to leave “Step 1”, “Directions”, and “Watch the video” out of the instruction text. This form does not write HowToSection. A recipe whose page groups steps under headings would need that grouping added by hand. One flat list is the piece this form can honestly carry.
aggregateRating is optional. Google’s recipe page says it follows the review snippet guidelines. Google’s own recipe example uses ratingValue and ratingCount. This form writes those two, and bestRating when you enter it. An empty best rating uses 5 as the ceiling, which is the scale Google assumes when the property is absent. A value above that ceiling is left out. The same page says a single review needs a real person or organization as the reviewer. This form does not write a Review. It writes the average only. A rating the page does not show should stay blank.
Google’s content guidelines limit the type. Use Recipe for a particular dish. “Facial scrub” and “party ideas” are the examples that page calls invalid. A procedure that is not a dish uses the HowTo schema generator. A gallery needs ItemList on a summary page that lists the recipes, with a unique URL for each one. This form writes one Recipe. It does not write the carousel. This form also leaves out datePublished, keywords, recipeCategory, recipeCuisine, and video. Those properties are on Google’s table. Add them by hand only when the page shows them. The publisher on the homepage uses the Organization schema generator.
Google’s structured data policies, read on 21 October 2026, say not to mark up content that is not visible to readers of the page, and that the structured data must be a true representation of the page content. The troubleshooting note on the recipe page says Google does not guarantee that a feature which uses structured data will show. The copy block is one script tag. Paste it into the HTML the server sends for that recipe. Answer engines often skip text that only appears after JavaScript runs. The free check lists the JSON-LD @type values on the homepage. A recipe URL at another path is outside that fetch. The GEO audit looks for markup that matches the copy. The longer note on which facts to repeat is the schema guide.
How to install it
- Copy the script.
- Paste it into the HTML the server sends for that recipe page, in the head or the body.
- Confirm the same name, image, ingredients, steps, time, yield, calories, and rating are visible on that page.
- Confirm a gallery of recipes, if you publish one, is a separate ItemList and not stuffed into this name.
What to leave out
- A time, a calorie count, or a rating the page does not show. Leave the rating blank.
- An author the page does not name. Leave the field blank.
- prepTime without cookTime, or cookTime without prepTime. Use totalTime when that is the only clock the page states.
- Calories without a yield. Google’s page says the yield has to be there.
- A facial scrub, a party plan, or a procedure that is not a dish. Use the HowTo generator for a procedure.
- “Step 1” or “Directions” inside the instruction text. Put the instruction only.
- The same Recipe block on every URL of the site.
Questions about Recipe schema
Does Recipe schema guarantee a Google rich result or an AI citation?
No. Google’s recipe documentation, read on 21 October 2026, says recipe structured data can make a page eligible for recipe results in Google Search and Google Images. A host carousel also needs ItemList markup on a summary page. Google does not guarantee that any structured-data feature will show. This generator writes one Recipe, not that list. The script does not make ChatGPT, Perplexity, Claude, Gemini, Copilot, Grok, Meta AI, DeepSeek, Mistral, Brave Search, You.com, DuckDuckGo, or Google AI Overviews cite the page. A time, a calorie count, or a rating that exists only in the script describes a dish the page does not show.
Which fields does this form require?
schema.org does not list a required property for Recipe. Google’s recipe table lists image and name as required for the rich result. Recommended properties on that page include description, author, prepTime, cookTime, totalTime, recipeYield, recipeIngredient, recipeInstructions, nutrition.calories, and aggregateRating. This generator writes a script once the dish name is present. The image, the description, the author, the times, the yield, the ingredients, the steps, the calories, and the rating are included only when they are valid. prepTime and cookTime are written only as a pair, because Google’s page says to use cookTime together with prepTime. nutrition.calories is written only when the yield is also present, because that page says a calorie count requires a yield. aggregateRating is written only when both a rating value and a rating count are valid.
When should this be Recipe, and when should it be HowTo?
Recipe is for preparing a particular dish. Google’s content guidelines say a facial scrub or party ideas are not valid names for a dish. A procedure that is not a dish uses the HowTo schema generator. Google stopped showing How-to rich results in September 2023. A recipe page still uses Recipe. A gallery of recipes needs a separate ItemList on the summary page. This form does not write that list.
Where should the script go?
On the page for that one dish, in the HTML the server sends, where a person can already see the name, the image, the ingredients, the steps, and any time, yield, calories, or rating. Google’s structured data policies say not to mark up content that is not visible to readers of the page. The script is built in the browser. Nothing is sent to CiteScore.
Get a free AI Answer Snapshot · Fix Pack, $49 · Run the free check
A separate GEO audit PDF covers one public URL.