See the picks

Guides

How hosts count visits, and why your store reads differently at every host

A visit sounds like a fact. It is a counting rule, and every host writes its own. The same store, with the same shoppers, can read as 30,000 visits at one host and 45,000 at another, and the difference decides your plan size and your overage bill. Here is how the counting works, host by host, and how to read your own numbers before you sign.

The two counting rules that run the industry

Unique person per day. Kinsta counts one unique IP address inside a 24 hour window as one visit, by its own published definition. WP Engine counts one unique visitor per day the same way. A loyal customer who checks your store every morning counts once a day, every day. That is why a store with 3,000 regulars who visit most days can pass 25,000 visits in a quiet month without a single ad running: the meter measures daily reach, not page loads and not total shoppers.

No visitor count at all. Rocket.net does not meter visitors. It meters storage and bandwidth instead: the Starter plan holds 10GB of storage and 50GB of bandwidth a month. Cloudways rents you a server and bills for the machine, so your crowd is not a line item at all. For stores whose traffic spikes hard, this rule is the whole argument, and our comparison page prices both shapes side by side.

What does not count, and what quietly does

Hosts filter the obvious noise. WP Engine's own docs say bots, static files, and blocked requests do not count as visits. Kinsta says it filters known bots and reports staging visits without billing them. What still counts is everything human-shaped: your own team checking the store, your developer testing checkout, the price-comparison scraper that behaves like a shopper, and every return visit on a new day. None of that is a scandal. It is the rule, printed in each host's docs, and it means your host's number will never match your analytics dashboard, which counts sessions by its own third rule. Expect the host's figure to run higher than your session count, and budget your plan size against the host's number, because that is the one on the invoice.

The same store, counted three ways

Take a store with 1,200 human visits a day, steady all month. As raw daily reach that is about 36,000 visits a month.

HostWhat it countsThis store reads asWhat happens next
KinstaUnique IP per 24 hoursAbout 36,000 visitsJust past the entry plan's 35,000. Overage about $0.50 that month, or step up a tier
WP EngineUnique visitor per dayAbout 36,000 visits11,000 past the entry plan's 25,000, at $2 per 1,000: about $22 of overage
Rocket.netStorage and bandwidth, not visitorsNot countedThe bill does not move. Watch the 10GB and 50GB caps instead

Same shoppers, same month, three different relationships with the meter. This is why we compare the overage rate and the counting rule together, never the headline limit alone: a generous limit on a fast meter can cost more than a tight limit on a slow one. Our True Cost Calculator runs your monthly visits through each host's real meter so the busy month stops being a surprise.

Why hosts count this way at all

A visit is a rough stand-in for work. Every human arrival asks the server to build pages, and checkout pages cannot be served from a saved copy, so they ask for live work each time. Counting unique daily visitors prices that work without metering every page load. It is a fair proxy with rough edges: a store on a busy shared office network can hide fifty shoppers behind one IP address and read low, while a store whose customers browse from phones on changing addresses reads high. Hosts know this. The count is a billing convention, not a measurement of your marketing, and treating it as one or the other on purpose is where owners get hurt.

How to read your own store before you sign

  1. Find your daily reach, not your pageviews. In your analytics, look at users per day across your busiest recent month, then multiply by the days. That is the closest home estimate of a host's visit count.
  2. Price the busiest month, not the average. Plan size bought for the average month bills overage in the month that matters most. Our WP Engine math and Kinsta math both work the busy month out loud.
  3. Ask the host two questions in writing. What exactly counts as a visit, and what does 1,000 visits past the limit cost? A host that will not answer both plainly has answered a third question for you.
  4. Watch the meter in your first busy season. Every host on this page shows usage as the month builds. The owners who get hurt are the ones who meet the number for the first time on the invoice.

Questions owners ask about visit counts

Why is my host's visit count higher than my analytics?

Because they count different things. Analytics counts sessions, usually with a 30 minute timeout, and misses shoppers who block tracking. Hosts count unique addresses per day at the server, including people your analytics never saw. The host's number is the billing number. Plan against it.

Do bots inflate my bill?

Known bots, no: the hosts on our comparison page filter them and say so in their docs. Bots that behave like shoppers are harder to separate, and every host's filter is imperfect. If your count jumps with no matching sales pattern, ask support to show you the traffic behind it before you pay to upgrade.

My traffic is spiky. Should I just avoid visit meters?

Not always. A slow meter, like Kinsta's $0.50 per 1,000, makes a spike a small bill. A fast meter, like WP Engine's $2 per 1,000, makes the same spike a real one. And a host with no visitor meter at all, like Rocket.net, makes it a non-event, at the price of watching storage and bandwidth caps instead. The shape of your traffic picks the shape of your meter.