Every podcast host stores your audio files and builds an RSS feed for Spotify, Apple Podcasts and the other apps. The differences show when you move a show with a year of old episodes, try to make sense of the listener numbers, or lock an episode for people who have paid.

The RSS feed is what the apps read

Your website and your RSS feed are two different things. The website is for people. The RSS feed is a list the apps read: the show’s name, description, cover art, who makes it, category and language, followed by every episode with a link to its audio.

Each episode needs at least:

  • its own ID that never changes
  • a title and publication date
  • a link to the audio file
  • the right file format and file size
  • a description or show notes
  • an explicit-content flag, where it applies

If an old episode gets a new ID in the move, podcast apps may treat it as new, and your whole archive can turn up as freshly published for your listeners. A good move keeps every episode’s ID.

The audio file has to download every time

Podcast apps often download large files in the background, over mobile data. A clever editor inside the host matters less than a file in the right format, at the right length, on an address that keeps working.

Check how large a file you can upload. A two-hour conversation should upload without stalling halfway.

Moving your podcast from another host

A safe move has four steps:

  1. Read in your current RSS feed and see what was found before anything moves.
  2. Bring over the show’s details, the episodes, the audio and the episode IDs.
  3. Listen to a few old and a few recent episodes in the new feed.
  4. Redirect the feed at your old host to the new address once everything checks out.

Don’t close the old account until the redirect works. Podcast directories and listeners’ apps need time to notice the change.

Downloads and listeners in your statistics

Podcast statistics usually count how many times the audio file was fetched. A directory may check the link without anyone listening, and one person can download the same episode several times.

A good report doesn’t count bots as listeners and has a clear rule for what a listener is, such as at most once per episode per day. App and country give a rough picture of where your listeners are, not an exact picture of who they are.

Premium episodes for paying listeners

An ordinary RSS feed is open: anything in it can be fetched by anyone with the address. A premium episode needs more than a “locked” label in an app, because its audio must not be in the open feed at all.

Connect the premium episode to something you sell, a course or a membership, and let her listen once she has logged in. Decide, too, what happens when her access ends.

A standalone host, or the podcast next to your courses

A standalone podcast host is enough when the show is a free channel out. Keeping it with your courses and email becomes more useful when the podcast should:

  • collect email addresses on its own page
  • lead to a course or membership
  • include premium episodes
  • share a login and access with what you sell
  • start emails and follow-up

In Idun Blue, your podcast gets its own RSS feed for Spotify, Apple Podcasts and the other apps, and you can move it in from services such as Acast, Libsyn or Buzzsprout without uploading episodes one by one. Premium episodes are connected to what you sell and played in the member app, not through a private RSS feed. See how podcast hosting works.