Is bot traffic inflating your analytics? A 15-minute audit

Inflated traffic is not a vanity problem. It moves conversion rate, cost per acquisition, bounce rate and every channel comparison built on top of them — which means it moves budget. This audit takes about fifteen minutes and gives you a defensible number.

Step 1 — Establish the baseline (3 min)

Pull sessions, conversion rate and average engagement time for the last 90 days. Write them down. Everything after this is measured against these three numbers.

Step 2 — Build the suspect segment (5 min)

Create a segment of sessions with one pageview and zero engagement time. Apply it. If it accounts for more than 10% of sessions, you have a material problem. Above 25%, your reporting is actively misleading.

Step 3 — Recalculate (2 min)

Exclude the suspect segment and read conversion rate again. The delta is what bot traffic is costing you in measurement accuracy. It is common to see a conversion rate move from 1.8% to 2.4% — the same business, described honestly.

Step 4 — Check the invisible layer (5 min)

Look at raw server or CDN logs for the same period and count requests to HTML pages. Compare with GA4 pageviews. The difference is traffic that never executed JavaScript: crawlers, scrapers, uptime monitors, AI agents. On a typical content site the gap is 30-60% of total requests.

What to do with the answer

• Report the cleaned numbers internally and explain the change once, clearly, before someone else notices the drop.
• Block scrapers and fraud tooling at the edge so they stop consuming bandwidth and polluting forms.
• Keep AI and search crawlers allowed — those visits are demand signals, not noise.
• Set up a permanent split so you never have to run this audit manually again.

The last point is the difference between a one-off clean-up and an honest dashboard. Bot Analytics keeps the human and bot streams separate by default, so the headline number in your weekly report is the one you can defend.