The right Spotify setup depends on how your show is distributed. Check the podcast's existing connection before following a sign-in tutorial or changing any feed settings.
Identify and link the existing show
- Select the correct podcast and open Podcast Settings → Integrations.
- Check which connection the podcast uses: legacy Spotify, Spotify Distribution, or Megaphone.
- For an existing Spotify listing, use the supplied Spotify show URL in the existing-show connection flow and verify the show name before linking it. Do not create a second show or disconnect a working integration just because a tutorial shows a different screen.
Spotify for Creators and Megaphone-hosted feeds may need a migration-specific path. Do not use a direct Spotify Distribution RSS import for those hosted feeds; ask support to confirm the right migration route.
Follow the connection you have
Legacy Spotify: Use its connection flow only if that is the setup shown for your podcast. Sign in with the account that has access to the intended show. Review any requested access and terms in the actual flow.
Spotify Distribution: Read the connection card's status and setup instructions. It distinguishes a live show, setup in progress, a show waiting for its first episode and disabled distribution. A genuinely new show may wait for the first episode to be published. If you already have a Spotify show and the status is unexpected, ask support to check the association before proceeding.
Megaphone: Follow the setup for that integration rather than the legacy Spotify sign-in sequence.
Verify the connection
After setup, inspect the episode's Spotify status and open the linked show to confirm it is the intended listing. A connection status or colored icon alone does not confirm every episode is live.
Do not switch hosting, replace a feed URL, reset a redirect or delete a duplicate-looking show as a general connection fix. Those actions can affect the existing catalog. Give support the Flightcast podcast, existing Spotify show URL and exact status or error so they can verify the connection and migration path.