You manage three, five, or ten WordPress sites, and every week it’s the same routine: logging in separately to each one, running the same updates on each one, and keeping the same plugins up to date on each one. At some point, you think: surely there has to be an easier way? WordPress Multisite is the built-in solution: a single WordPress installation that powers an entire network of sites, with one dashboard, one set of plugins, and one update cycle. It sounds like the solution to everything, but it’s definitely not for everyone. That’s why we’ll start with the decision-making process, because a poorly chosen multisite setup is harder to undo than it was to set up.
When Multisite Is the Right Choice (and When It Isn't)
Multisite works well when the sites in the network are truly part of the same entity: same owner, same administrator, similar technology. Think of a company with multiple brands or locations, a multilingual setup with one site per language, or an organization with departmental sites. A single update cycle, shared themes and plugins, and users who can access multiple sites with a single account—that’s where the benefits lie.
When multisite is a bad choice: an agency’s standalone client sites. All sites in a network share the same database and the same files. That means: if the network goes down, all sites go down. If a single client wants to leave, separating their site from the network is a major migration task. And not every plugin works well within multisite. Our opinion, based on what we see with clients: if you’re managing sites for different owners, opt for standalone installations on a good hosting plan. Multisite is for sites that are operated and managed as a single entity.
First things first: two choices and one safety net
You make your initial choice during installation, and that choice is set in stone afterward: will new sites on the network be assigned a subdomain (site1.yourdomain.nl) or a subfolder (yourdomain.nl/site1)? Subfolders are technically the simplest; subdomains look more independent but require a so-called wildcard setting in your DNS (your domain’s address book). If you want completely separate domain names for each site later on, you can do so with domain mapping: for example, you can link brand-a.nl to site 1 in the network. You configure this per site in the network management settings, though each linked domain must point to your hosting and requires its own SSL certificate.
The safety net: Make a complete backup of your files and database before you begin. The switch to multisite will change your wp-config.php, your .htaccess, and your database structure; with a backup, every step is reversible. You can read how to create one in our A Complete Guide to WordPress Backups and Migration.
At Surver: every website comes with an SSL certificate as standard, and our managed packages include daily automatic backups. If you have any questions about the DNS settings for subdomains, please contact our support team; they’re available seven days a week.
Enabling Multisite, Step by Step
- Open wp-config.php using the file manager in your hosting control panel and add the following line above the line that says “stop editing”: define(‘WP_ALLOW_MULTISITE’, true);
- Reload your dashboard. Under "Extras," you'll now see the new "Network Setup" section.
- First, deactivate all your plugins (WordPress explicitly asks you to do this here), select subdomains or subfolders, and click Install.
- WordPress now displays two code blocks: one for wp-config.php and one for .htaccess. Paste both into the specified locations in those files and save.
- Log in again. At the top of the toolbar, you'll now see "My Sites," with "Network Management" below it: the new top-level menu from which you manage the network.
- Reactivate your plugins—this time, either on a per-site basis or network-wide (more on that below)—and create your first additional site through Network Administration.
How Your Administration Will Change: Roles, Plugins, and Updates
Multisite introduces a new role above the familiar administrator: the super administrator (super admin). Only the super administrator can install themes and plugins, create sites, and manage the network. The administrators of the individual sites can only activate what the super admin makes available and manage content on their own site. That’s exactly what makes it so powerful for organizations: a department can populate its own site without ever risking any technical issues.
You install plugins and themes once at the network level. After that, for each plugin, you choose whether to activate it network-wide (active on all sites—useful for your caching and security plugins) or make it available so that sites can activate it themselves. You run updates once for the entire network, and that’s where you save a lot of time. The downside: a single bad plugin update immediately affects all your sites. So, with multisite, the safe update routine—which includes a backup beforehand and a check afterward—is even more critical than it is for a single site.
At Surver: With our managed packages, we handle the updates—including a compatibility check beforehand—and scan for malware. Especially in a network, where a single problem can affect all sites, that safety net is invaluable.
The restrictions you need to be aware of in advance
Three issues network administrators encounter in practice. Backups and migrations are more complex: all sites share a single database, so restoring or moving a single site requires more specialized work than with standalone installations. Plugin compatibility: most major plugins support multisite well, but check each plugin beforehand, especially for online stores and member-only areas. And resources: all sites share the processing power of a single hosting environment, so a spike on one busy site affects the entire network. As your network grows, be sure to scale up your hosting plan in a timely manner.
Is this your route?
In summary: Multisite is an excellent tool for a cohesive family of sites under a single administrator, but it’s the wrong choice for separate sites owned by different people. If you’re still unsure about your setup, start by building one site properly using our A Beginner's Guide to Creating a Website with WordPress; you can always expand to a network later. And before making the switch, learn more about what managing WordPress entails through our A Complete Guide to WordPress Management, because with multisite, you'll now manage all sites at once.
