What should a podcast website actually have on it?

Two things. A hub: one page that sends a listener to every platform and social account, with the player, the clips and the YouTube channel embedded so nobody has to leave to find the show. And an episode page for every episode: transcript, summary, show notes with timestamps and links, the player, and a title and description written for the question that episode answers. The hub does the routing; the episode pages do the ranking.

Why one page per episode? Isn't the show page enough?

Because search engines and AI assistants read text, not audio. An episode inside a podcast app is invisible to both. An episode page with the transcript and a written summary is a document they can rank and cite. On one show we run, that's 100+ episode pages on the show's own domain, each with a written title and meta description. A single show page can rank for the show's name. A hundred episode pages can rank for a hundred topics.

How does Podlink automate the content without making it sound generic?

The product transcribes the episode, then drafts the summary, show notes, chapters and post copy from that transcript — not from a guess about what a podcast episode usually contains — in the format you set once, with your brand voice switched on. That's the first draft. A person edits it, structures the page and publishes it. The AI removes the blank page; it doesn't remove the editor.

Does the site publish itself when I release an episode?

No. Today the content kit — transcript, show notes, summary, post copy — comes out of Podlink, and we build and publish the page as part of the service. There is no automatic feed-to-website pipeline, and we won't describe one until it exists.

Which platform do you build on?

The one you should keep. We've built and maintained podcast sites on WordPress and on static builds, and we'll work in Squarespace or Webflow if that's where you are. Templates come from your brand kit, the domain is yours, and if we part ways you keep the site, the templates and every page.

It's scoped on a call rather than listed, because the number moves with three things: how many episodes are in the back catalogue, which platform the site lives on, and whether you want monthly care with a page per new episode. We'll tell you a real figure on a 20-minute call, and we'll tell you if a simpler option fits better.

I already have a site. Do I have to start over?

Usually not. The hub can be a rebuilt home page on your existing site, and the episode-page template can live alongside your blog. Where a site is beyond saving we'll say so, and the move comes with 301 redirects so the search equity you already have carries over.

Podcast Websites

A website that works for the show, not just about it.

We build and maintain podcast websites that do two jobs: one hub that sends listeners to every platform, and an episode page per episode — transcript, summary, show notes — so the back catalogue keeps getting found in search and cited in AI answers.

Built on your domain, in your brand. You own it. Pricing is scoped on a call — no package to pick from a table yet.

Talk to us See the work Pricing: scoped on a call

100+episode pages written for search and AI answers on one show we run

A podcast website from Podlink is a hub site on your own domain — every listen link, social link and embedded player in one place — plus a page for every episode with the transcript, a summary and show notes, built to be found in search and cited in AI answers; pricing is scoped on a call.

Setup (one-time): Scoped on a call — hub site + episode-page template + back-catalogue migration
Ongoing: Optional monthly care: a page per new episode, updates, monthly ranking check
Best for: A show with a back catalogue and a website that does nothing after launch day

Shows we've produced, grown, or monetizedGo With Elmo LovanoUnemployableMoms Moving OnHell Has an ExitFruits of MotherhoodMadam TraderHarvesting HappinessWhy We TriSales SchoolThe Wolf's DenMimosa's with MomsYogaBiz AcademyStar Spangled Gamblers

Most podcast websites are a business card with a player on it

One page, a logo, three platform badges, maybe the latest episode embedded. It does nothing after launch day. Meanwhile every episode you publish is a page Google could rank and a passage an AI assistant could cite — except the only copy of it lives inside a podcast app, where search can't read it. The right website is the opposite: a hub that routes every listener, and an episode page per episode that compounds. Two years in, that's a hundred pages working for you instead of one.

What’s included

Every engagement ships with this.

The hub: home page with every listen link, social link and subscribe path, and players, clips and YouTube embedded where they belong
Episode pages: one page per episode with the transcript, a written summary, show notes with timestamps and links, and the player
Search and AI-answer structure on every page: titles, meta descriptions, headings and schema written for the query the episode answers
Your brand, your domain: templates built from your brand kit and your voice, on a platform you keep (WordPress, Squarespace, Webflow, or a static build)
Back-catalogue migration: existing episodes rebuilt as proper pages, with redirects so nothing you've earned is lost
Ongoing care: new episode pages as episodes ship, platform updates, fixes and monthly checks on what's ranking

How it works

The actual process, not a diagram.

1
Audit what you have
We look at your current site, your feed and your YouTube channel and tell you which of your episodes already have a search query worth owning. That's the build order.
2
Design the hub in your brand
A home page, an episodes index and an episode-page template, built from your brand kit on the platform you want to keep. You approve the template once; every page after that inherits it.
3
Fill the episode pages
Podlink transcribes each episode. From the transcript, the product drafts the summary, show notes, chapters and post copy in the format you set — with your brand voice switched on. We edit, structure and publish the page. The AI does the first draft; a person does the page.
4
Launch and redirect
Old URLs 301 to the new pages, the sitemap goes to Google, and every episode page carries the player, the listen links and the schema. Nothing you've earned disappears in the move.
5
Keep it compounding
Each new episode gets its page. We check monthly what's ranking and which back-catalogue episodes are worth a rewrite, and do the rewrite.

Proof

What this has produced.

My Divorce Solution · Financial services

$70K in new MRR within 90 days

Took over full production and turned the show into the category's authority asset — editing, show notes, episode art, clips and repurposing that added $70K in monthly recurring revenue within 90 days.

