Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Hosting · Guide

How to Choose Hosting for Agency Client Sites

Short answer

Choose hosting for agency client sites by matching the plan to each site, not by buying one plan for all of them. Check that the host supports PHP 8.3 or newer, offers staging and daily backups, and lets you add sites without a steep price jump. Then compare the renewal price, the visit limit, and the support hours before you sign up.

Key takeaways

  • WordPress.org recommends PHP 8.3 or newer, MariaDB 10.11 or newer, or MySQL 8.4 or newer, as of November 2026.
  • SiteGround StartUp costs $2.99 a month for the first term and renews at $17.99 a month, as of November 2026.
  • Kinsta charges $35 a month for 1 site with 35,000 visits, and $340 a month for 20 sites, as of November 2026.
  • WP Engine charges $2 for every 1,000 visits over a plan limit, so a traffic spike can raise the bill fast.
  • Check the live site in Tools, Site Health, Info, Server after launch to confirm the PHP version and limits.
  • Put the client, the billing owner, and the access rules in writing before you build the site.

What does agency hosting mean for client sites?

Agency hosting means one agency runs WordPress sites for several clients, often on one account or on separate plans per client.

Each client site still needs its own login, its own backups, and its own billing record. A shared login for all clients creates risk when a client leaves or when a staff member changes roles.

You can host client sites in three main ways. You can put each site on its own plan, group several sites on one multi-site plan, or run them on a managed cloud server that you control. The right choice depends on site count, traffic, and who pays the bill.

What should you check before you pick a host?

Check the technical baseline, the site limits, and the renewal price before you compare brand names.

WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater, or MySQL 8.4 or greater, as of November 2026. It also recommends Apache or Nginx and HTTPS support. A host that cannot meet that baseline is not a fit for new client work.

PHP versions have fixed end dates. PHP 8.1 reached end of life on 31 December 2025, PHP 8.2 gets security fixes only until 31 December 2026, and PHP 8.3 gets security fixes only until 31 December 2027. Ask the host which PHP versions it offers for new sites and how you switch between them.

Use this short checklist for each host you shortlist:

  • PHP 8.3 or newer, with a clear way to change the version per site
  • Staging sites included, so you can test changes off the live site
  • Daily backups with a stated retention period, plus a restore option you can use yourself
  • Free SSL certificates for every site on the plan
  • A visit, storage, or bandwidth limit that fits the largest client site, not the smallest
  • Support hours and a support channel your team can reach during client work hours

For a single-site decision, the general guide to how to choose WordPress hosting covers the same baseline in more detail.

Which type of hosting fits agency client sites?

Shared hosting fits small, low-traffic client sites, managed WordPress hosting fits most agency work, and managed cloud hosting fits agencies that want control over server size.

Shared hosting puts many sites on one server. It costs less at the start, but one busy site can slow its neighbours, and limits on CPU time can stop a site during a spike. It suits a brochure site with about 10,000 visits a month.

Managed WordPress hosting adds WordPress updates, caching, staging, and backups to the plan. The host handles the server layer, so your team spends less time on patching and more time on client work. Most agencies start here.

Managed cloud hosting gives you a server sized by RAM and CPU, with several sites on it. You pick the server size and scale it up when traffic grows. It suits agencies with 10 or more sites that want one bill and one server to manage.

Hosting typeBest forMain trade-off
Shared hosting1 to 3 small client sitesLow price, shared resources and strict limits
Managed WordPress hostingMost agency client sitesVisit and site limits set the price
Managed cloud hosting10 or more sites on one serverYou size the server and watch its use
Dedicated or enterprise plansHigh-traffic or regulated client sitesHigher cost and a longer setup

How much does agency hosting cost in November 2026?

Prices range from about $3 a month for a shared starter plan to $340 a month or more for a 20-site managed plan, as of November 2026.

Intro prices can mislead you. SiteGround lists StartUp at $2.99 a month for the first 12-month term, then $17.99 a month at renewal, as of November 2026.

GrowBig lists $4.99 a month first, then $29.99 a month. GoGeek lists $7.99 a month first, then $44.99 a month. Budget on the renewal figure, not the first-term figure.

Kinsta lists Single 35k at $35 a month for 1 site, 35,000 visits a month, and 10 GB of storage, as of November 2026.

WP 2 costs $70 a month for 2 sites, WP 5 costs $115 a month for 5 sites, and Agency 20 costs $340 a month for 20 sites. Kinsta lists no intro price, so the monthly price is the price you keep paying.

