Video, Audio & YouTube
Check your podcast RSS feed before Apple or Spotify sees it
Paste your feed URL or upload the XML file. You get duplicate episode GUIDs, missing artwork or author tags and audio links that return errors, as HTML, PDF and CSV.
- URL / XML
- Up to 500 episodes
Two episodes with unique GUIDs and HTTPS enclosures
- Feed root is RSS
- Episode count: 2
- Enclosure count: 2
result.json · findings.csv · http-evidence.csv · read-me.txt
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
Checking a podcast feed before you submit it
What you check
You paste your feed URL or upload the RSS XML file. One run covers up to 500 episodes. The tool looks for missing or reused episode GUIDs, missing artwork or author tags, and audio links that return errors. URL fetches have size and redirect limits. A redirect towards an internal address or an oversized response is refused rather than followed.
What the report shows
You get findings as HTML, PDF and CSV, plus http-evidence.csv with what each server returned, including the status code and reported file length. Each finding points back to the place in the feed it came from. A suggested XML change can be added as an optional file. Open the evidence file to check any failing audio link yourself before you edit the feed.
Profiles and what stays open
You pick a target profile: general podcast, Apple-compatible or Spotify-compatible. A checkbox turns on header checks for the audio files. Only the headers are requested, so full episodes are never downloaded. The cover image is checked for presence and reachability, not for how it looks. The tool reports what tends to cause a rejection. Whether a directory accepts your feed is decided by that directory.
Questions before you run it
Will this tell me whether Apple Podcasts will accept my feed?
No. It checks the feed against the target profile you pick and reports what tends to cause a rejection. Acceptance is decided by the directory, not here.
Does it download every episode audio file?
No. With enclosure header checks switched on it asks for headers only and records what the server returned, including status code and reported length, in http-evidence.csv.
What GUID problems does it catch?
Missing GUIDs and GUIDs reused across episodes, both of which make clients treat two episodes as the same item. Each finding points back at the feed node it came from.
Can I paste a feed URL instead of uploading XML?
Either works. URL fetches are bounded and hardened, so a redirect towards an internal address or an oversized response is refused rather than followed.
What does it check about the cover artwork?
The artwork reference is checked for presence and reachability against the selected profile, and the response evidence is written to the report. Visual quality is not judged.