What is Feed Redirect?
A feed redirect tells podcast directories and apps to fetch your RSS feed from a new URL. This is essential when migrating between hosting providers—it ensures subscribers continue receiving new episodes without needing to resubscribe.
How Feed Redirects Work
Old feed URL: https://old-host.com/feed/show
↓ (301 Redirect)
New feed URL: https://new-host.com/feed/show
↓
Apps follow redirect and update their stored URL
Types of Redirects
| Type | Code | Use Case | Permanence |
|---|---|---|---|
| Permanent | 301 | Migration complete | Apps should update URL |
| Temporary | 302 | Testing, temporary change | Apps keep old URL |
For migration: Always use 301 (permanent) redirects.
The Redirect Process
- Set up new feed on new hosting platform
- Verify new feed contains all episodes
- Configure redirect on old host pointing to new URL
- Test redirect by fetching old URL
- Wait for propagation (apps update over days/weeks)
- Monitor for any issues
Directory Behavior
| Directory | Redirect Handling |
|---|---|
| Apple Podcasts | Follows 301, updates listing |
| Spotify | Follows 301, re-ingests |
| Podcast Index | Follows 301, updates index |
| Individual apps | Most follow 301 automatically |
Common Redirect Issues
| Issue | Cause | Solution |
|---|---|---|
| Episodes duplicate | GUIDs changed | Preserve original GUIDs |
| Subscribers lost | No redirect set up | Always set redirect before canceling old host |
| Redirect chain | Multiple hops | Point directly to final URL |
| HTTP to HTTPS | Protocol change | Ensure HTTPS on new feed |
Why It Matters
A properly configured redirect is the difference between seamless migration and losing your entire subscriber base. There's no undo for a botched migration.
Why feed redirects are critical:
-
Subscriber preservation: Redirects ensure existing subscribers continue receiving episodes.
-
Directory continuity: Your Apple Podcasts/Spotify listings update without losing reviews or history.
-
Analytics continuity: Download tracking continues without artificial gaps.
-
SEO preservation: Existing links to your feed continue working.
The no-redirect disaster:
| What Happens | Without Redirect | With Redirect |
|---|---|---|
| Existing subscribers | Stop receiving episodes | Seamlessly continue |
| Directory listings | May go stale or duplicate | Update automatically |
| Reviews/ratings | Potentially lost | Preserved |
| Download numbers | Reset to zero | Continuous |
Redirect timing considerations:
| Phase | Redirect Status |
|---|---|
| Preparation | Set up new feed, verify content |
| Migration | Activate redirect on old host |
| Transition (2-4 weeks) | Both feeds "active" via redirect |
| Completion | Safe to reduce old host plan |
| Archive | Keep redirect active indefinitely |
The cardinal rule: Never cancel your old hosting account until redirects are in place and verified. Keep the redirect active for at least several months—some apps update slowly.
How to Use This in Dispatch
Set up 301 redirects when migrating from another host in Settings → Migration:
Migration tools:
- Import your existing podcast from another host
- Automatic RSS parsing to preserve episodes
- GUID preservation to prevent duplicates
- Redirect verification tools
Redirect configuration:
- Import your podcast from old host
- Verify all episodes imported correctly
- Configure redirect on your old host (they provide instructions)
- Use our redirect checker to verify it's working
- Monitor for any issues during transition
Redirect verification: We provide tools to test that your old feed URL properly redirects to your new feed and that directories are following the redirect.
Migration timeline:
- Day 1: Import complete, redirect active
- Week 1-2: Most apps follow redirect
- Month 1: Nearly all subscribers transitioned
- Ongoing: Keep redirect active on old host