
Blog Bots: How to Spot and Filter Bot Traffic
Imperva's 2026 Bad Bot Report found that bots made up more than 53% of all web traffic in 2025, up from 51% a year earlier. Humans are now the minority online. A common pattern on blogs: pageviews double year over year while newsletter signups stay flat. That gap is where blog bots live, and it's why many traffic charts mislead.
This guide is about bots visiting your blog, not AI tools that write blog posts. It covers how to spot bot traffic in GA4 and server logs, which crawlers to keep, and how to filter the rest.
Why Your Pageviews Don't Match Your Conversions
A pageview count that climbs while leads, sales or email signups stay flat almost always means bot traffic is inflating the top of the funnel. The disconnect shows up first in aggregate reports, then gets confirmed once you check engagement metrics against raw volume.
The Telltale Metrics
Watch three GA4 numbers together: average engagement time, views per session, and engagement rate (or its inverse, bounce rate). Human blog readers who land on a 2,000-word article typically stay for a minute or more and often click through to a related post. Bots hit one page and leave within a second or two. If a traffic spike shows an engagement rate near 0% (bounce rate near 100%) and average engagement time of a second or two, that's a script requesting a URL, not a reader.
Where the Traffic Comes From
Check your geography and device reports next. A sudden spike from a country with no relevance to your niche, arriving entirely on one browser version, is a strong signal of automated hits rather than organic reach. Real human traffic is messy, with mixed devices, mixed locations and mixed session lengths. Bot traffic is suspiciously uniform.
None of this means every anomaly is malicious. A lot of it is crawler traffic doing exactly what it's supposed to do.
Crawler Traffic vs. Human Traffic: Not the Same Threat
Not all bots are a problem, and treating them like one is a common overcorrection. Search engine crawlers, uptime monitors and legitimate SEO tools need to access your pages regularly, and blocking them can hurt the very rankings you're trying to protect.
Good Bots You Should Leave Alone
Googlebot, Bingbot and crawlers from tools like Ahrefs or Screaming Frog show up in server logs constantly. They rarely show up in GA4: many crawlers don't run JavaScript, and GA4 automatically excludes known bots, including the ones that do, such as Googlebot when it renders pages. If you see them in your raw server logs but not in GA4, that's expected behavior, not a leak.
Bad Bots That Skew Reporting and Cost You Money
The traffic that damages your analytics comes from scraper bots harvesting content, referrer spam faking a visit from a fake domain to get you to click back (less common in GA4 than it was in Universal Analytics), and click farms tied to ad fraud schemes. These generate fake pageviews that count in your dashboard and, if you run display ads, can burn advertiser budget on impressions no human ever saw. This is the category worth filtering aggressively; the crawlers indexing your site are not.
AI Crawlers and Scrapers: GPTBot, ClaudeBot, PerplexityBot
AI companies run their own crawlers to fetch pages, either to train models or to answer user questions. OpenAI, for example, lists separate bots: GPTBot crawls content that may be used for training, OAI-SearchBot gets sites into ChatGPT search results, and ChatGPT-User visits a page when a user asks ChatGPT about it. Anthropic's ClaudeBot and Perplexity's PerplexityBot play similar roles; check each vendor's documentation for its current user-agent names.
These crawlers generally don't run JavaScript, so they show up in server logs and CDN analytics, not in GA4. You can allow or block each one in robots.txt by user agent. Blocking them can remove your content from AI answers, so block training-only crawlers if you want, but think twice before blocking AI search and answer bots that can send readers your way.
GA4 Bot Exclusion Doesn't Catch Everything
Google Analytics 4 filters known bots automatically using the IAB/ABC International Spiders and Bots List, but that list only covers publicly declared bots that identify themselves honestly. It does nothing for spoofed user agents, headless browsers mimicking real sessions, or residential-proxy traffic pretending to be ordinary-looking Chrome users in US cities.
That's the trap: GA4 excludes known bots automatically (you can't switch it off or see how much it removed), so site owners assume the problem is handled. It isn't. A resourceful scraper or a fraud network built to inflate ad impressions specifically avoids that list.
To exclude your own team, define internal traffic by IP in Admin → Data streams → Configure tag settings → Define internal traffic, then activate the Internal Traffic data filter under Admin → Data filters. If you use Cloudflare, its bot analytics and bot-fight settings block much of the automated traffic before it reaches your site.
To close the rest of the gap, layer in server log analysis alongside GA4. Your access logs show every request, including the ones that never execute Analytics' JavaScript, which is where a lot of scraping and fake-referral traffic hides. Comparing user agents and request timing in your logs with your GA4 reports usually surfaces bot clusters that GA4 alone misses.
- Pull raw server logs for a 30-day window and export the IP and user-agent fields.
- As a starting point, flag any IP making more than a few hundred requests per day to a single blog post.
- Cross-check flagged IPs against known data center or hosting-provider ranges (a quick WHOIS lookup does this).
- Compare the timing and landing pages of those requests with spikes in GA4 (by hour, page, city and browser) to confirm they are the same traffic.
- Add confirmed non-search-engine bot IPs to a firewall or CDN-level block rule, not a GA4 filter alone.
- Re-check engagement rate and average engagement time for the affected pages a week later.
Rules of thumb, not fixed thresholds:
| Signal | Likely Human | Likely Bot |
|---|---|---|
| Avg. engagement time | 45+ seconds | Under 2 seconds |
| Views per session | 1.5–4 | Exactly 1 |
| Geo/device mix | Varied | Uniform, single browser version |
| Referrer source | Search, social, direct | Unknown or spoofed domain |
What to Measure Instead of Raw Pageviews

