A post has taken off. The site is on an entry plan, the analytics dashboard is climbing, and the question is practical: when monthly visits pass the plan allowance, does the host bill, throttle or suspend? The answer is written down by some hosts and absent from the pages of others, and the unit being counted is not the one in your analytics.
The meter on your host is not the meter in your analytics
An analytics session and a host visit are different units, and each host sets its own. A spike can look modest in the dashboard you watch and still land on an invoice, or the reverse. This piece reads four managed WordPress hosts, Flywheel, Pressable, Kinsta and WP Engine, and reports what each one’s own public pages say. It does not generalise beyond them.
The scope is the origin host’s own metering and overage policy. It is not about the CDN layer, which is a separate piece, and it is not about detecting downtime, which is covered in uptime monitoring for the page a social campaign sends traffic to. For the dashboard side of the mismatch, see why analytics can report social traffic differently.
What each host says a visit is, and what it does past the cap
All four pages were fetched on 10 October 2026. Figures are for the entry plan as listed on each page that day.
| Host | Entry plan visits per month | Definition of a visit | Stated consequence past the cap | Source, fetched |
|---|---|---|---|---|
| Flywheel | 25,000 monthly visits | A unique IP address in a 24-hour period. Known bots, spammers and attackers are removed before counting. | Overage billed per 1,000 extra visits. Its overage page states it does not turn off sites or plans due to traffic spikes. | getflywheel.com/pricing/ and overage page, 10 Oct 2026 |
| Pressable | Signature 1 lists 30K visits per month | None found on the pricing page read. The page links a separate knowledge base article on how visits are calculated, which was not read for this piece. | Usage above included visits and storage is billed at $1.20 per 1,000 visits. | pressable.com/pricing/, 10 Oct 2026 |
| Kinsta | 35,000 estimated monthly visits on the entry plan, alongside 20GB server bandwidth | Not applicable, visits are not metered. | No visit-based charge stated. The metered resource on the page is bandwidth. | kinsta.com/pricing/, 10 Oct 2026 |
| WP Engine | 25,000 visits per month on the 1 site plan | None found on the plans page. | No per-1,000 overage rate found. The page notes numbers are estimates only and says to get in touch for dynamic sites or traffic spikes. | wpengine.com/plans/, 10 Oct 2026 |
Two wordings deserve to be quoted exactly. Kinsta’s tooltip on the monthly visits row reads: “An estimate of the monthly visits this plan’s included bandwidth can support. Visits aren’t metered, so use this as a guide, not a limit. Actual capacity will vary by site.” A visit count is therefore not what triggers a bill on that page. Bandwidth is the figure with a cap.
WP Engine’s plan comparison carries the note on its Visits/mo row: “Numbers are estimates only. Get in touch for dynamic sites or traffic spikes.” That is an invitation to a conversation, not a published rule. Neither the Kinsta page nor the WP Engine page, as read, states throttling or suspension. Full terms of service were not read, so that silence is not a guarantee.
Flywheel quotes two overage rates
On 10 October 2026, two Flywheel pages gave two different figures. The FAQ on the pricing page says the overage cost is $1 per 1,000 extra monthly visitors. The overage pricing page says $2 per 1,000 extra monthly visitors. Both were fetched the same day.
This piece does not decide which is current. Before relying on either, confirm the rate in your own account or with Flywheel support. The next section shows the arithmetic at both.
Each page’s own worked example is consistent with its own rate. The pricing page says a Starter plan receiving 30,000 monthly visits is charged $5, which is 5,000 over 25,000 at $1 per 1,000. The overage page says a Starter plan receiving 35,000 visits is charged $20, which is 10,000 over at $2 per 1,000.
Turning a spike into the host’s unit
This is a hypothetical, not a case study, and the figures are arithmetic on published rates, not observed bills. Take a site on a 25,000-visit allowance whose month ends at 125,000 visits as the host counts them. The overage is 100,000 visits, or 100 blocks of 1,000.
- At Flywheel’s $1 per 1,000 (pricing page): $100.
- At Flywheel’s $2 per 1,000 (overage page): $200.
- Pressable has a different allowance, so compute it on its own 30K entry plan. Overage is 95,000 visits, or 95 blocks, at $1.20 per 1,000: $114.
The Pressable figure is not a like-for-like comparison with Flywheel’s, because the allowances differ, and it implies no ranking of the hosts. WP Engine is absent because no rate was found. Kinsta is absent because its page does not bill by visit.
Why would a host’s count differ from your session count? Take only Flywheel’s published definition, a unique IP address per 24 hours. By that definition, one office network or mobile carrier address can stand in front of many readers and be counted once, and one reader who appears from a home connection and then a phone network on the same day is counted twice. That is a consequence of the stated definition, not measured behaviour, and no claim is made about how far the two counts drift in practice.
Flywheel says it removes known bots, spammers and attackers before counting. That is its statement. No claim is made here about how well the filtering works.
A visit overage is also not the only metered cost a spike touches. Related reading: what a traffic spike does to chat widget pricing.
Three questions to put to a host before the spike, not after
- Is the allowance metered or an estimate? Kinsta and WP Engine word it as an estimate. An acceptable answer says which resource is actually metered and where that meter is shown in your account.
- What is a visit, and is the definition published? Only Flywheel’s definition was found on the pages read. No definition was found for WP Engine, and none on the Pressable pricing page. An acceptable answer is a written definition you can point to, including what is excluded.
- What happens past the cap? Billed overage with a stated rate, a conversation, or something else. This piece found a stated rate only at Flywheel and Pressable. An acceptable answer is a rate or a stated process, in writing, that matches your current plan.
What this piece did not check
Prices and allowances were verified on 10 October 2026 from each host’s own public pages, listed under Sources. Plan terms were read from those pages, not from customer accounts or terms-of-service documents, and throttling or suspension clauses in full terms were not read. Pressable’s knowledge base article on how visits are calculated was not read.
This is not Watchdog data and is not on the re-verification schedule. Rates and allowances can change after the date above.
Disclosure: followedapp is published by the team behind RecurPost, which is covered vendor #34 under the same rules as every other vendor. RecurPost is not a hosting product and is not discussed here beyond this line.
Next step
Before the next big post, open your host’s plan page, find the visit row, and write down the unit, the allowance and the stated consequence. Then send the three questions above to support and keep the reply.
FAQ
Is a host visit the same as an analytics session?
No, the unit is each host’s own. The one definition verified here is Flywheel’s, a unique IP address in a 24-hour period with known bots, spammers and attackers removed first. A published definition was not found on the other pages read.
Will my site be shut off if it goes over its visit allowance?
Flywheel’s overage page states it does not turn off sites or customer plans due to spikes in traffic, and bills overage instead. The Pressable, Kinsta and WP Engine pages read did not state a shutoff rule, and full terms of service were not read.
Sources
- Flywheel pricing page, fetched 10 October 2026, HTTP 200.
- Flywheel overage pricing page, fetched 10 October 2026, HTTP 200.
- Pressable pricing page, fetched 10 October 2026, HTTP 200.
- Kinsta pricing page, fetched 10 October 2026, HTTP 200.
- WP Engine plans page, fetched 10 October 2026, HTTP 200.