Traffic Source Classifier
Paste referrer URLs — one per line — and we'll classify each one as AI, Social, Search, Direct, or Referral. Bulk classify up to 100 at once.
Free. No account needed.
0 referrers
What Is a Referrer URL?
When someone clicks a link and arrives at your site, their browser automatically sends an HTTP header called the "Referer" (deliberately misspelled in the original HTTP specification from 1996). This header contains the URL of the page the visitor came from.
A visitor who clicked a link in a tweet arrives with a referrer of https://twitter.com. A visitor who clicked a Google search result arrives with https://www.google.com. A visitor who typed your URL directly, or followed a link from a Slack message, arrives with no referrer at all — and gets counted as "direct."
The classifier reads those referrer values and maps them to a human-readable category using the same classification logic that powers the VisitorPurse dashboard.
Why So Much Traffic Shows as "Direct"
"Direct" doesn't mean people typed your URL. It means the browser didn't send a referrer header. This happens more often than most founders realise — and for reasons that have nothing to do with someone actually navigating to you directly.
- Messaging apps strip referrers. Slack, WhatsApp, iMessage, Telegram, and Discord all open links in embedded browsers that don't pass the referrer header. Every link shared in a private group chat looks like direct traffic — this is what people call "dark social."
- HTTPS → HTTP loses the referrer. Browsers drop the referrer header for security when a user moves from a secure page (HTTPS) to an insecure one (HTTP). If your site isn't fully on HTTPS, you're losing attribution from every inbound link that comes from an HTTPS page.
- Email clients behave inconsistently. Gmail in a browser passes a referrer. Apple Mail does not. Outlook depends on the version. Email newsletters that drive traffic often look like direct visits in analytics.
- Some native mobile apps drop referrers. iOS and Android apps that open links in an in-app browser (rather than Safari or Chrome) often don't pass referrer headers at all.
The result: a significant portion of your most valuable traffic — word-of-mouth shares in Slack communities, newsletter mentions, private Reddit DMs — is invisible in standard analytics tools. VisitorPurse can't recover those (the referrer simply wasn't sent), but knowing why helps you set realistic expectations.
The Five Traffic Categories Explained
| Category | What it means | Common referrers |
|---|---|---|
| 🤖 AI | An AI chatbot recommended your site in an answer | chatgpt.com, claude.ai, perplexity.ai |
| 👥 Social | A social platform linked to you | twitter.com, reddit.com, linkedin.com |
| 🔍 Search | An organic search result was clicked | google.com, bing.com, duckduckgo.com |
| 🎯 Direct | No referrer header was sent | (empty) — dark social, typed URLs |
| 🔗 Referral | Another website linked to you | Any domain not in the above groups |
Where to Find Your Referrer URLs
If you're looking for raw referrer data to classify, here's where to get it:
- →GA4: Reports → Acquisition → Traffic Acquisition. Set the dimension to "Session source" and export the raw values.
- →Cloudflare Analytics: Your dashboard → Traffic → Top Referrers. Free on all plans.
- →Server access logs: Search for the
Referer:header in your nginx or Apache logs. Every request includes it if the browser sent one. - →VisitorPurse: Every event in your dashboard includes the raw referrer, already classified. No manual work needed.