How to spot spam in Analytics and what to do about it

Summary

Spam in Analytics typically appears as a sudden, unexplained increase in traffic—often from a single source (like Direct traffic), location, or IP. You can identify it by analyzing traffic patterns and fix it by excluding the traffic using Siteimprove Data Exclusion settings or filters.

Symptoms

• A large, unexplained increase in traffic
• Traffic patterns that do not align with marketing activity
• Unusual spikes without a clear cause

How to Identify Spam Traffic

Analytics spam has become a larger and larger issue over the last few years and can cause a lot of headaches and questions when spammers strike a site you are monitoring.

The first thing you want to check is if the traffic is all coming from a single traffic source.

• Most spam comes in the form of “Direct” traffic
• If most of the increase is from the Direct channel, investigate further

Most of the time, the spam traffic is going to be coming from a single user/machine or a few users/machines.

• Traffic concentrated in: 
  • A single city or state
  • A small number of locations
  • A limited set of IP addresses

If this pattern exists, it is extremely likely to be spam traffic.

Cause

Spam traffic is typically generated by automated bots or scripts that inflate traffic numbers without representing real user behavior.

This results in:

• Artificial traffic spikes
• Skewed analytics data
• Misleading performance insights

Resolution

Fortunately, there is an easy solution to “fix” this problem.

The easiest way to address this is by using the Siteimprove Data Exclusion settings.

It’s also possible to:

• Exclude traffic from Analytics using filters

For further information on these options see the article:

• How to exclude traffic from Analytics

Validation (Confirm the Fix)

• After applying exclusions or filters: 
  • Traffic levels normalize
  • Suspicious spikes disappear
  • Data more accurately reflects real user behavior

Prevention Tips

• Regularly monitor traffic sources for anomalies
• Watch for spikes in Direct traffic
• Investigate unusual geographic patterns
• Apply filters proactively when patterns emerge