You bought a plan that said “unlimited sites.” A month later, your third site takes six seconds to load, and your fourth site keeps getting a white screen. You’re not alone.
Most “multi-site” hosting plans work fine for two or three small blogs. But when you add a client site with a heavy theme or a WooCommerce store, the whole setup starts to choke.
This checklist is for anyone managing multiple WordPress sites—freelancers, agencies, or owners of several projects. Use it before you sign up, or use it right now to audit your current host.
Step 1: Check the site limit (and what “unlimited” really means)
Many hosts advertise “unlimited sites,” then hide resource limits in the fine print. The host might allow 10 sites, but if the CPU or inode limit is low, your 5th site will run like a crawl.
What to do:
Look for the actual resource cap (CPU cores, RAM, inodes) per account. If the host won’t publish these numbers, ask support: “How many typical WordPress sites with moderate traffic can I run on this plan?”
Step 2: Verify how resources are pooled
On shared hosting, all your sites share one pool of resources. If one site gets a traffic spike, the others slow down. On a VPS or cheap VPS, each site can have isolated resources.
What to do:
If you’re on shared hosting, ask if the host offers resource isolation per site. If you find yourself constantly fighting with a slow neighbor site, consider moving to a VPS hosting plan where you control the allocation.
Step 3: Test the control panel for multi-site management
Managing five sites from five different dashboards is a nightmare. You need a single panel where you can see all sites, update plugins across all of them, and manage domains.
What to do:
Look for a host that uses cPanel or a custom dashboard with a “multi-site overview.” Check if you can bulk-update plugins and themes, or if you have to log in to each site separately.
Step 4: Look for staging per site (not just one staging environment)
Some hosts offer one staging environment for the whole account. That means if you need to test a plugin update on site A, you can’t stage site B at the same time.
What to do:
Confirm that each site can have its own staging copy. This is crucial for client work where you need to test changes before pushing live.
Step 5: Check the backup and restore logic for each site
If your host backs up the entire account as one file, restoring a single site means restoring everything—and possibly overwriting your other sites.
What to do:
Ask: “Can I back up and restore individual sites separately?” If the answer is no, you’ll need a third-party plugin like UpdraftPlus for each site.
Step 6: Confirm the upgrade path (can you move one site to a VPS?)
As your sites grow, you might need to move one high-traffic site to a faster server while keeping the others on shared hosting. Not all hosts allow this without migrating the entire account.
What to do:
Check if the host supports “split migration”—moving a single site to a separate plan or VPS. A good host will let you upgrade one site without touching the others. For high-traffic projects, a fast VPS server can keep your flagship site running smoothly while the rest stay on a more affordable plan.
Step 7: Evaluate support response for multi-site issues
When you have a problem with one site, you don’t want to hear “try deactivating all plugins on all your sites.” Support should understand multi-site setups.
What to do:
Test support with a specific question: “My third site is running slow, but the other four are fine. What could be the cause?” If they give a generic answer, that’s a red flag.
Common mistakes when managing multiple WordPress sites
- Buying the cheapest plan without checking site limits. You end up with a host that caps you at three sites and charges extra for more.
- Ignoring resource isolation. One client’s traffic spike slows down all your sites.
- Not having a per-site backup strategy. You restore the wrong site and lose data.
- Using a host with no staging per site. You break a live site while testing a plugin update.
Mini scenario: How a freelancer rescued five client sites from a bad host
A freelancer managed five client sites on a cheap shared plan. The host allowed “unlimited sites,” but the freelancer hit the inode limit after the third site. The fourth and fifth sites loaded like dial-up. Support couldn’t help.
She migrated all five sites to a budget VPS plan with separate staging per site and per-site backups. Now each client site runs independently, and she can update them from one dashboard. The cost went up by $10/month, but her client retention rate went up by 80%.
FAQ
Q: What is the difference between “unlimited sites” and “unlimited resources”?
A: “Unlimited sites” usually means you can host many domains, but each site still shares the same CPU, RAM, and inode limits. Resources are never truly unlimited.
Q: Can I use cheap VPS hosting for client sites?
A: Yes, as long as you configure it properly (install a control panel like CyberPanel or use managed VPS). A cheap VPS can handle 5–10 low-to-medium traffic client sites.
Q: How often should I back up each site separately?
A: At least once daily for active sites. Weekly for staging or development sites. Test your restore process monthly.
