WordPress Multisite lets you run many sites from one install. One dashboard, shared users, shared plugins, one database with separate tables per site. Agencies love the idea. "One hosting plan, twenty client blogs." Sometimes that is exactly right. Often it is a shortcut that costs more later than separate installs ever would.
Before you enable Multisite on a shared plan or reseller account, understand what you are trading away.
What Multisite is good at
Multisite shines when sites are similar and centrally governed:
- A university with department subsites sharing one theme and SSO
- A franchise brand with location pages that all update from one plugin set
- Internal microsites that share editors and never need wildly different stacks
- Developer sandboxes where you spin up subsites quickly under one network admin
You update WordPress once for the network. You activate a security patch once. You manage users at the network level and grant per-site roles. For a homogenous fleet with disciplined governance, that is real efficiency.
What Multisite is bad at
Multisite is one blast radius. A bad plugin update, a compromised super-admin account, or a runaway cron job can affect every subsite on the network. There is no clean "this client is isolated" boundary like separate cPanel accounts or separate VPS instances.
Plugin compatibility is the other headache. Plenty of popular plugins either do not support Multisite or need network activation with quirks. WooCommerce on Multisite is possible but rarely what you want for unrelated client stores. Page builders, membership plugins, and custom post type tools may assume a single site.
Migration and offboarding hurt too. Moving one client off a Multisite network is surgery. Exporting a standalone WordPress install is a well-worn path. Agencies that promised "easy exit" regret Multisite when the client leaves.
Multisite vs separate WordPress installs on one plan
Most cPanel reseller and shared plans let you run multiple WordPress sites as addon domains or subdomains. Each install has its own database, plugins, and failure domain. You pay more disk and backup space, but Client A's bad update does not take down Client B.
Compare honestly:
- Multisite: lower overhead, faster subsite creation, shared users, single update surface, shared risk
- Separate installs: better isolation, simpler plugin choices, easier per-client billing and migration, more duplicate maintenance
For unrelated small business clients on one agency hosting plan, separate installs usually win. For one organization with many branches under one brand, Multisite can win.
Hosting plan limits still apply
Multisite does not cheat physics. Twenty subsites on a starter shared plan still share CPU, inodes, and MySQL connections. Traffic spikes on one subsite starve the others. Backup size balloons because one network dump includes everything.
Read our notes on shared hosting limits you hit before traffic does. Multisite often accelerates inode and database growth because every subsite adds tables and upload folders under one account.
Domains, SSL, and DNS
Mapping custom domains to subsites (domain mapping) is straightforward today but still an extra moving part. Each domain needs SSL. Wildcard certs help subdomains; mapped apex domains need their own coverage. Botched DNS on one mapped domain does not break the network, but it does break that client's launch week.
Document which registrar holds DNS for each mapped domain. Multisite centralizes WordPress admin, not your client's GoDaddy login.
Updates and governance
Network super-admins control the universe. Site admins on individual subsites may not install plugins at all, depending on policy. That is a feature for governance and a bug when a subsite owner needs one specific plugin yesterday.
Staging a Multisite change is harder than staging a single site. Test plugin updates on a copy of the full network, not just one subsite, before you click update on production.
Security and compliance
Clients with different compliance needs (health data, payment flows, government contracts) should not share a Multisite network with random marketing microsites. Auditors ask about isolation. "They are separate tables in the same database" is not the answer they want.
Compromise of any subsite admin with elevated rights can be a path to network-wide damage. Harden super-admin accounts, enforce MFA, and limit who gets network access.
When we recommend Multisite
We suggest Multisite when one organization owns all sites, the stack is uniform, and the team has someone who understands network admin. We steer agencies with unrelated clients toward reseller hosting with isolated accounts or separate installs per client.
If you are choosing Multisite only to save $20/month on hosting, the first painful migration will erase that savings.
Bottom line
Multisite WordPress on one hosting plan is a governance tool, not a free lunch. Great for one brand, many similar subsites. Risky for a mixed client portfolio, heavy WooCommerce, or anyone who needs clean per-site isolation.
Deciding between Multisite and separate installs for your stack? Talk with Swift Host. We will look at your client mix, plugin list, and growth plans and tell you which setup will still make sense in two years.
