Vibe Code a Food Blog
Free vibe coding prompt to build a WordPress recipe blog. WP Recipe Maker, recipe index, nutrition info, structured Recipe schema, and email funnel. Full food blog architecture.
Plan and produce a complete WordPress recipe / food blog architecture
optimized for Mediavine eligibility, recipe schema, and email-driven
retention. Output should be production-ready.
═══════════════════════════════════════════════════════════════
BUSINESS DETAILS
═══════════════════════════════════════════════════════════════
- Blog name: [BLOG NAME]
- Niche: [NICHE, e.g., one-pot weeknight dinners / Mediterranean /
plant-based baking / Asian noodle bowls]
- Author: [NAME], credential or background (chef / mom of 4 / nutritionist)
- Cadence: 2-3 recipes per week
- Monetization: display ads (Mediavine/Raptive) + affiliate links +
cookbook PDF + sponsored posts
- Goal: 100K pageviews/month for ad eligibility
═══════════════════════════════════════════════════════════════
BRAND
═══════════════════════════════════════════════════════════════
- Brand colors: warm cream (#f6efe1) + deep brown (#3a2a1f) + terracotta
accent (#c87a4c) + sage (#8a9a6f). Override if user provides; pass AA
contrast.
- Type: high-contrast display serif for headings (Lora, Fraunces,
Recoleta) + Inter for body. NO script fonts.
═══════════════════════════════════════════════════════════════
PLUGIN STACK (WP-CLI)
═══════════════════════════════════════════════════════════════
wp plugin install --activate
wp-recipe-maker
wordpress-seo
wp-rocket
shortpixel-image-optimiser
pretty-link
official-mailerlite-sign-up-forms
grow-social-pro
- Recipe management: WP Recipe Maker Premium (auto recipe schema, jump-to,
ratings, nutrition, print, video), alternative: Tasty Recipes
- Affiliate cloaking: Pretty Links
- Email: MailerLite or Flodesk (good for food blogs)
- Social: Grow Social for Pinterest pin generator
═══════════════════════════════════════════════════════════════
DATA MODEL
═══════════════════════════════════════════════════════════════
- Posts are recipes (WP Recipe Maker integrates with post type)
- Optional CPT: `cooking_method` if blog has heavy technique tutorials
- Taxonomies:
- `course` (Breakfast / Lunch / Dinner / Dessert / Snack / Side)
- `cuisine` (Italian / Mexican / Asian / etc.)
- `diet` (Gluten-free / Vegan / Low-carb / Dairy-free / Whole30)
- `season` (Spring / Summer / Fall / Winter)
- `method` (One-pot / Sheet-pan / Slow-cooker / Instant Pot)
═══════════════════════════════════════════════════════════════
SITE MAP
═══════════════════════════════════════════════════════════════
1. Home
2. Recipes index (filterable by course, cuisine, diet, season, method)
3. Recipe single
4. About (author + photo + story)
5. Cookbook (PDF download or print sales)
6. Resources / Shop (affiliate gear hub)
7. Start Here (new reader onboarding)
8. Work With Me (sponsored post rate card)
9. Newsletter (with 30-day meal plan lead magnet)
10. Contact
11. Privacy + Affiliate Disclosure + Recipe Copyright
═══════════════════════════════════════════════════════════════
HOME PAGE, BLOCK MARKUP
═══════════════════════════════════════════════════════════════
1. Hero recipe (full-bleed, "This week's favorite") with rating, prep
time, "Jump to recipe →" CTA
2. Browse by category cards (Breakfast / Lunch / Dinner / Dessert /
Snack, 5 cards with food photo overlays)
3. Most Popular Recipes (manually curated, 6-grid)
4. About snippet ("Hi, I'm [NAME]" + photo + 2-line bio + "More about
me →")
5. Email capture inline ("Get the free 30-day meal plan")
6. Latest Posts (8 cards with rating + prep time visible)
7. Browse by Cuisine (4-grid of cuisines)
8. Pinterest-style recent recipes grid (12 cards)
9. Footer with affiliate disclosure (visible from every page) + recipe
copyright note
═══════════════════════════════════════════════════════════════
RECIPE PAGE TEMPLATE (most important UX)
═══════════════════════════════════════════════════════════════
- Hero image (1200x900, ratio 4:3), must be photogenic, well-lit
- Recipe meta row: prep time / cook time / servings / difficulty / rating
- "Jump to recipe" button (sticky on mobile), critical UX
- Story (the writer's intro, important for SEO AND for ad inventory):
• 3-4 paragraphs minimum
• Personal context (when I make this, why I love it)
• Sensory description
• Tips and substitutions
- Pin-It image (Pinterest format 1000x1500) embedded or generatable via
Grow Social
- Ingredients section:
• Bulleted list with metric/US toggle (WP Recipe Maker handles this)
• Each ingredient as proper measurement + name (no decoration)
- Step-by-step instructions:
• Numbered steps with optional photo per step
• Each step short and active
- Recipe card (WP Recipe Maker block), printable, clean
- Notes / FAQ section (3-5 common questions: storage, freezing,
substitutions)
- Nutrition info (per WP Recipe Maker; clearly labeled "Estimated")
- "If you loved this, try", 4 related recipes
- Comments + 5-star rating system (WP Recipe Maker)
- "Tried it? Tag me on Instagram @[HANDLE]" + Pinterest "Save" CTA
═══════════════════════════════════════════════════════════════
RECIPE INDEX / SEARCH
═══════════════════════════════════════════════════════════════
- Sticky filter bar at top: Course / Cuisine / Diet / Season / Method
- Search input with autocomplete (recipe titles)
- Card grid (auto-fit, minmax 280px) with rating + prep time visible
- Infinite scroll OR load-more button (load-more preferred for SEO)
- "Trending this week" featured row at top
═══════════════════════════════════════════════════════════════
EMAIL & LEAD MAGNET
═══════════════════════════════════════════════════════════════
- Lead magnet: 30-day meal plan PDF (gated by email)
- Welcome series (5 emails):
Day 0: Deliver meal plan + "Welcome to my kitchen"
Day 2: My top 5 most-loved recipes
Day 5: Pantry essentials I always have on hand
Day 9: "How I plan a week of dinners" (story + downloadable template)
Day 14: "What kind of cook are you?", segmentation poll
- Weekly newsletter (Friday): this week's recipes + meal plan suggestions
+ reader wins
═══════════════════════════════════════════════════════════════
SEO STRATEGY
═══════════════════════════════════════════════════════════════
- Recipe schema (auto via WP Recipe Maker): name, image, recipeIngredient,
recipeInstructions, totalTime, recipeYield, nutrition, aggregateRating
- Article schema layered on top
- FAQPage schema for the "FAQ section" on recipes
- Image SEO: alt text describes the dish, file naming uses keywords
- Pinterest SEO: optimized pin titles + descriptions + boards
- Internal linking via Link Whisper
ADDITIONAL SEO REQUIREMENTS (implement all of these):
On-Page SEO for Every Page:
- Yoast/RankMath meta title template: "[Page Title] | [Site Name]" (under 60 chars)
- Meta description per page: 150-160 chars, include primary keyword + CTA
- Exactly ONE H1 per page — use the real, human headline; keep keywords in the title and meta, not the visible H1
- Logical H2 > H3 heading hierarchy, never skip a level
- Headings should include secondary keywords naturally,
keep the section's real, human label (keywords in title and meta, not stuffed headings)
- Every image must have a descriptive alt attribute with keywords
- Internal links between related content using descriptive anchor text
Structured Data (JSON-LD via Yoast/RankMath + manual where needed):
- Primary schema types: Recipe, Blog, Article
- BreadcrumbList on all pages
- FAQPage schema on any page with an FAQ/accordion section
- Article schema on all blog posts (auto via Yoast)
- Validate schema with Google Rich Results Test before launch
Open Graph & Social Sharing:
- og:title, og:description, og:image, og:url on every page
- twitter:card=summary_large_image on every page
- Default OG image set in Yoast; per-page overrides for key landing pages
- OG images should be 1200x630px, branded, with clear text
Content SEO:
- Write real, useful body copy for every page (not just headings and CTAs).
Every major section needs at least 2-3 sentences of descriptive text
that search engines can index.
- Blog content strategy: 10 seed articles targeting long-tail keywords
related to "recipe / food blog". List the titles and target keywords.
- Use the primary keyword once or twice where it reads naturally; keep the rest in titles and meta, never stuffed.
- Every CTA should use descriptive anchor text with the service keyword.
Technical SEO:
- XML sitemap split by post type (auto via Yoast)
- Canonical tags on all pages (auto via Yoast)
- robots.txt: allow all, point to sitemap
- 301 redirects plan for any renamed/moved content
- Breadcrumbs enabled via Yoast + schema
- Clean permalinks: pick one post-permalink base that fits the site (do not force /blog/ on a post-centric site); /%postname%/ is fine for pages
- Lazy load all images below the fold, eager load hero/LCP image
- Core Web Vitals targets: LCP < 2.5s, CLS < 0.1, INP < 200ms
SECURITY, ACCESSIBILITY & HONESTY (required):
- Escape all output (esc_html/esc_url/esc_attr), sanitize all input (sanitize_text_field + wp_unslash), and use a nonce + current_user_can() on every form handler and custom action. Emit JSON-LD with wp_json_encode().
- Target WCAG 2.2 AA: visible :focus-visible states, <label for> on every field, full keyboard operability, and @media (prefers-reduced-motion: reduce) around all motion.
- Never fabricate business data, testimonials, ratings, credentials, or stats; leave labeled {{TODO}} placeholders for anything the user has not supplied.
- PLUGIN INSTALL: some listed plugins are premium or not in the wordpress.org directory, so a single `wp plugin install` will error out. Split the list into free (wp.org) vs premium (upload/license), verify each slug, and note that gallery/group ACF fields and ACF Blocks need ACF Pro.
- Commit to ONE paradigm: a block theme (theme.json + block templates) OR a classic theme/builder — never mix them. If a plugin already owns a post type or feed (inventory, sermons, courses, job listings, podcast feeds), extend it — do not re-declare that CPT or emit a second, conflicting schema block.
═══════════════════════════════════════════════════════════════
PERFORMANCE (Mediavine eligibility critical)
═══════════════════════════════════════════════════════════════
- LCP < 2.5s, INP < 200ms, CLS < 0.1
- WP Rocket: page cache + critical CSS + lazy comments + delayed JS
- ShortPixel WebP + adaptive images
- Cloudflare for static assets
- Ads loaded after first paint (delay JS via WP Rocket)
- Pin/share buttons that don't block render
═══════════════════════════════════════════════════════════════
ANTI-PATTERNS TO AVOID
═══════════════════════════════════════════════════════════════
- No emojis in recipe titles
- No fake stock food photos (must be real, photographed in your kitchen)
- No "secret family recipe!" exclamation marketing
- No script fonts (no Pacifico, no Caveat, too cliche for food blogs)
- No popups within 5s of landing
- No "click here for the recipe" buried at the bottom, provide Jump-to
- No fake reader testimonials
- No "this is the BEST EVER!" headlines, be specific
- No autoplay video with sound
- No "you won't believe how easy" filler
═══════════════════════════════════════════════════════════════
DELIVERABLE
═══════════════════════════════════════════════════════════════
1. Site map
2. WP-CLI install commands
3. WP Recipe Maker setup walkthrough
4. Recipe taxonomy structure
5. theme.json
6. Block markup for homepage
7. Recipe template structure (with all sections)
8. Welcome email series (5 emails, full copy)
9. Content calendar template (4 weeks of recipes balanced by category)
10. Launch checklist (15 items)
This prompt gives ChatGPT or Claude a full WordPress build plan for a recipe and food blog — the kind where every post carries a proper recipe card with ingredients, steps, cook times, and nutrition, and a “jump to recipe” button because readers demand one. It specifies WP Recipe Maker with full Recipe structured data, a filterable recipe index, printable cards, and an email lead magnet as Gutenberg block markup. You get a plan for a food site that earns Google’s recipe rich results, not a plain blog with photos.
What does the food blog website prompt build?
The plan covers a homepage with a recipe grid, recipe posts with a jump-to-recipe button and a printable card, a recipe index filterable by course, cuisine, and diet, and story-style intros above the card. It specifies ingredient lists with a serving scaler, step-by-step instructions, nutrition display, and an email capture offering a free recipe ebook. Recipe structured data is built into every card so ratings, cook time, and calories can show in search. If you would rather hand it off, our WordPress build service ships the same setup for a flat fee.
Who is this food blog prompt for?
It is written for recipe developers, home cooks building an audience, food photographers who publish what they shoot, and niche food brands. It assumes real recipes with structured ingredients and steps, not a general lifestyle blog that mentions food occasionally.
What’s inside the prompt?
- A business details block for your cuisine, dietary focus, and audience
- A plugin stack led by WP Recipe Maker, with an ad manager, a newsletter tool, and image optimization
- A data model with course, cuisine, and diet taxonomies for the recipe index
- Gutenberg block markup for the recipe post, recipe card, and filterable index
- A jump-to-recipe button, printable cards, a serving scaler, and nutrition display
- Recipe structured data, Pinterest-ready images, and a keyword plan around dishes and ingredients
- Core Web Vitals targets for photo-heavy posts and a launch checklist
Frequently asked questions
Does every recipe get proper Recipe structured data?
Yes. The plan builds each recipe with WP Recipe Maker, which outputs Recipe structured data covering ingredients, steps, prep and cook time, yield, ratings, and nutrition. That markup is what makes a recipe eligible for the rich result with the photo, star rating, and cook time in Google.
Does it include a jump-to-recipe button and printable cards?
Yes. Every post has a jump-to-recipe button at the top so readers can skip the intro, and each recipe card has a print view that strips the page down to ingredients and steps. Both are expected on a modern food blog, and leaving them out costs you repeat visitors.
Can readers filter recipes by course, cuisine, or diet?
The recipe index is filterable by course, cuisine, and dietary tag such as vegan or gluten-free, using the taxonomies in the data model. A cook who lands on one recipe can find five more, which is how a food blog builds session depth and ad revenue.
How does the site collect email subscribers?
The spec includes an email capture offering a free recipe ebook or a weekly meal plan as the lead magnet, with a form in the post and a footer signup. Search traffic to recipes is seasonal, so the owned email list is what smooths it out, and it is built in from the start.
Which AI tools work with this prompt?
ChatGPT and Claude both return the full build spec. A food blog and a travel blog run on almost the same monetization engine, so if you cover both, the travel-blog prompt is a natural companion — and it is worth reading do you even need WordPress first, since recipe plugins are a real reason to choose it.
How to actually run this.
Copy the whole thing
All of it. Do not trim it down, every line is in there for a reason.
Swap in your details
Find the BUSINESS DETAILS part and drop in the real business. Name, what they do, all of it.
Paste and wait
Drop it into Claude for the first pass, or v0 if it is a landing page. Give it a minute.
Clean it up
Tweak the boring 10 percent. Spacing, mobile, that one cringe line. Ship it.
What’s next: from generated code to a website that works
The prompt did the hard 90 percent. What’s left is the boring 10 percent that turns a folder of code into a site people can actually find and trust. Here’s the whole checklist, in order.
1. Buy a domain
Grab your name at a registrar like Namecheap, Cloudflare, or Porkbun — about $10 to $15 a year for a .com. Skip the ten-year prepay and the upsells; you just need the domain and, ideally, the free WHOIS privacy most registrars now include.
2. Put it online
If the AI built you a static site (HTML, CSS, and JavaScript), you can host it for free: drag the folder into Netlify or Vercel, or connect a GitHub repo, then point your domain at it. If it built a WordPress theme, you need WordPress hosting — pick a managed host, install WordPress, upload the theme, and connect the domain. Either way, turn on HTTPS; it’s free and automatic on every modern host.
3. Wire up the parts AI skips
Generated sites almost always ship with a contact form that goes nowhere and a fake “success” message. Connect it to a real endpoint (Formspree, Web3Forms, or a plain mailto link) so leads actually reach you. While you’re in there: add a favicon, swap the placeholder images for your own compressed photos, and open the site on your phone to catch whatever breaks on a small screen.
4. Do the basic SEO and AI-search setup
This is what gets you found on Google and cited by ChatGPT, Perplexity, and AI Overviews. The essentials: a unique title tag and meta description on every page, one clear topic per page, an XML sitemap submitted to Google Search Console, basic structured data (Organization and FAQ schema), and an llms.txt file so AI crawlers can read you. If that reads like a foreign language, our SEO optimization service does it as a flat-fee pass, and our free SEO checklist walks the DIY route step by step.
5. Make it fast
AI builders love shipping four-megabyte images and render-blocking scripts. Compress your images, lazy-load anything below the fold, and run the page through PageSpeed Insights until Core Web Vitals turn green — speed lifts both rankings and conversions, so it’s the rare fix that pays twice. Our speed optimization service handles it if you’d rather not.
6. Get found locally, and measure it
Add analytics (GA4, or a lighter option like Plausible) so you can see what’s working instead of guessing. If you serve a local area, set up a Google Business Profile and use the exact same business name, address, and phone number everywhere — that consistency is what lands you in the map pack and in local AI answers.
7. Keep it alive
A website isn’t set-and-forget, especially on WordPress. Budget for backups, security, and updates so a routine plugin update doesn’t take the site down six months from now. Our care plans cover all of it from $290 a month, or you can do it yourself — you own all the code either way.
When it’s worth handing off
If any of these steps stall you — and hosting, DNS, and SEO stall a lot of people — that’s exactly what we’re for. We build the whole thing at a flat fee, ship it live, and hand you the code on GitHub, having read every line the AI wrote. Or take the free prompts and run with it yourself. Both outcomes are genuinely fine with us.
More from the stash.
Vibe Code a Church Website
Free vibe coding prompt to build a WordPress church site. Sermons, events, online giving, plan-a-visit, ministries, and Church schema. Full religious organization setup.
Vibe Code a Nonprofit Website
Free vibe coding prompt to build a WordPress nonprofit site. Donation flow, programs, impact stories, events, volunteer signup, and NGO schema. Full charity architecture.
Vibe Code a Hotel Website
Free vibe coding prompt to build a WordPress hotel site with booking. Room types, availability calendar, direct reservations, and LodgingBusiness schema. Full hospitality setup.
No free weekend? We will build it for you.
This is the exact prompt we would use. Flat fee, real deadline, code is yours.