Can you switch podcast hosts? What moves with you and what gets left behind

Apple tells podcasters to leave a redirect in place for at least four weeks. Buzzsprout says two to three. Transistor says two. Nobody says zero, and that gap is where shows lose their audience.

Can you switch podcast hosts? Yes, and your followers, your reviews and your back catalog all come with you, on one condition: your old host has to answer requests for the old feed with an HTTP 301 redirect pointing at the new one. Apple Podcasts, Spotify and every app downstream of them keep asking the old address for new episodes until something tells them otherwise. The 301 is that something. Set it, leave it up for a month, and the move is invisible to the people listening. Skip it and your show stops updating everywhere, with no error message anywhere, while your new host reports a perfectly healthy feed.

Any show can be listed on PodAnswer for free, which gives it a page of its own that can turn up when somebody searches the show's name, and you can add yours at podanswer.com/signup.

The file that does the moving

A podcast is a single XML file sitting at a web address. Apple Podcasts, Spotify, Overcast and Pocket Casts store that address and re-read it on a schedule. None of them store your audio. When you change hosts you are not moving a show, you are pointing thousands of stored addresses at a new file, and the redirect is the only instruction they will accept at scale.

Apple is explicit about who should issue it. Its guidance for changing hosting providers says that "Most hosting providers can help you migrate your old RSS feed URL to a different feed URL by implementing a 301 redirect," and that doing it at the old host migrates every follower, including the ones listening in apps Apple has never heard of. Apple adds that "Some hosting providers will also include the tag <itunes:new-feed-url> to help redirect traffic to your new RSS feed."

For a self-hosted feed Apple spells out both halves: configure the server to return an HTTP 301 for requests to the old address, add the <itunes:new-feed-url> tag to the new feed pointing at the new address, and keep both in place for at least four weeks so followers keep receiving episodes. It also warns against setting that tag to the Mirror URL shown in Apple Podcasts Connect.

Four weeks, three weeks, two weeks

The published advice does not agree, and the disagreement is worth reading closely because the numbers measure different things.

Apple's four-week minimum is about follower migration across its whole directory, including apps that sync from Apple on their own slow schedule. Buzzsprout tells hosts leaving its platform to "keep the redirect in place for 2-3 weeks before canceling your account," and in its own migration guide recommends keeping the old account "active for at least 2 weeks before deleting it," so directories have time to update and, in its words, you won't lose any subscribers or listings. Transistor's guide says it is best to wait two weeks before deleting the old hosting account, and notes that because the redirect takes effect immediately there should be no downtime for listeners. Podbean tells incoming shows to keep the old Buzzsprout account live for a few weeks after the redirect is complete.

Take the longest number. Four weeks of a cheap old plan costs less than one lost subscriber base, and nothing bad happens from waiting. Transistor also puts a figure on the directory lag: it can take 24 to 48 hours for Apple to propagate the new feed.

The identifier nobody looks at

The second way a migration goes wrong has nothing to do with redirects. Every episode in a feed carries a GUID, a unique string that identifies it. The podcast de facto standard documentation defines it as "A unique identifier for the episode," notes it "can be a link to the episode, but doesn't have to be," and reports it present in 98.4 percent of feeds, from a sample of 258,607 podcasts.

Apple's requirement is that the GUID never changes, even when the title or the audio URL does. When a new host generates fresh GUIDs on import, Apple sees a feed full of episodes it has never encountered. Apple's own troubleshooting is blunt about the symptom: if you notice duplicate episodes or a drastic change in your analytics after changing hosting providers, it is possible that your hosting provider changed the GUID during the migration process. Apple also warns that altered GUIDs can misrepresent Analytics data and affect a show's status on Apple Podcasts.

So before you set the redirect, open both feeds in a browser and compare the GUID of your oldest episode. If the two strings differ, stop and ask the new host to preserve the originals. This is a five-minute check that prevents a republished back catalog from appearing as a hundred brand new episodes in everybody's app, which is the single most damaging thing a feed can do to its listeners. Our guide to the podcast back catalog covers the other feed rules that govern old episodes.

Spotify is not downstream of Apple

