Recipe schema and SEO

01

Use the editor as the source

The public recipe and its structured data should describe the same dish. Update the recipe fields instead of injecting separate JSON-LD by hand.

• Title, description, image and author identify the recipe.
• Yield and time fields describe the result and preparation effort.
• Ingredient and instruction fields provide the cookable method.
• Nutrition and rating data must reflect information visibly available on the page.

02

Avoid duplicate Recipe markup

Run only one system that emits Recipe structured data for the page. If a theme or SEO plugin also generates a Recipe object, disable that output or configure the tools so their responsibilities do not overlap.

03

Validate after publishing

1. 1

   Open the public, canonical recipe URL in a private browser window.

2. 2

   Confirm that the visible title, image, ingredients, instructions and times are complete.

3. 3

   Test the URL with Google's Rich Results Test and review the detected Recipe object.

4. 4

   Resolve errors first; review warnings based on whether the information genuinely applies.

5. 5

   Retest after theme, cache or SEO-plugin changes.

04

Keep editorial SEO natural

Write for the person choosing and cooking the recipe. Use a descriptive title, a useful introduction and internal links that help navigation. Structured data supports understanding; it does not replace a strong public page.