Fix an RSS Feed That Stopped Updating
Published: October 2, 2026. Updated: October 2026 by Andrew Apell, who builds RSS Wrangler and previously built Flookup Data Wrangler
Quick Answer
When an RSS feed stops updating, I open the feed address in a browser first, rule out a cached copy second, check my reader's polling interval third, look for a recent site change fourth and validate the XML last. Most stalled feeds turn out to be a cache or a reader that has not polled yet.
A feed that worked last month and shows nothing today is the most common problem RSS readers hit, and almost always the one people misdiagnose. My instinct is to blame the XML. In practice the far more likely causes are a cached copy being served, a feed address that moved or a reader that simply has not checked yet. Work the checks below in order and you will usually find the cause in under two minutes.
First, Understand the Five Kinds of Broken
These look identical in a reader and have nothing in common. Knowing which one you have saves all the guesswork that follows.
| Symptom | What it actually is |
|---|---|
| Reader shows an error and nothing else | Usually a 404 or a refusal. The endpoint is gone or the server is blocking automated requests. |
| Reader shows the same old items, never new ones | A stale cached copy, or a reader polling on a slow schedule. Frequently not a fault at all. |
| Feed loads in the browser but the reader ignores it | Malformed XML, or an HTML page served where XML was expected. Browsers are far more forgiving than readers. |
| Feed works directly, fails in the reader | A redirect chain, or the site serves different content to automated clients. |
| New items arrive but some are repeated | The site changed how it generates item identifiers. The feed is live, the identifiers are the problem. |
Check 1: Open the Feed URL in a Browser
I paste the feed address into a tab of its own, away from my normal pages. What I want is simple: readable XML containing my newest item, or an unmistakable error. If I get an HTML page, a login wall or a 404, the problem is at the source and nothing else matters yet.
If you would rather not install anything, curl answers the same question:
| Command | What it tells you |
|---|---|
curl -I https://example.com/feed.xml |
The status code, without downloading the body. 200 means the endpoint answers. |
curl -L -I https://example.com/feed.xml |
The same, following redirects, so a chain shows up as several responses. |
curl -L https://example.com/feed.xml | head |
The first lines of the document, which shows whether you received XML or an HTML page. |
A chain of redirects that never settles is effectively a broken feed for most readers, even though it opens fine in a browser.
Check 2: Rule Out Caching Before Anything Else
This is the single most common cause and it takes seconds to rule out. Publishers often serve feeds through a CDN or a caching plugin, and a cached copy can hang around for minutes or hours after something new is published. I open the feed URL with the cache bypassed and see whether the new item appears. If it appears only when I bypass the cache, the feed is healthy and the cache is the whole story. There is nothing to fix, and the new item will reach my reader on its next normal check.
A feed that is correct but not yet updated is a waiting problem, not a broken one.
Check 3: Know Your Reader's Check Interval
Readers poll on a schedule, not continuously. Minutes for some, an hour for others, longer on free tiers. A post published thirty seconds ago has usually not been looked for yet. Before deciding anything is wrong, I find out how often my reader checks and then wait one full interval.
This also explains feeds that look intermittent. Nothing is broken. You are simply watching a slow poller.
Check 4: Did the Site Change Recently?
If a feed worked and then stopped, and it stopped soon after a site update, the update is the suspect. A theme change, a plugin update or a site migration can alter the markup the feed was generated from, or change the address entirely, without changing anything a visitor sees. If the feed was working a week ago and stopped the day after an update, stop debugging the reader and look at the site.
The same thing happens at the other end. A publisher may move a feed from one address to another and leave the old path returning an error rather than a redirect. That is the case our guide to finding a feed for any website exists to solve, including sites that hide the address in the page source.
Check 5: Validate the XML Last
Malformed XML is worth chasing only after the first four checks come back clean, and it is genuinely rarer than people expect. I run the feed through the W3C feed validator. It reports the first structural problem rather than making me read the document myself, and it tolerates none of the leniency a browser shows.
If you own the site and the validator complains, the usual culprits are an unescaped ampersand in a title, a stray control character inside an item or an empty required field. If you do not own the site, this is where fixing stops and reporting begins.
What You Can Fix, and What Only the Publisher Can
Being clear about this saves a lot of wasted effort. As a reader I can fix a wrong saved address, a slow polling interval, a feed hidden behind a filter in my own reader and a stale cache on my side. I cannot fix a site that has deleted its feed, a publisher that has stopped syndicating, a server blocking my reader's requests or markup that a recent update broke.
Deleting and re-adding the feed is the most-repeated bad advice in RSS support, and it almost never works. Everyone following a feed shares it, so if it is broken for me it is broken for every other subscriber too. Re-adding only helps when the address you saved has changed, and then you need the new address rather than the same one entered again.
Replace a Feed That Is Genuinely Gone
When a source has moved or died, the fix is to find the current feed and swap it. I open the site's home page in a browser and look for the orange feed icon in the address bar, or read the source for a line containing application/rss+xml. If neither is there, the publisher may publish a page URL that your reader can turn into a feed on its own, which most readers offer when a plain address fails.
I follow the new feed, confirm the first few items look right, then delete the dead one. I keep a copy of any folders I had built around it, because the new feed is a different subscription and will not inherit them.
This is where an OPML export turns a chore into a minute. I export my list before I start, so if several feeds have died at once I am restoring rather than hunting. The mechanics are in Back Up and Move Your Feed List, and the reason it matters is the one the Google Reader shutdown taught an entire generation of readers.
FAQ
Why did my RSS feed stop updating?
The most common causes, in order, are a cached copy being served, a feed URL that moved, a site change that altered the markup the feed was built from and a reader checking on a slow schedule. Genuinely malformed XML is far rarer than people assume.
How do I check whether an RSS feed is still alive?
Open the feed URL directly in a browser. You want HTTP 200 and XML you can read, not an HTML page or a login wall. Adding -I to curl shows the status code and redirect chain without downloading anything.
Does deleting and re-adding a broken feed help?
Almost never. Everyone following a feed shares it, so if it is broken for you it is broken for them too. Re-adding only helps when the saved address has changed, in which case you need the new address rather than the same one again.
Can I fix an RSS feed that is not mine?
Only in one case: when the feed is fine and your copy of the URL is wrong. If the site itself has broken the feed you cannot repair it, though you can report it to the publisher or find a new feed for the same source.
How do I stop feeds breaking in the first place?
Export your subscription list to OPML regularly and keep dated copies. A list backup turns replacing a dead feed into one step instead of rebuilding months of curation, which is the lesson from the Google Reader shutdown.
Summary
Work the checks in order and stop at the first one that explains what you are seeing. I open the feed URL first, rule out caching second, confirm my reader's polling interval third, look for a recent site change fourth and validate the XML only if all four come back clean. Most stalled feeds turn out to be a cache or a moved address, and both are quick to resolve once you know which one you have.
Related Articles
How to Find an RSS Feed for Any Website
Every method for discovering the feed of almost any site, including sites that hide it.
Read moreBack Up and Move Your Feed List
Your whole subscription list in one portable file, so replacing a dead feed takes a minute.
Read moreWhat Google Reader's Shutdown Taught RSS Users
Why owning your list is the difference between a five minute repair and rebuilding from scratch.
Read moreKeep Every Feed in One Place You Control
RSS Wrangler stores your subscriptions in your browser, so switching or repairing a list never means starting again. It is free, private and works offline.
Add to Chrome