Most apps resolve this automatically. Transistor's guide notes that Overcast, Pocket Casts and similar apps generally pull from Apple's directory, so they follow whatever Apple does. Spotify does not. It stores your feed address itself and has a form for changing it.

Spotify for Creators lists six steps: log in, click your podcast, go to Settings, where the current RSS feed link and hosting partner are both shown, click Update, enter the new link, then confirm the hosting provider and click Submit. Buzzsprout flags the same thing from its side, noting that Spotify needs an extra step beyond the redirect.

YouTube, if you distribute there by RSS, holds its own copy too. Shows that went through that setup should re-check it after the move, and our walkthrough of how to put your podcast on YouTube explains where that feed address lives. If episodes stop appearing on Spotify after a move, the feed address stored in Spotify for Creators is the first thing to check, ahead of everything in our piece on why a podcast is not showing up on Spotify.

The order that keeps the show live

Hosts get this backwards and pay for it. The sequence every migration guide describes, and the one Podbean's import flow enforces, runs in this order:

Sign up at the new host and import the feed by its URL. Podbean's flow asks for the RSS feed URL as the content source; Buzzsprout's asks you to search for the show by name, then imports the rest of the episodes after you upgrade, and says imports don't count against the monthly upload allowance.
Compare the two feeds. Episode count, titles, publication dates, cover art, categories and, above all, GUIDs.
Set the 301 redirect at the old host. Buzzsprout's own instruction calls this "one of the most important parts of moving your podcast to a new host."
Test it. Buzzsprout tells migrating shows to test the redirect to confirm it is working; Podbean has a "Check Redirect" button that gates the media import behind a working redirect.
Update Spotify by hand, and anywhere else holding a stored feed address.
Publish one new episode and confirm it appears in Apple Podcasts and Spotify.
Wait four weeks. Then cancel the old plan.

Publishing that test episode is the only real proof. A redirect that returns the right status code to a browser can still be pointed at a typo.

What stays behind

One thing does not travel. Transistor states plainly that podcast hosting providers can't migrate your analytics from your old host, and recommends exporting the old stats as CSV or Excel files, or at minimum saving screenshots, before the account closes. Apple makes a related point from the other direction: you may see atypical download metrics across hosting dashboards after migrating, while Apple Podcasts Analytics should remain consistent.

Export everything while you still have access. Total downloads by episode, your monthly trend, and your best and worst performers. Once the old account is gone, the numbers are gone, and you will want them the first time a sponsor asks for history. If you are not sure which of those numbers a sponsor will care about, our benchmark piece on how many podcast downloads is good is the place to start.

Questions hosts ask

Can you switch podcast hosts without losing subscribers? Yes, with a 301 redirect at the old host. Followers in Apple Podcasts, Spotify and third-party apps carry over, along with your reviews and ratings, because those live with the directory and not with the host.

Do I have to resubmit my show to Apple Podcasts? No. Apple's guidance says that when a hosting provider handles the migration with a redirect, you don't need to perform additional actions in Apple Podcasts Connect. If you have lost access to the old feed entirely, Apple's fallback is to sign in to Apple Podcasts Connect, select the podcast, click Edit next to the RSS feed URL, enter the new one and save.

How long does the switch take to show up? Transistor puts Apple propagation at 24 to 48 hours. Spotify updates once you submit the new address in Spotify for Creators. Smaller apps can lag by a week or more, which is the reason behind Apple's four-week figure.

Will my search rankings change? Your episode pages on the old host will eventually disappear, so anything you had ranking on Google from host-generated pages goes with them. Episode content indexed elsewhere is unaffected. Our podcast SEO guide covers where that traffic actually comes from.

Can I move only some episodes? You can, but a partial feed looks like a different show to the directories and splits your listener base across two addresses. Move the whole catalog.

A move is also a good moment to deal with the part of discovery that hosting does not touch, which is whether anyone searching a question your show already answered can find the episode that answers it. PodAnswer turns podcast transcripts into pages that answer those questions and link back to the show. The plans are laid out at podanswer.com/for-podcasters, and the pricing, Growth at $149 a month for four articles and Network at $349 a month for twelve, is at podanswer.com/pricing. Listing a show is free either way.