WordPress can run more than one website from a single installation, and many site owners only discover this when they already manage five or six separate sites and wonder whether there is an easier way. The feature is called WordPress Multisite, and it has been part of WordPress core since version 3.0. It powers university networks, media groups, franchise brands and the largest WordPress network of all, WordPress.com.
It is also one of the most misunderstood features in WordPress. Multisite can save a lot of time when the sites belong together, and it can create real problems when they do not. This guide explains how a network actually works, which setups suit which projects, why agencies should usually keep client sites apart, what Multisite means for hosting, backups and security, how to enable it correctly and how to get a site back out of a network if you need to.
What WordPress Multisite Actually Is
A Multisite network is one WordPress installation that serves many sites. All sites share the same WordPress core files, the same plugins and themes folder, and the same database. Each site gets its own content, settings and media, but the code underneath is common. The official Multisite documentation describes it as a way to create a network of virtual sites from one install.
Inside the database, each new site gets its own set of tables with a numbered prefix, such as wp_2_posts and wp_2_options, while network-wide tables track the sites themselves. Users are shared across the network: there is one users table, and a single person can hold different roles on different sites. Media for each site lives in its own folder under wp-content/uploads/sites/, so files stay separate even though the code does not.
The network adds a new role above Administrator, called Super Admin. The roles and capabilities page explains the split: Super Admins manage the whole network, including installing plugins and themes and creating sites, while site administrators manage only their own site. On a network, regular administrators cannot install plugins or themes at all, and they lose the ability to post unfiltered HTML. Those limits are deliberate, because anything installed affects every site.
Super Admins work from a separate dashboard, the Network Admin screen, where they add sites, manage users, enable themes and network-activate plugins. Once you see Multisite as “one shared codebase, many separate content stores,” most of its strengths and weaknesses follow naturally, starting with how the sites are addressed.
Subdomains, Subdirectories and Mapped Domains
Every network has to choose how its sites appear in the browser, and the choice is made during setup. A subdirectory network puts sites on paths, such as example.com/paris/, while a subdomain network uses addresses such as paris.example.com. On top of either, each site can be given its own mapped domain, such as example-paris.com, which WordPress has supported natively since version 4.5.
| Setup | Example Address | DNS and SSL Needs | Best For |
|---|---|---|---|
| Subdirectory | example.com/paris/ | Nothing extra, one certificate covers all sites | Brands that want everything on one domain |
| Subdomain | paris.example.com | Wildcard DNS for on-demand sites, wildcard or per-site certificates | Departments or locations that feel like separate sites |
| Mapped domain | example-paris.com | DNS for each domain, a certificate for each domain | Sites that need their own brand and domain |
The official guide to preparing a network lists a few restrictions worth knowing before you commit. A subdirectory network is not available if the existing site has been live for more than a month, because of possible permalink clashes, and the main site’s posts get a /blog/ prefix in their URLs. Subdomain networks cannot run on localhost or a bare IP address, and WordPress should sit in the web root. Changing the network type later is possible but not simple.
If the sites will each have their own domains anyway, the subdomain or subdirectory choice matters less, and the domain mapping documentation explains how to point each one at its site. With addressing settled, the bigger question is whether your project should be a network at all.
When Multisite Is the Right Choice
Multisite shines when many sites share the same people, the same design system and the same set of plugins, and when one team is responsible for all of them. In those cases, updating once instead of fifty times is a real saving, and new sites can be launched in minutes from a consistent starting point.
The strongest real-world fits share that pattern:
- Universities and schools, where each department, faculty or research group gets a site with a common theme, shared logins and central control by the web team.
- Franchises and multi-location businesses, where each location needs its own pages, staff and local content, while the brand team controls design and plugins.
- Media groups and publishers running several related titles or language editions with the same editorial workflow.
- Company intranets and internal portals, where teams need separate spaces but the same users and security rules.
- Platform-style services that give many users a site from a template, the same model WordPress.com is built on.
In each of these, the sites belong to one organization with one technical owner, and they are meant to stay together. If a site might need its own plugins, its own developer or its own future, that is a warning sign, and it is exactly the situation most agencies are in.
Why Agencies Should Usually Keep Client Sites Separate
It is tempting for an agency with dozens of client sites to put them all into one network and update everything in one click. In practice, it usually trades a small amount of saved update time for a large amount of shared risk, and it creates problems that only appear later, often at the worst moment.
The first problem is shared fate. Every client runs the same plugin versions, so a bad update or a vulnerable plugin hits every client at once. A security breach on one site can reach the shared database and files of all the others. One client’s traffic spike or heavy import slows everyone, because they share the same server resources and the same database.
The second problem is independence. Client A wants a booking plugin, client B needs a specific WooCommerce extension, and client C has a developer who wants to deploy custom code. In a network, every plugin is installed for everyone, so each request becomes a network-wide decision.
The third problem appears at the end of the relationship. When a client leaves, they will want their site as a normal WordPress install, with their content, media, users and settings. Extracting one site from a network is real work, which we cover later in this guide, and doing it under deadline for a departing client is not where an agency wants to spend unbilled hours.
The better pattern for agencies is one site per installation, ideally with isolated hosting per site, and a management layer that handles updates, backups and monitoring across all of them. That keeps the time savings without tying every client’s risk together. Multisite still has a place inside an agency, for example for one client who runs a network of related sites, but that network should belong to that client alone.
Pros and Cons at a Glance
By now the trade-offs are fairly clear, but it helps to see them side by side. The same shared design that makes Multisite efficient is what makes it risky when sites do not belong together.
| Pros | Cons |
|---|---|
| One core, plugin and theme update covers every site | One bad update or vulnerability affects every site |
| Shared users, one login across sites | Users table is shared, so account mistakes spread |
| Fast launch of new sites from a consistent setup | Site admins cannot install their own plugins or themes |
| Less disk space for duplicated code | Shared database and server resources between sites |
| Central control of design and functionality | Per-site backups, restores and migrations are harder |
| Ideal for one organization with many sites | Some plugins are not built or tested for networks |
If most of the left column matters to you and most of the right column does not, Multisite is likely a good fit. If the right column describes your situation, separate installations will be easier to live with, which brings us to one of the most common practical issues, plugins.
Plugin and Theme Compatibility
Most popular plugins work on a network, but “works” can mean different things. Some plugins are network-aware, with settings at the network level and per-site options where they make sense. Others were built for single sites and behave unexpectedly when activated network-wide, for example by storing settings in the wrong place, creating tables only for the main site or showing licensing screens on every site.
Themes are simpler: a Super Admin enables a theme for the network, and each site can then activate any enabled theme. Plugins can be network-activated, which runs them on every site, or left for individual site admins to activate.
Before adding a plugin to a network, check its documentation and support forum for Multisite mentions, test it on a staging copy of the network, and activate it on one site before network-activating it. A WordPress staging site is even more valuable here than on a single install, because a bad update reaches every site at once. Update in small batches and check a few representative sites after each batch, not only the main site.
Performance and Hosting Needs
A network is one application with one database, so its hosting must be sized for the whole network, not for the average site. Every site’s visitors, admin users, cron jobs and searches hit the same PHP workers and the same database. A busy network needs more memory and CPU, a well-tuned database, page caching that understands multiple domains, and an object cache helps keep shared queries fast.
Server configuration matters too. Multisite needs URL rewriting through .htaccess or equivalent Nginx rules, subdomain networks need wildcard DNS and suitable SSL certificates, and many budget shared plans either limit Multisite or do not support it at all. Check with your host before you enable it. A managed WordPress hosting environment with isolated resources removes most of these questions, because the server is not shared with unrelated accounts and can be tuned for the network.
Backups, Restores and the Security Blast Radius
Backups are where many network owners get surprised. Most backup tools treat a network as one site: one set of files and one database. That is fine after a full server failure, but the common request is narrower, such as “restore the Paris location’s site to last Tuesday without touching the other forty.” That means pulling out only that site’s tables and uploads folder and importing them without overwriting the other sites or the shared users table. It can be done, but it is not a one-click restore.
Plan for it before you need it. Keep offsite backups of files, database and configuration, write down how a single-site restore works for your network, and test it once on staging. A restore process that has never been tried is a hope, not a plan.
Security follows the same logic. The blast radius is how much damage one compromise can do. On a single site, a vulnerable plugin exposes one site. On a network, the same plugin runs everywhere, the database is shared and Super Admin accounts control every site, so one weak Super Admin password is effectively a key to the entire network.
That does not make Multisite insecure, but it changes how you protect it. Keep the number of Super Admins small, require two-factor authentication for all of them, install only plugins you need and remove anything abandoned quickly. Server-level filtering that stops malicious requests before WordPress loads is especially valuable, because it protects every site at once. And accept that a security incident on a network is a network incident: cleanup has to cover shared code, every site’s content and the shared users table.
How to Enable Multisite on a WordPress Site
If Multisite still fits after all of that, enabling it is a short, well-documented process. The official steps to create a network work on any host that supports URL rewriting, and the key is preparing properly rather than rushing into wp-config.php.
- Take a full backup of files and database, and ideally do this first on a staging copy.
- Confirm pretty permalinks work, and deactivate all plugins.
- Open wp-config.php and add `define( ‘WP_ALLOW_MULTISITE’, true );` above the line that says “That’s all, stop editing!”
- Reload the dashboard and go to Tools, then Network Setup. Choose subdomains or subdirectories, set the network title and admin email, and click Install.
- Copy the generated lines into wp-config.php and replace the WordPress rules in .htaccess with the new ones shown on screen, keeping backups of both files.
- Log in again, open My Sites, then Network Admin, and reactivate plugins one at a time.
The WP_ALLOW_MULTISITE line only unlocks the Network Setup screen. The real switch is the block of constants WordPress gives you in step 5, including `MULTISITE` and `SUBDOMAIN_INSTALL`. After that, test logins, permalinks and media uploads on the main site and on a new test site before you build anything real on the network.
How to Split a Site Out of a Network
Sooner or later, a site may need to leave: a franchise location is sold, a department moves to its own platform or a client relationship ends. WordPress has no built-in “detach site” button, so splitting a site out means building a standalone install from that site’s parts. Doing it carefully avoids broken links, lost media and missing users.
The usual process looks like this:
- Set up a fresh single-site install on the destination hosting, ideally on staging first.
- Export that site’s tables, the ones with its numbered prefix such as wp_5_, and rename them to the standard prefix of the new install.
- Copy its media from wp-content/uploads/sites/5/ into the new uploads folder.
- Recreate the users who belong to that site, because users live in the shared network tables and are not part of the site’s own tables.
- Install the same theme and plugins the site used, then run a search and replace on URLs and upload paths, for example with WP-CLI search-replace.
- Point the domain to the new server and add 301 redirects if any URLs change.
For smaller sites, exporting content with the built-in WordPress exporter and importing it into a new install can be simpler, though it does not carry over settings, widgets or every plugin’s data. If the address changes, follow Google’s guidance on site moves with URL changes so rankings carry over. Our guide on how to migrate a WordPress site covers testing and DNS switching without downtime.
How Webueno Handles WordPress Multisite
Webueno hosting runs one site per DigitalOcean VPS, so a network gets a server of its own rather than sharing resources with unrelated accounts. Staging and live run on the same server, which makes it practical to test plugin updates against a full copy of the network before they reach every site, and the PHP version is set per hosted site, so a network can stay on the version its plugins support without affecting anything else.
For security, The Gatekeeper filters requests at the server before PHP runs, which protects every site in a network at the same layer. On one site it stopped about 17,000 attacks in 23 days, with 33.9% of all requests stopped before PHP ran. Its scanner also checks inside zip files, and Sentinel AI explains threats in a way you can act on. If something does get through, our malware cleanup service handles the recovery.
Optional add-ons are chosen per site. Daily offsite backups cover files, database and configuration, uptime monitoring checks every 3 minutes and alerts after 3 failed pings, and maintenance plans cost $10 per site for Monthly, $20 for Weekly and $60 for Daily. Hands-on work, such as enabling a network, auditing plugins for Multisite compatibility or splitting a site out of a network, is done through tickets in the Webueno platform with tracked time. It is billed in credits at $42, where 1 credit equals 1 hour, and bundles save up to 21%, bringing the rate to $33.18 an hour, with no contracts.
For agencies, we usually recommend keeping each client on its own site and server, and managing them all through a white-label agency account where you set your own margin. That gives you central management without the shared risk of putting different clients into one network.
Choosing Between a Network and Separate Sites
WordPress Multisite is an excellent tool for one organization running many related sites with the same people, design and plugins. Universities, franchises, publishers and intranets get real value from it. It is a poor fit for unrelated sites with different owners, which is why agencies usually do better with separate installs and good central management. Whichever way you go, plan hosting, per-site restores and security for the setup you actually choose, and know how a site would leave before you add it.
If you want help deciding, setting up a network on isolated hosting or moving a site out of one, create your Webueno account and open a ticket. We will look at your sites and tell you honestly which setup fits.
Frequently Asked Questions
What Is WordPress Multisite Used For?
It runs many websites from one WordPress installation with shared core files, plugins, themes and users. Common uses include university departments, franchise locations, publisher networks, intranets and platforms that give users their own site.
Is WordPress Multisite Good for Agencies Hosting Client Sites?
Usually not. Client sites in one network share plugins, the database and server resources, so one bad update or breach affects all clients, and handing a site back to a departing client is real work. Separate installs with central management are safer.
Should I Choose Subdomains or Subdirectories?
Choose subdirectories if you want everything under one domain with one SSL certificate. Choose subdomains when sites should feel separate, keeping in mind that they need wildcard DNS and suitable certificates. Either can use mapped custom domains.
Can I Turn Off Multisite After Enabling It?
There is no simple off switch. Removing the network constants only makes sense while the network has a single site. Once other sites exist, each one has to be moved into a standalone installation, so test Multisite on staging before committing.
Do All WordPress Plugins Work on Multisite?
Most popular plugins do, but not all are built for networks. Some store settings incorrectly or behave oddly when network-activated. Check the documentation, test on staging and activate on one site first.
How Do I Back Up a Single Site in a Multisite Network?
Back up that site’s database tables, which share a numbered prefix, along with its uploads folder. Many backup tools only back up the whole network, so confirm per-site export and restore works before you need it.