If you publish an RSS feed alongside your newsletter or blog, you’ve probably wondered how many people actually subscribe to it. The answer is: you almost never know, and the number you do see is usually wrong.
RSS was built in an era when privacy meant something different. Readers pull your feed; your server logs the request. That’s it. There’s no mandatory ping-back, no central registry, no “subscribe” event that fires when someone adds your feed to their reader.
Here’s what actually happens when someone subscribes, where the data lives, and how to get a realistic picture of your RSS audience.
What your server sees
Every time an RSS reader checks your feed, it makes an HTTP request. Your web server logs that request with a timestamp, IP address, and user agent string. That’s the raw material.
If you run WordPress, those logs live in your hosting provider’s control panel or via SSH at /var/log/apache2/access.log or /var/log/nginx/access.log. Most shared hosts archive or rotate logs after 7–30 days, so anything older than that is gone unless you explicitly save it.
User agents tell you which app fetched the feed: Feedly, Inoreader, NewsBlur, Apple Podcasts (if it’s a podcast feed), or a custom-built scraper. They don’t tell you how many people subscribed via that service—just that the service itself requested your feed.
Feedly, for example, fetches your feed once and caches it for all its users who subscribe to you. One request might represent 500 subscribers, or five. You can’t tell from the log.
What FeedBurner used to show (and why it stopped working)
FeedBurner was the go-to solution for RSS analytics until Google effectively abandoned it in 2021. It acted as a proxy: you pointed your feed URL to FeedBurner, and it served a wrapped version of your feed while counting requests and estimating subscriber counts.
It worked—barely—by analyzing user agent strings and request patterns, then applying heuristics to guess unique subscribers. But those heuristics broke as RSS readers changed how they cache and poll feeds. By 2023, most FeedBurner stats were flatlined or wildly inaccurate.
If you still use FeedBurner in 2026, the subscriber count you see is almost certainly stale. It hasn’t been maintained in years, and major readers like Feedly have changed their polling behavior multiple times since.
Where subscriber counts actually live
Some RSS services do report subscriber counts—but only if they choose to, and only for their own platform.
Feedly shows you how many Feedly users follow your feed if you claim it via their publisher tools. Log in at feedly.com, search for your feed, and look for the “Claim this feed” option. Once verified, you’ll see a follower count under the feed’s public page. It’s accurate for Feedly, but tells you nothing about Inoreader, NetNewsWire, or any other reader.
Substack and Beehiiv both offer RSS feeds for newsletters, but neither exposes a public subscriber count for the feed itself—only for email subscribers. If someone adds your Substack RSS to their reader, you won’t see that in your Substack dashboard.
WordPress plugins like Jetpack Stats will show you feed views in aggregate, lumped together with other traffic. You can filter by /feed/ in your stats panel, but again, it’s requests, not subscribers.
How to measure RSS readership in 2026
If you need real numbers, track clicks instead of subscriptions. Embed a unique UTM parameter in every link inside your RSS feed:
https://yoursite.com/article?utm_source=rss&utm_medium=feed&utm_campaign=main_feed
Then measure those clicks in Google Analytics, Plausible, or Fathom. This tells you how many people read and acted on your feed content, which is more useful than a theoretical subscriber count anyway.
You can also set up a redirect link for one high-value post per week and track how many RSS readers click through. Tools like Bitly or your own URL shortener will give you exact click counts.
Another option: if you run a podcast feed, most podcast hosting platforms (Transistor, Captivate, Buzzsprout) report per-app download stats. They can’t tell you subscriber counts either, but they break down listens by Apple Podcasts, Spotify, Overcast, etc., which gives you a clearer picture than a blog RSS feed ever will.
What to do if you need proof for sponsors
Sponsors usually don’t care about RSS subscribers—they care about reach. If you monetize via sponsorships and someone asks for RSS metrics, give them:
- Total feed requests per month (from server logs or a plugin like Jetpack)
- Click-through rates on UTM-tagged links in recent feed posts
- Feedly follower count (if you’ve claimed your feed)
- Email subscriber count as the primary metric, with RSS as a bonus
No sponsor expects RSS to be your main channel in 2026. If they do, they’re either very niche (developer tools, open-source communities) or haven’t updated their media kit requirements in a decade.
Want more operator-focused breakdowns like this? Subscribe to One Two Three Send and get one article like this every day, covering everything from newsletter tools to WordPress hosting to AI prompts that actually work.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.