Enter a feed URL.
Get every defect that breaks readers.
Your RSS or podcast feed was rejected with "invalid" and nothing else useful. Feedprobe fetches it, parses it the way a reader does, and reports each specific problem — missing guids, unparseable dates, encoding mismatches, wrong content types — with what breaks as a result.
Analyze a feed
No signup, no email, no stored data
What the tool detects
-
Defect
Missing or duplicate guid / id
Items without a stable unique identifier can cause podcast directories to skip episodes or overwrite existing listings. Duplicate guids produce stale or dropped episodes. -
Defect
Missing title or link
Items with no title display as blank in readers. Items with no link cannot be opened. The channel/feed itself also needs a title to be listed in directories. -
Defect
Unparseable date
A pubDate or updated value that cannot be read means the item cannot be sorted into newest/oldest order — readers may place it arbitrarily or drop it entirely. -
Defect
Encoding mismatch
A declared charset that does not match the actual bytes produces garbled or missing characters for accented text. The HTTP header and XML declaration saying different things causes readers to disagree about how to decode the document. -
Defect
Wrong content type
A feed served as text/html (a web page) or application/json is not what a reader expects. Many readers reject feeds with the wrong Content-Type outright. -
Advisory
Parse failure or http error
If the document is not XML, not a feed, or empty, the report says exactly where parsing failed. If the server answers with an error page, the report marks every verdict as not established — it does not grade a 404 as a feed.
How it works
- Paste the feed URL that was rejected by your directory or reader.
- Feedprobe fetches it and parses it the way a real reader does — RSS 2.0 or Atom.
- Each finding is listed with what breaks as a result, color-coded by severity.
- Fix the defects one at a time and re-check until the report is clean.