WP Engine lists Startup at $35 a month billed monthly, or $336 a year, as of November 2026. That plan covers 1 site, 25,000 visits a month, and 10 GB of storage.

Business plans start at $400 a month billed annually. WP Engine charges $2 for every 1,000 visits over a plan limit.

Cloudways lists its Starter plan at $20 a month for 2 GB of RAM, 2 vCPU, and 5 apps, as of November 2026. DigitalOcean servers through Cloudways start at $11 a month. Offsite backup storage costs $0.033 per GB, and extra CDN bandwidth costs $0.02 per GB.

Host and planPrice as of November 2026SitesVisits or size
SiteGround StartUp$2.99 first term, $17.99 renewal1About 10,000 visits a month, 10 GB
SiteGround GrowBig$4.99 first term, $29.99 renewalUnlimitedAbout 100,000 visits a month, 50 GB
Kinsta Single 35k$35 a month135,000 visits a month, 10 GB
Kinsta WP 5$115 a month5125,000 visits a month, 30 GB
Kinsta Agency 20$340 a month20500,000 visits a month, 50 GB
WP Engine Startup$35 a month, or $336 a year125,000 visits a month, 10 GB
Cloudways Starter$20 a month5 apps2 GB RAM, 2 vCPU

Prices exclude tax on most host pages, and they can change. Check the live pricing page at checkout and note the renewal date in your client file.

How do you compare hosts on limits that matter?

Compare visit limits, storage, backup retention, and overage fees, because those four numbers decide the real monthly cost.

A visit limit counts unique visitors in a set period. Kinsta counts each unique IP address in a 24-hour period as one visit, and it notifies you at 80% and 100% of use.

WP Engine charges $2 per 1,000 visits over the limit. A site that doubles its traffic for one month can double part of its bill on a visit-based plan.

Storage limits decide how many sites fit on a plan. SiteGround gives 10 GB on StartUp, 50 GB on GrowBig, and 100 GB on GoGeek.

Kinsta gives 10 GB on its single-site plans and 50 GB on Agency 20. Count images, backups, and staging copies, not just the live site files.

Backup retention decides how far back you can restore. Kinsta keeps daily backups for 14 days on Business plans and 30 days on Agency plans, as of November 2026.

Ask each host how long it keeps backups and whether you can download a copy yourself. The guide to how to back up WordPress explains how to keep a second copy outside the host.

Uptime promises also differ. Kinsta guarantees 99.9% uptime on Business plans and offers up to a 99.99% uptime SLA on Enterprise plans, as of November 2026. Read what the promise covers and how you claim credit if the host misses it.

How do you set up a client site the right way?

Set up the site in this order: plan, staging, build, check, then launch, with access and billing recorded at each step.

1. Record the client, the owner, and the payer

Write down who owns the domain, who owns the hosting account, and who pays the renewal. If the agency pays, note the markup and the renewal date. If the client pays, use the client email on the account so a renewal notice reaches them.

2. Create the site on a staging copy first

Create the site as a staging site or a private install, not on the live domain. Add the theme, the plugins, and the client content there. Test the contact form, the checkout if the site sells online, and the mobile layout before you point the domain at it.

3. Set the PHP version and the memory limit

Set PHP to 8.3 or newer in the host panel, then check the live value in WordPress. Open Tools, then Site Health, then the Info tab, then Server, and read the PHP version line. That screen shows the version WordPress runs, not the version a command line reports.

4. Add backups, SSL, and security basics

Turn on daily backups and confirm the retention period. Check that the SSL certificate covers the site and that the site loads on https. Add a separate admin account for the agency and one for the client, with different emails and strong passwords.

5. Launch and check the live site

Point the domain at the host, wait for DNS to update, then open the live site in a private browser window. Click the main pages, send a test form, and check that images load. Fix any mixed-content warning before you tell the client the site is live.

Allow 1 to 3 hours for a simple site setup, plus extra time for content, DNS, and client review. A store or a site with many plugins takes longer, so book that time in the project plan.

How do you handle billing, access, and handover?

Put billing, access, and handover in writing before you build, so no one argues about them when a client leaves.

Decide who owns the account. The cleanest setup is a client-owned account with the agency added as a collaborator or team member. That way the client keeps the site if the agency changes, and the agency can still work on it day to day.

If the agency owns the account, charge the client a clear monthly hosting fee and state the renewal date in the contract. Note which plan the fee covers and what happens if the site outgrows it. A fee that covers a $35 a month plan cannot also cover a $115 a month plan.

