A directory rejected your feed and told you almost nothing useful. Feedparse tells you what actually broke and why.

Where your feed goes, start to finish

You paste a URL. Feedparse fetches what lives there, parses it the way a real reader would, and reports what it found — format, item count, dates, and every defect that actually breaks readers.

What Feedparse actually checks

Most feed validation tools tell you "invalid" and nothing more. Feedparse checks the six defects that actually break real readers and directories, and explains what breaks as a result.

• DATES Missing or unparseable publication dates. Without a parseable date, readers cannot order your items chronologically — some skip the item, some hide it entirely.
• GUID Missing or duplicate GUIDs. Each item needs a unique identifier. Without one, a reader cannot tell whether it has already seen that item, and re-publishes it on every refresh. Duplicate GUIDs confuse two items into one.
• TITLE Items with no title. Most readers display a blank entry or skip the item entirely when the title element is missing.
• LINK Items with no link. Without a destination URL, your readers have nowhere to go for the full content. Some directories reject feeds with linkless items.
• CONTENT TYPE Wrong Content-Type header. Serving your feed with an HTML content type causes strict readers to reject it without even looking at the XML.
• ENCODING Encoding declaration mismatch. When the XML encoding declaration disagrees with the HTTP Content-Type charset, different readers interpret the bytes differently — producing garbled text.

Not "invalid" — here is what actually broke

Every finding comes with a plain-English explanation of what breaks as a result, so you know which issues to fix first.

Download and copy work on the live tool. This preview uses example data.

What Feedparse catches

Feedparse runs a comprehensive set of checks against any RSS, Atom or podcast feed URL you submit. These are the defect categories it detects:

• GUID Missing or duplicate GUID. Every item in a feed needs a unique, permanent GUID. Without one, podcast directories reject the episode — and duplicate GUIDs cause players to skip new content.
• DATE Unparseable date. RSS dates must follow RFC 822. A malformed or missing pubDate means directories cannot sort or display your episodes correctly.
• CONTENT TYPE Content-Type mismatch. Your feed URL must return application/rss+xml or the correct XML media type. A wrong Content-Type header causes many feed readers and directories to refuse the feed entirely.

What this tool cannot do

Feedparse is a diagnostic, not a feed management service. It answers when you ask it, and it is honest about what it cannot do.

• ✕ No email alerts or scheduled re-checks. This tool has no way to send email and no scheduled jobs. It checks one feed when you submit one URL. If a feature needs email or cron, this product does not have it yet.
• ✕ No saved feeds or accounts. Feedparse does not store feeds, track changes over time, or remember you between visits. Every analysis is a fresh fetch from the URL you provide.
• ✕ No media downloads. The tool examines only the feed XML. It does not follow enclosure links, download audio files, or verify media availability.
• ✕ Cannot reach all hosts. Some hosts behind Cloudflare's own network may report as unreachable. If your feed is on a Cloudflare-hosted domain and you see a connection error, try fetching it from a different address.

Free. No account. No catch.

Feedparse is free for unlimited single-feed analysis. No registration, no trial period, no credit card.

No paid tier is offered — this product has no accounts, no server-side storage, and no email sender. For billing questions, contact feedparse@agen2ic.ai.

You have questions. We have answers.