Feedparse
Getting started with Feedparse
Feedparse is a feed diagnostic tool — you paste a feed URL, it tells you what is wrong and why. Here is how it works, and how to get the most out of it.
- Go to the App page. That is where the tool lives. No account, no login — just a URL field and a button.
- Paste your feed URL into the field. Any public RSS 2.0, RSS 1.0, RSS 0.91/0.92, or Atom feed works. Podcast XML files are RSS 2.0 with additional namespace elements, and Feedparse checks those too.
- Click “Analyze feed”. Feedparse fetches the feed, parses it, and returns a structured report: format, item count, date range, and a list of structural defects with plain-English explanations of what breaks as a result.
- Fix the defects it finds. Each finding tells you exactly what is wrong and why a reader or directory cares. Start with the ERROR-level items, then address WARNING-level items.
- Re-run the analysis after making changes to confirm the fixes took effect. Nothing is stored between runs, so every analysis is a fresh check.
Common questions, answered plainly
What defects does Feedparse actually detect?
Feedparse checks six categories: GUID (missing or duplicate unique identifiers), dates (missing or unparseable publication dates), titles (items with no title element), links (items with no destination URL), Content-Type headers (serving feed XML with the wrong media type), and encoding mismatches (when the XML declaration and HTTP headers disagree about the character encoding). Each finding comes with a plain-English explanation of what actually breaks for readers and directories.
My podcast feed was rejected by Apple Podcasts / Spotify — will Feedparse tell me why?
Feedparse checks the structural defects that are a common cause of rejection: missing GUIDs, unparseable dates, wrong Content-Type headers. If the feed has one of these issues, the report will flag it and explain why it matters. However, Feedparse does not simulate every directory’s validation rules — a feed that passes Feedparse’s checks may still be rejected by a particular directory for content-policy reasons, artwork requirements, or other criteria that are outside the scope of a structural feed analysis.
Do you store my feed URL or its contents?
No. Feedparse fetches your feed, analyzes it in memory, returns the result to your browser, and discards everything. Nothing is logged, stored, or retained server-side between requests. There are no accounts, no saved histories, and no tracking.
Why does my feed show as unreachable when I can open it in my browser?
If your feed is served from a domain that uses Cloudflare’s own network, this tool may not be able to reach it — the platform cannot open a connection to hosts that are themselves inside Cloudflare. Try accessing the feed from a non-Cloudflare URL or a direct IP address, or confirm that the feed is served from a different origin.
Can I check a password-protected or private feed?
No. Feedparse rejects URLs containing embedded credentials (
username:password@), private IP ranges, loopback addresses, and NUL bytes for security reasons. Only public feeds on public URLs can be analyzed.I fixed the defects Feedparse reported but my feed is still being rejected — what else could it be?
Feedparse checks structural defects in the feed XML itself, but directories and readers have additional requirements beyond well-formed XML. Common non-structural reasons for rejection include: artwork that does not meet the directory’s size or format requirements, content that violates the directory’s policies, an unresponsive or slow feed host, or the directory’s own ingestion backlog. If Feedparse reports no defects and your feed is still rejected, check the directory’s submission guidelines for non-XML requirements. Feedparse is a diagnostic, not a guarantee of acceptance.
How do I download or share my report?
After analysis, two buttons appear below the report: “Download report (.txt)” saves a plain-text copy of the full analysis, and “Copy report” copies the same text to your clipboard so you can paste it into an email, ticket, or message. Both work entirely in your browser — no data is sent to any server when you download or copy.
What Feedparse cannot do
Feedparse is a live diagnostic tool, not a feed management service. It answers when you ask it, and it is honest about what is not built yet.
- ✕ No email alerts or scheduled re-checks. Feedparse has no email sender 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, accounts, or history. Every analysis is a fresh fetch. Nothing is stored between visits. There is no way to track how a feed changes over time.
- ✕ No media downloads or audio verification. Feedparse examines only the feed XML. It does not follow enclosure links, download audio files, check media availability, or validate artwork dimensions.
- ✕ Cannot access Cloudflare-hosted feeds. The platform cannot open connections to hosts that are themselves inside Cloudflare. If your feed returns a connection error and is on a Cloudflare domain, try a non-Cloudflare address.
- ✕ No bulk or batch analysis. The tool analyzes one feed URL at a time. A Pro tier with bulk analysis is planned but not yet available.
- ✕ No API or programmatic access. Feedparse is a web tool with no public API. It cannot be integrated into scripts or automated workflows.
Still stuck? Reach out
If you have checked the guidance above and your question is not answered, or if you believe Feedparse has misdiagnosed your feed, the best way to reach us is by email.
Send a detailed description of your issue to
Please include the feed URL and a copy of the report Feedparse returned, if available. Emails are answered by a human. If your question is about billing or a feature request, mention that in the subject line so it reaches the right person.
Note: Feedparse is provided without a registered legal entity. There is no phone number, no live chat, and no social media support channel. Email is the only way to reach us, and we respond as promptly as we can.