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.
Source-backed 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-reported evidence
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.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Substack and Distribution, using evidence from Substack Support: How do I move my podcast to Substack? as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.