Help & Support
Updated: August 08, 2026
Getting started
rssdoc is a feed diagnostic tool. It fetches an RSS 2.0 or Atom feed URL, parses it the way a real reader or podcast directory does, and reports every defect it finds — in plain language, with an explanation of what breaks as a result.
To use it:
- Go to the Diagnose page.
- Paste your feed URL (must start with
http:// or https://).
- Click Diagnose.
- Read the report: format detected, item count, date range, and any defects found with their consequences.
No account, no signup, and no email required. Results appear in your browser and are not stored anywhere.
Frequently asked questions
My feed was rejected by Apple Podcasts / Spotify / a podcast directory. Can rssdoc help?
Yes — that is exactly what rssdoc is built for. When a directory rejects a feed, it usually gives a vague error like "invalid feed" with no detail. rssdoc fetches your feed and checks for the specific defects that cause rejections: unparseable dates, missing titles or links, duplicate GUIDs, encoding mismatches, and wrong Content-Type headers. If rssdoc finds a problem, the report tells you what to fix.
If rssdoc reports no defects but the directory still rejects the feed, the issue may be a directory-specific policy, a server-level block, or an editorial requirement that rssdoc cannot detect from the feed alone. See the "no defects found" question below.
What feed formats does rssdoc support?
RSS 2.0 and Atom (including Atom 1.0). rssdoc detects which format a feed uses automatically and applies the correct validation rules — GUIDs and pubDate for RSS, IDs and updated dates for Atom, including namespace conventions for both. It does not support RSS 0.9x or custom XML formats that are not standard syndication feeds.
The tool said "no defects found" but my feed is still broken in readers. What now?
A clean rssdoc report means the feed's structure, dates, GUIDs, titles, links, encoding, and Content-Type all look correct. Some issues that rssdoc cannot detect include:
- Directory-specific policies — Apple Podcasts, Spotify, Google Podcasts, etc., each have their own content and metadata requirements that go beyond feed structure.
- Server-level issues — Your host may be rate-limiting or blocking the directory's fetcher IPs, or serving a cached/stale version.
- Media file problems — rssdoc does not download or validate enclosures (audio files, artwork images). A missing or corrupt audio file can cause podcast directory rejection even when the feed XML is valid.
- Editorial issues — Missing show notes, inappropriate content, copyright violations, or duplicative episodes cannot be detected from feed structure.
If you have checked these and still cannot diagnose the problem, contact support with the feed URL and the exact error message you received from the directory.
Does rssdoc check my podcast artwork, show notes, or audio files?
No. rssdoc only fetches and validates the feed XML itself. It does not follow enclosure links, download media files, or validate image dimensions, audio format or bitrate. If your podcast artwork or audio file is the cause of a rejection, rssdoc will not find it. An honest "no defects found" result means the XML is valid — the problem is likely elsewhere.
How long does a diagnosis take?
Most feeds are analysed within a few seconds. The server-side fetch and parse has a 15-second timeout. If your feed takes longer than that to respond, rssdoc will report a fetch error. Very large feeds (thousands of items) may approach this timeout. If your feed consistently times out, try testing a smaller feed or check your server's response time.
Is my feed data saved or stored anywhere?
No. rssdoc does not store, cache, or persist any data. The feed URL you submit is used only to fetch the feed for diagnosis. The results exist in memory on the current page and are discarded when you close or refresh the page. rssdoc does not use cookies, localStorage, or any browser storage mechanism. See the Privacy policy for full details.
Known limitations
rssdoc is a diagnostic tool with a deliberately narrow scope. Here is what it does not do:
- No media validation — rssdoc does not download or validate enclosure links, audio files, video files, or artwork images.
- No crawling — Only the single feed URL you submit is fetched. rssdoc does not follow links, crawl pages, or discover feeds.
- No alerts or scheduled checks — rssdoc answers when you ask it. There is no email sender, no notification system, and no recurring monitoring.
- No feed submission — rssdoc does not submit feeds to any directory, aggregator, or third-party service.
- No accounts or history — Results are not saved. Every diagnosis begins fresh. Pro features (batch checking, history, JSON export) are planned but not yet available.
- No editorial review — rssdoc validates structure, not content. It cannot detect missing show notes, inappropriate content, or directory-specific policy violations.
- 15-second timeout — Feeds that take longer to respond than 15 seconds will return a fetch error.
- No legal entity — The operator has not yet registered a legal entity. No company name, registered address, or jurisdiction applies.
Note on support availability: Email and phone support are not yet available. The operator has not set up a mailbox or a contact form for this tool. This section will be updated with a working contact method once one is established.
If you have a question or problem that is not covered in this Help Centre:
- For tool bugs — Record the feed URL (if shareable), the exact output you saw, and what you expected. When a contact method is established, this information will help us reproduce the issue.
- For feature requests — Let us know what you need. Planned features include batch checking, JSON export, and per-feed history. Suggestions help inform priorities.
- For urgent issues — There is no emergency contact route today. If a feed problem is time-sensitive, review the FAQ above and check your server logs while we work on setting up a support channel.
The operator is reviewing options for a support mailbox and will update this page when one is available. Until then, your patience is appreciated.