WordPress Hosting Visit Limits: What Happens When You Exceed Them
Almost every WordPress hosting plan advertises a number: “up to 25,000 visits a month” or similar, printed right under the price. It sounds precise, like a speed limit sign. In practice it is one of the least precise numbers in hosting, and what actually happens when you go over it depends entirely on the provider you signed up with.
Some hosts throttle your site once you cross the line, meaning pages load slower for everyone until the billing cycle resets. Others bill you extra. Some do nothing visible until the underlying server resources genuinely run out, at which point the site can go down regardless of what the number said. The label rarely tells you which you are getting.
Short answer: A visit limit is a hosting provider’s estimate of how much traffic a plan can handle, and what happens if you exceed it (throttling, an overage charge, or nothing until the server itself runs short) depends entirely on that provider’s own policy. It is a marketing proxy, not a guaranteed technical ceiling.
This article is one of several in GoodHost’s WordPress hosting knowledge centre looking at how hosting plans are actually specified, and what the numbers on a pricing page really mean.
What actually is a “visit” in a hosting plan’s advertised limit?
Most hosts count a visit as one unique visitor session within a rolling period, usually 24 hours, regardless of how many pages that visitor looks at. A visitor who reads ten pages in one sitting typically counts once, though the exact counting method varies by provider and is rarely documented.
Because the definition is not standardised across the industry, a “20,000 visits” plan from one host and the same figure from another are not necessarily handling the same amount of actual server load. The number reflects what the provider expects its hardware to cope with, based on an assumption about an average page.
Why do hosts use visits as the measure instead of something more technical?
Visits are easy to explain to a customer who is not technical, in a way CPU allocation, memory limits or entry processes are not. “20,000 visits a month” sounds like a clear, comparable number, even though what actually determines whether a server copes is a mix of concurrent load, page complexity and database queries, not the raw visit count alone.
A lightweight brochure site and a busy WooCommerce store generate wildly different server load at the exact same visit count, since a store runs far more database queries per page. A visits number flattens that difference into one figure, convenient for marketing and imprecise for anyone sizing a plan correctly.
What actually happens if a site goes over its visit limit?
It depends entirely on the host, and policies are not consistent across the industry. Broadly, providers respond in one of a few ways: throttling performance, charging an overage fee, prompting an upgrade, or doing nothing until the physical server resources are exhausted, at which point the site can slow or go offline regardless of the stated limit.
- Performance throttling, where the site is deliberately slowed to protect the shared server it sits on.
- An automatic overage charge added to the next invoice.
- A prompt or requirement to upgrade to the next plan tier before service continues normally.
- No visible policy at all until server resources run genuinely short, which can mean the outage arrives with no warning.
Because this varies so much, it is worth reading a provider’s actual overage policy before you rely on a visits number to plan your budget, rather than assuming it works the way another host’s plan did.
Does GoodHost’s WordPress hosting use visit limits?
No. GoodHost’s WordPress plans do not cap visits at all. Instead, each plan publishes the actual container resource limits it runs on: vCPU, RAM, entry processes, IO throughput and IOPS. That is a genuine technical ceiling rather than a traffic estimate, and it is a detail most hosts do not disclose.
| Plan | Price/month + GST | Storage | vCPU | RAM | Entry processes | IO | IOPS |
|---|---|---|---|---|---|---|---|
| WP 10 | $45 | 10 GB | 400% | 4 GB | 40 | 8 MB/s | 4,000 |
| WP 20 | $79 | 20 GB | 600% | 6 GB | 60 | 12 MB/s | 6,000 |
| WP 50 | $169 | 50 GB | 800% | 8 GB | 100 | 16 MB/s | 8,000 |
Each plan runs one site per account, with its own dedicated slice of resources rather than resources shared across many customer sites. That does not mean unlimited traffic, a server still has a physical ceiling, but it means the number you are shown is a real specification, not an estimate designed to sound reassuring.
How do you work out whether a plan’s resources are actually enough for your site?
Look at your current traffic if the site is already live, and be honest about spikes, a launch, a sale, a press mention, rather than only your average day. Compare that against a plan’s stated technical limits rather than its marketing headline.
If you run WooCommerce or another database-heavy plugin set, expect to need more headroom than a simple brochure site at the same visitor count. Our guide on what managed WordPress hosting actually includes covers that distinction, and our breakdown of real WordPress hosting costs in Australia lays out how pricing tracks against the resources you get.
What are the warning signs that a site is close to its plan’s ceiling?
Slower load times during your busiest hours, intermittent errors that only appear under load, and a dashboard that turns sluggish specifically when traffic is up, are all worth taking seriously. These overlap with other causes too, so rule those out before assuming the plan is too small.
Our article on the nine real causes of a slow WordPress site covers the non-hosting reasons, worth checking first since they cost nothing to fix.
Frequently asked questions
Is a “visit” the same as a “page view” in hosting terms?
No. A visit generally refers to one visitor session, often within a 24-hour window, while a page view counts every individual page loaded during that session. A single visit can include many page views, so the two figures are not interchangeable.
Do bots and crawlers count toward a hosting plan’s visit limit?
This depends on the host’s counting method, and it is not always disclosed clearly. Search engine crawlers and other automated traffic can inflate visit counts on some setups, which is one more reason the figure is an imprecise measure of real human demand.
Can I check my current visit count before choosing a plan?
If your site already has analytics installed, your existing visitor numbers are the most reliable starting point for sizing a new plan, better than guessing from traffic estimates alone. Look at your busiest month, not just your average, since that is what a plan actually needs to cope with.
Does a higher visit limit always mean better hosting?
Not necessarily. A high advertised visit number does not tell you anything about the underlying CPU, memory or database performance a plan actually provides. Two plans with the same visit figure can perform very differently under real load, depending on what sits behind that number.
What should I do if my site keeps hitting its host’s visit limit?
Confirm exactly what your current host’s policy is when the limit is exceeded, since that determines how urgent the problem is, then compare your real traffic against plans that publish actual technical resource limits rather than another estimated visits figure.
If visit limits and vague traffic estimates are the reason you are shopping around, it is worth looking at how GoodHost’s WordPress hosting plans lay out their actual resource specs instead.