Substack podcast import, then 301 the old feed
After importing a podcast into Substack, submit the new feed to directories and 301 the old host's feed so the audience moves with you instead of starting from zero again.
Why this can grow a startup
Content migrations often copy the archive and forget the distribution plumbing. Substack's podcast-import guide keeps the real job in view. Importing the back catalog is only the first half. The publication still has to tell podcast directories about the new feed and ask the old host to redirect listeners through a 301. That is the difference between a clean handoff and a fake relaunch where the archive looks complete but the audience is stranded.
Company example
Substack's podcast migration guide says publishers should submit the new feed to podcast directories and ask the previous host to redirect listeners with a 301 permanent redirect after import.
Source and metric
Source: Substack Support: How do I move my podcast to Substack?
Substack explicitly calls for 2 post-import steps: resubmit the new feed to directories and set a 301 redirect from the old host.
When to use it
Use this when Substack, Distribution, Retention is relevant to substack, podcast migration, feed redirect and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Substack Support: How do I move my podcast to Substack? and identify what is directly supported.
- Choose one channel context: Substack, Distribution, Retention.
- Define the test around Substack explicitly calls for 2 post-import steps: resubmit the new feed to directories and set a 301 redirect from the old host..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.