Keepstone

Managed WordPress Pricing Models: Per-Visit, Per-Site and the Overage Trap

Posted Jul 16, 2026

Managed WordPress hosting is sold on three pricing models: per-visit tiers (the most common), per-site plans, and pay-as-you-go by server size. The model decides where your bill goes as you grow, and the single biggest surprise in this market — the tier jump, where crossing a visit cap either triggers an overage charge or pushes you to a plan that can cost roughly double — comes from not understanding which model you're on. This guide makes the three models concrete.

Model 1: per-visit tiers

Most premium managed hosts — Kinsta, WP Engine, Flywheel, Pressable — price by a monthly 'visits' allowance. Each plan is a fixed tier: an entry plan might allow 25,000 visits for around $25 to $35 a month, the next tier 50,000 to 75,000 for roughly double, and so on. Within your tier the price is flat no matter how the traffic moves day to day. The catch is the cap. Go over it and one of two things happens: the host bills an overage — commonly advertised around $1 for every 1,000 extra visits, read September 10, 2026 — or it moves you up to the next tier. Either way, your bill steps up rather than rising smoothly, which is why we call it the tier jump.

A trap inside the trap: hosts define a 'visit' differently. Some count unique visitors with bots and uptime monitors filtered out; others count closer to raw requests. Two plans that both advertise '25,000 visits' can therefore hit their caps at very different amounts of real traffic. Before you buy on a per-visit plan, read the host's own definition and check what's excluded — it decides how often you'll pay the jump.

Model 2: per-site (or by resource)

Some hosts price mainly by how many WordPress installs you run and how much storage you use, rather than by a hard visit cap. Nexcess, for example, advertises managed WordPress from around $21 a month and states it doesn't charge visit overages, using a fair-use and PHP-worker model instead — so spiky traffic on a WooCommerce store doesn't trip a meter. This model is friendlier for unpredictable traffic and for agencies running many small sites, but it has its own limit: sustained heavy load can bump into worker or resource ceilings, and the host may ask you to upgrade for performance rather than for a visit count.

Model 3: pay-as-you-go by server

Managed cloud hosts like Cloudways let you choose a server size — starting around $11 a month on a small instance — and manage WordPress on top of it. There is no visit cap and no overage; you pay for the server you pick and resize it when you need more. That puts you in control of the cost curve, which many owners prefer, but it also means you decide when to scale, and getting the sizing wrong shows up as a slow site rather than an automatic upgrade. Backups and a CDN are often paid add-ons on this model, so the headline price isn't quite the all-in price.

Monthly vs annual, and intro discounts

Two smaller pricing factors sit on top of all three models. First, paying monthly usually costs around 20% more than paying annually — the advertised 'from' price is almost always the annual rate. Second, unlike budget hosting, managed WordPress rarely runs a deep promo-to-renewal cliff; the intro price is close to the ongoing price. When there is a discount, it's often a first-term percentage off or a couple of months free that reverts to the standard rate, not a 3x renewal spike. So the number to plan around is the standard tier price, at the visit level you expect to reach.

The overage arithmetic, worked out

The overage is where a per-visit plan surprises people, so it's worth doing the sums once. Take a 25,000-visit plan at $35 a month with an overage advertised around $1 per 1,000 extra visits. If your site settles at 40,000 visits, that's 15,000 over the cap — roughly $15 in overage, taking the bill to about $50 a month. At 60,000 visits you're 35,000 over, adding about $35, which lands near the price of simply moving up to the next tier. That crossover point is the key insight: once your overage approaches the cost of the next plan, you should switch to that plan, because it usually comes with a higher cap and better resources for the same money. Hosts count on people paying overages out of inertia rather than upgrading; knowing the crossover saves you from it.

How to read a managed pricing page

Read every managed pricing page in the same order, and the marketing falls away. First, confirm whether the 'from' price is monthly or annual — it's nearly always annual, so add about 20% if you'll pay monthly. Second, find the visit cap or the resource limit, and the host's definition of a visit, so you know what you're actually being sold. Third, find the price and cap of the next tier up — that's your real cost if you grow. Fourth, check what's bundled versus an add-on, especially the CDN, backups and staging, because two plans at the same headline price can include very different things. Fifth, note the refund window before committing to an annual term. Five questions, in that order, and you can compare any two hosts honestly regardless of how their pages are dressed up.

One more variable cuts across all three models: what a plan includes versus charges extra for. A per-visit plan that bundles an enterprise CDN, backups and staging can be better value than a cheaper pay-as-you-go server where each of those is a paid add-on, even though the second one looks less expensive at first glance. When you compare, add the cost of the add-ons you'll actually need to the base price so you're comparing all-in figures. The model tells you where your bill goes as you grow; the inclusions tell you what the base price really covers. Judge both together, and the genuinely cheapest option for your situation usually looks different from the one with the lowest headline number.

The practical takeaway: identify the model before the price. On a per-visit host, budget for the tier above your current traffic; on a per-site host, budget for the installs and resources you'll use; on pay-as-you-go, budget for the server plus add-ons. Our ranking of the best managed WordPress hosting labels each host's model and shows the next tier, and our guide to when to upgrade to managed helps you time the step so you're not paying for headroom early.

Pricing questions

What happens if I go over my managed hosting visit limit?
One of two things, depending on the host: an overage charge (often advertised around $1 per 1,000 extra visits) or an automatic move to the next plan tier. Most hosts warn you as you approach the cap. Either way the bill steps up, so it's worth knowing your host's rule before your traffic grows.
Which pricing model is cheapest?
For unpredictable or spiky traffic, a no-cap model (per-site or pay-as-you-go) usually avoids surprise overages. For steady, predictable traffic that sits comfortably inside a tier, per-visit plans are simple and competitive. The cheapest model is the one that matches your traffic pattern, not a single winner.
Is managed WordPress cheaper paid annually?
Yes, almost always. Monthly billing typically costs about 20% more than the annual rate, and the advertised 'from' price is usually the annual one. If you're confident in the host, paying yearly is the cheaper choice — just confirm the refund window first.

See how this fits the field: the best managed WordPress hosting, ranked, or read whether managed WordPress hosting is worth it.