How Much of My Website Traffic Is Bots?

Tony CarnevaleUpdated November 21, 202611 min read
WebsiteMaintenance.com
Last 30 days
344visits
Portland, OROn Pricing
Bothell, WAOn Website Repair
Everett, WAOn Care Plans
Seattle, WAOn Home
Bot trafficBots are recorded but hidden from every number by default.
Datacenter browserScript · Ashburn, VA
No user agentScript
GooglebotGoogle · Search engine
GPTBotOpenAI · AI crawler
AhrefsBotAhrefs · SEO tool
Visits reaching the demo site: each person joins the visit count, and each bot is named and filed under Bot traffic, outside every number.

The short answer

When Venbit Intelligence Research measured this on tracked small business websites, bots made 39% of all recorded visits over 90 days, and the middle half of those websites sat between 27% and 56%. Your own share depends on the tool you count with. A host log counts every request and runs high. A script tracker misses crawlers that never run its script. Venbit Intelligence removes the bots it sees before anything is counted and names them.

What to know

  • Bots made 39% of the visits recorded on tracked websites over 90 days. On more than a third of tracked websites, bots outnumbered people.
  • Google's own help says GA4 excludes known bots automatically and the exclusion cannot be turned off. A crawler not on that list, or a script posing as a browser, is counted.
  • Venbit Intelligence detects bots by user agent, by an empty user agent, and by datacenter cities such as Ashburn, then hides them from every number by default.
  • Googlebot and Bingbot are the index, GPTBot and ClaudeBot are how an assistant learns to quote you, and Ahrefs or Semrush bots are a competitor reading your pages.
  • A spike is judged by what the visits did. One page, zero seconds, no scroll, no click, all from one town, is a script.
  • Direct means the visit arrived with no referrer, which is what a script, a pasted link and a bookmark all look like.
  • Your own browser is a visit too. Settings has a switch to stop counting it.

About four in every ten visits to a small business website are bots. Venbit Intelligence Research counted them on tracked websites over 90 days, and 39% of recorded visits were automation. Nobody can give you the figure for your own website without looking at it.

The tool you look with decides most of the number.

Your host's stats page counts every request that hit the server, crawlers included, so it runs high. A tracker that runs as a script only sees browsers that run scripts, and a crawler that reads the text and leaves does not, so it runs lower. Venbit Intelligence drops the automation it does see before anything is counted, which is why our visit counts run lower than the estimator tools claim. The check below shows what your own browser is telling this page as you read.

Check this visit

See how a website tells you from a bot

These are the signals your browser is handing this page as you read. Scroll and watch the third row change.

Reading your browser

  • What your browser calls itself…

    Googlebot, GPTBot and the other honest crawlers put their own name here. Yours names a browser people use.

    • Googlebot
    • Bingbot
    • GPTBot
    • ClaudeBot
  • Automation flag…

    A browser driven by a script reports it through this flag. Yours says a person is at the controls.

  • Something a person doesNothing yet. Scroll or move.

    A visit that starts under suspicion, from a datacenter town for one, is counted as a person again the moment it clicks, taps, fills a field or opens a second page.

  • Time with this tab in front0s

    Engaged time runs only while the tab is visible and focused. A script that loads the page and leaves shows zero.

  • The town your connection resolves toRead on the server

    Your browser cannot report this, so it is not shown here. The server reads it from the IP address, and a cloud town such as Ashburn, Virginia starts a visit out hidden.

Compare your host count with your analytics

Take last month from your hosting panel (visits or unique visitors) and the same month from your analytics.

Enter both numbers to see the share that was machines.

Bot share of recorded visits on tracked websitesMiddle half

Venbit Intelligence Research, over 90 days in autumn 2026: 39% of recorded visits on tracked websites were bots. Recorded means the bot ran the page's script. Crawlers that only read the text are on top of that. Nothing on this page is stored or sent.

On the demo site, WebsiteMaintenance.com, the dashboard counted 347 visits in the last 30 days, every one of them a person. The AI search section under it shows Meta AI read 90 pages and other bots read 18 in the same window, and none of those reads is in the 347. Any site's answer has that shape, a human count with the bot count kept beside it.

Bots are 39% of visits on the sites we measure

In all, the script recorded 375,967 visits and judged 146,638 of them to be bots. Those are visits where a browser, or something acting as one, loaded the page and ran its script. Each was recorded, judged to be automation, and left out of the owner's numbers. On more than a third of tracked websites, bots outnumbered people. Advertising made almost no difference to the share.

39%
Median bot share on the sites that buy clicks
41%
Median bot share on the sites that do not

A website gets crawled because it exists and is linked, and crawlers do not check whether it is popular first.

Thirty-nine percent is a floor. The crawlers that fetch a page's text and never run a script, GPTBot and ClaudeBot among them, are missing from that count, because no script-based tool sees them arrive. A host log does see them, which is one reason a hosting panel reports several times what any analytics tool shows.

Why your visit counts don't match

