A podcast host stores audio and publishes an RSS feed that podcast apps can read. That sounds simple. The difficult parts appear when you migrate an old show, publish in two languages, interpret listening data or restrict an episode to paying members.
These are the parts worth checking before choosing a tool.
The RSS feed is what apps consume
Your website and RSS feed serve different audiences. The website is for people. The feed contains structured show details — title, description, cover, author, category and language — followed by episodes and their audio enclosures.
Each episode needs at least:
- a stable identity (GUID)
- title and publication time
- a working audio URL
- the correct media type and file size
- a description or show notes
- an explicit-content value where relevant
If an old episode changes identity during migration, an app may treat it as new. A sound import therefore preserves the original GUID values.
Audio needs dependable delivery
Podcast apps often download large files over mobile networks and in the background. The essential feature is not an elaborate editor inside the host. It is a correctly described file at a URL that keeps working.
Check upload limits as well. Long recordings should be able to go directly into media storage instead of passing through a small web request limit.
Migrate without starting over
A safe move has four steps:
- Read the existing RSS feed and preview what was found.
- Import show data, episodes, audio and original GUIDs.
- Check several old and recent episodes in the new feed.
- Redirect the old feed to the new address once the result is verified.
Do not close the old host before the redirect works. Directories and listener apps need time to discover the change.
A download is not the same as a person
Podcast measurement normally starts with requests for the audio file. A directory may probe the link without a listener, and one person can fetch an episode several times.
A useful report should exclude technical HEAD requests and state its unique-listener rule, such as counting at most once per episode per day. Treat app and country as delivery breakdowns, not exact audience demographics.
Public and premium require separate access paths
A public RSS feed is anonymous. Anything inside it can be fetched by anyone with the address. A premium episode therefore needs more than a locked badge in an app — its audio URL must stay out of the public feed.
Link premium audio to a paid product or membership and deliver it after sign-in. Decide what happens when access expires as well.
Should podcasting share a platform with the business?
A standalone podcast host is enough when the show is only a free public channel. A connected platform becomes more useful when the podcast should also:
- collect email addresses on its own page
- lead into a course or membership
- include premium episodes
- share accounts and access with other products
- trigger email and follow-up
Idun Blue can import or host a podcast, publish an RSS feed, measure downloads and link premium episodes to a product. See how podcast hosting works.