A podcast RSS feed is a plain XML file with one channel block describing the show and a stack of item blocks, one per episode, each carrying an enclosure tag pointing straight at an audio file on a server somewhere. Apple Podcasts, Spotify, YouTube Music and every other app do not store your episodes themselves. They read that one file, follow the enclosure link to fetch the audio, and check back on a schedule for new items. Understand that mechanism and most of what confuses people about hosting or losing a feed stops being mysterious.
This guide covers what a feed actually contains, the itunes namespace tags directories rely on, a few Podcasting 2.0 tags worth knowing, and the part that causes real damage when it goes wrong: moving a show to a new host without the redirect that keeps subscribers attached. If you have not picked a host yet, choosing a podcast hosting platform and starting a podcast from scratch are worth reading alongside this one.
How an RSS Feed Actually Works
RSS stands for Really Simple Syndication, the same RSS 2.0 standard blogs have used since the early 2000s, extended with extra vocabularies layered on top. Every feed is one XML document with a single rss root element, and inside it sits exactly one channel representing the show: title, description, language and cover image. Nested inside sit the item elements, one per episode. No separate database, no hidden API, no proprietary format. The whole show lives inside this one text file, usually just called the feed.
A real feed carries more than this minimum, categories, episode artwork, season and episode numbers, but stripped down to what actually works, a channel wrapping one episode's worth of RSS looks close to this:
The Episode Item and Its Enclosure Tag
Each item needs very little to be technically valid, but one tag does all the real work: a title, a permanent guid, and an enclosure. The enclosure is the pointer: a url attribute pointing at the audio file, a type such as audio/mpeg, and a length giving the file's size in bytes. An app's play button reads that one tag and fetches whatever sits at that url. Only the enclosure actually plays audio.
- <rss version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">
- <channel>
- <title>The Night Shift</title>
- <description>Stories from people who work while the rest of us sleep.</description>
- <language>en-us</language>
- <itunes:image href="https://cdn.example.com/night-shift/cover.jpg"/>
- <item>
- <title>Episode 14: The Long Drive</title>
- <guid isPermaLink="false">night-shift-ep14-7f3a</guid>
- <pubDate>Mon, 16 Nov 2026 19:00:00 +0000</pubDate>
- <enclosure url="https://cdn.example.com/night-shift/ep14.mp3" type="audio/mpeg" length="28451200"/>
- <itunes:duration>1801</itunes:duration>
- </item>
- </channel>
- </rss>
A few details matter more than they look. The guid is not the audio file's URL; isPermaLink="false" tells apps to treat it as a stable identifier, so renaming the file later does not change the episode's identity. itunes:duration here is plain seconds, the format most hosts output automatically. The enclosure's length is the file's byte size, not its running time, a detail that trips up anyone hand-typing a feed.
The itunes Tags Most Platforms Actually Rely On
The itunes namespace, declared once in the feed's opening rss tag as xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd", is what turned plain blog syndication into something that could run a podcast directory. Apple built it for Podcasts Connect, and because every app had to interoperate with what Apple expected, most directories simply read the same tags. At show level, title, description, link and language sit alongside required itunes:category, itunes:explicit and itunes:image, with itunes:author, podcast:locked and podcast:guid recommended. At episode level the required list is shorter: title, enclosure and guid, with description, pubDate and itunes:duration recommended. A missing required tag does not vanish overnight, but it commonly fails validation or gets flagged later.
None of this means writing these tags by hand. Every mainstream host, Libsyn, Buzzsprout, Transistor, Captivate, Podbean, Spotify for Podcasters and the rest, generates this XML from your dashboard and regenerates it the moment you publish or swap cover art. Upload an episode and set a title, and the host writes a new item, assigns a guid, measures the file's length and duration, and slots it into the feed. That automation is also why the file stays reliable across hundreds of episodes: a person maintaining that many items by hand is where most invalid-XML problems come from.

