Writing recipes for clarity, consistency & structured parsing

Overview

Consistently written recipes are easier for readers to follow, and easier for Allspice to scale, parse into ingredients, match in search, and turn into guided cooking steps.

The guidelines below cover ingredient lists, instructions, and metadata. Every recipe post also needs schema.org Recipe JSON-LD; see Metadata & structured data.

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.)

The wording changes how much the reader measures, so choose it deliberately.

5. Specify amounts by weight when referencing packages

Avoid: 2 (14-ounce) cans corn
Instead: 28 ounces canned corn

A total weight is unambiguous and scales correctly.

Exception: when an ingredient is only sold in one package size and you use the whole package, a count with the size in parentheses is fine: 1 (8-ounce) package cream cheese

6. Avoid brand names

Use generic ingredient names unless the brand is essential to the outcome.

Correct: 1 cup semi-sweet chocolate chips
Avoid: 1 cup [brand name] chocolate chips

7. Break out multi-component recipes

For recipes with distinct elements, give each one its own heading:

For the Crust    For the Filling    For the Sauce

Use the same headings in both the ingredient list and the instructions. Readers can follow each component, and Allspice can keep the groups separate when it parses the recipe.

Writing clear, scalable instructions

1. One action per step

Put each major action in its own step. Guided cooking shows one step at a time, so combined actions make steps harder to follow.

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 hour, 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"

That way the instructions stay correct when the recipe is 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

Allspice reads your recipe metadata for search, recipe details, and scaling, so keep it accurate:

• Every recipe post includes schema.org Recipe JSON-LD (required: pages without it are not treated as recipes)
• 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

Quality standards

• Recipes should be original and tested.
• Quantities and yields should be accurate.
• Instructions should be verified by someone following them exactly as written.

Why this matters

Readers who cook a recipe successfully are more likely to come back. Clear structure also keeps scaling, grocery lists, and guided cooking accurate, and makes your recipes easier to find in search. For how Allspice reads and cleans up recipe data, see Recipe parsing.