New Feed URLs | Redirect

Move your podcast away from Podigee

Use this guide to move to another host or to your own hosting. First, import your episodes at the destination and check the new public RSS feed and audio files. If you use Spotify Video, arrange the API-to-RSS change with Podigee Support before setting redirects.

Find the redirect fields

1. Sign in with the account that owns the podcast. These controls are for podcasts hosted by Podigee, not externally hosted podcasts.
2. Open the podcast and its Podcast settings. Find Redirects.
3. If the fields are hidden, select Begin the process under Redirection. Read the information, select the acknowledgment only if you understand it, and continue.
4. Complete the destination checks below before unlocking or editing a field. The form saves changes automatically. Enter the correct destination feed in each applicable feed-format field. The blog URL is separate.
5. Reload the settings to check the saved values, then test the old feed URLs and the existing platform listings.

If the controls are missing, check the owning account and contact Podigee Support with the podcast link. If inline help does not open, use this direct guide. Do not cancel or delete the old hosting before completing the checks below.

Feed redirects and the RSS element

The new MP3, AAC, OGG and OPUS feed URL fields set HTTP 301 redirects for the old feed URLs. Use the correct destination feed for each format that is in use.

The separate RSS element <itunes:new-feed-url> tells supported apps the new address in the feed. It does not replace the HTTP redirect.

The new blog URL redirects your podcast website. It is not a destination for an RSS feed.

Checks before you save

1. Copy the full destination URL from the new host. Use an RSS feed, not a podcast website.
2. Make sure that the destination feed opens and contains the correct episodes.
3. Test the audio files. Make sure that existing episodes keep their GUIDs.
4. The destination must not redirect back to the old feed. Prevent redirect loops.
5. After you save, check the old feed URL and your existing platform listings. Do not submit the same podcast as a new show.

Read the Apple Podcasts requirements for a feed change and the rules of your other platforms. If you are not sure, contact Podigee support before the change.

Compare the complete source and destination catalogs

A redirect changes the feed address. It does not copy missing episodes or media to the new host.

1. Before the redirect, compare your expected published episode count with the source feed and the destination catalog. Exclude drafts and episodes you do not intend to move.
2. Check the oldest and newest expected episodes in both places.
3. Check several specific missing episodes by title, publication date, and GUID (the episode's stable feed identifier).
4. Open their media URLs to check playback.
5. In the classic view, open the podcast's Feeds tab. Check Number of feed items. A limit can leave older published episodes out of the first feed page. Custom feeds can also filter the selection. See Standard feeds.

If the source feed is limited, make the required episodes available in the source feed before the destination imports them. Check the actual feed again after a setting change. Do not assume that the new host reads every page. If the source contains the episodes and playable files but the destination does not, give the new host the source URL and examples of missing episodes.

After a redirect is live, opening the old URL usually shows the destination feed. That does not prove what the original source contained. Use your saved pre-move feed or compare the original episode list and files in your Podigee account. Ask Podigee and the destination host to coordinate source access if needed. Do not turn a live redirect off as a test.

Keep the old hosting available until the comparison and playback checks pass. Then continue with the existing-platform checks below and the cancellation guidance.

Redirects after cancellation or deletion

Podigee does not guarantee a permanent redirect after cancellation or deletion. Complete and test the migration before the old service ends. Do not treat a working redirect today as a promise of later availability.

1. If you use Spotify Video, arrange the API-to-RSS change with Podigee Support first.
2. Set up and test the feed redirects.
3. Check the original platform listings and episode playback.
4. Complete the migration before the old hosting service ends.

A feed redirect does not restore RSS delivery for a Spotify API connection. Use the Spotify Video migration section and Cancellation before you end the old service.