Inoreader referrer traffic
Inoreader is an RSS and feed-reader service where people subscribe to your feed and read articles in the reader. Web clicks can appear as inoreader.com referrals, but app and mobile reads often send no referrer, so UTM tags are the reliable way to attribute Inoreader-driven visits.
What this means
Inoreader is a feed reader where people subscribe to RSS/Atom feeds, including yours, and read new articles inside the reader. When a subscriber clicks through on the web, traffic can reach your site as a referral from inoreader.com.
This is a loyalty channel: feed subscribers are returning readers who opted into your content, which is qualitatively different from one-off social or search discovery.
Why the referrer can be missing
Inoreader's mobile apps and in-app readers commonly open articles without forwarding a Referer header, sending those reads to direct or unknown traffic. Referrer-policy downgrades reduce detail further.
Feed readers carry your item link as published, so add utm_source=inoreader (or a broader utm_source=rss) and utm_medium=referral to the canonical link in your feed. The query string survives the reader, so feed clicks stay attributable even when the Referer header is absent.
- Host you may see: inoreader.com (web)
- Recommended tags: utm_source=inoreader, utm_medium=referral
- App reads often arrive direct/unknown — UTM in the feed link recovers them
How it appears in analytics and logs
A referrer on inoreader.com means a subscriber clicked through from the reader on the web. App and mobile reads often arrive with no referrer and blend into direct, so the header understates Inoreader unless links are tagged.
Diagnostic use case
Recover Inoreader feed clicks that would otherwise be filed as direct, and distinguish loyal RSS-subscriber traffic from organic search.
What WebmasterID can help detect
WebmasterID groups Inoreader referrals as a feed-reader channel and reconciles them with your UTM tags, so loyal RSS-subscriber clicks stay separate from genuine direct traffic.
Common mistakes
- Assuming all Inoreader reads show inoreader.com — app reads arrive as direct.
- Not tagging feed links, so RSS-subscriber clicks vanish into direct.
- Treating returning feed subscribers as new search discovery.
Privacy and accuracy notes
Attribution uses only the Referer header and any UTM parameters. No Inoreader subscriber is identified. WebmasterID records the channel, not the person.
Related pages
- Feedly referrer traffic
Feedly is an RSS feed reader where subscribers follow your content and click through to read in full. Web clicks can appear as feedly.com referrals, but mobile-app reads frequently send no referrer, so UTM tags on your feed links are the reliable way to attribute Feedly traffic.
- Pocket referrer traffic
Pocket is a save-for-later reading service where people queue articles to read on their own schedule. Web reads can appear as getpocket.com referrals, but the apps frequently send no referrer and reads are time-shifted, so UTM tags are the reliable way to attribute Pocket-driven visits.
- Referrer grouping into channels
Analytics platforms do not report every raw referrer separately — they map hosts into channel groups such as organic search, paid, social, referral, email, and direct. Understanding the default rules explains why a click ends up in one bucket versus another, and why a custom source can be misfiled until you adjust the grouping.
- Campaign links
Tag feed links so RSS-reader clicks are attributable despite a missing referrer.
Sources and verification notes
- InoreaderRSS/feed reader; in-app referrer behaviour is a general reader-app pattern.
- MDN — Referer header
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.