On this page
Your recipes are scattered across bookmarks, screenshots, and Notion pages. Cooklang showed that publishing recipes as a static site works. Wire takes it further: structured metadata, search, quality enforcement, and an AI pipeline that enriches recipes with sourced technique explanations, ingredient substitutions, and cultural context. The same content pipeline powers a niche blog or a digital garden. Recipes are just content with different conventions. For more patterns, explore all Wire use cases.
The Pain Point
Recipe blogs are the most hated genre on the internet. Ten paragraphs of life story before the ingredients list. Ad-bloated WordPress themes that take 8 seconds to load. No search that actually works. And if you want to self-host your family recipe collection, the tools (Nyum, Cooklang) are minimal: no quality gates, no enrichment, no SEO structure.
The economics are getting worse. Google's AI Mode now generates full competing recipes on search results pages, blending ingredients and steps from multiple sources into what recipe blogger Adam Gallagher called "Frankenstein recipes". Traffic losses across food blogging range from 30% to 80%, and organic CTR on AI Overview queries fell 61%, dropping from 1.76% to 0.61% (Seer Interactive, September 2025). Matt Rodbard, founder of Taste, called it "an extinction event in many ways" for sites dependent on advertising revenue. Eb Gargano illustrated the quality gap: AI once suggested baking a 6-inch Christmas cake for 3 to 4 hours. "You'd end up with charcoal," she told Bloomberg.
Google Is Course-Correcting. Structured Data Wins.
On March 4, 2026, Google updated AI Mode to add tappable dish cards that link back to recipe creator sites. Google VP Robby Stein confirmed cook time metadata will follow, acknowledging "there's more work to be done." The update responds to 18 months of backlash from recipe creators who watched AI-generated summaries replace their content without attribution. Google had already killed Recipe Quick View in July 2025 after Bloomberg confirmed insufficient compensation to creators.
The fix is partial. Discovery queries ("easy dinners for two") now surface creator links through the new card format. But branded queries still show AI-generated competing recipes, and the new tappable cards may not be visually intuitive as clickable elements. Recipe sites that enforce complete Schema.org Recipe markup, author credentials, and cook time metadata gain the signals Google now prioritizes for AI Mode visibility. Sites that cannot guarantee metadata completeness get filtered out of the new card format entirely.
This is where Wire's build gates matter. A recipe site that validates frontmatter at build time, refuses pages without titles and descriptions, and enforces structured metadata ships content that meets Google's new requirements by default. No manual checklist. No "I forgot the cook time."
How Wire Fits
Wire treats recipes as content pages with enforced structure. Frontmatter metadata (title, description, created date, tags for cuisine, diet, and course) is validated at build time. No recipe publishes without it.
The enrich command adds depth that distinguishes your recipes from AI slop. Wire's enrichment pipeline researches technique explanations, sourced nutrition context, and ingredient history from the web. A pasta recipe gains a paragraph on why you salt the water, cited from a culinary source. This is the kind of first-person, tested content that nearly half of 3,000 surveyed US adults trust more than AI-generated alternatives (Raptive survey).
Search works out of the box. search_index.json powers instant search across your entire collection. "Recipes with tahini" returns results without scrolling through category pages. The crosslink command connects related recipes automatically; your hummus recipe links to your falafel recipe without manual maintenance.
Build gates catch the rest. No broken links to ingredient substitution pages. No orphan recipes unreachable from the index. No pages missing the metadata that Google's AI Mode now requires for visibility.
What to Customize
wire.yml
nav:
- index.md
- Cuisines:
- Overview: cuisines/index.md
- Techniques:
- Overview: techniques/index.md
Prompt Overrides
Write a _styleguide.md for recipe writing:
- Ingredients as a clean list (this is one place where lists beat prose)
- Technique explanations in prose (why you fold instead of stir)
- Sourced tips from culinary authorities (Serious Eats, ATK, Kenji Lopez-Alt)
- No life stories. No "I remember when grandma made this on a rainy Tuesday."
Components
Use :::cards for recipe grids on category pages. Use :::tabs for variations (vegan, gluten-free). Use :::stats for nutrition highlights. Use :::recent 12 on the homepage for latest additions.
Beyond Google: Why Multi-Channel Matters
58.5% of US Google searches now end without a click to any external website. AI Mode does send traffic on 69% of transactional queries, suggesting recipe sites with strong transactional intent signals may recover some clicks. But recipe sites treating Google as their sole distribution channel face existential risk. Pinch of Yum's Bjork Ostrom called this the "most existential point for us as business owners". Successful recipe publishers are diversifying: Sip and Feast built a YouTube strategy, Taste pivoted to food journalism and podcasts.
Meanwhile, AI slop is flooding adjacent platforms. Multiple bloggers documented AI-run sites cloning entire recipe catalogs, rewriting instructions, tweaking photos, and generating synthetic family images. These clones spread across Pinterest, Facebook, and Etsy, eroding trust in recipe content everywhere.
Wire's content pipeline produces the structured, high-quality base content that performs across channels. The RSS feed syndicates new recipes. The search index serves your own site search. llms.txt makes your recipes available to AI agents. Search is one distribution path, not the only one. For recipe collections serving multiple languages, the multi-language hub pattern handles translation and per-language sitemaps.
Scope
Wire generates a search index, RSS feed, sitemap, JSON-LD Article schema (extend to Recipe schema with a template override), responsive layout, reading progress, and print-friendly HTML. It does not handle meal planning, shopping list generation, or recipe scaling. Those are JavaScript features you add on top of the static output. Wire does not parse Cooklang syntax natively. Write recipes in standard markdown.
To get started, create wire.yml with cuisine or course categories, write your first recipe with structured ingredients and method, then run python -m wire.chief enrich to add sourced technique context. Run python -m wire.chief crosslink to connect related recipes, and python -m wire.build --serve to cook from localhost. See all Wire use cases for more patterns.