monthly recurring revenue added in 90 days: $70K; monthly recurring revenue added in 90 days
increase in website traffic: 150%; increase in website traffic
growth in podcast subscribers: 70%; growth in podcast subscribers
and still a client: 5 yrs; and still a client

Read the case study →

Moms Moving On · Michelle Dempsey-Multack · Lifestyle / self-improvement

Four renewals, and a 17-month sponsorship sold

Production, clips and monetization for a divorce-and-coparenting show — a multi-year relationship that ended with us selling and running its longest brand partnership.

contract renewals across the relationship: 4; contract renewals across the relationship
continuous sponsorship sold, managed and renewed: 17 mo; continuous sponsorship sold, managed and renewed
host's Instagram growth during the campaign: 2×; host's Instagram growth during the campaign
listenership growth year over year: 15%; listenership growth year over year

Read the case study →

The work

Pages we've built, rebuilt or maintain

The episodes index on Go With Elmo's website: a grid of episode cards, each one a link to its own page with a guest name and episode number. — Go With Elmo — the episodes index. 100+ episode pages, each with a written title and meta description.

A single episode page on Go With Elmo's website: episode number, guest name as the headline, a one-line description, and Watch on YouTube and Apple Podcasts buttons above the embedded player. — Go With Elmo — one episode page: headline, description, listen buttons and the player, on the show's own domain.

An episode post on My Divorce Solution's website: category tag, episode number and title as the headline, publish date, cover image, and a sidebar promoting the podcast with a Listen Now button. — My Divorce Solution — an episode page on the client's WordPress site, where every new episode gets its own post.

Is this for you?

We’d rather tell you now.

This is for you if

You have a back catalogue — 20 episodes or 200 — and none of it ranks for anything
You want the site on your own domain, in your brand, on a platform you keep
You'd rather pay for pages that compound than for a redesign that sits there

It isn’t if

You want a free link-in-bio page — that's podlink.fm, and it's already free
You publish a handful of episodes a year with no plan to continue — the pages won't have time to compound
You want it to run with nobody touching it — the content kit is automated, the publishing is still a person

Pricing

Scoped on a call, priced to the show you actually have.

There isn't a package table here yet, and we'd rather tell you a real number on a 20-minute call than print one that's wrong for your show. Three things move it: how many episodes you have, which platform the site lives on, and whether you want the pages maintained as you publish.

Scope is the number of episodes to migrate, the platform you're on, and whether you want us to keep publishing pages as episodes ship.

What the call covers

How many episodes are in the back catalogue, and how many of them have a search query worth owning
Platform: keep what you're on, or move — we'll say which and why
One-time build, or build plus monthly care with a page per new episode
What you'll own at the end: the site, the templates, the content, the domain

Talk to us

We publish real numbers on every other service page. This one is new enough that the honest answer is a scoped quote, not a table that’s wrong for half the shows that read it. You’ll get a figure on the call, in writing.

Why Podlink

The content kit comes from the product. The pages come from us.

Podlink transcribes the episode and writes the show notes, summary and post copy from the transcript, in the format you set once, with your brand voice on. That's live today. The website work runs on top of it: we take that kit, edit it, structure the page and publish it on your site. One company holds both halves, so the page matches what was actually said and the brand matches what you actually sound like.

Questions

The things people ask before signing.

What should a podcast website actually have on it?: Two things. A hub: one page that sends a listener to every platform and social account, with the player, the clips and the YouTube channel embedded so nobody has to leave to find the show. And an episode page for every episode: transcript, summary, show notes with timestamps and links, the player, and a title and description written for the question that episode answers. The hub does the routing; the episode pages do the ranking.
Why one page per episode? Isn't the show page enough?: Because search engines and AI assistants read text, not audio. An episode inside a podcast app is invisible to both. An episode page with the transcript and a written summary is a document they can rank and cite. On one show we run, that's 100+ episode pages on the show's own domain, each with a written title and meta description. A single show page can rank for the show's name. A hundred episode pages can rank for a hundred topics.
How does Podlink automate the content without making it sound generic?: The product transcribes the episode, then drafts the summary, show notes, chapters and post copy from that transcript — not from a guess about what a podcast episode usually contains — in the format you set once, with your brand voice switched on. That's the first draft. A person edits it, structures the page and publishes it. The AI removes the blank page; it doesn't remove the editor.
Does the site publish itself when I release an episode?: No. Today the content kit — transcript, show notes, summary, post copy — comes out of Podlink, and we build and publish the page as part of the service. There is no automatic feed-to-website pipeline, and we won't describe one until it exists.
Which platform do you build on?: The one you should keep. We've built and maintained podcast sites on WordPress and on static builds, and we'll work in Squarespace or Webflow if that's where you are. Templates come from your brand kit, the domain is yours, and if we part ways you keep the site, the templates and every page.
What does it cost?: It's scoped on a call rather than listed, because the number moves with three things: how many episodes are in the back catalogue, which platform the site lives on, and whether you want monthly care with a page per new episode. We'll tell you a real figure on a 20-minute call, and we'll tell you if a simpler option fits better.
I already have a site. Do I have to start over?: Usually not. The hub can be a rebuilt home page on your existing site, and the episode-page template can live alongside your blog. Where a site is beyond saving we'll say so, and the move comes with 301 redirects so the search equity you already have carries over.

Works well with

Most shows need two of these, not one.

Growth Campaigns

Turn a show that exists into a show that compounds.

Podcast Editing

Production that turns episodes into a business asset.

Podcast Clips

Short-form video that brings your show to where the audience is.

Ready to talk about podcast websites?

A 20-minute call. We'll tell you what we'd do, what it costs, and whether it's the right first move for where your show actually is.