CheckRSS

CheckRSS › Guides

RSS feed not working? Ten causes and their fixes

A feed can fail in two ways: readers reject it, or they accept it and never show anything new. Start by checking it, then find your case below.

Check the feed first

Try:

The feed does not load or is rejected

1. The XML is broken

One stray character is enough to make the whole feed unreadable. The usual culprits are a bare & in a title or link (it must be written &), an HTML entity such as   (XML does not know it), or text pasted from a word processor with invisible control characters.

Fix: the checker reports the line. Escape the character, or wrap the text in <![CDATA[ … ]]>. If a plugin builds the feed, the cause is usually one post: edit the post named on that line.

2. Something is printed before the XML

A feed must start with <?xml as its very first characters. A blank line, a PHP warning or a debug message in front of it breaks strict readers. On WordPress this is almost always an empty line after a closing ?> in functions.php or in a plugin file.

Fix: remove the blank space. Switching plugins off one by one finds the file quickly.

3. The address returns a web page

The feed address answers, but with HTML: a login page, a cookie wall, a "checking your browser" page, or the home page after a redirect. A person sees a page; a feed reader sees garbage.

Fix: exclude the feed address from whatever is intercepting it: the bot protection, the consent tool, the maintenance mode or the membership plugin.

4. A firewall blocks feed readers

Feed readers are programs, and security services treat programs as bots. The feed works in your browser and returns 403 to everyone else. This is the most common reason a feed "works for me" and for nobody else.

Fix: add a rule that lets requests to the feed address through without a challenge. In Cloudflare that is a custom rule that skips bot checks for the feed path.

5. The wrong content type

The server should label a feed as application/rss+xml, application/atom+xml or application/xml. Labelled text/html, some readers refuse it, and labelled text/plain some will not even try.

Fix: set the Content-Type header for the feed file in the server or hosting configuration.

The feed loads but readers show nothing new

6. A cache is serving an old copy

A caching plugin or a CDN keeps the feed for hours or days. You publish, the feed in the cache stays the same, readers see nothing.

Fix: exclude the feed from the page cache, or cap its lifetime at a few minutes. Then purge the cache once.

7. Identifiers that change

Readers recognise an item by its guid (in Atom: id). If the identifier changes, for example because it contains a tracking parameter or the site moved from http to https, every item shows up again as new. If two items share one identifier, one of them is never shown.

Fix: make the identifier permanent and unique per item. Once published, never change it.

8. Dates that are missing, wrong or in the future

Readers sort by date. An item with no date, a date in a local format, or a date in the future ends up in the wrong place or is hidden until that date arrives. Old dates on new posts bury them below what the reader already showed.

Fix: RSS wants the form Sat, 14 Nov 2026 08:00:00 GMT; Atom wants 2026-11-14T08:00:00Z. Check the time zone setting of the site.

9. The feed moved

After a redesign or a change of platform the feed lives at a new address and the old one returns 404, or redirects to the home page. Existing subscribers are silently cut off.

Fix: add a permanent (301) redirect from the old feed address to the new one, and keep it in place for good. Readers follow it and update the subscription.

10. The feed is too big or too slow

A feed that lists every post since the site began, each with its full text, can reach many megabytes. Readers give up on downloads that take too long, and some cut the file off, which leaves broken XML.

Fix: limit the feed to the latest 10 to 50 items. Podcasts are the exception: they should list every episode, but with short descriptions.

If the feed is not yours

You cannot fix it, but you can tell which side the problem is on. If the checker shows the feed as valid and fresh, the trouble is in your reader: remove the subscription and add it again, or ask the reader's support. If the checker shows errors, send the site owner a link to the result. Most are glad to hear about it.

Questions

How often do feed readers check a feed?

It varies from every few minutes to once a day, depending on the reader and on how often the feed has changed in the past. A delay of an hour between publishing and seeing the post is normal.

The feed is fine in the checker but broken in one reader. Why?

That reader is probably blocked by a firewall (cause 4), or it holds on to an old copy. Warnings in the check result are worth a look too: a reader may be stricter than most about one of them.

Does a redirect break a feed?

One permanent redirect is fine. Chains of several redirects, or a redirect from https back to http, cause trouble in some readers.