GA Bridge
← What's new

Hide likely bots: no more phantom visitors from Council Bluffs

iPhone 1.0.1 (28)Android 1.0 (29)Web
The Likely bots sheet: 132 sessions hidden today from 5 places, with Council Bluffs, Ashburn, Boardman and Lanzhou at 0–1% engaged

If you look at your city reports in Google Analytics, you may have noticed the same few places turning up: Council Bluffs, Iowa, Ashburn, Virginia, Boardman, Oregon, Lanzhou, China. One visitor, gone in a second, day after day. These aren't people. Council Bluffs and The Dalles host big Google data centres, and Ashburn and Boardman host Amazon's. The "visitor" is a crawler, a link-preview fetcher or a headless browser. Google filters known bots, but plenty get through (how to spot bot traffic in Google Analytics 4 shows how to find them yourself).

On a small site, that noise is a real share of the numbers. GA Bridge can now leave it out.

How it decides

Every hour, GA Bridge looks at the last 28 days of activity by city across all your sites, today included. A place counts as a likely bot when its visits look hollow:

  • almost none are engaged (GA's measure: 10 seconds or more, two or more pages, or a conversion) and they last under a couple of seconds;
  • or each visit is one page and nothing else: no scroll, no click, no engagement time, just the page view GA records on arrival;

and it keeps happening: on several days, on several of your sites, or as a burst of eight or more visits to one site in a day.

A short list of known data-centre towns (Council Bluffs, Ashburn, Boardman, The Dalles, Prineville, Boydton, Lanzhou) needs no repeat, and is hidden even when a few of its visits look engaged, since a crawler mixed in with the odd real visit used to slip through. Behaviour still decides, though: if most visits from Ashburn actually read your pages, the town isn't hidden.

What gets hidden

With Hide likely bots on (it's on by default), those places are left out of the requests to Google, so totals, trends, charts, countries, sources and pages are GA's own exact figures, minus the bots. Live counts drop them too, so the "live now" dot stops lighting up for a crawler.

Nothing hidden silently

At the bottom of your list of sites, a line says exactly what was taken out: "Bot detection hid 132 sessions today, from 5 places". The figure is Google's own count of sessions from the hidden places, asked with the same list and the same dates as the numbers above it, so the two always agree. If any site doesn't answer, the line shows no figure rather than a partial one. Tap it to see the places.

Since iPhone 1.1.2 (35), each site's own screen carries the line too, straight under its headline figure. There it counts that site alone, for the time frame on screen, and it opens the same list. Hide a place or mark one Not a bot and the site's numbers, its bot line and its typical day are all fetched again, so the chart never compares a day without bots against an average that still has them.

The Likely bots sheet, also in the settings menu, lists every hidden place with its evidence ("0% engaged · 12 days · 3 sites · data centre"). Since build 29 you can correct it: swipe a place to mark it Not a bot, or long-press any city in a country's regions to hide it yourself.

Since iPhone 1.2 (36) and Android 1.2 (33), the bot line is a full-width button at the foot of every screen, and the sheet it opens is about the numbers you came from. Under the title it says which: "Northwind Coffee · Today" on a site's screen, "All 7 sites · Today" from the dashboard. Hidden today lists only the places taken out of those numbers, each with its sessions, so they add up to the line above. The rest of the 28-day watch list sits underneath, folded away as "12 more places on watch", with its 28-day evidence; with Hide likely bots off it's open, as "Would be hidden". How the check decides is behind a How do we detect bots button at the bottom.

What changed in 1.1.1

In iPhone 1.1.1 (34), Android 1.1.1 (31) and the web app, the check got stricter about the bots that were still getting through:

  • Today counts. The check used to stop at yesterday and run once a day, so a place that started sending bots this morning showed up in today's numbers. It now runs every hour with today included.
  • One-page visits. Visits that load one page and do nothing else are now a sign of a bot, not just visits under two seconds.
  • Data-centre towns like Ashburn are hidden even with a few engaged visits mixed in.
  • Nothing cut off. On busy sites the check used to read only the 10,000 biggest city-days, which left out exactly the one-visit rows bots leave. It now reads every row, and can hide up to 500 places instead of 100.
  • The counter under the list of sites, above.

Get it on your phone, or open it now.

On the App Store and Google Play: £2.99 once, no subscription. On a Mac or PC, the web app is free for now and works straight away with the Google account you use for Analytics.

Web: any modern browser. iPhone: iOS 17 or later. Android: on Google Play.