Filtering bot traffic tells you what worked instead of leaving you to guess. When half your "readers" are bots, every content decision downstream of that traffic, such as what topics to write next, which headlines to test and which format performed best, gets built on numbers that never reflected real people.
A blog post that gets 5,000 bot-inflated pageviews looks like a win. Teams then produce more posts in that format, chasing a pattern that never resonated with anyone, and months of editorial calendar go into replicating a result that doesn't exist. Over time, a whole content strategy can end up pointed at the wrong signal.
The fix is refocusing on metrics tied to real reader behavior: scroll depth, return visits, email signups and engagement time filtered to exclude flagged bot sessions. Once you strip out the noise, a lot of "high-performing" content turns out to be mediocre, and posts that looked ignored sometimes show real engagement once the fake traffic is subtracted.

Clean analytics only matters if it changes what you publish next. Once bot sessions are filtered out and you can see real engagement and referral sources, the next step is producing content that holds up against that cleaner baseline, consistently rather than as a one-time audit. If keeping up that output is the hard part, DraftSEO writes and publishes 30 articles a month per site to WordPress and 90+ other platforms; you can start for free and compare the output with your filtered analytics before committing. See current plans on the DraftSEO.ai pricing page.
Frequently Asked Questions
How do I know if my blog traffic spike is bots or a real audience?
Check engagement rate, average engagement time and views per session for the spike window. Real audience growth shows varied engagement; bot spikes show near-uniform sessions of a second or two from a narrow geography or device type.
Should I block all crawler traffic to stop bots from hurting my analytics?
No. Blocking indiscriminately can stop Googlebot and Bingbot from indexing your site. Filter malicious scrapers and spoofed traffic at the server or CDN level, and leave verified search engine crawlers untouched.
Does GA4's default bot filtering fully solve this problem?
No. GA4 only excludes bots on the IAB/ABC known-spiders list, missing spoofed user agents and fraud-network traffic. Server log analysis alongside GA4 catches what the default filtering misses.
Should I block AI crawlers like GPTBot?
It depends on what you want. Blocking a training crawler such as GPTBot in robots.txt signals that your content shouldn't be used for model training. Blocking AI search or answer bots can keep your pages out of AI answers, which may cost you visibility, so most blogs block selectively rather than across the board.
Do bots affect my Google rankings?
Google hasn't described bot visits as a ranking factor. Their main effect is distorting your analytics, which can lead to bad content decisions, and heavy scraping can slow your server. Blocking legitimate search crawlers, on the other hand, can hurt rankings.


