← Docs
SEO

Recipe SEO Metadata

Structured metadata patterns that get your recipes surfaced in Google rich results, recipe carousels, and voice search.

JSON-LD Schema

Google parses JSON-LD embedded in <script type="application/ld+json"> blocks. This is the canonical format for recipe rich results.

{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "Sourdough Boule",
  "image": ["https://cdn.example.com/boule.jpg"],
  "author": { "@type": "Person", "name": "Maya Chen" },
  "datePublished": "2026-01-14",
  "description": "Overnight cold-fermented sourdough...",
  "prepTime": "PT30M",
  "cookTime": "PT45M",
  "totalTime": "PT15H",
  "recipeYield": "1 loaf",
  "recipeCategory": "Bread",
  "recipeCuisine": "French",
  "nutrition": {
    "@type": "NutritionInformation",
    "calories": "210 calories",
    "carbohydrateContent": "42 g"
  },
  "recipeIngredient": [
    "500g bread flour",
    "350g water",
    "100g active starter",
    "10g salt"
  ],
  "recipeInstructions": [
    {
      "@type": "HowToStep",
      "text": "Autolyse flour and water for 1 hour."
    }
  ]
}

Meta Tags

Standard Open Graph and Twitter Card tags ensure rich previews on social platforms.

<meta property="og:title" content="Sourdough Boule" />
<meta property="og:description" content="Overnight cold-fermented..." />
<meta property="og:image" content="https://cdn.example.com/boule.jpg" />
<meta property="og:type" content="article" />
<meta name="twitter:card" content="summary_large_image" />

Validation

Test your markup with the Google Rich Results Test and Schema.org Validator. Both catch missing required fields before they cost you rich-result eligibility.