Have you noticed an increase in the amount of Bot Traffic your website has received over the past few months? As any Internet service, Google Analytics is susceptible to spam, and Bot Traffic, which affects almost every website’s data and is something that is becoming a serious issue for digital marketers.
What is Bot Traffic in Google Analytics?
Bot traffic in Google Analytics is non-human traffic to your website from spiders and robots. It appears to be legitimate traffic but it is actually spam, and is generally low quality traffic that will skew your aggregated data. An example of this can be seen in the metrics of the image below:
When making business decisions, it is essential to have the right data on the table, and bot traffic is something that could cloud the judgement of the decision maker, therefore it’s incredibly important to spot this traffic to ensure data reporting is accurate and appropriate.
How can you identify Bot Traffic in Google Analytics?
Do you look at your Google Analytics data on a daily basis?
In the below screenshot from Google Analytics, a huge spike in web traffic can be seen in May. Was this increase in traffic expected? Was there any event or special social promotion taking place?
If the answer is NO, this is probably the result of a bot traffic.
How to Spot Bot traffic in Google Analytics:
-
Click on Acquisition on the left hand column, then click All Traffic and Channels. From this list, under the Default Channel Grouping column of the report that will appear, click Referral.
-
Do you recognise all of your referral sources? If not and they don’t look relevant to your business, this might be the first clue that this is bot traffic. Don’t miss out any referrals. Scroll down the page and click “show rows” on the right to get the full list of referrals (By default, Google Analytics will show you just the first 10).
-
Pay attention to the metrics – Do you have visits that show 100% bounce rate and 00:00:00 average visit duration? If so you might be looking at bot traffic.
-
Dive a bit further and detect Ghost referrer Spam. Click on Secondary Dimension and type “hostname”. Then press enter.
Any Hostname that is not your website is bot traffic and you should exclude it. If the Hostname is not your website, this means that these referrers don’t know who they are targeting which makes them invalid and should be excluded from your reports.
The image below shows an example of ghost referrer spam - these invalid sessions need to be excluded from the reports to have a clear view of activity.
Some examples of Bot Traffic in Google Analytics
You should check your spam following the instructions provided in the guidelines above, but just to make you a little bit more familiar with common spammers to help you to spot them quickly we have put together some examples for you:
4webmasters.org
trafficmonetize.org
free-share-buttons.com
buttons-for-website.com
site3.free-share-buttons.com
make-money-online.7makemoneyonline.com
site35.simple-share-buttons.com
100dollars-seo.com
webmonetizer.net
best-seo-solution.com
forum.topic55627636.darodar.com
buy-cheap-online.info
addons.mozilla.org
semalt.semalt.com
acunetix-referrer.com
thumbnail.ws
flipboard.com
urlopener.com
wiki.vodia.com
google.de
duckduckgo.com
mys.yoursearch.me
What can you do to ignore Bot Traffic in Google Analytics?
Until Google fixes this problem, there are some options you can consider in the meantime.
Option 1
One of the practices many digital marketers have opted for and the one we recommend is to create filters that exclude the particular bot or bots that are skewing data. To do this, follow our steps below:
On the top of the Google Analytics interface click Admin
-
From the PROPERTY column choose Tracking Info and then Referral Exclusion List
-
You will need to follow the next steps for every domain name that you want to exclude
-Click +ADD REFERRAL EXCLUSION
-Copy and paste a domain name
-Click Create
-Repeat for all the domain names
This is the fastest option to deal with bot traffic, but remember filters will only apply to your data moving forward and your historical data will still contain bots.
It is crucial that you create a new view in Google analytics before adding any filters.
This will make sure you keep all the original data saved and under your control, with no risk in losing any data. With the new view you can play around, adding filters and not having to worry about losing data.
Option 2
Another option that you can implement if you don’t want to create a new view or new filters is to download everything into Excel and filter the data that you need.
This method is safe but is very time consuming. You have to exclude the bot traffic and then recalculate average bounce rates and average times spent on the site.
.png?width=500&height=320&name=Image_1__Dynamics_365_to_HubSpot_Migration__What_Enterprise_Teams_Need_to_Know%20(3).png)
.png?width=500&height=320&name=Image_1__Why_CRM_Implementations_Fail_(And_What_Enterprise_Teams_Can_Do_About_It).png)
.png?width=500&height=320&name=Blog%20Cover_%20AEO%20for%20HubSpot_%20What%20Enterprise%20Teams%20Should%20Be%20Doing%20Now%20(1).png)
.png?width=500&height=320&name=How%20to%20Fix%20a%20Broken%20GTM%20Strategy%20_(Before%20You%20Throw%20More%20Budget%20at%20It).png)
