How to move podcast from SoundCloud to a new host

To move podcast from SoundCloud, import the complete show at the destination before changing SoundCloud's feed. Compare the two RSS feeds, enter the new URL in Subscriber redirect, verify the existing directory listings, and publish one routine episode from the new host.

SoundCloud is explicit that its redirect does not transfer content. The catalog must already be present and correct at the destination before you point listeners there.

Before you move podcast from SoundCloud

Choose the destination based on the features your podcast needs. Compare publishing controls, storage, private content, team permissions, support, monetization, and analytics. Our podcast hosting company comparison can help if you are still deciding.

SoundCloud supports Podder's analytics prefix. If independent measurement is the only reason you are considering a move, you can install the prefix on SoundCloud without changing hosts. Move when the destination also fits your publishing and operating requirements better.

For a planned move, keep the SoundCloud account and RSS feed active. Gather the current feed URL, original audio files where available, show artwork, and credentials for Apple Podcasts Connect, Spotify for Creators, and other claimed platforms.

Create a compact migration record:

Use the general host switching guide for the checks shared by every migration. The steps here focus on SoundCloud's Content Settings and redirect policy.

1. Import the podcast at the destination

Create the show at the new host and run its import tool with the active SoundCloud RSS URL. Leave SoundCloud unchanged until the import completes. The new host must be able to fetch both the feed and its audio.

Count the imported episodes and inspect different parts of the archive. Play a recent episode, an older one, and any trailer. Compare titles, descriptions, publication dates, season and episode numbers, duration, and artwork.

SoundCloud tracks that were never added to the RSS feed will not appear as podcast episodes to an importer. Private tracks, drafts, scheduled items, comments, followers on SoundCloud, account analytics, and profile content also need separate handling. Decide what to retain on SoundCloud and what to rebuild elsewhere.

Do not set the redirect if the destination catalog is incomplete. Fix missing audio or metadata while the original feed still points to SoundCloud.

2. Compare the SoundCloud and destination feeds

Open both RSS URLs in a feed viewer. At show level, compare title, author, description, category, language, explicit-content setting, and artwork.

At episode level, compare GUIDs as well as visible details. Apple's hosting-provider migration guide says GUIDs should remain unchanged. It also recommends consistent metadata, audio, and season and episode numbers. If the importer assigns a new GUID to an old release, an app can display a duplicate.

Keep the show identity stable while you move it. Delay a new title, artwork, or mass archive edit until one normal destination-hosted episode has distributed. That gives any listing problem one likely cause.

If the feed mechanics are unclear, what an RSS feed is explains the public records that importers and directories read.

3. Set SoundCloud's Subscriber redirect

SoundCloud's official transfer-to-another-host instructions give one direct control:

1. Sign in to SoundCloud.
2. Open Content Settings.
3. Find Subscriber redirect.
4. Paste the destination RSS feed URL.
5. Save the setting.

Copy the RSS address from the destination host. Do not use its website homepage, public show page, or an Apple or Spotify listing.

SoundCloud warns that adding any URL or text to this field redirects the podcast feed. Leave it empty if you intend to keep SoundCloud as the feed host. For this migration, enter the destination only after its catalog passes your checks.

The redirect does not copy episodes. It only points requests for the old SoundCloud RSS URL to the new location. Stop publishing podcast episodes through the old feed after the redirect.

4. Verify the old SoundCloud RSS URL

Open the old SoundCloud feed in a private browser window. It should resolve to the destination RSS feed rather than a SoundCloud profile, sign-in page, or error response.

Then inspect the existing show in the listening apps that matter to your audience. Confirm that episodes appear once, artwork is correct, and both recent and older audio play. Do not submit the destination feed as a new podcast. The redirect is meant to move the existing listing and its followers.

Apple says a 301 redirect from a major host normally handles the feed change without another edit in Apple Podcasts Connect. Use Apple's manual feed-update route only when the old feed cannot redirect.

SoundCloud says a free account can keep the 301 redirect in place indefinitely at no cost. That allows you to preserve the old address without maintaining a paid hosting plan. Keep account access and a record of the destination URL.

5. Update Spotify for Creators

Spotify asks externally hosted podcasts to update the RSS link and hosting provider after a host change. Its current update instructions give this sequence:

1. Sign in to Spotify for Creators and select the podcast.
2. Open Settings.
3. Review the current RSS link and hosting partner.
4. Select Update.
5. Enter the destination RSS URL.
6. Confirm the new host and submit.

This updates Spotify's record for the existing show. The SoundCloud redirect still serves other apps and feed subscribers that request the old URL.

6. Publish one ordinary episode

After the redirect works and your main directory listings remain intact, publish the next regular episode from the destination. Keep the normal schedule and production format so the release gives you a clean migration test.

Confirm that the episode appears once in Apple Podcasts, Spotify, and the other apps you monitor. Compare the title, description, artwork, duration, and audio. Check that the destination host records new requests.

Review your website and production systems too. Replace embedded SoundCloud players only where you want the destination's player instead. A podcast feed redirect does not rewrite page embeds, profile links, or SoundCloud followers.

Export any SoundCloud reports and billing records you need. Label the final report with the cutover date. The destination host begins a separate measurement series, and the public RSS feed does not carry SoundCloud's private analytics history.

7. Decide what remains on SoundCloud

A podcast migration does not require deleting your SoundCloud profile. You may keep the free account to preserve the feed redirect or continue using the profile for non-podcast audio. Separate that choice from the podcast feed cutover.

Before changing a paid plan or removing content, confirm:

• The old SoundCloud RSS URL reaches the destination feed.
• Imported episodes appear once and play.
• Spotify recognizes the new feed and host.
• Apple and other important apps retain the existing show.
• One new episode has distributed from the destination.
• Reports, files, and billing records are saved.
• Website players and production links have been reviewed.

If a check fails, retain access to both accounts while support traces the issue. Include the two feed URLs and one affected episode in your request.

Podder does not migrate SoundCloud content or analytics history. If you stay on SoundCloud, you can add the Podder prefix there. If you move, wait until the destination feed is stable and confirm that the new host supports third-party prefixes before you start Podder Analytics.