WordPress multisite: when it makes sense, and when it does not
Multisite runs many sites from one WordPress install with shared updates and users. When it helps, when separate installs are safer, and how to set it up.
By Sohail Hussain21 November 20265 min read
WordPress multisite runs many websites from one WordPress installation. The sites share the same core files, the same plugins and themes, one set of updates and one list of users, while each keeps its own content and settings. It makes sense when one team runs many similar sites built the same way: branch or franchise sites, regional sites under one brand, departments of a university. It does not make sense for unrelated sites, for sites that need different plugins or hosting, or for any site that might one day be sold, handed to another agency or moved on its own.
Most businesses asking about multisite have two or three sites, and for them separate installations are simpler and safer.
What is WordPress multisite?
A feature built into WordPress that turns one installation into a network. A new role, the super admin, manages the whole network from a network admin area: creating sites, installing plugins and themes, and managing users.
Each site in the network has its own posts, pages, media and settings, stored in its own set of database tables. Everything else is shared:
- Plugins and themes are installed once, by the super admin. They can be activated network-wide or made available for each site to switch on. Site administrators cannot install their own.
- Users live in one shared table. A person can belong to several sites with a different role on each.
- Updates happen once for the whole network.
Sites are addressed either as subdirectories (example.com/india/) or subdomains (india.example.com), chosen when the network is created. Individual sites can also be given their own domains.
We set up and maintain WordPress, including the occasional network, as part of our website design and development work. More often, we end up advising against it.
When does multisite make sense?
When the sites are siblings: built from the same theme, using the same plugins, managed by the same team, with editors who each look after one site.
- A company with 30 branch or dealer sites, each with local contact details, team and news, all in one brand design.
- A university or hospital group where each department or facility runs its own site under one design system.
- A franchise network where head office controls the design and plugins, and each franchisee edits their own pages.
- An agency or publisher running many small, near-identical microsites.
The benefit is control at scale. One theme update reaches every site. A new plugin is approved once. A security fix is applied once, not 30 times.
When is it the wrong choice?
- The sites are unrelated. A corporate site, a shop and a recruitment microsite with different designs and plugins gain nothing from sharing an installation, and lose independence.
- One site might leave. Selling a brand, moving a site to a different agency, or giving a subsidiary its own hosting means extracting it from the network. It is possible, but it is a migration project.
- The risk should be separate. A vulnerable plugin or a bad update affects every site at once. So does downtime.
- Plugins are not network-ready. Many plugins work in multisite, but some do not, and some premium licences are priced per site anyway. Check every plugin you need before you commit.
- Hosting cannot support it. The official guide notes that some shared hosts restrict which kinds of network you can run, and subdomain networks may need wildcard DNS.
How does multisite compare with separate installations?
| Multisite network | Separate installations | |
|---|---|---|
| Updates | Once for all sites | Once per site, though tools can batch them |
| Plugins and themes | Chosen centrally by the super admin | Each site chooses its own |
| Users | One shared list, roles per site | Separate users on each site |
| Risk | One problem can affect every site | Problems stay on one site |
| Hosting | One environment sized for the busiest site | Each site hosted to suit it |
| Moving one site elsewhere | A migration project | Copy it and go |
| Best for | Many similar sites run by one team | A few sites, or different sites |
For two or three sites, separate installations managed with a dashboard tool or WP-CLI get most of the convenience of multisite without the coupling. The case for a network grows with the number of similar sites; with only a handful, the coupling usually costs more than it saves.
What about multilingual sites on multisite?
One common pattern uses a network with one site per language, and a plugin such as MultilingualPress to link translations between them. It keeps each language's content cleanly separate and lets each language team work independently.
The more common approach runs all languages in one site with a plugin such as WPML or Polylang. That is simpler to host and update, and suits most company sites. WPML vs Polylang vs TranslatePress compares those plugins, and subdomain vs subfolder vs ccTLD covers the URL choice that comes with either approach.
How do you set one up?
The official guide to creating a network lists the steps. In short:
- Back up the files and database, including
wp-config.phpand.htaccess. - Check that pretty permalinks work, and deactivate all plugins.
- Add this line to
wp-config.php, above the line that says to stop editing:
define( 'WP_ALLOW_MULTISITE', true );
- Go to Tools → Network Setup, choose subdomains or subdirectories, and run the installer.
- Add the constants and rewrite rules WordPress then shows you to
wp-config.phpand.htaccess. Copy them from that screen, not from a blog post; they are generated for your installation. - Log in again and reactivate plugins from the network admin.
Two restrictions catch people. If the site has been running for more than a month, WordPress does not offer subdirectories, because they can clash with existing permalinks. And changing between subdomains and subdirectories after setup is possible but, in the guide's words, "might not be easy". Decide before you start.
Hosting with SSH and WP-CLI makes running a network far easier, and our hosting cost calculator gives a rough monthly figure for the combined traffic. For the wider choices about running WordPress for a business, see WordPress for business websites.
Was this guide useful?