Vibe Code a Podcast Website
Free vibe coding prompt to build a WordPress podcast site. Episode archive, embedded player, transcripts, subscribe links, and PodcastSeries schema. Full audio content setup.
Plan and produce a complete WordPress site architecture for a single
podcast (host or co-hosted show) with episode archive, transcripts,
subscribe links, and sponsor inquiry. Output should be production-ready.
═══════════════════════════════════════════════════════════════
BUSINESS DETAILS
═══════════════════════════════════════════════════════════════
- Podcast name: [PODCAST NAME]
- Host(s): [NAME(S)]
- Topic: [WHAT IT'S ABOUT]
- Audience: [WHO]
- Cadence: [WEEKLY / BIWEEKLY / SEASONAL]
- Episodes published so far: [N]
- Monetization: sponsorships + Patreon + merch + course
- Existing podcast host: [LIBSYN / BUZZSPROUT / CASTOS / TRANSISTOR /
ANCHOR]
- Goal: grow audience, convert listeners → email subscribers → revenue
═══════════════════════════════════════════════════════════════
BRAND
═══════════════════════════════════════════════════════════════
- Brand colors: derive from podcast cover art. Default: dark surface
(#0e0e0e) + cream highlight (#f5efe4) + ONE accent (electric color
picked from cover art). AA-contrast for body.
- Type: bold display sans for headings (Manrope, Söhne alternative) +
Inter for body + monospace for episode numbers/timestamps.
═══════════════════════════════════════════════════════════════
PLUGIN STACK (WP-CLI)
═══════════════════════════════════════════════════════════════
wp plugin install --activate
seriously-simple-podcasting
seriously-simple-stats
wordpress-seo
advanced-custom-fields
wp-rocket
shortpixel-image-optimiser
fluent-crm
- Podcasting: Seriously Simple Podcasting (Castos), handles RSS feed,
iTunes submission, basic stats. Alternative: PowerPress (Blubrry).
- Audio hosting: Castos / Buzzsprout / Libsyn, NEVER host audio on WP
- Email: FluentCRM or ConvertKit
- Optional: Memberful for paid bonus episodes
═══════════════════════════════════════════════════════════════
DATA MODEL
═══════════════════════════════════════════════════════════════
- Episode is a post (with SSP plugin meta: audio_url, duration, season,
episode_number, episode_type, full/trailer/bonus)
- ACF on episode: transcript (textarea, large), guests (relationship to
guest CPT), sponsors (relationship to sponsor CPT), timestamps
(repeater: time + title), references_links (repeater: title + url)
- CPT `guest`, name, bio, photo, social_links, episodes_appeared_in
(auto-populated reverse relationship)
- CPT `sponsor`, name, logo, promo_code, link
- Taxonomies: `season`, `topic`
═══════════════════════════════════════════════════════════════
SITE MAP
═══════════════════════════════════════════════════════════════
1. Home (latest episode + show description)
2. Episodes archive (filterable by season, guest, topic)
3. Episode detail (player + show notes + transcript)
4. Subscribe (links to Apple, Spotify, Overcast, YouTube, RSS)
5. About / Host
6. Guests directory
7. Sponsors / Advertise with us
8. Merch (Shopify or simple WooCommerce)
9. Newsletter
10. Patreon / Membership (if applicable)
11. Press Kit (one-sheet PDF, stats, logos, bios)
12. Contact / Guest Pitch
═══════════════════════════════════════════════════════════════
HOMEPAGE, BLOCK MARKUP
═══════════════════════════════════════════════════════════════
1. Hero with cover art (square, large), podcast name, tagline, "Play
latest episode" big button + Subscribe-on-your-app buttons row
2. Show description (2-3 paragraphs explaining what listeners get)
3. Recent episodes (6 cards: cover art mini, title, guest name, date,
"Listen" button)
4. About host snippet (photo + 2-line bio + "More about [HOST] →")
5. Past guests grid (12 small avatars in grid, visual proof of guest
quality)
6. Newsletter signup ("Get show notes + bonus content via email")
7. Sponsorship CTA strip ("Want to reach our audience? Advertise →")
═══════════════════════════════════════════════════════════════
EPISODE PAGE TEMPLATE
═══════════════════════════════════════════════════════════════
- Hero with episode art (large) + title + guest names + "Listen-on-X"
buttons (Apple / Spotify / YouTube / Direct download)
- Embedded audio player (sticky on mobile during scroll)
- Episode description (3-4 paragraphs)
- Timestamped show notes (clickable timestamps that jump player to that
point, small JS needed)
- Guest cards (linked to guest profile pages)
- Sponsors of this episode (with promo codes prominently)
- Full transcript (collapsible <details>, open by default for SEO)
- Related episodes (4 cards, same guest, same topic, or chronologically
adjacent)
- Comments / discussion (optional)
═══════════════════════════════════════════════════════════════
SUBSCRIBE PAGE
═══════════════════════════════════════════════════════════════
- Big buttons for every major podcast app (Apple Podcasts, Spotify,
Overcast, Pocket Casts, Castbox, Stitcher, YouTube, RSS, Amazon Music)
- "How to listen" mini-guide for newer users
- QR code that opens podcast in default app
- "Already a listener? Leave a review" with link
- Embed code for sharing the podcast on a website
═══════════════════════════════════════════════════════════════
GUEST PITCH FORM (on About page)
═══════════════════════════════════════════════════════════════
- "Want to be a guest?" form (open public, but you'll filter)
- Fields: name, expertise area, why this show, your bio, social links,
pitched topic
- Auto-routes to host email + tags in CRM
═══════════════════════════════════════════════════════════════
SPONSORS / ADVERTISE PAGE
═══════════════════════════════════════════════════════════════
- Audience demographics (downloads/month, age, location, interests)
- Engagement stats (listen-through rate, social engagement)
- Pricing tiers: pre-roll / mid-roll / post-roll, host-read vs produced
- Booking form for sponsorship inquiry
═══════════════════════════════════════════════════════════════
EMAIL FLOWS (FluentCRM or ConvertKit)
═══════════════════════════════════════════════════════════════
- Welcome series after newsletter signup (3 emails, 7 days)
- New episode notification (every release, opt-in)
- Bonus content (Patreon-style, exclusive to subscribers)
- Re-engagement at 30 days inactive
═══════════════════════════════════════════════════════════════
SEO STRATEGY
═══════════════════════════════════════════════════════════════
- Schema: PodcastSeries + PodcastEpisode + AudioObject
- Full transcripts are huge for SEO (each episode is searchable text)
- Internal linking between related episodes
- Sitemap segmented by post type
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: PodcastSeries, PodcastEpisode
- 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 "podcast". 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
═══════════════════════════════════════════════════════════════
- Audio on external host (Castos/Buzzsprout), never on WP server
- Lazy-load embeds (iframes for Apple/Spotify embeds)
- WP Rocket + ShortPixel + Cloudflare
═══════════════════════════════════════════════════════════════
ANTI-PATTERNS TO AVOID
═══════════════════════════════════════════════════════════════
- No autoplay audio on hero
- No emojis in episode titles
- No "MUST-LISTEN!" / "BLEW MY MIND" filler in episode descriptions
- No fake guest bios, verify everyone
- No buried RSS feed (subscribers should find it in 1 click)
- No transcripts hidden behind paywalls (transcripts boost SEO)
- No script/handwritten fonts
- No real podcast platform logos as images, use official "Listen on
Apple Podcasts" badges or just typeset names
═══════════════════════════════════════════════════════════════
DELIVERABLE
═══════════════════════════════════════════════════════════════
1. Site map
2. WP-CLI install commands
3. SSP / PowerPress setup walkthrough
4. Episode CPT + ACF JSON (transcript, timestamps, guests, sponsors)
5. theme.json
6. Homepage block markup
7. Episode page template (with sticky player + transcript)
8. Sponsors / Advertise page
9. Email automation specs
10. Apple Podcasts / Spotify submission process
11. Launch checklist (15 items)
This free prompt gives ChatGPT or Claude a full build plan for a single-show podcast website: one feed, one brand, built around an episode archive, an embedded player on every episode, transcripts, and subscribe links for the major apps. It is written for an independent host or a small team running one show who wants a real home for the podcast instead of relying only on Spotify and Apple. What comes back is a complete WordPress specification, not a landing page.
What does the podcast website prompt build?
The plan centers the site on your one show. The homepage leads with the latest episode and a play button, and the episode archive lets listeners search and filter by season or topic. Every episode gets its own page with an embedded audio player, full show notes with clickable timestamps, guest details, and a transcript. An about page introduces the host and the premise, a guest directory links each guest to their appearances, and a subscribe page collects Apple, Spotify, YouTube, and RSS in one spot. A newsletter signup and a sponsor or advertise page complete the set, each shipped as Gutenberg markup on a shared theme.json.
Who is this podcast prompt for?
It fits solo hosts, co-hosted interview shows, and small studios running a single title. If you are producing several shows under one brand, you want a multi-show podcast network build instead, which handles cross-show discovery and shared sponsors. For one show, this prompt keeps the architecture lean. You can see the tools we use to run these builds, and if you would rather not assemble the feed and player yourself, our WordPress build service can deliver it ready to publish.
What’s inside the prompt?
- A brand block for your show name, host, cover-art colors, and audience
- A stack built on Seriously Simple Podcasting for the feed and player, optionally paired with Castos hosting, plus Yoast SEO and Mailchimp for the newsletter
- A data model with an episode structure plus season, guest, and topic taxonomies
- A theme.json design system tuned for cover art, waveforms, and readable show notes
- Gutenberg markup for the homepage, episode archive, single episode page, about, guest directory, subscribe, and sponsor pages
- Podcast RSS feed configuration wired to Apple Podcasts and Spotify submission
- PodcastSeries and PodcastEpisode structured data, an XML sitemap, and per-episode keyword and title guidance
- Core Web Vitals targets, media caching notes, and a launch checklist for a single-show site
Frequently asked questions
Does every episode get its own player and transcript?
Yes. Each episode is a separate page with an embedded audio player, show notes with clickable timestamps, and a full transcript. The transcript makes the episode searchable on your own site and gives search engines real text to index, which a player embed alone never provides.
Can listeners subscribe on Apple, Spotify, and other apps?
The subscribe page gathers your show’s links for Apple Podcasts, Spotify, YouTube, and the raw RSS feed in one place, with follow buttons on the homepage and every episode. Listeners pick their app without hunting for the feed URL.
How does my show’s RSS feed stay in sync with the site?
Seriously Simple Podcasting generates and maintains the feed from the episodes you publish in WordPress, so posting a new episode updates the feed that Apple and Spotify read. You manage one show in one place instead of copying details between a host and a website.
Will episodes and transcripts show up in search?
The plan marks the site up as a PodcastSeries with PodcastEpisode entries and leans on the transcripts for indexable text, so episode pages can rank for the topics and guests you cover. Titles and show notes are structured for episode-level keywords rather than one generic homepage.
Can I sell sponsorships and build an email list?
Yes. The sponsor page includes a rate-card layout and a contact route for advertisers, and the Mailchimp newsletter signup turns one-time listeners into subscribers you can reach directly when a new episode drops.
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 an Event Planner Website
Free vibe coding prompt to build an event planner portfolio. Real event galleries, service packages, inquiry form, and SEO schema. One elegant HTML file,…
Vibe Code a Marketing Agency Website
Free vibe coding prompt to build a WordPress marketing agency site. Services, case studies, team, free audit funnel, blog, and ProfessionalService schema. Full agency…
Vibe Code a Bakery Website
Free vibe coding prompt to build a neighborhood bakery website. Menu with daily specials, custom cake orders, bakery story, and local SEO markup. One…
No free weekend? We will build it for you.
This is the exact prompt we would use. Flat fee, real deadline, code is yours.