Three kinds of tool give three different counts.

  • The host log

    The biggest number, because it is the most literal. Every request for a page, an image, a stylesheet or a feed is a line in it, whether a person or a script asked for it. Uptime monitors hit the home page around the clock, and the host's stats page adds those lines up and calls them visits.

  • A script tracker

    Smaller. GPTBot and ClaudeBot read the page's text and leave without running its scripts, as a note under the crawler list in the demo site's AI search section says, so those reads never reach it. Google's own help says GA4 excludes traffic from known bots and spiders automatically and that the exclusion cannot be turned off, so a GA4 count is a filtered one before you touch it.

  • Visits from people

    The third count, the one I built Venbit Intelligence to show, with the bots recorded but hidden from every number by default. You can open the bots when you want to know who read you. They stay out of the chart you grow.

AI searchLast 30 days
AIVisitsLeadsPages read
ChatGPTOpenAI · last seen Sep 27, 202626▲ 2500%00
Meta AIMeta · last seen 1h ago0090▲ 1025%
Visitors Meta AI sent

Nobody clicked through from Meta AI in this period.

What Meta read
Meta AIReading it to train a model90 pages1h ago
Other botsNot AI assistants · 4 bots——18

GPTBot, ClaudeBot and most other AI crawlers read pages without running scripts, so the pages read here are the ones loaded the way a browser does.

The AI search card on the demo site: ChatGPT sent 26 visits, while Meta AI read 90 pages and sent nobody, and those reads stay out of the visit count.

How bot traffic gets filtered out

The definitions page in the portal states the rule in one sentence. Crawlers, scanners and datacenter traffic, detected by user agent, by empty user agents, and by known cloud-region cities such as Ashburn. Bots are recorded but hidden from every number by default.

  • User agent

    The string a browser or a script sends to say what it is. Well-behaved crawlers announce themselves in it, Google's as Googlebot and OpenAI's as GPTBot. The tracker works out the name at the moment the visit is recorded and stores it on the visit, because the user agent itself is not kept.

  • Empty user agent

    Scripts that send no user agent at all are dropped for that silence.

  • Datacenter city

    A person's connection resolves to roughly where they live. A cloud server's connection resolves to the town the datacenter sits in, and Ashburn, Virginia, is the best known of them.

City is read from the IP address and is approximate, so a datacenter town is only a suspicion. A person browsing through a VPN that exits in one starts out hidden with the machines, and the flag is withdrawn the moment they send a form. A crawler that names itself is never let back in.

One more case matters for the inbox. A headless browser filling out your contact form can look clean at the moment it submits, then give itself away on the thank-you page twenty seconds later.

The bot flag lands after the submit, and the lead leaves the inbox with it.

Catch the bots that pretend to be people

A crawler that gives its name is the easy case. The harder ones arrive in an ordinary copy of Chrome with a believable name, and no single request gives them away. They are caught on behaviour, and each rule below is one the tracker applies today.

  • Automated clicker. Events arrive faster than a hand can produce them. Before this rule existed, one visit on a tracked website wrote 26,084 events in 36 minutes.
  • Site crawl. A run of one-page visits walks through the site page after page, none of them staying to read.
  • Replayed clicks. Two visitors click the same spots on a page down to the pixel. People never land on identical coordinates twice, and a recorded script always does.
  • Profile mill. Many brand-new visitor ids appear from one address inside one hour.
  • Spam referrer. The visit claims to come from a site on the public referrer-spam list, a trick meant to make owners curious enough to open the name in their reports.
  • Junk address. The visit lands on a path scanners probe for, or on a mangled link no person follows.
  • Cloud browser. The connection comes from a cloud provider's servers, where no home, office or phone network connects from.

The cloud browser and the spam referrer are suspicions, and they are treated as such. The behaviour rules run the other way round.

The two suspicions

  • Either one hides a visit only until that visitor clicks, taps, fills a field or opens a second page
  • Then the flag is withdrawn and the visit is counted, because a person on a work VPN should never be thrown out with the scripts

The behaviour rules

  • A visit is convicted on what it did, such as an inhuman click rate
  • It stays out whatever it does next

AI crawlers and other bots to know

Half of the bots on a small business site matter, and the names tell you which half.

  • Googlebot and Bingbot

    The index. If they stop coming, you stop appearing.

  • OpenAI and Anthropic crawlers

    Reading your pages is how your site gets quoted in an assistant's answer, which on the demo site turned into 26 visits from ChatGPT last month and no leads yet.

  • Ahrefs and Semrush bots

    A competitor's tool reading your pages.

  • A bare curl request

    Somebody's script.

The AI search section lists the AI crawlers with the pages each one read, next to the people each assistant sent and whether any of those people became a lead, so the reading and what it turned into sit on one screen.

A sudden spike from one country

The worry that sends most people to this question is a spike, a Tuesday with five times the usual visits, all from a country you do not sell to. Whether that was a script or a crowd is written in the rows under the number, so open the visitor trails list for that day.

Automation

  • Lands on one page and stays zero seconds
  • Scrolls nowhere, clicks nothing and leaves
  • A hundred rows like that from one town is a script

People

  • Read for a while
  • Move between pages
  • A few of them reach the form

