A small business site receiving a few hundred visits a month can have a tenth or more coming from the business itself. Those visits cluster on the pages you happen to check, never convert, and distort exactly the numbers you use to make decisions.

Why this matters more at small scale

On a site with a hundred thousand visits, internal traffic is a rounding error. On one with four hundred, you and two staff checking it a few times a week are a visible share of the total.

The distortion is worse than the volume suggests, because internal traffic is not spread evenly. It concentrates on the homepage, whatever page was recently changed, and the pages you happen to be interested in. Those are precisely the pages you are trying to evaluate.

It also never converts, which drags down the conversion rate of exactly the pages carrying the most internal visits.

Who counts as internal

The developer case is the largest and the most overlooked. A fortnight of build work can produce hundreds of sessions on a site that normally sees a few hundred a month, which makes that month's figures useless for comparison.

Filtering by network address

The standard approach: identify the addresses your business uses and tell the analytics to exclude them.

Find your address by searching for what my IP address is from the office connection. Add it as an internal traffic rule in your analytics settings.

Two limitations to be aware of. Many business connections have addresses that change periodically, so a filter set once may stop matching. And it does not cover staff working from home or checking the site on mobile data, which for a small business is a large share of the internal traffic.

Where the connection uses a fixed address, this covers the office reliably. Where it does not, it is a partial measure rather than a complete one.

The approach that covers mobile and home

Since address filtering misses anyone off the office network, the practical supplement is a browser-level exclusion.

Most analytics platforms support an opt-out mechanism, and browser extensions exist that block analytics entirely. Asking each person who regularly visits the site to install one covers them everywhere rather than only at the office.

It requires cooperation, which for a business with three or four people is realistic. For a larger team it is worth combining with address filtering rather than relying on either alone.

Do not delete, exclude

An important distinction in how the filter is configured.

Where the platform offers it, mark internal traffic rather than discarding it entirely, so it can be excluded from reports while remaining available. That means a filter set wrongly does not permanently destroy data, which is otherwise unrecoverable.

Test any new filter before relying on it. Set it up, visit the site yourself, and confirm the visit appears as internal rather than as a customer. A filter that silently does nothing is worse than none, because you believe the numbers are clean.

The other traffic worth excluding

Internal visits are the main one and not the only distortion on a small site.

Bots and crawlers are filtered automatically by most platforms now, though unusual traffic spikes with no engagement are worth investigating rather than celebrating.

Referral spam, where fake referrals appear in reports to attract attention, is less common than it was and still appears occasionally.

Form test submissions inflate your conversion count, which matters more than the traffic distortion because conversions are the number you actually act on. Excluding the address you test from is worth doing for that reason alone.

When to set it up

At the beginning, alongside the rest of the configuration, because filters generally apply going forward rather than retroactively.

A filter added a year in leaves twelve months of contaminated history that cannot be corrected, which undermines exactly the year-on-year comparison you would want to make. That is the same reason the baseline is worth recording on day one, as set out in setting up analytics for the first time.

Frequently asked questions

Why should I exclude my own visits from analytics?

On a small site you and your staff can be a tenth or more of the traffic, concentrated on the pages you happen to check, and those visits never convert.

Who counts as internal traffic?

You, your staff, your web developer or agency, anyone testing forms, and automated monitoring. The developer case is the largest and most overlooked during a build.

How do I filter my own traffic?

Find your network address and add it as an internal traffic rule in your analytics settings. Note that many business connections have addresses that change periodically.

Does address filtering cover everyone?

No. It misses staff working from home and anyone checking the site on mobile data. A browser-level opt-out for each regular visitor covers those cases.

Should filtered traffic be deleted or marked?

Marked, where the platform allows it, so it can be excluded from reports while remaining available. A wrongly configured filter that discards data destroys it permanently.

When should I set this up?

At the beginning, since filters generally apply going forward rather than retroactively. Adding one a year in leaves twelve months of contaminated history that cannot be corrected.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Analytics numbers that include everyone in your office?

We set up filtering that covers mobile and home as well as the office, and test it before you rely on the figures.

Start a Conversation