The feed is the podcast
There is no central place where podcasts live. Apple Podcasts does not hold your episodes. Spotify does not hold your show. What exists is one text file, at a web address your host controls, and every app in the world reads that file. That file is your RSS feed. Everything else, from the listing in Apple Podcasts to the download number on your dashboard, is a consequence of what is in it.
RSS stands for Really Simple Syndication, and the specification that defines it (RSS 2.0, maintained by the RSS Advisory Board) describes it as “a dialect of XML”: a structured text format with tags, the same family as HTML. A feed opens with a single <rss> element, which contains a single <channel>. The channel is your show. Inside it come the show-level facts, then any number of <item> elements, one per episode. Each item carries the episode’s title, description, date, a permanent ID and, in the <enclosure> tag, the address of the audio file. The audio itself is never in the feed; the feed points at it.
The RSS 2.0 spec was written for news headlines, so it says nothing about podcasts specifically. Podcasting works because the spec allows extensions “defined in a namespace”, and two namespaces do most of the work: Apple’s itunes: tags, which every app has read for years, and the newer podcast: namespace from the Podcast Index, part of the project its authors call “Podcasting 2.0”. Stripped to the parts that matter, a feed looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:podcast="https://podcastindex.org/namespace/1.0">
<channel>
<title>Your Show</title>
<link>https://yourshow.example</link>
<description>What the show is about.</description>
<language>en</language>
<itunes:image href="https://.../cover-3000.jpg"/>
<itunes:category text="Business"/>
<itunes:explicit>false</itunes:explicit>
<itunes:type>episodic</itunes:type>
<podcast:guid>917393e3-1b1e-5cef-ace4-edaa54e1f810</podcast:guid>
<item>
<title>Episode title</title>
<description>Show notes.</description>
<guid isPermaLink="false">a-string-that-never-changes</guid>
<pubDate>Thu, 06 Nov 2026 09:00:00 +0000</pubDate>
<enclosure url="https://.../ep-12.mp3"
length="41256320" type="audio/mpeg"/>
</item>
</channel>
</rss>Read that once and three things about podcasting become obvious. Distribution is the act of giving apps this URL. Measurement is the act of counting who asks for the file in the enclosure. And ownership is a question of who controls the URL at the top. The rest of this guide walks through each.
Where to find your feed
Your hosting provider generates the feed and publishes it. Every host shows the URL somewhere in the show’s settings or distribution page, usually labelled RSS feed, feed URL or distribution. Spotify for Creators documents its own under Settings and then Availability, created when you publish your first episode, and its help page is blunt about everyone else: “If you use another hosting platform, contact them to get your RSS feed.” We will not guess at other hosts’ URL patterns here; the dashboard is the authoritative place.
Two things to know once you have it. The feed is public by design: apps that have never heard of you will fetch it, and Spotify warns that the email address in it is visible to anyone with the link. And the URL is an asset. If it lives on your host’s domain, you depend on that host to redirect it if you ever leave; the section on moving hosts covers what that means.
If you want to see what the apps see without reading XML, paste the URL into PodLink’s free feed analyzer. It reads the feed and shows the show title and artwork, the episode count and the latest episodes, and whether an analytics prefix is already on the enclosure URLs. It never modifies the feed; it only reads it, the same way an app does.
What's inside that actually matters
A real feed has more tags than the skeleton above, and most of them are harmless. These are the ones that decide how your show looks, whether it passes validation, and whether episodes stay stable over time.
| Tag | Where | Why it matters |
|---|---|---|
<title> | channel and item | Required at the channel level in RSS 2.0 and by Apple; the show name and episode titles the apps display and search. |
<description> | channel and item | Required by RSS 2.0 at the channel level; Apple's validator rejects a feed without it. Item descriptions are your show notes. |
<itunes:image> | channel (and item) | Your cover art, as an href. Apple accepts 1400–3000 px square via RSS; Spotify falls back to it for any episode without its own art. |
<itunes:category> | channel | Apple's validator fails a feed with no category; Spotify says categorization is needed for its recommendations. Case-sensitive, ampersands escaped. |
<itunes:explicit> | channel and item | Apple requires true or false; Spotify also accepts yes, no and clean. Missing it is one of Apple's listed validation errors. |
<itunes:type> | channel | episodic (newest first) or serial (play oldest to newest), per Spotify's specification. |
<podcast:guid> | channel | A permanent ID for the show itself from the Podcast Index namespace, meant to follow the podcast across hosts and feed URLs. |
<guid> | item | The episode's permanent ID. Apps use it to tell new episodes from old; Apple says it must never change, even if the title or audio URL does. |
<enclosure> | item | The audio: url, length in bytes and MIME type. RSS 2.0 and Apple require all three; Apple ignores duplicate enclosure URLs. |
<pubDate> | item | Publish date in RFC 822/2822 format with a time-zone offset. Apple rejects other formats; Spotify uses it to order episodes. |
The enclosure
The <enclosure> tag is the reason RSS became the podcast format. The RSS 2.0 spec gives it three required attributes: url (where the file is), length (its size in bytes) and type (a MIME type such as audio/mpeg). Apple’s requirements repeat all three and add that each episode’s enclosure must be unique; Apple Podcasts “will ignore duplicate enclosure URLs”. Spotify’s specification requires url and type and treats length as optional.
Two kinds of GUID
The item-level <guid> is the episode’s permanent identity. The RSS spec says there are “no rules for the syntax of a guid”; it is a string, and the point is that it never changes. Apple is stricter in practice: every episode must have one, it must be unique, and it must stay the same even when the title or the enclosure URL changes. Where a host does not provide a GUID, Apple says it will use the enclosure URL instead, which means a changed audio URL becomes a new episode. Keep that in mind before you re-upload a file.
The channel-level <podcast:guid> is newer and does the same job for the show. The Podcast Index namespace defines it as a UUIDv5 generated from the feed URL (with the protocol scheme and trailing slashes stripped) and a fixed namespace, assigned once and then meant to “follow the podcast from then on”, even if the feed URL changes. You can recognise one by shape: 36 characters with four hyphens. If your host writes it into the feed, that value is canonical, and a new host is supposed to import it rather than mint a new one.
Dates and characters
Apple requires <pubDate> in RFC 2822 form, with the day of the week, a 24-hour time and a time-zone offset, and rejects formats like 7/6/2014 1:00:00 PM. Tags and values are case-sensitive (Kids & Family, not Kids & family) and an ampersand must be written &. Hosts handle this for you; it matters when you are reading a validator’s error message.
How Apple, Spotify and the other apps use it
You submit a feed URL to a directory once. That is the whole of “getting on” Apple Podcasts or Spotify: you tell them where the file is, they validate it, and from then on they re-read it on their own schedule. Publishing an episode is your host adding an <item> to the feed; every app notices in its own time.
How much time is the release-day question. Spotify’s delivery specification says that once it has subscribed to a podcast it will “check the feed URL for any metadata change several times per hour”, that it honours the feed’s last-modified and etag headers so it does not re-download needlessly, and that publishers should “allow for at least an hour” for a change to reach listeners. Its creator-facing help page says new episodes and edits can take up to 24 hours to appear everywhere. Apple does not publish a refresh interval on the pages we fetched, so we won’t invent one.
One Spotify detail matters more than it looks. The specification says podcast playout is “handled by Spotify”: it downloads your audio and serves it to listeners from its own infrastructure rather than fetching your file each time. It also notes that changing the audio or image binary without changing the URL will not trigger a new download. Two practical rules follow: a replaced file needs a new URL, and Spotify plays will not normally show up in any measurement that counts requests to your file. More on that below.
Smaller apps read the same file with fewer rules, which is why fixing something in the feed fixes it everywhere. For how the text in the feed is searched inside the apps, see the podcast SEO guide.
Artwork, category and the other show-level fields
The channel-level tags are set once and rarely touched, which is why they are so often wrong. Four are worth getting right before you submit anywhere.
- Artwork. Apple’s Show Cover spec is a 3000 by 3000 pixel square; when the art arrives via RSS, Apple accepts 1400 by 1400 up to 3000 by 3000 and says the largest is preferred. PNG or JPG, no transparency, no alpha channel. Spotify asks for a 1:1 image in the highest resolution you have. One 3000-pixel square, saved without transparency, satisfies both. The URL goes in
<itunes:image>; Apple also requires the server to answer HEAD and byte-range requests so the art and the audio can be fetched and streamed. - Category. At least one
<itunes:category>from Apple’s list, spelled and capitalised exactly as Apple spells it. Apple’s validator fails a feed with no category or an unsupported one; Spotify’s specification says the category is “needed for Spotify to perform recommendations”. Pick the category your listeners would browse, not the one with the least competition. - Explicit.
<itunes:explicit>must be present. Apple wants true or false; Spotify also accepts yes, no and clean. Missing it is on Apple’s list of validation errors. - Language and type. Apple requires a
<language>tag with a supported ISO code.<itunes:type>tells apps whether the show is episodic (newest first) or serial (meant to be heard in order), which changes how a new listener is dropped into your catalogue.
All of these are set in your host’s dashboard and written into the feed. If a change does not appear in the apps, check the XML first: right there means the apps have not re-read it yet; wrong there means the problem is upstream.
Moving hosts without losing a listener
Because the feed URL is what every app and every subscriber’s phone has stored, changing hosts means changing that URL without anyone noticing. Apple documents two mechanisms, and good hosts do both for you.
- A 301 redirect. The server that answers the old feed URL returns an HTTP 301 (“moved permanently”) pointing to the new feed. Any app that asks for the old address is sent to the new one. Apple says this is how most hosts migrate a feed and that it carries followers “even those outside of Apple Podcasts”.
- The
<itunes:new-feed-url>tag. Inside the new feed, this tag names the new URL so Apple can update its record. Apple asks that you keep both the tag and the 301 in place for at least four weeks, and warns not to point the tag at the Mirror URL shown in Apple Podcasts Connect. - Identical GUIDs. Apple’s own warning: altering GUIDs during a move “may result in duplicate episodes” and misrepresented analytics. Most host dashboards do not display GUIDs, so compare the old and new feeds in a feed viewer or validator before you redirect. The same goes for season and episode numbers if you use them.
- A fallback if the old host is gone. If you no longer have access to the old feed, Apple lets you edit the RSS feed URL for the show directly in Apple Podcasts Connect. That fixes Apple; it does not fix subscribers in apps that stored the old URL, which is why the redirect is the real answer.
If your new host supports <podcast:guid>, make sure it imports the existing value rather than generating a fresh one. That is the entire purpose of the tag: an identity for the show that survives a change of address. And expect your host dashboards to disagree for a while. Apple notes that download metrics in hosting dashboards can look atypical after a migration while Apple’s own analytics stay consistent. A measurement that sits outside both hosts, like the prefix described next, carries straight across.
How downloads are measured through the feed
There is no play button in an RSS feed, so nobody can count plays from it. What can be counted is requests for the file in the enclosure: filter out bots and duplicates, and you have a download. Your host does this on its own servers, which is where the number on your dashboard comes from.
An analytics prefix moves that counting to a place your host does not control. A short address is prepended to each enclosure URL in the feed, so https://cdn.host.example/ep-12.mp3 becomes https://prefix.example/e/cdn.host.example/ep-12.mp3. Every app that requests the audio hits the prefix first, is redirected to the real file, and the request is logged on the way through. Nothing about the audio changes. The Open Podcast Prefix Project (OP3), the open-source prefix PodLink reads rather than runs, describes its setup as prepending its address to episode URLs with no signup, notes that more than one prefix can coexist on a URL, and publishes a public stats page for every show it measures. Most hosts expose this as a single settings field.
PodLink’s download analytics are built on that kind of independent count: daily downloads over time, downloads per episode with the first seven days called out, top countries and the apps people listen in, measured from the day the prefix goes on (nothing before that date can be reconstructed, by anyone). The Show Report puts the same numbers on one sharable page, and because the source is open, a sponsor can check it. The sponsors guide explains why that matters more than a bigger number from your own dashboard.
The Spotify boundary
Spotify’s specification says playout is, in the normal case, handled by Spotify: it downloads your audio and serves listeners from its own servers (the same document describes a passthrough arrangement for some providers, where the app streams from the source). So in the normal case a Spotify listener does not request your enclosure URL, does not pass through the prefix, and does not appear in any prefix-based count, yours or anyone’s. That is a measurement boundary, not zero listeners. Spotify reports those plays in Spotify for Creators, whichever host you use, and in Megaphone when that is the host. PodLink shows the boundary rather than papering over it: the listening-apps breakdown is of prefix-measured downloads, and a connected host export is a separate window, not Spotify’s own count.
Common feed problems, and what they look like
These are the feed problems that come up most, with the symptom you will actually see.
- Episodes duplicated in apps. A GUID changed, usually during a host migration or a re-upload. Apps saw a “new” item and listed it next to the old one. Apple names this outcome explicitly. The fix is to restore the original GUIDs if your host allows it; if not, remove the duplicates and accept that the analytics for those episodes split in two.
- A new episode is missing in one app. Usually timing: the feed is right and the app has not re-read it yet. Check the feed itself. If the item is there, wait; Spotify says up to 24 hours across all platforms. If it is not, the host has not published it.
- Replaced audio or artwork that did not update. The file changed but its URL did not. Spotify’s specification says a changed binary at the same path triggers no new download; its support page suggests saving the file under a slightly different URL so apps notice.
- Wrong duration, or playback that will not scrub. Look at the enclosure: a wrong
length, a wrongtype, or a server that does not answer HEAD and byte-range requests, which Apple requires for streaming. - Validation failures on submission. Apple’s published list of common errors is short: no category or an unsupported one, no description, no language, no explicit tag, no channel title, no episodes with a valid enclosure, or a feed that cannot be fetched or parsed. Each maps to one tag in the table above.
- Downloads that dropped off a cliff. Either a migration moved the counting from one host to another (Apple notes dashboards can look atypical after a move), or a GUID or enclosure change split an episode’s history. Measurement that sits outside the host tells those apart from a real audience change.
How to check your feed
You do not need to read XML to keep a feed healthy. You need to look at it from the outside once in a while, the way an app does.
- A validator. Apple validates the feed when you submit it in Apple Podcasts Connect, and its support page points to two external tools for more detail, Cast Feed Validator and Podbase’s podcast validator. Run one before you submit and again before any migration.
- The raw feed. Open the URL in a browser. Confirm the title, the artwork URL, the category and the explicit flag are what you think they are, and that the latest item has a
<guid>, a<pubDate>and an<enclosure>with all three attributes. - PodLink’s free analyzer. Paste the URL into /analyze and you get the readable version: the show as the apps will display it, the episode count and latest episodes, and whether the analytics prefix is on the enclosure URLs. It is free, needs no account, and never touches the feed. If the prefix is missing, the sign-up flow shows the setting for your host.
Owning the pieces around the feed
The feed is the podcast, but it is not the whole business. The feed’s <link> should point at a website you own, with a page per episode that search engines and AI assistants can actually read, which is what PodLink builds as podcast websites ($3,500 one-time for the hub site and the episode-page system; Build + Episode Care adds $400 a month and we publish every new episode’s page). The listen links you share should go through one page you control, so a change of host or app never breaks a link in an old post; PodLink’s link in bio is built for that. For what to do once the plumbing is sound, read how to promote a podcast.