CorrectFeed

RSS feed 404 Not Found: how to fix a broken feed URL

If your RSS feed returns 404 Not Found, the feed URL is broken from the reader’s point of view.

That usually means one of four things:

  • the feed URL changed
  • the route no longer exists
  • a redirect or rewrite is broken
  • the server is returning the wrong thing for the feed path

Quick answer

To fix an RSS feed 404, first confirm the exact feed URL, then make sure it returns:

  • HTTP 200
  • RSS or Atom XML
  • a stable canonical path with no redirect chain

If the old feed URL changed, the safest fix is usually one stable 301 redirect to the new canonical feed URL.

Fast checklist

  1. Confirm the exact feed URL your reader is trying to fetch.
  2. Check whether that URL still exists.
  3. Make sure it returns XML, not HTML.
  4. If the feed moved, add one stable 301 redirect.
  5. Validate the final endpoint.

Common causes of RSS feed 404 errors

1. The feed URL changed

Examples:

  • /feed/ changed to /feed.xml
  • a platform migration changed the default feed path
  • http became https
  • www or non-www behavior changed

2. The route disappeared

Examples:

  • a CMS or theme update disabled feed routes
  • a static site stopped generating the feed file
  • a headless rebuild dropped the XML endpoint

3. A CDN, proxy, or rewrite broke the path

Examples:

  • feed requests now hit a missing origin path
  • rewrite rules no longer map to the XML endpoint
  • a proxy serves an error page instead of the feed

4. The URL is “almost right” but not actually correct

Examples:

  • using a page URL instead of the feed URL
  • missing /feed/, /rss.xml, or /atom.xml
  • using a comments feed instead of the main site feed

Step 1: confirm the exact feed URL

Before fixing anything, make sure you are debugging the real feed URL.

Common feed URL patterns include:

  • WordPress: /feed/ or /?feed=rss2
  • Ghost: /rss/
  • static sites: /feed.xml, /rss.xml, or /atom.xml

If you are not sure which feed URL is supposed to be canonical, check the site’s HTML for feed discovery links.

Step 2: check what the endpoint actually returns

A broken feed URL should not be diagnosed only in the browser UI. Check the raw response.

Useful commands:

curl -I https://example.com/feed.xml
curl -L -I https://example.com/feed.xml
curl -L https://example.com/feed.xml | head

What you want:

  • HTTP 200
  • XML output
  • a <rss> or <feed> root element

What often goes wrong instead:

  • 404 HTML page
  • login wall returned as HTML
  • block page from a WAF or proxy
  • redirect chain that never settles cleanly

Step 3: fix moved URLs with one stable redirect

If the feed used to exist at one path and now lives at another, prefer:

  • one 301 from old URL to new URL
  • no chains
  • no loops
  • no flip-flopping temporary redirects

Many readers are fragile around feed redirects, so simpler is better.

Step 4: make the canonical feed path obvious

If your site publishes a feed, include discovery links like:

<link rel="alternate" type="application/rss+xml" title="RSS" href="https://example.com/feed.xml">
<link rel="alternate" type="application/atom+xml" title="Atom" href="https://example.com/atom.xml">

That helps readers, browsers, and crawlers locate the correct feed URL.

Step 5: validate the repaired feed

Once the 404 is fixed, validate the endpoint to make sure it is not only reachable, but also parseable.

Use:

If the endpoint now returns XML but the feed still fails, the problem has moved from URL reachability to feed validity.

When this page should hand off to other pages

Use this page for the exact problem: RSS feed returns 404 Not Found.

If the problem turns out to be something else, go to:

Prevent future feed 404s

  • keep one canonical feed URL for the long term
  • treat the feed path like a public API
  • monitor status code and XML output
  • avoid user-agent-specific behavior on feed endpoints
  • allowlist feed paths in CDN and WAF layers when needed

FAQ

Why is my RSS feed returning 404 Not Found?

The feed URL may have changed, the route may no longer exist, a rewrite rule may be broken, or a CDN, CMS, or proxy may be serving the wrong endpoint.

Will redirecting the old feed URL fix the problem?

Usually yes, if you use one stable 301 redirect from the old feed URL to the new canonical feed URL and avoid redirect chains.

What should the fixed feed URL return?

The working feed URL should return HTTP 200 and valid RSS or Atom XML, not an HTML page, login wall, or error template.

Fix RSS/Atom feeds and OPML lists

Paste a feed/OPML URL, upload a file, or paste XML — then validate and fix it.

Fix my feed / Import OPML Back to Help