WordPress multisite hosting is hosting built to run a network of WordPress sites from a single WordPress installation. One set of core files, one pool of plugins and themes and one place to manage everything. It saves time when the sites are related, and it creates shared risks when they are not.
This guide explains how a WordPress multisite works, what WordPress multisite hosting needs to handle it and six risks to weigh before you network your sites. It is written for developers, agencies and organizations deciding between one multisite network and a collection of separate installs.
What WordPress multisite is
The WordPress developer documentation describes Multisite as a feature that lets you create several instances of WordPress managed within one installation. Each site keeps its own content and its own database tables. Only the user table is shared across the network.
A network can be path-based, with sites at example.com/site1 and example.com/site2, or domain-based, with separate domains or subdomains for each site. A super admin oversees the network, controlling settings, plugins, themes and the creation of new sites.
That structure is why WordPress multisite hosting suits some projects very well. It is also why it can hurt when used for the wrong ones.
When WordPress multisite hosting makes sense
WordPress multisite hosting fits groups of sites that share ownership, branding and rules. Typical examples include a university with department sites, a franchise with location sites, a publisher with regional editions or a company with country sites.
In each case, one team manages the theme and plugins, and individual site managers only handle content. Updates happen once for everyone, and permissions are centralized.
When separate installs are the better choice
For unrelated client sites, separate installs are usually safer. WordPress hosting for agencies often works better with one account per client, because each client can have different plugins, update schedules and risk profiles.
If you run client sites as an agency, a cPanel account per client under a reseller hosting plan gives you isolation without a shared codebase. Our guide to the best reseller hosting for agencies covers that setup.
What WordPress multisite hosting needs from the server
A network behaves like one larger site from the server’s point of view. That changes what you should check.
Start with memory and PHP workers. Each request to any site in the network uses the same pool, so a plan that suits one small site can run short when ten sites are active at once. Check the memory limit per process and the worker count, and ask whether limits apply per site or to the whole network.
Next, check the database. All the sites’ tables sit in one database, so performance depends on how well it is tuned and how large it grows. Object caching, such as Redis, reduces database load across every site in the network.
Finally, check WordPress requirements. WordPress.org recommends PHP 8.3 or greater and MariaDB 10.11 or greater or MySQL 8.0 or greater, and Multisite needs URL rewrites enabled. Confirm that your host supports all of that on the plan you choose.
Risk 1: One failure can affect every site
With WordPress multisite hosting, all sites in the network share the same core files, plugins and themes. A bad plugin update or a security flaw hits the whole network at once.
A staging copy of the entire network helps. Test every update there first, and keep plugin choices lean. The fewer plugins you network-activate, the smaller the blast radius.
Risk 2: Shared resources and noisy sites
All sites in the network draw from the same server resources. A busy site can slow down the others, and your host’s limits apply to the network as a whole.
Plan your WordPress multisite hosting around the combined traffic of all sites, plus headroom. Check how many PHP workers the plan has, how much memory each process gets and whether visit limits apply to the network total. Our VPS web hosting is a good fit for larger networks because you control the resources.
Risk 3: Backups and restores get harder
Restoring one site out of a network is not as simple as restoring a single install. Because every site’s tables live in one database, you need either a per-site export or a full network restore.
Ask your WordPress multisite hosting provider whether it can restore a single site’s tables and files without rolling back the others. Test a restore before you launch, since you will not enjoy learning how it works after an accident.
Risk 4: Not every plugin supports multisite
Some plugins and themes are not designed for networks. They may store settings in the wrong place, break on network activation or fail when sites use different domains.
Check each plugin’s documentation and test it on a staging network. Prefer plugins that say they support multisite, and avoid anything that modifies core behavior in unusual ways.
Risk 5: Domains, DNS and SSL need planning
A domain-based network needs a way to map each domain to its site and a certificate for each hostname. Subdomain networks usually need wildcard DNS, and certificates must cover the subdomains.
Ask your host how SSL works on multisite. You want certificates that issue and renew automatically as you add sites, because a manual process breaks at the worst moment.
Risk 6: WooCommerce multisite adds complexity
WooCommerce multisite is possible, with a separate store on each site in the network. But stores need more server resources, careful caching rules and checkout capacity, and those needs multiply across the network.
Every store also has its own orders, products and payment settings. If the stores are unrelated businesses, separate installs on a plan sized for each store are simpler. Read our guide to WooCommerce hosting requirements before you commit to a plan.
Security on a multisite network
Security deserves its own thought on WordPress multisite hosting, because the network shares code and a super admin account controls everything. If an attacker takes that account over, every site is at risk.
Use strong, unique passwords and two-step authentication for every super admin. Keep the number of super admins small. Limit who can install plugins and themes, since each addition affects the whole network.
At the server level, look for a firewall, malware scanning and account isolation. Our guide to secure WordPress hosting lists what to ask for. Also test restores for the network as a whole and for a single site, so you know what recovery looks like.
Path-based or domain-based: how to choose
Your network type affects URLs, SEO and setup effort. The table below shows the main differences.
| Question | Path-based network | Domain or subdomain network |
|---|---|---|
| Example URLs | example.com/site1 | site1.example.com or site1.com |
| Best for | Sections of one brand | Separate brands or regions |
| Setup effort | Lower | Higher (DNS, domain mapping, SSL) |
| Separate domains | No | Yes |
Pick path-based if the sites are sections of one brand and you want a simple setup. Pick domain-based if each site needs its own identity.
What to ask about WordPress multisite hosting
- Do you support WordPress multisite, and have you run networks of my size?
- Can the plan handle the combined traffic of every site?
- How do SSL certificates work for subdomains and mapped domains?
- Can you restore a single site, or only the whole network?
- Is there a staging copy of the entire network?
- Who handles network-wide updates and incidents?
The answers will tell you how much of the WordPress multisite hosting work stays with you. For help scoping a network, contact our team, or look at our WordPress hosting and custom hosting solutions for larger builds.
Migrating separate sites into a network
Many teams arrive at multisite after running several separate sites. Moving them takes care. Start by listing every plugin and theme in use across the sites and checking which ones support networks. Standardize on as few as you can.
Next, build the network on a staging environment. Import content one site at a time, test forms, menus and media, and compare pages to the originals. For domain-based networks, set up domain mapping and SSL before you switch DNS.
Plan the cutover for a quiet period and keep the old sites available until the new ones are verified. If you want help, our team can scope the move and run it for you. Get in touch and describe your sites.
Managing a multisite network day to day on WordPress multisite hosting
A healthy network depends on routine. Keep the list of network-activated plugins short. Review super admin accounts every quarter and remove anyone who no longer needs access. Apply updates on staging first, then to production on a schedule.
Document what each site owner may and may not change. Without that, one editor’s well-meant change can affect other sites. Add monitoring so you hear about downtime before your users do.
WordPress multisite hosting FAQ
What is WordPress multisite?
It is a WordPress feature that runs several sites from one installation, sharing core files, plugins and themes, with separate content per site and a shared user table.
Is multisite good for agencies?
For unrelated client sites, WordPress multisite hosting is usually the wrong tool, because a shared codebase ties their risks together. It works for networks of related sites that share branding and policies.
Does multisite hosting cost more?
WordPress multisite hosting has to cover the combined traffic and resources of every site, so it usually costs more than a single-site plan. It can cost less than running many separate plans for a group of small sites.
Can I run WooCommerce on a multisite network?
Yes, with a store per site. Plan for more server capacity, careful caching and more testing, since every store has its own orders and settings.
Can I convert separate sites into a multisite network later?
Yes, but it takes planning. You will need to import content, check plugin compatibility and set up domain mapping, so test on a staging copy first.
Sources
Related reading: secure WordPress hosting, managed WordPress hosting and web development services.