Online Tool Store
· 4 min read
How to Ship a Podcast Episode Cleanly
Manesh Jayawardhana
CIO & Co-founder
The episode goes out with the wrong episode number, no chapters, and a description that still says “TODO: write this”.
Two of those can be fixed and will take days to propagate to everyone. The third is fine because nobody reads descriptions, right up until someone does.
Metadata is hard to change after publishing
Podcast apps cache feed data. Correcting a title, a description or an episode number after publishing means the fix reaches people whenever their app next refreshes, which varies from minutes to never.
Some listeners will keep the original version indefinitely. Some apps store the original at first download and never update it. For an episode number in particular, that means a permanently wrong entry in someone’s library.
Which makes the pre-publish checks the ones that matter. Everything on that list is cheap before and expensive after.
| Item | Before publishing | After |
|---|---|---|
| Episode number | Trivial | Permanently wrong for some |
| Title and description | Trivial | Days to propagate, incomplete |
| Chapters | Part of the export | Requires re-upload |
| Transcript | Cheap | Retrofitting a catalogue is expensive |
Transcripts and chapters before publishing
Both feel optional at the moment of publishing, and both are much more work to add later.
Transcripts make episodes searchable, serve listeners who cannot use audio, and provide text you can reuse for show notes, social posts and search visibility. Produced as part of the release they cost a few minutes of cleanup on an automated draft. Retrofitted across two hundred episodes they are a project.
Chapter markers let listeners skip to sections and give the episode structure in the player. Added at export they are part of the workflow; added later they require re-uploading the audio, which for some hosts means a new file and the GUID risk that comes with it.
The pattern is the same for both: cheap when it is part of the process, expensive as a retrofit. That is an argument for putting them in the pre-publish group even though nothing breaks without them.
Group the checklist by phase
A flat list of twenty-three items gets partially completed. Three groups get worked through.
Pre-publish — audio final, loudness checked, metadata correct, chapters embedded, transcript ready, artwork correct, description written, episode number verified.
Publish — upload, check the feed updated, verify it appears correctly in at least one directory.
Post-publish — social posts, newsletter, notify any guest, add to the website, update any index.
The middle group takes two minutes and catches the errors that matter. Checking the feed actually updated, and that the episode looks right in one app, is the step that finds a broken upload before listeners do.
The post-publish group is the one that gets abandoned
Everything before publishing has an obvious forcing function — the episode cannot go out without it.
Everything after has none. The episode is live, the work feels finished, and promotion becomes optional in a way it was not intended to be.
Two things help. Keeping the post-publish list genuinely short, so it is three items rather than nine. And doing the parts that can be prepared in advance — drafting the social post while writing the show notes, when the material is already in your head.
A guest notification is the item most worth protecting. A guest who is not told their episode is live cannot share it, and they are usually the largest single source of new listeners for that episode.
Common mistakes to avoid
- Publishing before checking the episode number.
- Treating transcripts and chapters as post-publish tasks.
- Not verifying the feed updated and the episode renders correctly.
- A flat checklist that gets abandoned halfway.
- Forgetting to tell the guest.
How to do it with Episode Release Checklist
The Episode Release Checklist groups tasks by phase.
- Choose what your show actually produces so the list has no steps you skip.
- Complete the pre-publish group fully — these are the expensive ones to fix later.
- Verify the feed and one directory before moving on.
- Keep the post-publish group short enough that it happens.
Other planning tools are in the tools directory.
Frequently asked questions
What gets forgotten most?
Chapter markers and transcripts, because both feel optional at publishing and are far more work to add later. Episode numbering and telling the guest are close behind.
Why does metadata matter after publishing?
Because apps cache feed data, so a correction takes days to propagate and some listeners keep the original permanently. Getting it right beforehand is much cheaper.
Should transcripts be part of the release?
If you can. They make episodes searchable and serve listeners who cannot use audio. Produced at release they cost little; retrofitted across a back catalogue they cost a lot.
Final thought
Put the transcript and the chapters in the pre-publish group. Nothing breaks without them, and adding them later costs ten times as much.