Your new episode is live on your host but has not appeared in Apple Podcasts after a day, Spotify refuses the show because it cannot verify ownership, or a listener reports that downloads fail. Most of these problems are visible in one place: the podcast's RSS feed, which every app and directory reads.
The Podcast Feed Checker & Episode Downloader fetches a feed, checks the show and every episode against the requirements Apple Podcasts and Spotify publish, shows release statistics, and lets you play, download or convert episodes.
What is a podcast RSS feed?
In simple terms
A podcast is an RSS feed: an XML file at a fixed address that describes the show (title, artwork, category) and lists the episodes. Each episode has an enclosure — a link to the audio or video file. Podcast apps check the feed regularly, show new episodes and download the files from the enclosure links.
Technical background
The format is RSS 2.0 with extra tags in the itunes: namespace (http://www.itunes.com/dtds/podcast-1.0.dtd), which Apple introduced and other directories adopted. The <enclosure> element has three attributes: url, length (bytes) and type (MIME type such as audio/mpeg). <guid> identifies an episode permanently, so apps do not show duplicates when a title or file changes. <pubDate> uses the RFC 2822 date format, and <itunes:duration> gives the length as seconds or HH:MM:SS.
Why use the Podcast Feed Checker?
- Find missing or invalid tags before submitting a show to Apple Podcasts, Spotify or other directories.
- Understand why a directory rejects the feed or hides episodes.
- Check that episode files are reachable through tracking redirects and match the type and size in the feed.
- See the release rhythm, episode count, average length and total size at a glance.
- Download episodes for archiving, editing or offline listening, or convert them to MP3.
Who should use it?
Podcasters and producers before launch and after changing hosts, hosting providers and agencies checking client feeds, developers generating RSS feeds, and anyone who needs an episode file from a public feed.
How the Podcast Feed Checker works
The NetTools.tech server downloads the feed with the same SSRF-protected client as the other web tools: only public addresses, up to five redirects with each target checked again, at most 10 MB (compressed feeds are unpacked). Your browser then parses the XML as inert data — nothing from the feed is executed.
The show is checked for title, description (Apple shows up to 4,000 characters), language code, an Apple Podcasts category from the official list, the explicit flag, author, owner e-mail, website link, show type, and the block, complete and new-feed-url tags. The artwork must be present, HTTPS and JPEG or PNG; your browser measures its size when it loads. Every episode is checked for a title, an enclosure with an http(s) URL, an audio/video type and a length, a unique GUID, a valid publication date (dates in the future are noted) and a duration. Up to 500 episodes are checked; larger feeds are reported.
On request, the server checks the first ten episode files: it follows each enclosure URL like a podcast app, through tracking redirects, and reports the final HTTP status, content type and size — reading headers only (a HEAD request, or the first 16 KB when HEAD is refused).
How to use the NetTools.tech Podcast Feed Checker
- Open the Podcast Feed Checker and paste the feed URL from your hosting provider, for example
https://feeds.example.com/my-show.xml. - Press Check feed. The show title, artwork and categories appear at the top, followed by the key figures.
- Read the Feed check list: errors first, then warnings and notes.
- In Episodes, filter by title, and press Check the first 10 episode files to test the downloads.
- Use Play to listen, Download to save the original file from the podcast host, or Convert to open the episode in the Media Converter and extract MP3, M4A or another format.
- Export the findings and the episode list as CSV or JSON, copy them, or print a report.
Understanding the results
| Result | Meaning | What to look for |
|---|---|---|
| Feed check | Errors, warnings and notes by area (Feed, Artwork, Episodes) | Errors block directory submission; warnings cause display or ownership problems |
| Episodes | Number of <item> elements and the newest date | A newest date older than expected means new episodes are not in the feed |
| Release rhythm | Median days between episodes | Gaps show irregular publishing or deleted episodes |
| Average length | From itunes:duration | Missing durations are listed as notes |
| Declared size | Sum of enclosure lengths | Zero means the feed omits lengths |
| Artwork size | Measured by your browser | Must be square, 1400–3000 px for Apple Podcasts |
| File check | Final status, redirects, type and size of the episode file | Non-200 status, HTML instead of audio, size different from the feed |
Example: a feed with two problems
An illustrative feed at https://feeds.example.com/my-show.xml with 120 episodes returns these findings:
- Error (Feed): No
<itunes:explicit>; Apple Podcasts requires true or false. - Warning (Episodes): 3 enclosures have no length in bytes.
The episode file check shows HTTP 200 · 3 redirects for each of the ten newest episodes: the files are served through a tracking service and then from the host's storage, which is normal. Adding <itunes:explicit>false</itunes:explicit> to the channel and letting the host fill in the missing lengths fixes the feed; Apple Podcasts reads the corrected feed on its next refresh.
Common use cases
- Validating a feed before submitting to Apple Podcasts, Spotify, YouTube Music or other directories.
- Checking a feed after moving to a new host (redirects,
new-feed-url, GUIDs preserved). - Finding why episodes do not download in some apps.
- Downloading an episode to clip or quote it, or converting it to MP3 for an older player.
Troubleshooting
"This URL returned a web page, not an RSS feed"
You pasted a show page. Use the RSS address from your hosting dashboard; Apple Podcasts and Spotify pages are refused because they are not feeds.
"This is not a valid RSS feed"
The XML is broken or the document has no <rss><channel>. A common cause is an unescaped & in a title or description; wrap such text in CDATA or escape it as &.
Episode file check fails
A status of 403 or 404 usually means the storage link expired or the file was removed. An HTML content type means the URL leads to a web page, not the audio. A size that differs from the feed's length points to a replaced file without an updated feed.
Duplicate GUIDs
Apps treat episodes with the same GUID as the same episode, so one of them disappears. Give every episode a permanent unique GUID and never change it afterwards.
Common mistakes
- Submitting the directory page instead of the RSS feed URL.
- Changing GUIDs when moving hosts, which makes apps show every episode again.
- Using artwork that is not square or smaller than 1400 px.
- Serving files over plain HTTP, which some apps block.
- Leaving
<itunes:block>yes</itunes:block>set after testing, which hides the show from Apple Podcasts.
Limitations
- The checker validates the feed's structure and required fields, not the content policies of the directories.
- Artwork dimensions are measured in your browser; file contents (bitrate, loudness) are not analyzed — use the Media Converter's Audio Quality tab for that.
- Only feeds reachable at a public URL can be checked; private or paid feeds that need sign-in are not supported.
- Feeds over 10 MB and episodes beyond the first 500 are not processed.
Security & privacy
The feed is fetched by the NetTools.tech server through the SSRF-protected client and parsed in your browser; nothing is stored. Episode file checks read only HTTP headers. Download and Play load the file directly from the podcast host in your browser, so the host sees your IP address as it would in any podcast app. Do not paste private feed URLs that contain personal access tokens into any public tool.
Related tools
- Video & Audio Downloader / Media Converter: convert episodes to MP3 or M4A, or check audio quality (guide).
- Sitemap Checker: validate another kind of XML feed (guide).
- Redirect Checker: follow an enclosure's redirect chain hop by hop (guide).
- HTTP Status Checker: check what a feed or file URL answers (guide).
- Web & SEO tools overview.
Summary
The Podcast Feed Checker fetches a podcast RSS feed, checks the show and every episode against the requirements Apple Podcasts and Spotify publish, and tests the episode files the way a podcast app would. Episodes can be played, downloaded directly from the host or converted to MP3 with the Media Converter.
Frequently asked questions
Where do I find my podcast's RSS feed URL?
Your hosting provider shows it in its dashboard, often under Distribution, Settings or RSS. Apple Podcasts and Spotify show pages are not feeds; the checker refuses them and needs the RSS address those directories read from.
Which tags does Apple Podcasts require?
At show level a title, description, language, at least one itunes:category, itunes:explicit (true or false) and itunes:image artwork of 1400 to 3000 pixels. Each episode needs a title and an enclosure with URL, type and length; a unique guid and a pubDate are strongly recommended.
Why does Spotify need the owner e-mail?
When you submit a show, Spotify and other directories send a verification code to the e-mail address in itunes:owner to confirm you control the feed. Without it you cannot claim the show.
Can I download podcast episodes as MP3?
Yes. Episodes are published in the feed's enclosures for download. Use Download for the original file from the podcast host, or Convert to extract MP3, M4A or another format with the Media Converter.
What does it mean when an episode file check shows several redirects?
Many podcasts route downloads through analytics or tracking services, which redirect to the real file. That is normal; a problem is a final status other than 200, an HTML page instead of audio, or a size that differs from the length in the feed.
Does a clean result mean my show will be accepted?
It means the feed has the required fields in a valid form. Directories also review the content, check the artwork image and audio files, and apply their own policies.