Podcast website SEO
A show that lives only on Spotify and Apple has no pages of its own for Google, Bing, or an AI assistant to find. I build the website that fixes that: your RSS feed turned into a fast static site on your domain, one page for every episode, updated on its own when a new one drops.
The working example is my own show's site, described in the podcast site case study.
What gets built
- A page for every episode at an address that never changes, with the cover art, a player that streams from your host, the show notes, and the full transcript in the HTML where crawlers can read it.
- Titles and descriptions written for search, each unique and sized for the results page, drafted with AI and reviewed by me.
- PodcastSeries and PodcastEpisode structured data, plus Person markup for the host, so search engines and assistants connect every episode to the show and the show to you.
- A share card for every episode, sized at 1,200 by 630 pixels, with the cover art and the episode title, so links on Facebook, LinkedIn, and X show the whole image instead of a cropped square. The method is in how social share cards work.
- A home page, an archive, and an about page with every place to subscribe.
- A sitemap, an llms.txt file, and an RSS feed, and the site registered in Google Search Console and Bing Webmaster Tools.
It runs itself
A scheduled job reads your feed every morning, adds new episodes, picks up transcripts your host posts late, and rebuilds the site. If the feed suddenly lists far fewer episodes than the site holds, the job stops and publishes nothing, so a bad day at your host never empties the archive. When the audio stays with your host, your download numbers stay whole there.
Your domain, your feed, your audio
You own the domain and the repository from day one. The site can mirror the show you already publish on Spotify, Apple, or any other host, reading that feed so nothing changes for your listeners. If you'd rather own the whole chain, the site can publish its own RSS feed for the directories, with the audio files stored on your own domain, for example in Cloudflare R2, which charges no fees for downloads. The check for new episodes runs nightly by default, or on whatever schedule suits your release days.
Where it lives and what it costs to run
The site is plain HTML on GitHub Pages, behind Cloudflare. Hosting and HTTPS cost nothing, so your only running cost is the domain, plus storage if you keep your own audio files. There is no WordPress install to patch, no plugin to update, and no database to back up. The repository is yours from the first day, and every change is in its history.
Episodes that grow into articles
An episode that drew a reaction is a good start for a written piece. I can turn an episode into an article in your voice, built from the transcript and checked claim by claim before it goes up. That work is described under fact-checked articles written with AI.
What I'll need from you
Your RSS feed address, your domain or the name you want, the cover art at full size, and an hour to agree on how episode pages should read. Transcripts from your host are ideal. When a host doesn't provide them, I'll propose another source.
How it's delivered
A standard build from an existing feed takes about an afternoon of my time, and it's quoted as a fixed-scope project after a short call. Ongoing additions, such as articles or new page types, can be billed by the hour. Terms are on Hire Me. For the static approach in general, see static websites built for search.
Updated