Add /feed/ to the end of any WordPress site URL. Go ahead, try it on your own site. You’ll see an XML document listing your most recent posts with full content — titles, excerpts, dates, author names, and often the entire post body.
Now ask yourself: who’s reading this?
For most business websites, portfolios, agency sites, and WooCommerce stores, the answer is nobody. RSS readers peaked in 2013 when Google Reader shut down. The technology still exists, and some people still use it, but the vast majority of WordPress sites are generating RSS feeds that nobody subscribes to and nobody reads.
What does read them? Content scrapers, spam bots, and SEO tools harvesting your content.
What is RSS in WordPress?
RSS (Really Simple Syndication) is a standardized XML format that lets people subscribe to your content using feed reader apps. When you publish a new post, the RSS feed updates, and subscribers see it in their reader without visiting your site.
WordPress generates multiple RSS feeds by default:
- Main feed —
yoursite.com/feed/ - Comments feed —
yoursite.com/comments/feed/ - Category feeds —
yoursite.com/category/news/feed/ - Tag feeds —
yoursite.com/tag/wordpress/feed/ - Author feeds —
yoursite.com/author/admin/feed/ - Custom post type feeds — if applicable
- Search results feed —
yoursite.com/?s=keyword&feed=rss2
Each of these generates tags in your HTML , advertising their existence to feed readers and bots. That’s half a dozen URLs exposing your content in a structured, easy-to-scrape format.
Why should you care?
Content scraping. Your RSS feed is the easiest way to steal your content automatically. Scraper bots subscribe to your feed and republish your posts on spam sites within minutes of publishing. They get your full content delivered in a clean, structured format — no need to even visit your site. If your feed includes full post content (the WordPress default), you’re essentially handing scrapers a gift.
Information disclosure. Author feeds reveal your WordPress usernames. Comment feeds expose email addresses if you use Gravatar. The main feed shows your publishing schedule, content strategy, and site structure — all useful intelligence for attackers or competitors.
Unnecessary tags in . Each feed adds a discovery link to your HTML. That’s extra markup on every page, and while the performance impact is minimal, it’s part of the broader cleanup that improves page efficiency.
404 crawl waste. Bots discover your feed URLs and keep requesting them. If you later change your permalink structure or remove categories, those feed URLs return 404s that clog your crawl logs and waste Googlebot’s crawl budget.
You probably have zero subscribers. Unless you’re running an active blog with a content-focused audience, your RSS subscriber count is almost certainly zero. Check your server logs for requests to /feed/ — you’ll likely see only bots, not humans using Feedly or Inoreader.
The quick fix
Add this to your theme’s functions.php or site-specific plugin:
// Disable all RSS feeds
add_action( 'do_feed', 'ovkit_disable_feeds', 1 );
add_action( 'do_feed_rdf', 'ovkit_disable_feeds', 1 );
add_action( 'do_feed_rss', 'ovkit_disable_feeds', 1 );
add_action( 'do_feed_rss2', 'ovkit_disable_feeds', 1 );
add_action( 'do_feed_atom', 'ovkit_disable_feeds', 1 );
function ovkit_disable_feeds() {
wp_redirect( home_url(), 301 );
exit;
}
// Remove feed links from head
remove_action( 'wp_head', 'feed_links', 2 );
remove_action( 'wp_head', 'feed_links_extra', 3 );
This does two things: it redirects any feed URL to your homepage with a 301, and it removes the discovery tags from your HTML . Clean and complete.
301 vs 404: Redirecting to the homepage is better than returning a 404. It’s a gentle signal to feed readers and crawlers that the content moved, rather than an error. Existing backlinks to your feed URL pass link equity to your homepage instead of hitting a dead end.
The one-click solution
OvKit includes Disable RSS Feeds under Features → Cleanup. One toggle removes all feed output: main feed, comment feed, category feeds, tag feeds, author feeds, and the tags in . Feed URLs return a proper redirect instead of XML.
What happens after you fix this?
- No more RSS XML available — scrapers lose their easiest content source
is cleaner — fewertags on every page- Author usernames stop leaking via author feed URLs
- Feed-related 404s disappear from your crawl logs
- Your site’s content stays on your site — visitors need to actually visit to read it
Verify: add /feed/ to your URL. You should be redirected to your homepage instead of seeing XML.
FAQ
What if I’m running a blog and people actually subscribe via RSS?
Then keep it. RSS is genuinely useful for content-focused sites with engaged audiences. Check your server logs or add an RSS subscriber tracking parameter to confirm you have real subscribers. If you see Feedly, Inoreader, or NewsBlur user agents hitting your feed regularly, those are real readers. Don’t disable something people are using.
Does disabling RSS affect my SEO or Google News?
For standard SEO, RSS has no impact on rankings. Google crawls your site directly, not through your RSS feed. However, if you’re in Google News and rely on your RSS feed for article submission, keep the main feed active. Most Google News publishers have migrated to sitemap-based submission, but verify your setup first.
Will disabling RSS break any plugins like Mailchimp or email newsletter tools?
Some newsletter plugins (Mailchimp, MailPoet) can use RSS to auto-send new post digests to subscribers. If you use an RSS-to-email feature, disabling RSS will break that automation. Switch to a plugin-native method (most newsletter tools have direct WordPress integration) before disabling RSS.
Related reads: