The RSS feed: boring technology that runs podcasting
7cubit Team
More in Podcasting
When a podcast app shows your episode, it usually got the information from an RSS feed. The feed tells the app what the show is called, which episodes are public, and where the audio file can be fetched. It is not exciting, but it is why one published episode can reach multiple directories without a separate upload every week.
In Podcast Studio, the feed lives under Distribution. The useful questions are what it contains, why drafts stay out, and how to copy the URL when a directory asks for it.
Find the feed in Distribution
Open Podcast Studio and choose Distribution. Under RSS Feeds, find the card for your show. Use the copy icon to copy the URL, or the open icon to inspect the feed in a browser.
If the URL is not shown yet, save the show with a valid RSS slug and complete the show settings. The feed address is generated from that setup; it is not a URL you need to invent or type from memory.
What the feed contains
At the show level, the RSS feed carries identity information such as title, description, cover art, category, language, and the explicit flag. Directory apps use those fields to catalogue the show and display its public listing.
At the episode level, a published item includes a title, description, publish date, duration, and an audio enclosure. When an episode has them, the feed can also expose a transcript link and chapter markers. That is how a navigation feature can travel with the episode instead of staying inside one player.
Show setup is therefore part of distribution. A strong episode cannot compensate for an empty description, an unsuitable category, or cover art that was never added to the Show.
Why only published episodes appear
Draft and scheduled episodes do not appear in the public feed until they go live. This keeps half-finished work out of listening apps. It also explains the common “my episode is missing” report: the episode may be edited and saved, but it has not been published.
Publishing is the handoff from private production to public distribution. A Web Studio recording bridged into Podcast Studio, a draft cut in the Editor, or a chapter list waiting for review is not yet a feed item. If a directory does not show an episode, check its publish state before rebuilding the show.
Boring is a feature
Feeds are read by many clients, cached, and interpreted with slightly different tolerances. Stable enclosures, complete metadata, and clear episode titles are more useful than clever workarounds. The feed should be predictable enough that you can publish, then return to making the next episode.
That does not mean distribution is automatic in every direction. The feed is the underlying artifact. Spotify connections and Apple’s submission flow sit on top of it, and each platform can have its own timing or requirements.
How Distribution fits the workflow
Distribution is where you find the RSS URL, the Spotify connection, and Apple submission tools. The same feed address can be copied into Apple Podcasts Connect during a self-serve submission. Once a show is approved, new published episodes can travel through the feed.
Keep the source of truth simple: finish the episode in Podcast Studio, publish it when it is ready, and use the feed to understand what directories can read. A platform button is convenient; knowing what the feed says is how you diagnose the edge cases.
RSS is shared infrastructure. It stays useful because the show is portable instead of trapped in one player.
Copy the URL from Distribution, publish only finished work, and keep the show fields honest. That covers most of the work this deliberately quiet technology does.
RSS feed checklist
- The Show has a title, description, cover art, category, language, and explicit setting.
- The episode is published rather than still a draft or scheduled item.
- The feed contains a stable audio enclosure and the episode metadata you expect.
- The URL was copied from Podcast Studio's Distribution area rather than typed by hand.