Why Podcasting Has No Central Platform, Just RSS
The line that confuses people until they have moved a show once: podcasting has no central platform. There is no single company a show is registered with, the way a YouTube channel lives inside YouTube's own database. A podcast is just a feed URL. Apple Podcasts, Spotify, YouTube Music, Pocket Casts and Overcast are, from the feed's point of view, simply clients: each fetched your feed's address once at submission, and each quietly re-checks it on its own schedule afterward. None of them store your episodes; they cache what the feed told them and refresh that cache periodically.
That architecture has a practical payoff: you own the feed URL, not any directory, and as long as it keeps resolving to a valid feed, you can move the hosting behind it to a different company without losing a subscriber, provided the move is done correctly. Choosing a podcast hosting platform covers feed portability across today's major hosts; every reputable one supports importing and exporting a feed, because the mechanism, an RSS document and a redirect, is the same open standard everywhere.
Moving Hosts Without Losing Subscribers
The order matters, because getting it wrong is how shows quietly lose their audience. First, unlock the old feed if it carries a podcast:locked tag, which some hosts set by default to stop unauthorized imports. Second, the new host imports the feed: every enclosure url and every item guid must carry over unchanged, since an app that sees a changed guid on an old episode can treat it as newly published and push it to every subscriber at once. A show-level podcast:guid tag exists so a show keeps one identity across the move. Third, add an itunes:new-feed-url tag in the old feed and set its server to return a permanent 301 redirect. Apple's documentation says both should stay at least four weeks, with the original guids maintained exactly.
The redirect is the whole migration
The redirect is not a courtesy, it is the mechanism. Every subscriber's app has your old feed URL saved from the day they subscribed, and keeps checking that exact address unless something there tells it, authoritatively, where to go next. Skip the redirect and you have not moved your show. You have published a second, empty one next to a copy nobody's app will ever check again.
Google's own retirement of Google Podcasts in 2024, when the app shut down and listeners were pointed at YouTube Music, illustrates the same principle in reverse: a directory can disappear and a show built on an open feed does not disappear with it. Shows that had submitted to Google Podcasts kept existing exactly as before everywhere else, because no other app depended on Google's app continuing to exist. A feed outlives any single directory, which is the point of an open standard rather than one company's platform.
Common Feed Problems That Break Distribution
Most feed problems fall into a small number of repeat offenders, invisible until a directory's own parser chokes on them, because a feed that looks fine in a browser can still be broken XML underneath.
- Invalid XML. An unescaped ampersand, writing "Rock & Roll" instead of "Rock & Roll", is among the most common parse failures reported in Apple's own support community.
- A missing required tag. Apple checks for itunes:category, itunes:explicit and itunes:image at show level, and title, enclosure and guid on every item; drop one and a submission can fail.
- A changed feed URL with no redirect. Letting the old address go dark instead of a 301 plus itunes:new-feed-url is the single most avoidable way to lose an audience overnight.
- Changed episode guids during a migration. Fresh guids on existing episodes make apps see every old episode as newly published, flooding subscribers with re-downloads.
- A locked feed nobody remembers setting. podcast:locked stops someone stealing a show, but it also blocks your own new host from importing it until set back to no.
- A server that blocks crawlers. A self-managed server that rate-limits requests, or fails to support byte-range requests some apps rely on, fails intermittently.
Running a feed through more than one validator before publishing catches most of this early. Apple publishes its own validator inside Podcasts Connect, and independent tools such as Castos's free validator check for the same failures, though the two do not always agree. The deeper fix is rarely to hand-edit XML at all: a well-built host validates this file on every publish, which is why a show's choice of host matters more once years of back catalog ride on it.
How Directories Actually Re-poll Your Feed
Submitting a show is a one-time event. After that, each directory periodically requests your feed's URL again and compares the result to what it already has. Apple's documentation says its systems check feeds routinely and that a detected change should typically appear within about 24 hours, with a manual Refresh Feed option for when it has not. In practice it often runs faster: Podnews has reported Apple's crawler checking its feed roughly every eight minutes on one day, up from roughly two hours measured earlier. Other directories run their own schedules, so an episode can appear on one app within minutes and take hours longer on another, which is also why a feed mistake can look like several different problems depending on the app a listener happens to use.
None of the apps above read a proprietary format. The same open vocabulary that makes a feed portable between hosts is also what makes it readable by apps nobody at Apple or Spotify had to approve in advance, which is exactly the opening the next, optional set of tags builds on.
The Podcasting 2.0 Tags Worth Knowing
The itunes namespace has not meaningfully changed in years, which is part of why Podcasting 2.0, led by the nonprofit Podcast Index, has spent several years adding a separate podcast namespace on top of the same feed, declared as xmlns:podcast="https://podcastindex.org/namespace/1.0". None of these tags are required anywhere, and most mainstream directories ignore the ones they do not support, which is exactly why adding them is low risk: a tag nothing reads does nothing, and a tag one app reads gives that app's listeners something extra.
podcast:value: Paying a Show Directly, Per Listen
podcast:value, placed on the channel or an item, sets up a payment destination for direct, listener-to-creator micropayments over the Bitcoin Lightning Network, what the Podcasting 2.0 community calls value-for-value. It carries a required type attribute, almost always lightning, a required method such as keysend, and holds one or more podcast:valueRecipient children that split a payment by percentage across a host, co-hosts or a producer. An item-level tag overrides the channel-level one, letting a show route a sponsor's cut differently on one episode. A handful of apps, Fountain among them, stream these payments in real time; most mainstream apps ignore the tag.
podcast:chapters: Clickable Chapters Without Touching the Audio File
podcast:chapters sits on an item and points, through a required url attribute, at a separate JSON file holding chapter titles, start times and optional images, with type set to application/json+chapters. Because the chapter data lives outside the audio, a podcaster can add or fix chapters after publishing without re-uploading anything, and a supporting app can show chapter art without parsing ID3 tags out of an MP3. A full walkthrough of adding chapters covers the file format itself; this tag is just the pointer.
podcast:transcript: One Tag Per Transcript File or Language
podcast:transcript also sits on an item, and one episode can carry several: plain text, the same transcript as WebVTT or SRT captions, a translated version, each with its own url and matching type. An optional language attribute marks which language a file is in, and rel="captions" tells an app the file includes timecodes for display as closed captions. Apple Podcasts reads this tag directly and displays a submitted transcript, an easier path to accessible show notes than a hand-built page, and the same need connects show notes that rank in search to carrying a show into other languages.
↗ Try the tool
Auto Clean Up
None of this plumbing matters if the audio sitting behind the enclosure tag is inconsistent, noisy or mistagged. Auto Clean Up cleans breaths, dead air and uneven levels across a whole batch of episodes before you publish, so the file your feed points listeners at is the same clean, correctly leveled take every time, whether an app fetches it the day you publish or pulls it out of a four-year-old back catalog entry after a feed migration.
Open Auto Clean Up →Frequently Asked Questions
Do I ever need to edit my podcast's RSS feed by hand?
Almost never. Every mainstream host generates and updates the file from your dashboard. The narrow cases where podcasters touch raw XML are adding a Podcasting 2.0 tag their host does not yet support, or setting up itunes:new-feed-url and a 301 during a self-managed migration.
Do Apple Podcasts and Spotify read the same feed?
Yes, the same one. There is no Apple-specific or Spotify-specific feed; you submit one URL to each directory once, and each independently polls it afterward. Differences in how a show looks between apps come from display choices, not from different data being sent to each one.
How fast does a new episode actually show up after I publish it?
It varies and is rarely instant. Apple says a change should typically appear within about 24 hours, with a manual refresh option for when it has not, while Podnews has measured Apple's crawler checking a feed roughly every eight minutes on some days. Other directories run their own schedules.
Will I lose subscribers if I switch podcast hosts?
Not if the migration happens in order: unlock a podcast:locked feed, import every episode with guids unchanged, then add itunes:new-feed-url and a permanent 301, leaving both for at least a month. Lost subscribers almost always mean a redirect was skipped or removed too early.
Do I need Podcasting 2.0 tags for my show to work normally?
No. The itunes tags are what every mainstream directory checks for; the podcast namespace tags for value-for-value, chapters and transcripts are optional extras a growing number of apps support but no major directory requires.
How do I check whether my feed is actually valid before something breaks?
Run it through more than one validator, since different tools catch different problems. Apple publishes its own validator inside Podcasts Connect, and independent tools such as Castos's free RSS feed validator check for the same common failures. None guarantee perfect display, but they reliably catch markup broken enough that a feed cannot be read at all.
Sources and Further Reading
- Podcast Standards Project, PSP-1 Podcast RSS Specification: required and recommended tags, the itunes namespace declaration, and enclosure attributes.
- Podcastindex.org, Podcast Namespace specification: the Podcasting 2.0 tag set, including podcast:value, podcast:valueRecipient, podcast:chapters and podcast:transcript.
- Apple Podcasts, Content Requirements: technical requirements for a podcast feed, including enclosure tags and byte-range support.
- Apple Podcasts, Change the RSS feed URL: itunes:new-feed-url, the 301 redirect, the four-week minimum, and the guid-preservation warning.
- Apple Podcasts, Validate your podcast RSS feed: Apple's validation process and common failure categories.
- Apple Podcasts, Refresh a podcast: routine feed checking and the manual refresh option.
- Podnews, Apple Podcasts brings back the 'refresh' button: the crawler-frequency observations cited in the polling section.
- Castos, Free RSS Feed Validator: an independent validator referenced in the feed-problems section.
- TechCrunch, Google Podcasts to shut down in 2024: a directory disappearing without affecting a show's own feed.
- VoiceEditSuite, Choosing a Podcast Hosting Platform in 2026 and Dynamic Ad Insertion: companion guides.