Keep a simple access sheet for each client. List the host login, the WordPress admin login, the domain registrar, and the email used for each one. Store it in a password manager, not in a shared document or an email thread.

For handover, remove agency accounts, hand over the access sheet, and confirm the client can log in. Keep a note of the handover date and who received it. The yearly cost guide for how much it costs to maintain a WordPress site can help you price the ongoing care separately from hosting.

How do you check that hosting is working after launch?

Check speed, uptime, backups, and the PHP version in the first week, then repeat the checks each month.

Open Tools, then Site Health, in the WordPress dashboard and read the Status tab. It flags an outdated PHP version and other server issues. Then open the Info tab and the Server section to confirm the PHP version, the database version, and the memory limit.

Check that a backup ran after launch and that you can restore it on staging. A backup you have never restored is a guess, not a safety net. Note the backup date and the retention period in the client file.

Watch the visit count in the host dashboard for the first month. If a site uses 80% of its visit limit in week 2, plan an upgrade before the month ends. That avoids overage fees and a slow site at month end.

For speed, the guide to how to speed up WordPress lists the checks to run after a launch, from caching to image size.

How do you manage many client sites without losing track?

Use one dashboard, one naming rule, and one monthly check for all client sites.

Give each site a clear name in the host panel, such as the client name plus the domain. Use the same naming rule for staging sites, so you never edit the wrong copy. Keep a list of every site, its plan, its renewal date, and its visit limit in one sheet.

Use the host team features or a management dashboard to reach all sites from one login. That saves time and cuts the risk of a shared password. The guide to how to manage multiple WordPress sites covers the dashboard options in detail.

Run the same monthly check on every site: updates, backups, PHP version, and visit use.

WordPress runs 39.2% of all websites and 57.9% of sites with a known CMS, according to W3Techs data from 13 November 2026. That scale means plugin and PHP updates arrive often, so a monthly check is not optional for client work.

What mistakes should you avoid?

Avoid buying on the intro price, sharing one login across clients, and skipping the staging check.

Do not pick a host by its first-term price alone. A $2.99 a month plan that renews at $17.99 a month costs about $216 a year from year 2, while a $35 a month plan with no intro price costs $420 a year. Both numbers matter, and the client should see both before they agree.

Do not put all client sites on one shared login. When one client leaves, you must change a password that other clients still use. Give each client site its own account or its own team access.

Do not skip staging for a plugin or PHP change. A change that breaks a checkout or a form on a live client site costs more in trust than the 10 minutes a staging check takes.

Do not ignore visit limits. A plan with 25,000 visits a month is a poor fit for a site that already gets 20,000 visits. Check the last 3 months of traffic before you pick the plan, and pick the next size up if the site is growing.

Frequently asked questions

Should the agency or the client own the hosting account?

The client should own the account in most cases, with the agency added as a collaborator or team member. That way the client keeps the site, domain, and billing history if they change agency. If the agency owns the account, the contract should state the monthly fee, the plan, the renewal date, and how handover works.

How many client sites can one hosting plan hold?

It depends on the plan limit, not on the server alone. Some plans allow 1 site, some allow 5, 10, or 20 sites, and some allow unlimited sites within storage and visit limits. Check the site count, the storage, and the visit limit together, because a plan can allow many sites and still run out of storage or visits.

What happens if a client site goes over its visit limit?

It depends on the host. Some hosts charge overage fees, such as $2 for every 1,000 extra visits, while others notify you and ask you to upgrade. Check the overage rule before you sign up, watch the visit count in the first month, and upgrade early if the site is close to its limit.

Do I need a separate staging site for each client?

Yes, each client site should have its own staging copy. A shared staging site mixes client content and makes it easy to push the wrong change live. Use staging for plugin updates, theme changes, and PHP version changes, then check the staging copy before you apply the change to the live site.

How often should I review hosting for client sites?

Review each client site monthly for updates, backups, PHP version, and visit use, and review the plan and price every year before renewal. A yearly review catches renewal price rises, sites that have outgrown their plan, and PHP versions that are close to end of life.

Sources

  1. Requirements WordPress.org
  2. Supported Versions PHP.net
  3. WordPress hosting plans Kinsta
  4. Managed Hosting Platform WP Engine
  5. The Complete Guide to Website Hosting Costs in 2026 SiteGround
  6. Cloudways Pricing and Plans Cloudways
  7. CMS Market Share Trends: Top Content Management Systems (Nov 2026) Search Engine Journal

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test