Podcast RSS Feed Analyzer
Paste any podcast RSS feed URL and get instant stats — total episodes, latest and earliest release dates, publishing cadence and the ten most recent episodes with runtimes.
Analyse a feed
Paste the RSS/Atom feed URL from your podcast host (Buzzsprout, Simplecast, Anchor, RSS.com, Libsyn, etc.).
Last updated: September 2026
How it works
We send your feed URL to the CreatorAiHub RSS worker, which fetches the XML server-side (avoiding browser CORS restrictions) and parses both RSS 2.0 and Atom into clean JSON. From that we count episodes, find the newest and oldest pubDate, compute the average gap between consecutive episodes, and list the ten most recent items with their durations from the itunes:duration tag when present.
How to use this tool
- Grab your podcast's RSS feed URL from your host — it's usually shown as "RSS feed" in your show settings or on your public podcast page.
- Paste it into the box and click Analyze.
- Read the stats: total episodes, first and latest release, and how often you publish on average.
- Scroll the recent-episode list to spot missing titles, short/long outliers, or dates that look wrong before submitting to a directory.
- Click Copy Results to paste a plain-text summary into your notes or a colleague's DM.
Frequently asked questions
Which feed formats are supported?
Both RSS 2.0 (the standard for podcast feeds, with <item> elements) and Atom (with <entry> elements). If your host emits a valid feed, this tool will read it. Podcast-specific fields like itunes:duration are picked up when present.
Why does the tool sometimes report "durations unavailable"?
Podcast feeds carry duration via the <itunes:duration> tag. Some feeds (especially blog-style RSS feeds or shows still on legacy hosts) don't include it. The tool shows the episode without a duration in that case — it doesn't fail the analysis.
Is this a full feed validator?
No — it's a fast look at the shape of the feed. For strict compliance checks (Apple/Spotify submission errors) use a formal validator. This tool is what you reach for while you're editing the feed and want to eyeball what listeners will see.
Why not fetch the feed directly from my browser?
Most podcast hosts don't send CORS headers, so a direct browser fetch fails silently. Routing through our RSS worker lets us parse the feed reliably and return normalised JSON your browser can render.
Does this work for large back-catalogues?
Yes — the worker parses the entire feed. Very long feeds (thousands of episodes) will take a couple of seconds longer to fetch. The recent-episode list is always capped at 10 so the UI stays quick regardless of catalogue size.