Connection
| Check | Level | Why it matters and what to do |
|---|---|---|
| Status code | Error | Anything other than 200 means readers get no feed. 403 usually points to a firewall, 404 to a moved feed, 5xx to a fault in the site. |
| HTTPS | Warning | Feeds on plain http can be altered on the way, and some apps refuse them. Serve the feed over https and redirect the old address. |
| Permanent redirect | Warning | The address you gave has moved. Update links to point at the new address. Keep the redirect for existing subscribers. |
| Redirect chain | Warning | More than three hops slow every request and some readers give up. Redirect straight to the final address. |
| Temporary redirect | Note | Readers keep asking the old address. Fine if intended; use 301 if the move is permanent. |
| Content type | Warning | Expected: application/rss+xml, application/atom+xml, application/feed+json or application/xml. text/html and text/plain make some readers reject the feed. |
| Character encoding | Warning | The HTTP header and the XML declaration name different encodings. Readers pick one and may show garbled letters. Use UTF-8 in both. |
| Conditional requests | Note | With an ETag or Last-Modified header, readers can ask "anything new?" and get a tiny answer. Without one they download the whole feed every time. |
| Response time | Warning | Readers fetch thousands of feeds and drop slow ones. If the feed takes seconds to start, cache it. |
| Size | Warning | Feeds of several megabytes are slow to fetch and parse. Limit the number of items or shorten the content, except in podcast feeds. |
XML
| Check | Level | Why it matters and what to do |
|---|---|---|
| Well-formed XML | Error | Unclosed tags or illegal characters stop strict parsers at that point. The line number is reported. |
| Unescaped ampersand | Error | A bare & must be written &, in text and in links alike. |
| HTML entities | Error | XML knows only five named entities. , é and the like are undefined. Use the character itself or wrap the text in CDATA. |
| Content before the declaration | Error | Nothing may come before <?xml, not even a blank line. |
Feed
| Check | Level | Why it matters and what to do |
|---|---|---|
| Required elements | Error | RSS needs title, link and description in the channel. Atom needs title, id and updated (a missing updated is reported as a warning, because readers cope with it). JSON Feed needs version, title and items. |
| Self link | Warning | The feed should state its own address with <atom:link rel="self">. Readers use it to find the feed again after it was copied or moved. |
| Link to the site | Warning | The channel link must be a full address starting with https://, so readers can send people to your site. |
| Language | Warning | If present, it must be a valid code such as en or en-US. Podcast directories require it. |
| Format version | Note | Old versions (RSS 0.9x, Atom 0.3) still work in most readers, but RSS 2.0 or Atom 1.0 is the safe choice. |
| Not a feed | Error | The address returns a web page, a sitemap, an OPML list or other content. The finder can locate the real feed. |
Items
| Check | Level | Why it matters and what to do |
|---|---|---|
| Title or description | Error | An RSS item needs at least one of the two. Atom entries need a title. |
| Identifier | Warning | Without a guid (Atom: id, where it is required) readers guess which items are new, and guess wrong when a title is edited. |
| Duplicate identifiers | Warning | Two items with one identifier look like one item. Readers show only one of them. |
| Dates | Error | RSS dates use the form Sat, 14 Nov 2026 08:00:00 GMT, Atom and JSON Feed use 2026-11-14T08:00:00Z. Dates that cannot be read are an error; missing dates and dates in the future are warnings. |
| Links | Warning | Item links must be full addresses. A link like /post/1 leads nowhere inside a feed reader. |
| Relative addresses in content | Warning | Images and links written as /images/a.jpg break when the content is shown outside your site. Use full addresses. |
| Freshness | Note | How long ago the newest item was published. A feed that has been quiet for a year may be abandoned, or stuck behind a cache. |
| Order | Note | Readers expect the newest item first. |
Podcast
These run when the feed has audio or video enclosures. The cover art and audio checks need a second request and run on the podcast validator and the main checker alike.
| Check | Level | Why it matters and what to do |
|---|---|---|
| Cover art | Error | Required by every directory: square, 1400 to 3000 pixels on each side, JPEG or PNG. A missing itunes:image is an error; a wrong size is a warning. |
| Category | Error | Apple Podcasts requires at least one itunes:category. |
| Explicit flag | Warning | itunes:explicit should be true or false. |
| Language | Error | Required for podcasts. |
| Author and owner | Warning | itunes:author is shown under the title. The owner e-mail is how some directories confirm that the show is yours. |
| Enclosures | Warning | Each episode needs an enclosure with url, type and length. Episodes without one are invisible to podcast apps. |
| Episode identifier | Warning | Each episode needs a guid that never changes, or apps will download episodes twice. |
| Audio delivery | Warning | The audio host must answer byte-range requests, or Apple Podcasts cannot stream the episode. HTTPS is expected, and long redirect chains (tracking prefixes) are noted. |
| Podcasting 2.0 tags | Note | podcast:guid and podcast:locked are optional but protect the show when it changes host. |
Run the checks on a feed
Try: