CheckRSS

CheckRSS › Guides

Every check, explained

What the checker looks at, why it matters to the programs that read your feed, and the usual fix. Results come in three levels: Error Warning Note

Connection

CheckLevelWhy it matters and what to do
Status codeErrorAnything 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.
HTTPSWarningFeeds 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 redirectWarningThe address you gave has moved. Update links to point at the new address. Keep the redirect for existing subscribers.
Redirect chainWarningMore than three hops slow every request and some readers give up. Redirect straight to the final address.
Temporary redirectNoteReaders keep asking the old address. Fine if intended; use 301 if the move is permanent.
Content typeWarningExpected: application/rss+xml, application/atom+xml, application/feed+json or application/xml. text/html and text/plain make some readers reject the feed.
Character encodingWarningThe HTTP header and the XML declaration name different encodings. Readers pick one and may show garbled letters. Use UTF-8 in both.
Conditional requestsNoteWith 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 timeWarningReaders fetch thousands of feeds and drop slow ones. If the feed takes seconds to start, cache it.
SizeWarningFeeds of several megabytes are slow to fetch and parse. Limit the number of items or shorten the content, except in podcast feeds.

XML

CheckLevelWhy it matters and what to do
Well-formed XMLErrorUnclosed tags or illegal characters stop strict parsers at that point. The line number is reported.
Unescaped ampersandErrorA bare & must be written &, in text and in links alike.
HTML entitiesErrorXML knows only five named entities.  , é and the like are undefined. Use the character itself or wrap the text in CDATA.
Content before the declarationErrorNothing may come before <?xml, not even a blank line.

Feed

CheckLevelWhy it matters and what to do
Required elementsErrorRSS 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 linkWarningThe 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 siteWarningThe channel link must be a full address starting with https://, so readers can send people to your site.
LanguageWarningIf present, it must be a valid code such as en or en-US. Podcast directories require it.
Format versionNoteOld 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 feedErrorThe address returns a web page, a sitemap, an OPML list or other content. The finder can locate the real feed.

Items

CheckLevelWhy it matters and what to do
Title or descriptionErrorAn RSS item needs at least one of the two. Atom entries need a title.
IdentifierWarningWithout a guid (Atom: id, where it is required) readers guess which items are new, and guess wrong when a title is edited.
Duplicate identifiersWarningTwo items with one identifier look like one item. Readers show only one of them.
DatesErrorRSS 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.
LinksWarningItem links must be full addresses. A link like /post/1 leads nowhere inside a feed reader.
Relative addresses in contentWarningImages and links written as /images/a.jpg break when the content is shown outside your site. Use full addresses.
FreshnessNoteHow long ago the newest item was published. A feed that has been quiet for a year may be abandoned, or stuck behind a cache.
OrderNoteReaders 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.

CheckLevelWhy it matters and what to do
Cover artErrorRequired 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.
CategoryErrorApple Podcasts requires at least one itunes:category.
Explicit flagWarningitunes:explicit should be true or false.
LanguageErrorRequired for podcasts.
Author and ownerWarningitunes:author is shown under the title. The owner e-mail is how some directories confirm that the show is yours.
EnclosuresWarningEach episode needs an enclosure with url, type and length. Episodes without one are invisible to podcast apps.
Episode identifierWarningEach episode needs a guid that never changes, or apps will download episodes twice.
Audio deliveryWarningThe 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 tagsNotepodcast:guid and podcast:locked are optional but protect the show when it changes host.

Run the checks on a feed

Try: