Open your analytics and “Direct” is often the biggest slice. It reads like a place people come from. In practice it’s the bucket for every visit that arrived without a label, and plenty of those visits had a source that got lost on the way.
A visit only gets credited to a source when the browser tells your site where it came from. Many things stop that. Some you can fix, and the rest you can learn to read.
Vireo sorts every visit into six groups
The “Where visitors come from” card on the Overview screen puts each visit in one of six groups: Direct, Search, AI assistants, Social, Email and Other sites. A group with nothing in it is hidden, except Direct, which always shows. Each group header counts every site in the date range, including the ones outside the ten listed under it. When none of a group’s sites made the top ten, the card says “None of these made the top ten. Filter by this source to list them.”
Vireo checks a visit in a fixed order: Android app names first, then AI assistants, Email, Search, Social, and finally Other sites. That order settles the edge cases. It’s why mail.google.com counts as Email and gemini.google.com counts as an AI assistant, while google.com stays in Search. The ChatGPT traffic post covers the AI group in full.
Search covers Google, Bing, Yahoo, DuckDuckGo, Baidu, Yandex, Ecosia, Startpage, Brave and Qwant, with their country domains and subdomains. The Google app on Android shows as “Google app” and counts as Search. Social covers the big networks, from Facebook, Instagram, X and LinkedIn to Reddit, Hacker News, YouTube, Mastodon instances and Bluesky. Email covers webmail such as Gmail, Outlook, Yahoo Mail, Proton Mail and Fastmail, plus the Gmail and Outlook Android apps. Other sites is every referring host that no other group claims.
Vireo stores the referrer’s host only: the site’s address, lowercased, without www.
Direct is what’s left over
The card describes Direct as “Visitors who arrived with no referrer: typed the URL, used a bookmark, or came from an app or email client.”
Vireo works it out by subtraction. It takes everything your site served and removes everything a referrer claims. Whatever remains is Direct. Pageviews come out exact.
Why a visit loses its source
A browser reports where a visitor came from in the Referer header. When someone clicks a link, the header holds the address of the page that contains the link. MDN adds that “the request’s referrer policy defines the data that can be included”, and several things switch the header off.
Apps and email clients are the first. The Vireo docs note that many apps and browsers strip the referrer, and so do links in PDFs and email clients. A reader who taps your link in a mail app looks identical to someone who typed your address.
Plain HTTP is the second. When a page sets no policy, browsers use the default referrer policy, strict-origin-when-cross-origin. For a link to another site, it sends only the origin, with no path. When the link goes from HTTPS to a less secure destination, it sends nothing at all. If your site is still on HTTP, visits from HTTPS sites arrive as Direct.
Publishers can also opt out on purpose. A site that sets Referrer-Policy: no-referrer omits the header, and so does any link with rel=“noreferrer”. The W3C Referrer Policy spec lists every policy a site can choose.
Your own site adds to it. A click from one of your pages to another isn’t a referral, so Vireo drops the referrer, ignoring www. Because Direct is every pageview minus the referred ones, those internal pageviews end up in Direct. The server also drops your own hosts, connected sites, headless front-end origins, localhost, private-network names such as .local, .internal and .test, and bare IP addresses. Those pageviews count as Direct too.
Untagged campaigns are yours to fix. A newsletter or social post link with no tags depends on whatever the app sends, and often that’s nothing.
Then there’s automation. Bots often arrive with no referrer, so they pile into Direct. Vireo filters some automated visits that arrive with no referrer, and an optional setting catches more. That’s why bot filtering matters for your Direct number. The posts on reading a traffic spike and how much traffic is bots go deeper.
Each visit counts under the source it came from
Vireo credits each visit to the source it arrived from that day, without following anyone across days. A returning visitor who types your address today is Direct today. The cookieless analytics post explains how that works.
How to shrink Direct, and read the rest
You can’t empty it, but you can cut it down.
Tag the links you send. Newsletter links, social posts and partner links should carry UTM tags, and the UTM links guide shows how. With utm_medium=email or utm_medium=newsletter, the free plugin credits the visit to Email. Those clicks often arrive with no referrer, so the tracker sends them as the utm_source followed by .email, and they land in Email instead of Direct. The Email group appears in Where visitors come from once the range has email visits. This works in the free plugin and needs no Pro.
Read the names. Android apps send a referrer like android-app://com.google.android.gm, which looks like gibberish. Vireo translates the known ones into plain names: Gmail, Outlook, LinkedIn, Facebook, X, Reddit, Slack, Telegram and Google app. Once one of those apps sends a referrer, you’ll see it by name. The referrer directory explains the confusing entries and why the full URL is missing, with pages for the Gmail app, t.co, l.facebook.com and Outlook’s safelinks.
The bot panel is worth a look too. Bot filtering is always on, and the Referrer spam count shows how many hits from spam hosts were kept out of your totals. The bot filtering docs explain each kind.
On plain HTTP, visits from HTTPS sites arrive without a referrer, so move to HTTPS if you haven’t.
The Source filter at the top of the dashboard helps with the rest. It narrows the totals, the daily chart, Top pages and the referrer list to one group, Direct included. Filter to Direct and you can see which pages that traffic reads. Click any referrer’s name to open its own screen, with pageviews in range, visitors in range, a daily chart and the posts it sent people to. The referrers docs go through each screen.
Search Console covers search terms. Google doesn’t pass search terms to sites, so no analytics plugin can read them from a visit. Search engines that hide the search itself still pass their own name, so those visits land in Search. Search Console shows the searches behind that traffic. It’s free and runs through a Google service account, and the Search Console docs walk through the setup.
When a referral spike is spam
A surge from a domain you’ve never heard of may be referrer spam: fake visits that exist only to get a domain into your reports. Vireo ships with a bundled list of known referrer-spam hosts, the Matomo list. Hits from them never reach your totals. They’re counted under “Referrer spam” in the bot panel instead.
A host that isn’t on the list gets caught by behavior. When a host first seen in the last 45 days sends at least 30 pageviews over two or more days, and nearly every visit views one page with few landing on a post, Vireo tags it “suspected junk” in Where visitors come from. Administrators see a “Block this referrer” button beside the tag.
Blocking adds the host to the “Blocked hosts” list under Settings, Tracking. Its visits are filtered like bots from then on, and earlier rows are hidden from reports. Blocking deletes nothing, and removing the line unblocks the host. A suspect stays in the list but is left out of What changed and the weekly highlights.
If the spike looks like real readers, the traffic spike post lists the signs.
What’s free and what’s Pro
The free plugin covers everything above: the six groups, the Email channel, the Source filter, referrer screens, spam handling and Search Console. Vireo Pro adds reports on UTM campaigns by Source, Medium and Campaign, in the Campaigns tab. In the free plugin, a tagged link’s visit counts under the referrer it came from, and email-tagged links go to Email.
Shrink what you can, accept the rest
Tag the links you send and move the site to HTTPS. Whatever stays in Direct arrived without a label, and you can leave it there.