Vibe Code a Podcast Network Website
Free vibe coding prompt to build a WordPress podcast network. Multi-show architecture, cross-show discovery, network sponsors, and PodcastSeries schema. Full network setup.
Plan and produce a complete WordPress site architecture for a podcast
NETWORK hosting multiple shows, with cross-show discovery, network-wide
sponsorship sales, and shared infrastructure. Output should be
production-ready.
═══════════════════════════════════════════════════════════════
BUSINESS DETAILS
═══════════════════════════════════════════════════════════════
- Network name: [NETWORK NAME]
- Shows: [N] (current + planned to grow)
- Hosts: [N] hosts across shows
- Audience: combined [X]K monthly downloads
- Monetization: network-wide sponsorships + per-show sponsorships +
Patreon + merch + live events
- Goal: cross-promote shows, sell sponsors at scale, grow network
═══════════════════════════════════════════════════════════════
BRAND
═══════════════════════════════════════════════════════════════
- Brand colors: network identity (often dark with single bold accent
per network) + cream highlight + accent. Each show may have its own
cover-art color scheme, but the network frame stays consistent.
- Type: bold display sans for headings (Manrope, Söhne alternative) +
Inter for body + monospace for episode numbers.
═══════════════════════════════════════════════════════════════
ARCHITECTURE DECISION
═══════════════════════════════════════════════════════════════
- Single site (recommended) with CPTs for shows + episodes, much easier
to manage cross-show discovery, shared listener accounts, unified
sponsor management
- Alternative: Multisite (only if shows need fully separate admin teams)
- Justify the recommendation in 3 lines
═══════════════════════════════════════════════════════════════
PLUGIN STACK (WP-CLI)
═══════════════════════════════════════════════════════════════
wp plugin install --activate
seriously-simple-podcasting
wordpress-seo
advanced-custom-fields
wp-rocket
shortpixel-image-optimiser
fluent-crm
memberful-wp
- Podcasting: Seriously Simple Podcasting supports multiple feeds (one
per show), perfect for networks
- OR custom feed generation if SSP is limiting
- Memberful or MemberPress for paid bonus content
- Audio hosting: Castos or Buzzsprout, never on WP server
═══════════════════════════════════════════════════════════════
DATA MODEL
═══════════════════════════════════════════════════════════════
- CPTs:
- `show`, fields: name, tagline, cover_art (square 1400x1400),
description, host_relationship, category (taxonomy), language
(taxonomy), rss_feed_url, apple_url, spotify_url, youtube_url,
sponsorship_open (boolean), monthly_downloads, audience_demo
- `episode`, relationship to `show`, audio_url (Castos), duration,
season, episode_number, episode_type, guests (relationship),
sponsors (relationship), transcript, timestamps, references
- `host`, name, bio, shows hosted (auto-reverse relationship),
social_links, photo
- `sponsor`, name, logo, promo_code, link, active_campaigns
(relationship to shows or episodes), pricing_tier
- `network_news`, announcements, new show launches, milestones
- Taxonomies:
- `show_category` (Comedy / Business / Politics / Tech / etc. -
cross-network)
- `language`
- `season` (scoped per show via meta, not a true taxonomy due to
duplication)
═══════════════════════════════════════════════════════════════
SITE MAP
═══════════════════════════════════════════════════════════════
1. Home (network discovery)
2. Shows (index, all shows in the network)
3. Show pages (one per show, show landing with all episodes)
4. Episode pages (cross-network episode archive)
5. Hosts (directory)
6. Sponsors / Advertise with us (pricing + booking)
7. About the Network
8. Network Newsletter
9. Apply to Join the Network (for podcasters)
10. Press
11. Contact
12. Patreon / Membership (network-wide bonus content)
13. Live Events (in-person + virtual)
═══════════════════════════════════════════════════════════════
HOMEPAGE, BLOCK MARKUP
═══════════════════════════════════════════════════════════════
1. Hero with network branding + headline ("Smart podcasts, one home") +
"Browse shows" CTA + "Latest episode" mini-player
2. Featured show this week (large card with cover art + description +
"Listen now" CTA)
3. Latest episodes across the network (8 cards: cover art mini + show
name + episode title + duration + date, sorted reverse-chronological)
4. Browse all shows (grid of show covers, visually striking)
5. Hosts preview (8 host avatars in a row, "Voices of the network")
6. Network sponsorship CTA strip ("Reach our 500K monthly listeners")
7. Newsletter signup ("Get a weekly briefing from the network")
═══════════════════════════════════════════════════════════════
SHOW PAGE TEMPLATE
═══════════════════════════════════════════════════════════════
- Hero with show cover art (large) + show name + tagline + "Listen-on-X"
buttons (Apple / Spotify / YouTube / RSS)
- Description (3-4 paragraphs about the show)
- About the hosts (host cards with photo + name)
- All episodes (paginated, filterable by season)
- Sponsors of THIS show (separate from network sponsors)
- Subscribe to this show's newsletter (per-show opt-in)
- Apple Podcasts / Spotify subscribe widget
═══════════════════════════════════════════════════════════════
EPISODE PAGE (cross-network template)
═══════════════════════════════════════════════════════════════
- Show name + cover art prominent (so listener knows which show)
- Episode title + guests + "Listen on" buttons
- Embedded audio player (sticky on mobile)
- Show notes with timestamps (click to seek)
- Transcript (collapsible)
- Guests (linked to host/guest profiles)
- Sponsors with promo codes
- Related episodes:
- From same show (chronologically adjacent)
- From other shows in the network with similar topic
- "Subscribe to this show" CTA inline
═══════════════════════════════════════════════════════════════
DISCOVERY FEATURES
═══════════════════════════════════════════════════════════════
- Search across all shows + episodes (Algolia or built-in)
- Filter by topic / language / host / show
- "If you liked this episode, try", cross-show recommendations
(manual editorial OR auto via shared taxonomy)
- Episode pages link to related episodes regardless of show
- Genre / category pages (e.g., /category/tech aggregates tech episodes
from every show)
═══════════════════════════════════════════════════════════════
SPONSORS / ADVERTISE PAGE
═══════════════════════════════════════════════════════════════
- Network reach stats (combined downloads + demographics)
- Show-by-show breakdown (each show's audience demographics in a table)
- Pricing tiers:
- CPM (cost per 1000 downloads)
- Flat fee per episode
- Season sponsorship (X episodes of one show)
- Network-wide takeover (all shows for a week)
- Sponsor inquiry form (Gravity Forms multi-step):
Step 1: Company + contact
Step 2: Budget range + campaign goal
Step 3: Show preference (or "open to recommendations")
- Past advertisers logo strip (typeset names with permission)
═══════════════════════════════════════════════════════════════
APPLY TO JOIN THE NETWORK (PODCASTER SIDE)
═══════════════════════════════════════════════════════════════
- Form for podcasters wanting to join:
- Show name, description, format
- Episodes published so far
- Audience size + demographics
- Why this network (textarea)
- Sample episode URL
- Auto-route to network curation team
- "We review applications monthly" expectation set
═══════════════════════════════════════════════════════════════
EMAIL & NEWSLETTERS
═══════════════════════════════════════════════════════════════
- Network-wide weekly newsletter (best of the week across all shows)
- Per-show opt-in (release notifications)
- Membership newsletter (Patreon-style, exclusive content)
- Welcome series for new subscribers:
Day 0: Welcome + 5 recommended episodes from across the network
Day 3: Most popular shows
Day 7: Network sponsorship offer (cross-promo)
═══════════════════════════════════════════════════════════════
SEO STRATEGY
═══════════════════════════════════════════════════════════════
- Schema: PodcastSeries (per show), PodcastEpisode (per episode),
Organization (network), Person (hosts)
- Transcripts on every episode (huge SEO win)
- Sitemap segmented by post type
- Internal linking dense: episode → show → host → related episodes
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, Organization
- 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 network". 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)
- Object cache (Redis), required for cross-show queries
- Lazy-load all audio embeds
- WP Rocket + Cloudflare
- Per-show RSS feeds cached aggressively
═══════════════════════════════════════════════════════════════
ANTI-PATTERNS TO AVOID
═══════════════════════════════════════════════════════════════
- No autoplay audio on hero
- No emojis in show names or episode titles
- No fake guest bios
- No transcripts behind paywalls
- No fragmented "each show looks completely different", unified network
frame, individual show identity through cover art + colors
- No real Apple/Spotify logos as decorative, use official badges
- No buried RSS feeds (every podcast app needs RSS in 1 click)
- No "MUST-LISTEN!" filler in episode descriptions
- No script/handwritten fonts
═══════════════════════════════════════════════════════════════
DELIVERABLE
═══════════════════════════════════════════════════════════════
1. Architecture decision (multisite vs single site) + justification
2. Site map
3. WP-CLI install commands
4. Full data model: CPTs (show, episode, host, sponsor) ACF JSON +
register PHP + relationship setup
5. theme.json
6. Homepage block markup (with cross-show discovery)
7. Show page template
8. Episode page template (with cross-network related-episodes section)
9. Sponsorship inquiry multi-step form + routing
10. Apply-to-join-network form
11. Newsletter setup (network + per-show)
12. Launch checklist (25 items)
This free prompt gives ChatGPT or Claude a full build plan for a podcast network website that hosts multiple shows under one brand, with a network homepage, individual show pages, per-show episode archives, cross-show discovery, and network-wide sponsorships. It is written for studios and media companies running several titles that need each show to stand on its own while the network moves listeners between them. The output is a complete WordPress specification for a multi-show operation, not a single feed.
What does the podcast network website prompt build?
The plan is built for many shows sharing one platform. The network homepage features every show and surfaces the latest episodes across the roster. Each show gets its own page with distinct artwork, a host lineup, and its own episode archive, so it feels like a standalone site inside the network. Cross-show discovery recommends related episodes from sister shows to keep listeners in the family. A network sponsor page presents a rate card spanning all shows, a shared newsletter reaches the whole audience, and a host directory ties talent to their programs. Every page ships as Gutenberg markup on a shared theme.json with per-show accents.
Who is this podcast network prompt for?
It fits podcast networks, media companies, agencies running client shows, and studios scaling past a single title. A small team manages the whole roster from one WordPress install, and the plan works as a brief for a developer. If you run only one show, a single-show podcast build keeps things simpler and avoids the network overhead. To budget the project, what a WordPress build costs is listed up front, and our WordPress build service can stand up the network if you would rather produce than build.
What’s inside the prompt?
- A brand block for the network name, colors, and the shows and audiences it covers
- A stack built on Seriously Simple Podcasting or Castos for managing multiple feeds, ACF Pro, Yoast SEO, Mailchimp, and WP Rocket
- A data model with show and episode structures plus network-wide topic and host taxonomies
- A theme.json design system with a network shell and per-show accent theming
- Gutenberg markup for the network homepage, individual show pages, per-show archives, cross-show discovery, sponsor, and about pages
- Multiple podcast RSS feeds, one per show, wired to Apple Podcasts and Spotify
- Multiple PodcastSeries entries plus Organization markup for the network, an XML sitemap, and per-show keyword targets
- Core Web Vitals goals, media caching notes, analytics recommendations, and a launch checklist for a multi-show rollout
Frequently asked questions
Can each show keep its own branding under one network?
Yes. Every show gets a dedicated page with its own artwork, color accents, host lineup, and episode archive, while sharing the network’s header, footer, and account. Listeners experience each show as its own destination, and you manage them all from one dashboard.
How does one plugin manage multiple podcast feeds?
Seriously Simple Podcasting and Castos both support multiple podcasts in a single WordPress install, each with its own RSS feed for Apple and Spotify. You assign an episode to a show and the right feed updates, so a five-show network does not need five separate sites.
Does cross-show discovery actually move listeners between shows?
That is the point of a network. Episode pages recommend related episodes from sister shows, and the homepage surfaces the newest across the roster, so a listener who came for one show finds the next. It is the main advantage a network has over five standalone sites.
Can I sell network-wide sponsorships?
The network sponsor page presents a rate card covering ad placements across every show, with audience figures and package options, and a contact route for advertisers. Selling one buy across the roster is easier to pitch than negotiating each show separately.
How is a network marked up differently from a single show?
Each show is marked up as its own PodcastSeries with PodcastEpisode entries, and the network itself carries Organization markup that ties the shows together. That tells search engines and AI answers you run a family of shows, not one program, which a single-show setup cannot express.
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 News Magazine Website
Free vibe coding prompt to build a WordPress news magazine. Multi-author workflow, breaking news bar, sections, ad zones, newsletter, and Article schema. Complete editorial…
Vibe Code an Auto Dealership Website
Free vibe coding prompt to build a WordPress auto dealership site. Inventory listings, financing app, trade-in valuation, and AutoDealer schema. Full dealership architecture.
Vibe Code an Architect Portfolio Website
Free vibe coding prompt to build an architecture portfolio. Project gallery, design philosophy, awards, inquiry form, and SEO-optimized markup. One editorial HTML file.
No free weekend? We will build it for you.
This is the exact prompt we would use. Flat fee, real deadline, code is yours.