WP Engine Surprise Overage Bill: How Visit-Based Pricing Really Works
The bill that catches people out reads something like this: you're on a $30/mo plan, you didn't change anything, your analytics look flat, and the invoice comes in at $70. That's overage, and it surprises people because visit-based billing measures something different from what most owners think "visits" means. Once you understand how WP Engine actually counts a visit, the surprise goes away, and so does the question of whether to absorb the overage or upgrade. This walks through both, with the math.
How a "visit" is actually counted
WP Engine defines a billable visit as one unique IP address per day (UTC) that requests dynamic content and isn't blocked. A few consequences fall out of that definition that aren't obvious:
- Static assets don't count. Images, CSS, and JavaScript files aren't billable visits, so a content-heavy page isn't penalized for its assets.
- One IP, one visit per day. The same person hitting your site ten times in a day is one visit, but the same person across five days is five visits.
- Bots are filtered, mostly. WP Engine excludes known bots, and since September 2025 also excludes suspected bots (unrecognized agents behaving like bots). What still counts is bot traffic that successfully disguises itself as a normal browser.
The intent, in WP Engine's framing, is to measure human traffic against the server resources it uses, not to mirror an analytics dashboard. That's a reasonable goal, but it's also exactly why the number on your invoice is a stranger to the number in Google Analytics.
Why it never matches Google Analytics
This is the root of most "surprise" bills. Your host's visit count and your Google Analytics users count measure different things and will basically never agree:
- Google Analytics runs JavaScript. It only counts visitors whose browser executes its tracking script, which most bots never do. So GA filters out a lot of automated traffic by default.
- WP Engine counts server-log IPs. It sees every request that reaches the server, including the disguised bots that beat its filter, which GA never recorded.
The result is a structural gap, the host number is usually higher, and the difference is largely bot traffic plus the unique-IP-per-day counting method. A site showing 30k users in GA can easily be billed for 45k visits, and that 15k difference is what tips you into overage. It isn't a billing error, it's two different rulers. (I go deeper on the bot side of this in are AI bots inflating your hosting bill.)
The overage math (and the plan ladder)
Overage is a flat $2 per 1,000 visits over your plan's limit, the same rate across tiers. The plans themselves step up the included visits (published rates, confirm current pricing):
| Plan | Price | Included visits | Overage |
|---|---|---|---|
| Startup | ~$30/mo ($360/yr) | 25,000 | $2 / 1,000 |
| Professional | ~$55/mo | 75,000 | $2 / 1,000 |
| Growth | ~$109/mo | 100,000 | $2 / 1,000 |
| Scale | ~$267/mo | 400,000 | $2 / 1,000 |
So if your Startup site sees 45,000 billed visits, that's 20,000 over, or $40 of overage on top of $30, a $70 month. WP Engine doesn't throttle or take your site down for going over (their stated policy is to treat spikes as success, not punish them), which is good for uptime but means the meter just keeps running unless you act.
When to upgrade instead of paying overage
This is the part nobody spells out, and it's just arithmetic. Paying overage forever is the expensive default. Compare staying on Startup-plus-overage against the flat Professional plan:
The rule of thumb that falls out: once your overage charge is bigger than the gap to the next plan, upgrade. A one-off spike is fine to absorb (and WP Engine won't cut you off for it); a steady month-after-month overage means you're on the wrong tier and paying a premium for it.
How to avoid a surprise bill
- Watch the host's number, not just analytics. WP Engine shows your billable visits in the dashboard, and emails at 80% and 100% of plan. Treat those emails as action items, not noise.
- Close the bot gap with a WAF. A lot of overage is disguised bot traffic. Putting Cloudflare in front and blocking or rate-limiting abusive crawlers stops them before they count as a visit.
- Right-size the plan. If you're steadily over, run the break-even above and upgrade; if you're far under, you may be over-paying for headroom you don't use.
- Compare billing models if it's chronic. Kinsta's visit overage is $0.50 per 1,000 (a quarter of WP Engine's), and its 2025 bandwidth-based option doesn't bill for scraper and bad-bot traffic at all. If bots are your problem, the billing model itself may be the fix.
FAQ
Why is my WP Engine bill higher than my plan price?
You exceeded your plan's monthly visit limit and were charged $2 per 1,000 extra visits. It can happen without an obvious traffic spike because WP Engine counts unique IPs per day in server logs (including disguised bots), which runs higher than Google Analytics users.
How does WP Engine count a billable visit?
One unique IP per day (UTC) requesting dynamic content and not blocked. It excludes static assets, known bots, and (since September 2025) suspected bots. It measures human traffic against server resources, not analytics pageviews.
When should I upgrade instead of paying overage?
When overage exceeds the gap to the next plan. On Startup ($30, 25k visits) vs Professional ($55, 75k), break-even is about 37,500 visits. Consistently 12,500+ over your limit means the flat plan is cheaper than overage.
Will WP Engine take my site down if I go over?
No. Their stated policy is not to throttle or suspend for traffic spikes, the meter simply runs at $2 per 1,000 over. That protects uptime, but it also means overage keeps accruing until you upgrade or reduce billable traffic.