Direct traffic is the amount of web traffic you receive from users who visit your website through a URL directly from their browsers. In terms of Google Analytics (GA), it is defined as the traffic that has arrived on your website with no source or data.
Many times when GA finds no data on the traffic source it attributes the sessions to direct traffic.
Reasons why direct traffic occurs:
- Manual URL entry and bookmarks by frequent users
- Toggling from a secure link on an HTTPS web page to a non-secure HTTP webpage
- Missing or broken GA tracking code
- Incorrect/improper redirection
- Landing on a webpage from non-web documents like word documents, power points, excels, pdfs, etc.
- Dark Social – no attributed sources like email, Whatsapp, Skype, SMS, Facebook Messenger
Key steps you can take to minimize the level of unnecessary direct traffic in your reports:
- Migrating from HTTP to HTTPS – is the present and future of the web and has a positive effect on your ability to track referral traffic.
- Managing your redirects – Be meticulous about using any vanity URLs with UTM parameters to redirect traffic to the new page.
- Campaign Tagging at its best – Avoid tagging internal links to carry out meaningful attribution.
- Perform an analytics audit – Data integrity is very crucial. Good audits of analytics involve a review of your traffic measurement plan and rigorous testing at the page and property level.
Following these steps will help you achieve a drastic reduction in the total level of direct traffic reported in Analytics.
Struggling with direct traffic in Google Analytics? We share what direct traffic means and how to get an accurate view of how website visitors are finding and engaging with your business.
Google Analytics is an essential tool for marketers looking to understand how well their content and campaigns are working to drive traffic and engagement on their site.
In this blog we’re going to discuss:
- What direct traffic is and why it appears in Google Analytics
- What causes direct traffic
- How to minimise your direct traffic and get more insight to your traffic source
Let’s get started!
What is direct traffic in Google Analytics?
Direct traffic in Google Analytics is defined as website visits that occurred as a result of a user typing your URL directly into their browser or through bookmarks.
If Google Analytics can’t track the source of your traffic, then it will also categorize this as direct traffic. This could include a link in an offline document like a pdf or Word document.
We’ll discuss what exactly causes direct traffic in Google Analytics in the next section.
If you’ve used Google Analytics for a while, you’ll know there’s a handy report under acquisition that allows you to break down your website traffic by source and channel.
Channels include:
- Organic search
- Direct
- Referral
- Social
- Email and more
These channel reports allow you to see which channels are responsible for driving the most traffic. And, with the right tools and tracking, you can even see which channels are driving more actions on your site; from phone calls to form submissions and live chat.
Remember, Google will try and minimize direct traffic in its reports for you automatically. If a user visits your site via an organic search and returns via a direct search a week later, both sessions will be attributed to organic search. But, this is only for a particular lookback period, as set by Google.
You can view direct traffic by heading to your acquisition report and selecting, ‘All traffic’ and ‘channels’.

Why is your direct traffic so high?
The reason why direct traffic is so high is that it’s Google’s catch-all. If a session can’t be attributed, then Google Analytics will add it to direct.
So, anytime you’re tracking isn’t set up correctly, you’ll likely see significantly higher direct traffic.
But, this isn’t the only reason why it’s so high. In fact, there are a few key reasons why Google will credit traffic as being ‘direct’.
What causes direct traffic?
Now that we better understand what direct traffic actually is, what causes it?
Well, we already talked about how it’s for direct searches. But, there are a few ways your sessions might be getting categorised as ‘direct’ despite having another referrer.
Manual address entry and bookmarks
This is the classic reason for direct traffic. And as far as Google Analytics is concerned, there’s no way around it.
Generally, users, once familiar with your business, will write your URL directly into their search bar. Remember, if they’ve visited your site before, chances are their device has remembered the URL making it a quicker route than writing it in a search engine.
Missing or broken tracking code
If you’re developing your site or creating new templates, you need to be careful that any new pages include Google Analytics code.
Without it, GA can’t track where a user has come from. And so, if a user lands on this page and then moves to a second page, that does have the code, Google Analytics has no choice but to attribute it as a direct search.
Non-web documents
Links embedded in docs created with Word, Google, or Acrobat will not pass on referrer information. And so, by default, any user who visits via this link will be categorized as direct.
To a degree, this is inevitable and will account for a small quantity of your direct traffic. But, where possible, use tagged links (we’ll get onto that later) by adding UTM parameters. It allows Google to still scrape referral data even if it’s coming from a non-trackable source.
HTTP – HTTPS
If a user follows a link on a secure page (HTTPS) that leads to a non-secure page (HTTP), no referrer data is passed on. So, all sessions of this type are listed as direct traffic instead of as a referral.
This is part of how the secure protocol was designed and so cannot be avoided. If you find your referral traffic has dropped but your direct has increased, it could be that a major referrer has migrated to HTTPS.
By now, the majority of sites have migrated to HTTPS, so again this is unlikely to be a huge contributor.
Dark Social
Dark social basically refers to social shares that can’t be properly attributed. It could be links shared on Facebook messenger, over WhatsApp, via email, or Skype for example.
According to a recent study, upwards of 80% of link sharing is now done via these channels, making attribution even more difficult for marketers.
You can basically think of dark social as word of mouth marketing taken online; elusive but highly rewarding.
Social media sites don’t pass referral data to Google Analytics
Ever noticed traffic on Facebook that is listed as direct (or other) in Google Analytics? There’s a simple reason for that.
When Facebook isn’t sending referral data across to analytics, it means that GA is unable to locate its source. So, you guessed, it reverts to default.
How to reduce direct traffic in Google Analytics
There are four easy ways you can reduce direct traffic in Google Analytics.
- Use an attribution tool to track your customer journeys in full and attribute the correct source
- Migrate to HTTPS
- Use UTM tags and parameters
- Avoid using vanity URLs
Minimizing your direct traffic is key. After all, the less direct traffic you have, the more accurate your channel attribution is.
Here’s how you can reduce direct traffic allocation in Google Analytics:
Using an attribution tool
While there are some technical fixes to reducing your direct traffic, marketing attribution is the best option when it comes to getting a complete fix.
When users are typing your URL directly into their search bar, you’re always going to see direct traffic as part of your acquisition report.
So, why not just understand the steps users who do this took, before searching you directly?
With tools like Ruler, you can see how channels influenced that direct search and understand the full customer journey.
Attribution tools like ours will track every new lead and every touchpoint they have in their journey from the awareness stage to the decision stage.
Migrate to HTTPS
If you want to decrease direct traffic, then a good solution for that (and for general site security) is to migrate to HTTPS.
Here’s a good guide you can follow.
Use UTM tags and parameters
Tagging your URLs should be standard practice as a marketer. Campaign tracking, also known as “UTM tracking codes” simply allows you to add a special tracking code to your URL. It helps to identify how users are getting to your site and ultimately, how your campaigns are performing.
We wrote a quick guide to tracking links with UTM tags.
Redirect your vanity URLs
Managing your redirections is key to good site structure and user experience. It also helps with tracking.
When using plain vanity URLs with no UTM tags, remember you’re going to get quite limited referral data.
Redirect your vanity URLs to a page with all the appropriate tags and you’ll be able to guarantee that Google Analytics will accurately track those sessions.
Wrapping Up
While direct traffic in Google Analytics can be a nuisance, hopefully, these steps will help you minimize your direct referrals. And remember, with an attribution tool you can completely omit the reliance on direct traffic completely.
You’ll be able to see full customer journeys and attribute your closed revenue on your own terms.