The engagement bar on each row is the quickest tell. Two more places are worth a look.

  • Referrer column

    Those rows will say direct. Direct means the visit arrived with no referrer, which is what a script, a pasted link and a bookmark all look like, and it says nothing about somebody typing your address.

  • Visitor map

    On the demo site it says 336 of 347 visits came from the United States, where the business sells. A spike that moved that line toward a country the business has never served deserves a look.

Settings has an alert for this, a traffic spike above a number of visits in an hour that you choose, so you hear about it in the hour it happens. If you would rather watch it live, the Live screen shows who is on the site right now, with the page each person is reading.

WebsiteMaintenance.com
Right now
2 people on your site now
Everett, WALeadOn Care Plans · 3 pages so far
Seattle, WALeadOn Home
Bothell, WALeadOn Website Repair
Watch live
The Right now post in the Feed on the demo site lists the people on the site this minute, with the page each one is reading.

A spike is one half of the worry. The drop that is the other half has its own list of causes, and most of them have nothing to do with bots.

Visits with no engagement

The quieter version of the worry is a count that looks fine with nothing behind it. Visits, but no scrolls, no clicks, no forms. Two definitions settle most of these.

  • Engaged time

    Counts only while the tab is visible and focused, so a tab left open in the background adds nothing.

  • Bounce

    A visit that saw one page, stayed under ten seconds and did nothing, no scroll, click or lead.

On the demo site, engaged time is 51 seconds and the bounce rate is 54 percent, which is a site people read. A site with visits and no engaged time is a site nobody is reading, and if those visits also passed the bot filter, they are either people who left at once or automation the filter did not catch.

The other inflater is you.

Every time you open your own site to check a change, that is a visit, and on a quiet site you and your designer are a visible share of them. Settings has a switch for it, Leave my visits out, and it stops counting the browser you switch it on in. Turn it on in every browser you use, and ask whoever works on the site to do the same.

Settings
TrackingGoalsNotificationsTeamAccountPlanSupport

Your own visits

Leave my visits out

Switching opens websitemaintenance.com in a small window to set it for this browser. Close it once the page loads. Switch it on in each browser and phone you use.

Ad blockersOptional. Counts the visitors whose blocker stops the tracker, by serving it from your own domain.
Settings on the demo site, with Leave my visits out switched on so the owner's own checking stops counting as visits.

Real visits without leads is a different problem with a different fix, and that one starts at the funnel. The bot filter will not help with it.

What to do with the number

Judge growth on the human count and nothing else.

That holds at your desk and in Venbit Intelligence for iPhone, which shows the same figure. A chart that includes bots moves when a crawler changes its schedule, and you will spend a morning on a line that means nothing. The demo site's 347 against the previous period is people compared with people, which is the only comparison that tells you about the business.

If your current tool gives you a bigger number than ours will, the two tools disagree about what a visit is and about nothing else. The estimator tools and the host logs are measuring requests. How much traffic a small business site should get has measured figures behind it, and all of them are counts of people.

See this on your own website

Venbit Intelligence installs with one line on your site. Free for 14 days, no card needed.

More website analytics guides

Every question in this series, from Website Analytics for Small Business Owners.

Leads inbox4
Ad performance4
SEO tracking3
Visitor behaviour4
Feed and notifications3
Goals and measurement4
Privacy, AI and teams3
Venbit Intelligence Research19

Tony Carnevale

Founder, Venbit

Tony started Venbit in Mill Creek, WA in 2011 and still does the work: web design, SEO, and the website analytics product the company builds and runs for its own clients. The numbers and screens in his articles come from that product, not from a content mill.

Questions & Answers

  • Google's own help says GA4 excludes traffic from known bots and spiders automatically, using a list maintained by the IAB, and that this exclusion cannot be turned off. Known is the operative word. A crawler not on that list, or a script pretending to be a browser, is counted. Any script-based tool, GA4 and ours included, also never sees crawlers that read the page without running scripts.

  • Because it is counting requests. People are a smaller number. Every crawler, uptime monitor and scanner that fetches a page is a line in the server log, and the host's stats page adds them up. A script tracker only records browsers that ran the script, and Venbit then drops the automation it did see. The host figure answers a different question.

  • They are how an assistant learns what your site says, and that learning is what later sends a person who asked ChatGPT for a recommendation. On the demo site, ChatGPT sent 26 visits in 30 days. The crawlers read pages without running scripts, so they cost you nothing in the visit count. What they cost in server load is a question for your host.

  • One page, zero engaged time, no scroll, no click, no form, and a referrer of direct because a script sends none. One row like that is a person who left fast. Fifty rows like that from one town in one hour, especially a datacenter town such as Ashburn, is automation, and the tracker will have hidden most of them already.

  • It can try, and some do. The submit itself can look clean, so the judgement does not end there. A headless browser that gives itself away on the thank-you page seconds later is flagged as a bot after the fact, and the lead goes out of the inbox with the flag. People with a pitch are a different problem, and the spam filter in Settings is for them.

More guides with a tool

See all 23 guides