What Is a Podcast RSS Feed?
One file, hosted by you, that every app on earth copies from. Lose control of it and you lose the audience.
A podcast RSS feed is a single XML file that lists your show and every episode in it. Apple Podcasts, Spotify, Overcast and the rest do not store your audio. They read this one file on a schedule and copy what they find.
That is the whole architecture, and it has a consequence most people only discover at the worst moment: the feed is the show. The directories are windows onto it.
When you submit a podcast to Apple, you are not uploading anything. You are handing over a URL and asking Apple to check it periodically. When you publish a new episode, your host rewrites the file and the apps notice on their next visit.
So the file is the product, the directories are distribution, and the audio host is a vendor you can replace.
The reason this matters more than it sounds is what happens when you change podcast hosts.
Your subscribers are not stored in Apple or Spotify. Each listener's app holds a feed URL and checks it. If that URL stops working, or starts returning somebody else's show, every one of those apps quietly stops delivering your episodes. No message is sent to the listener. The show simply goes silent in their library.
This is why moving hosts is done with a redirect and not with a re-upload. The old feed URL has to answer with a permanent redirect pointing at the new one, and it has to keep answering that way for months, because podcast apps check on their own unhurried schedule and a dormant listener's app might not look for weeks.
Hosts that make this hard are making it hard on purpose. A host that will not let you set a redirect on the feed you are leaving is holding your audience, not your files.
The defensive move is to publish the feed on a domain you control and point it at whatever host you currently use. Then the host is genuinely replaceable and the apps never see a change.
What is actually inside the file
Open a podcast feed in a browser and you get XML, which looks forbidding and is not.
The top of the file describes the show once: title, author, description, language, cover art URL, and the categories the directories use to file you. Apple reads the artwork and the categories from here, which is why changing your cover art is a feed edit and not an upload.
Below that is one block per episode. Each block carries a title, a publication date, a description, a duration, a unique identifier, and the thing that makes it a podcast rather than a blog post: an enclosure pointing at the audio file, with its URL, its type and its size in bytes.
That enclosure URL is where the audio actually lives. The app fetches it directly from your host. Apple never touches the file.
Why Apple and Spotify do not host your episodes
It would be cheaper for you if they did, and they do not, for a reason that works in your favor more often than against it.
Because the directories only read a pointer, no directory can hold your show hostage. If Apple removed your podcast tomorrow, Spotify and every independent app would continue to serve it, because each is reading the same file independently.
It also means your download numbers are yours. The request for the audio file hits your host, so your host counts it. Spotify reports what happened inside Spotify, but the feed-level count covers everyone.
The exception worth knowing is that Spotify and YouTube have both built ingestion paths that copy audio into their own systems for some shows. When that happens, those plays stop appearing in your host's numbers and start appearing only in theirs, which is the beginning of the audience moving out of your file and into their platform.
Finding your own feed URL
Every host exposes it, usually under a heading like Distribution, Settings or Feed.
If you cannot find it there, you can pull it out of Apple Podcasts. Apple's public lookup service will return the feed URL for any show by its Apple ID, and the Apple ID is the long number at the end of the show's Apple Podcasts link.
A faster sanity check: paste the feed URL into a browser. If XML appears, the feed is live. If you get an error page, or a login screen, the directories are getting the same thing and your show has stopped updating for everyone.
It is worth testing this occasionally rather than assuming. A feed that breaks does not alert you — it simply stops producing new episodes in people's apps, and the first sign is a download number that falls off a cliff.
The tags Apple will refuse you over
Apple is the strictest reader, so a feed that satisfies Apple satisfies almost everything else.
The cover art has to be square, at least 1400 by 1400 pixels, no larger than 3000, and in JPEG or PNG. Artwork that is slightly off-square is the single most common rejection.
The show needs an explicit-content flag, a category drawn from Apple's own list, a language code, and a valid owner email address. Apple uses that email to verify you control the show, so an address you cannot read is a submission that stalls.
Each episode needs a globally unique identifier that never changes. If your host regenerates identifiers — some do, after a bulk edit — apps treat every episode as new and your listeners get a notification storm for a back catalog they already heard.
What a download counts as here
A download is a request for that enclosure URL, and that definition is looser than it sounds.
The IAB's measurement guidelines exist precisely because the raw number is inflated: a partial fetch, a prefetch by an app that downloads automatically overnight, and a listener who actually heard the whole episode can all look identical in a server log.
Certified hosts filter on bytes delivered and deduplicate by listener and day. Uncertified counting does not, and the gap between the two numbers can be large.
This is the number sponsors ask for, which is why the certification matters commercially rather than academically. A sponsor comparing two shows is comparing two server logs, and they will discount the one that cannot say how it counted.
Treating the feed as the thing you own
The practical version of everything above is short.
Publish the feed at an address on your own domain. Keep the owner email on an account you will still read in three years. Before switching hosts, confirm the old host will serve a permanent redirect, and leave it in place far longer than feels necessary.
And check the file occasionally with a validator, not just with your own podcast app, because your app has probably cached a working copy and will keep showing you a show that the rest of the world can no longer see.
The show that survives a host going out of business is the one whose feed address never belonged to that host.
Questions people ask about podcast feeds
Do I need an RSS feed to publish a podcast?
Yes, for Apple Podcasts and most independent apps. Spotify and YouTube now accept direct uploads too, but a show that exists only inside one platform cannot be listed anywhere else.
Where do I get a podcast RSS feed?
Your podcast host generates it automatically when you create the show. You do not write the XML yourself unless you are hosting the files on your own server.
Can I change my podcast RSS feed URL?
You can, but only with a permanent redirect left on the old address. Without one, every existing subscriber's app keeps checking a URL that no longer answers and the show stops updating for them silently.
Why is my new episode not showing up?
Apps re-read the feed on their own schedule, often a few hours apart. If a day passes, check that the feed URL still returns XML in a browser and that the episode's publication date is not set in the future.
Is the RSS feed how downloads are counted?
Indirectly. The feed points at the audio file, and the request for that file is what gets counted by your host. Platforms that copy your audio into their own system count separately.
Does the feed hold all my episodes forever?
Most hosts include the full back catalog by default, but some trim the feed to a recent window to keep the file small. If old episodes vanish from apps, that setting is the first place to look.
Keep reading
- add plays to a podcast episode — Directories rank shows partly on how many people press play early, and you can add plays to a podcast episode while the feed is still finding its audience.
- what each platform decides to call a play — Every platform draws the line between a fetch and a listen somewhere different, and what each platform decides to call a play compares them.
- the thirty-second rule — Spotify's own threshold is stricter than a download, and the thirty-second rule explains what it does and does not pay for.