Troubleshooting · Troubleshooting
How to Fix a Broken RSS Feed in WordPress
Short answer
A broken WordPress RSS feed usually comes from a wrong feed URL, stale permalink rules, invalid XML, a plugin or theme conflict, or a stale cache. Open yoursite.com/feed/ and yoursite.com/?feed=rss2, run the feed through the W3C validator, and re-save Settings → Permalinks. Fix the exact error the validator or browser shows, then purge the cache and check the feed again.
Key takeaways
- The main WordPress feed is usually yoursite.com/feed/, and yoursite.com/?feed=rss2 is the query-string form of the same feed.
- WordPress uses RSS 2.0 as its default feed type unless a plugin changes it through the default_feed filter.
- Re-saving Settings → Permalinks rebuilds the rewrite rules that make /feed/ work.
- A feed must be valid XML, and the W3C validator reports the exact line where parsing fails.
- A stale cache can keep serving an old feed after you fix the site, so purge the feed URL after each fix.
- Back up the site before you switch themes or turn off plugins to find a conflict.
What does a broken RSS feed mean in WordPress?
A broken RSS feed means a reader, app or service cannot read the XML list of your recent posts.
An RSS feed is a machine-readable version of the content of a blog or website, as WordPress.org explains in its RSS block documentation. Readers use that XML file to show new posts without visiting the site.
A feed can fail in several ways, so the fix depends on the exact symptom. It can return a 404 page, a blank page, an XML error, a login page or old posts. Note the exact message before you change anything.
How do you find your WordPress RSS feed URL?
Your main feed is usually at yoursite.com/feed/, with yoursite.com/?feed=rss2 as the query-string form.
WordPress creates feeds for posts, comments, categories, tags and authors. The main posts feed is the one most readers use, so test that address first.
The default feed type is RSS 2.0. Developer.WordPress.org states that the default feed is rss2, unless a plugin changes it through the default_feed filter, in its get_default_feed() reference.
| Feed | Example address | What it holds |
|---|---|---|
| Main posts feed | yoursite.com/feed/ | Recent posts in RSS 2.0 |
| Query-string feed | yoursite.com/?feed=rss2 | Same posts, without pretty permalinks |
| Atom feed | yoursite.com/feed/atom/ | Recent posts in Atom format |
| Comments feed | yoursite.com/comments/feed/ | Recent comments |
| Category feed | yoursite.com/category/news/feed/ | Posts from one category |
WordPress also lists rss, atom and rdf as feed types in its get_the_content_feed() reference. Most readers expect RSS 2.0, so use that address when you share the feed.
What should you check first when the feed fails?
Open both feed addresses, note the HTTP status and the first lines of the response, then validate the feed.
Start with the two main addresses in a browser. If /feed/ fails but /?feed=rss2 works, the feed itself is fine and the problem is in the URL routing. If both fail the same way, the cause is deeper.
Use the W3C Feed Validation Service next. It works with RSS 0.90 through 2.0 and Atom feeds, and you enter the feed address and click Validate. The validator checks the feed against the RSS 2.0 specification and reports errors with line numbers.
| Symptom | Likely cause | First action |
|---|---|---|
| 404 on /feed/ | Stale rewrite rules or wrong URL | Re-save permalinks, then test again |
| XML parsing error | Extra output or bad characters in a post | Validate the feed and read the line number |
| Old posts only | Stale cache | Purge the feed URL at every cache layer |
| Login or HTML page | Feed blocked, redirected or disabled | Check security and redirect plugins |
| Feed works, one post missing | Post status, date or category filter | Check the post status and Reading settings |
If the 500 error guide matches what you see, fix that server error first. A feed cannot return valid XML while the site returns a 500 error.
Why does the feed return a 404 error?
A 404 on /feed/ usually means WordPress rewrite rules are stale, the URL is wrong, or the server cannot route pretty permalinks.
WordPress.org lists three permalink types and six structures on its Using Permalinks page. The six options are Plain, Day and name, Month and name, Numeric, Post name and Custom Structure. The default setting is Plain.
Fix stale rules first, because it takes seconds and needs no code change.
- Go to Settings → Permalinks in the WordPress dashboard.
- Leave the selected structure unchanged.
- Click Save Changes.
- Open yoursite.com/feed/ again in a fresh browser tab.
Saving the page rebuilds the rewrite rules. If /?feed=rss2 worked before this step and /feed/ works after it, the rules were the problem.
If the 404 stays, check the address itself. A category feed needs the exact category slug, and a feed on a site in a subfolder needs that folder in the address. The 404 error guide covers the same rewrite checks for posts and pages.
WordPress.org also says your host should set up the web server for Pretty permalinks, and you should contact your host if that setup is missing. That applies when saving permalinks never fixes a 404.
Why does the feed show an XML parsing error?
An XML parsing error means something broke the XML before the reader could parse it, often extra text printed before the XML declaration.
XML is strict. A blank line, a PHP warning or a stray character before <?xml makes the whole document unreadable to a strict parser. The browser may show a message such as “XML declaration allowed only at the start of the document.”
The RSS 2.0 specification, current version 2.0.11 published by the RSS Advisory Board on March 30, 2009, lists three required channel elements: title, link and description. The RSS 2.0 specification defines those three as the name of the channel, the URL of the website and a phrase describing the channel.
Find the exact fault with the validator.
- Paste the feed URL into the W3C Feed Validation Service.
- Click Validate and read the first error, including its line number.
- Open the post named near that line and look for pasted code, odd characters or broken HTML.
- Fix or remove that content, save the post, then validate again.
A “headers already sent” warning points to the same kind of extra output. The headers already sent guide explains how extra output before headers breaks a page.
Turn off on-screen PHP warnings on a live site while you work. Debug output printed into the feed is itself invalid XML, so it hides the real fault. Use the debugging handbook to log errors to a file instead of showing them.
Why does the feed show old posts or missing posts?
A feed that shows old posts is usually stale cache, while a missing post is usually a status, date or Reading setting problem.
Check the post first. A draft, scheduled post or private post does not appear in a public feed. A post with a future date also stays out until that date passes.
Then check Settings → Reading. WordPress.org explains on its Reading Settings page that “Syndication feeds show the most recent” controls how many posts a feed holds. The same page says “For each article in a feed, show” chooses Full text or Excerpt.
If the feed holds only a few posts, raise the number in that setting and save it. If readers see only short text, switch the setting to Full text. The page notes that an excerpt could save bandwidth, so the choice is a trade-off between feed size and reader convenience.
Cache is the next layer to clear. Purge these in order:
- The cache plugin on the site, if one is active.
- The host cache or CDN cache for the exact feed URL.
- The feed reader, by removing and re-adding the feed.
Cloudflare documents single-file purge in its purge by single-file guide. A single-file purge removes that cached resource across all data centers, and the next request fetches the latest version from the origin server.
Cloudflare also lists a Free plan limit of 800 URLs per second for single-file purges, as of November 2026. That limit is high enough for a feed URL, so purge the feed address only.
If changes are not showing on normal pages too, the cache is the likely cause for the feed as well.
How do you find a plugin or theme that breaks the feed?
Turn off plugins and switch themes in a safe order, testing the feed after each change, until the feed works again.
Feed problems often start after a plugin update, a new theme or a new redirect rule. A plugin can disable feeds, redirect them or print extra output. A theme can do the same from its functions.php file.
Back up the site before you start. The WordPress backup guide shows how to make a backup you can restore if a change makes things worse.
Follow this order on a staging copy when you can:
- Turn off caching, security and SEO plugins first, then test the feed.
- Turn off the remaining plugins one at a time, testing after each one.
- Switch to a default theme such as Twenty Twenty-Five, then test the feed.
- Turn the plugins back on one at a time until the fault returns.
The last plugin or theme you re-enable before the fault returns is the suspect. Check its settings for a feed, redirect or “disable RSS” option before you remove it.
Theme feed links matter here too. Developer.WordPress.org says automatic feed links enable post and comment RSS feeds by default, and classic themes add them with add_theme_support( 'automatic-feed-links' ). Its Theme Functions handbook adds that block themes have this support enabled automatically.
How do you fix feed settings in WordPress?
Set the feed count and the full-text choice in Settings → Reading, then re-save permalinks and clear the cache.
These settings control what the feed holds, not whether the feed loads. Use them after the feed itself works.
- Go to Settings → Reading.
- Set Syndication feeds show the most recent to the number of posts you want in the feed.
- Under For each article in a feed, show, pick Full text or Excerpt.
- Click Save Changes.
- Re-save Settings → Permalinks if you changed anything about URLs.
- Purge the feed URL in your cache plugin and CDN.
A custom feed needs one more step. Developer.WordPress.org states that add_feed() adds a new feed type, such as /atom1/, and requires one-time use of flush_rules() to take effect. Its add_feed() reference documents that rule, and re-saving permalinks performs that flush from the dashboard.
Check Tools → Site Health if the feed still fails. The Site Health Info tab lists the WordPress version, PHP version, active plugins and themes.
Developer.WordPress.org notes that the debug information filter feeds that Info screen and was introduced in version 5.2.0. Share that Info tab with your host when you ask for help.
How do you know the feed is fixed?
The feed is fixed when it returns a 200 status, validates cleanly and shows your latest post in a reader.
Run these three checks in order.
- Open yoursite.com/feed/ and confirm the XML lists your latest post with its correct title, link and date.
- Run the same URL through the W3C Feed Validation Service and confirm it reports no errors.
- Add the feed to a feed reader and confirm the latest post appears there.
A browser message about missing style information is not an error. Browsers show raw XML without styling, and that message does not mean the feed is broken.
Wait for the reader to refresh if the first check passes but the reader still shows old posts. Readers poll feeds on their own schedule, so a reader can lag behind a fixed feed for a while.
Remove and re-add the feed in the reader if it still shows old posts after an hour.
What mistakes should you avoid?
Do not edit core WordPress files, do not guess at the feed URL, and do not leave debug output on a live site.
- Do not edit
wp-includes/feed-rss2.phpor other core files. Updates overwrite those files, so the fix will vanish. - Do not add a feed plugin on top of a broken feed without finding the cause first. A new plugin can hide the error instead of fixing it.
- Do not change the permalink structure to fix a feed. Changing the structure changes every post URL on the site.
- Do not turn off security or caching for the whole site to test a feed. Turn off one plugin at a time and turn it back on after the test.
- Do not share a feed URL with tracking parameters. Use the clean
/feed/address so readers and validators fetch the same file. - Do not skip the backup before you switch themes or turn off plugins. A backup is the fastest way back if a test breaks the site.
Frequently asked questions
What is the WordPress RSS feed URL?
The main feed is usually yoursite.com/feed/, and yoursite.com/?feed=rss2 is the query-string form of the same feed. Category feeds add /feed/ after the category address, and the comments feed is at yoursite.com/comments/feed/. Use the address your site actually serves, not a guessed variation, and test it in a browser before you share it with readers.
Why does my RSS feed show a 404 error?
A 404 on /feed/ usually means the rewrite rules are stale or the URL is wrong. Go to Settings → Permalinks and click Save Changes without changing the structure, then test the feed again. If the query-string form /?feed=rss2 works but /feed/ does not, the feed is fine and the routing is the problem. If both fail, check the server setup with your host.
Why does my feed show old posts after I publish a new post?
Old posts in a feed usually mean a cache is serving an old copy, or the reader has not polled the feed again. Purge the feed URL in your cache plugin, host cache and CDN, then remove and re-add the feed in the reader. Also check Settings → Reading to confirm the feed count is high enough to include the new post.
Can a plugin disable my WordPress RSS feed?
Yes, a plugin can disable, redirect or change a feed. Security, SEO and feed-control plugins sometimes include a feed setting, so check those settings first. If you cannot find the setting, turn off plugins one at a time on a staging copy and test the feed after each change. The plugin that restores the feed when turned off is the likely cause.
How do I check if my WordPress RSS feed is valid?
Paste the feed URL into the W3C Feed Validation Service and click Validate. It checks the feed against the RSS or Atom specification and reports errors with line numbers. Fix the first error it lists, save the change, then validate again. A clean result plus your latest post in the feed means the feed is valid.
When should I contact my host about a broken RSS feed?
Contact your host when the feed returns a server error, when re-saving permalinks never fixes a 404, or when the feed fails the same way with all plugins off and a default theme active. Send the host the exact feed URL, the error message, the validator result and the Site Health Info tab. Those four items let the host check the server, cache and rewrite rules.
Sources
- RSS block WordPress.org
- Settings Reading screen WordPress.org
- Customize permalinks WordPress.org
- get_default_feed() WordPress Developer Resources
- RSS 2.0 Specification RSS Advisory Board
- Feed Validation Service W3C
- Purge by single-file Cloudflare Docs
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
