Writing Recipes for Clarity, Consistency & Structured Parsing
Our goal is simple: help readers cook successfully - and help our system understand your recipes accurately.
On this page
Overview
Clear structure improves:
- Reader comprehension
- Recipe scaling accuracy
- Ingredient extraction
- Metadata reliability
- Search relevance
- Guided cooking features
Below are formatting and structural guidelines that make a measurable difference.
Ingredient List Best Practices
1. List Ingredients in Order of Use
Ingredients should appear in the order they are used in the instructions. If several are added at the same time, list them:
- In descending order by quantity
Example: 1/2 cup sugar, 1 tablespoon baking powder, 1 teaspoon ground cinnamon, 1/4 teaspoon allspice - If quantities are identical, list alphabetically
Example: 1/4 teaspoon dried basil, 1/4 teaspoon dried dill, 1/4 teaspoon dried rosemary
2. Use Numerals and Fractions
Use numerals rather than spelling out numbers. Use fractions instead of decimals.
Correct: 1 cup, 1/4 cup, 1/2 teaspoon
Avoid: One cup, 0.25 cup
3. Use Total Quantities (Avoid Repeating Measurements in Steps)
If an ingredient is used more than once, list the total amount once and mark it as "divided."
Example: 3/4 teaspoon ground cinnamon, divided
Then in the instructions:
Preferred for scaling:
- "Add half of the cinnamon…"
- "Use the remaining cinnamon…"
Avoid restating fixed quantities in individual steps (e.g., "add 1/4 teaspoon…"). When a recipe is scaled, fixed quantities in instructions can become incorrect.
4. Describe Ingredients Precisely
Terms to the left of the ingredient describe how it is purchased or measured. Terms to the right describe preparation after measuring.
Examples:
- 2 cups cooked basmati rice, cooled (Measure cooked rice, then cool it.)
- 1 cup walnuts, chopped (Measure walnuts, then chop.)
- 1 cup chopped walnuts (Measure after chopping - different volume.)
Be intentional - wording changes yield different results.
5. Specify Amounts by Weight When Referencing Packages
Avoid: 2 (14-ounce) cans corn
Instead: 28 ounces canned corn
This prevents ambiguity and scales correctly.
If needed, use parentheses for package size: 1 (8-ounce) package cream cheese
6. Avoid Brand Names
Use generic ingredient names unless the brand is essential to outcome.
Correct: 1 cup semi-sweet chocolate chips
Avoid: 1 cup Tollhouse chocolate chips
7. Break Out Multi-Component Recipes
For recipes with distinct elements, separate clearly:
For the Crust For the Filling For the Sauce
Do this in both:
- Ingredient list
- Instructions
This improves readability and structured parsing.
Writing Clear, Scalable Instructions
1. One Action per Step
Separate each major action into its own paragraph. This improves guided cooking, step-by-step display, and clarity.
2. Include Heat Levels and Timing
Be specific:
- "Simmer over low heat"
- "Bake 18–22 minutes, until light golden brown"
- "Sear 1 minute per side"
Use numerals for timers: Bake for 1 hr, Cook 20 minutes
3. Indicate Cookware Size When Relevant
Examples:
- "In a large mixing bowl…"
- "Heat a 10-inch skillet…"
4. Avoid Restating Fixed Quantities in Instructions
As noted above, avoid: "Add 1/2 teaspoon salt"
Prefer: "Add half of the salt"
This ensures instructions remain correct when scaled.
5. Finish with Serving and Storage Notes
Conclude with:
- Serving temperature
- Garnish suggestions
- Storage guidance
Example: "Store in an airtight container at room temperature for 3–4 days."
Metadata & Structured Data
Accurate metadata improves discoverability and prevents mismatched search results.
Please ensure:
- Correct prep time, cook time, and total time
- Accurate serving size and yield
- Complete nutrition information (if provided)
- High-quality primary image
- Step-by-step images included in structured data if available
- FAQs included in schema when present
Inaccurate metadata can lead to incorrect placement in search results.
Quality Standards
A few important notes:
- Recipes should be original and tested.
- Quantities and yields should be accurate.
- Instructions should be verified by someone following them exactly as written.
Readers are significantly more likely to return to sites where they cook successfully the first time.
We reserve the right to review and discontinue service for content that is clearly auto-generated or not human-tested. Our goal is to promote high-quality, trustworthy recipes.
Why This Matters
When recipes are written with structural clarity:
- Readers succeed more often
- Scaling works correctly
- Ingredient intelligence improves
- Guided cooking is accurate
- Search results are more relevant
- Engagement and return visits increase
Clear structure benefits everyone.