In this guide
The bundled website trap
Plenty of hosts throw in a website, and dedicated builders like Podpage exist to make one out of your feed in an afternoon. Buzzsprout, Captivate, and Fireside all hand you a site with the plan. Early on that is a gift. It saves you buying hosting and a theme just to have somewhere for episode pages to live.
The bill comes later. If that site lives entirely inside the host's infrastructure, leaving the host can take the website with it, and by then the site is worth something: search rankings on episode pages, links from guests pointing at their own appearance, a domain people type from memory. That is a heavier loss than swapping out a player.
Find out who owns the domain
Before anything else, work out where the domain is actually registered. If you bought it yourself at a registrar like Namecheap or Cloudflare and pointed DNS at the host, you are fine. You can repoint it anywhere this afternoon. Google Domains is gone, by the way. Those names live at Squarespace now.
If the host or the website builder registered the name for you as part of the plan, find out whether you can actually take it or whether you are only borrowing it while you pay. Some will transfer it free or for a small fee, others make it deliberately tedious. Ask now, not the week you are trying to leave.
Getting the written content out
Episode pages hold more than a player: show notes, transcripts, guest bios, sometimes years of blog posts. Very few builders offer a clean export of any of it. Not always malice, but the effect is the same.
So plan on copying the important pages into a plain document by hand. Home, about, and whichever episodes actually get search traffic. For a big archive, chase the traffic rather than completeness. Rebuilding three hundred episode pages nobody visits is not a good weekend.
DNS, SSL, and the handoff
Moving the site means repointing DNS and getting a new SSL certificate so the domain still loads over https. WordPress hosts and builders like Squarespace or Webflow issue certificates automatically once DNS resolves, but there is a window, a few hours to a day, where it is still provisioning.
Do not announce the new URL during that window, and keep the old site up if you can. A failed certificate does not show a tidy error, it shows a full-page security warning. Load the new site in a private window and look for the padlock before you tell anyone.
Rebuild or migrate
A handful of pages? Rebuild. It is faster than picking a migration apart, and you get to fix the layout you have quietly hated for two years.
A large archive pulling real search traffic to individual episode pages? Migrate properly, and set 301 redirects from the old episode URLs to the new ones. Same idea as the feed redirect, different content. Those rankings took years and they will not come back on their own.
Before you start
- Confirm who actually owns your domain registration before deciding anything
- Ask the current host whether domain transfer is free, paid, or blocked
- Manually copy your highest-traffic show notes pages before cancelling
- Set up DNS on the new host and wait for SSL to fully provision
- Test the new site in a private browser window before announcing it
- Set up 301 redirects from old episode page URLs if they get search traffic
- Keep the old site live until the new one is fully verified
Common pitfalls
- Cancelling before confirming whether you can take the domain with you
- Losing years of show notes with no export because you assumed one existed
- Announcing the new site before its SSL certificate has finished provisioning
- Letting high-traffic old episode URLs 404 with no redirect in place
Product references and review status
This guide is editorial guidance. It does not yet have claim-by-claim verification notes. Use these original product references and the dated linked reviews to check requirements before committing.