Distribution
What podcast distribution actually involves
Publishing a podcast is easy. Being findable on the platform your listener already opens is a different job, and it is the one that decides whether the work gets heard.
A podcast is not a file. It is a feed, and the feed is the product.
That distinction is the whole of podcast distribution, and almost everyone meets it the hard way. You record an episode, upload it somewhere, send the link to a WhatsApp group, and wonder why the audience does not grow. The link worked. The episode played. Nothing compounded, because a link is a one-time event and a feed is a standing instruction.
What a feed actually does
A podcast feed is a text document that lists your episodes. Every listening platform reads it on a schedule. When a new episode appears in the feed, the platform collects it and puts it in front of everyone who subscribed. You publish once. Eight platforms update themselves.
This is why the feed matters more than any individual episode. It is the only thing a platform knows about you. If it moves, breaks, or belongs to someone else, your back catalogue and your subscribers go with it.
Three practical consequences follow, and they are the ones worth planning around.
The feed should live in an account with your name on it. Not a studio’s account, not an editor’s, not an agency’s. This sounds obvious until you want to move, and discover that moving means asking someone else for a password. We build the feed in the client’s own account every time, which occasionally costs an awkward early conversation and has never once been regretted.
Submission happens once per platform. Each listening platform needs the feed submitted and verified. That is a one-off job, and it is boring: forms, confirmation emails, a review wait of a few days. Then it never needs doing again. Most independent podcasts are on one or two platforms, not because the others rejected them, but because nobody did the boring part.
The catalogue follows the feed. Submit after fifty episodes and all fifty appear. This is worth knowing if you have been publishing to one platform for a year and assume you have missed the window. You have not.
The part that differs across two markets
Now the corridor question, because this is where a default setup quietly fails.
If your audience is split between Canada and Ghana, your listeners are not using the same apps. Apple Podcasts is a reasonable default assumption in Toronto. It is a poor one in Accra, where the phone is more likely to be Android and the app more likely to be Spotify or YouTube. A show distributed to the platforms a Canadian agency thinks of first will be invisible to half its intended audience, and the analytics will not say so. They will just show lower numbers.
So the platform list is not a formality to be copied from a template. It is a decision that follows from where people actually are.
Two more differences matter in the same direction.
File size is a cost, not a detail. On metered mobile data, a 90MB episode is a real decision for a listener and a 30MB one is not. Spoken word compresses well, and the difference between a carelessly exported file and a correctly exported one is often two thirds of the size at no audible loss. That is not audiophile fussiness. It is the difference between someone downloading your back catalogue and someone downloading one episode.
Many listeners will arrive through a share, not a subscription. A link forwarded in a WhatsApp group is the dominant discovery path in a lot of the world, and it lands on whatever page the link points at. If that page is a platform’s web player, the listener meets the platform’s branding, the platform’s recommendations, and a prompt to install an app. If it points at your own site with a player on it, they meet you. Both should exist. Only one of them is yours.
Why the site and the feed belong together
This is the argument for not treating a podcast as separate from the website, and it is the mistake we see most often.
A show distributed to eight platforms and a site with no player is two assets that do not help each other. The site cannot prove the work is any good, because proving it means sending the visitor somewhere else. The podcast cannot capture anyone, because a platform is not going to hand you an email address.
Put a player on the site and the two start compounding. A first-time visitor can hear the work in the first ten seconds without installing anything or leaving. Someone who arrives from a shared link lands on your domain, where the next thing they see is yours to decide. The archive becomes something you own rather than something you rent.
For one spoken-word artist we work with, listening had to come before reading on every screen, because his audience needed to hear the work before they would trust it. The site is built around that order. It is not a design preference. It is what the distribution made obvious.
What to ask before you start
If you are commissioning this, four questions will tell you most of what you need to know about whoever is doing it.
Whose account will the feed live in? If the answer is not yours, ask what happens when you leave.
Which platforms, and why those? A list that is not justified by where your audience is, is a list copied from somewhere else.
Who publishes episode fifty? If the answer is the agency, you have bought a dependency rather than a capability. The publishing workflow should be something you can run on a Tuesday afternoon without calling anyone.
What happens on the website? If nothing, half the value is sitting unused.
None of this is technically hard. It is mostly patience, a few forms and one decision about ownership made early rather than late. But it is the difference between a podcast that exists and one that is actually findable, and that difference is almost entirely made in the first week.