WordPress Multisite Explained: When to Use It and How to Set It Up

WordPress Multisite lets you run many websites from one WordPress installation, sharing the same core files, plugins and themes and managed from a single Network Admin dashboard. It suits organizations with many similar sites, such as a university with department sites, a franchise with one site per location, or an agency hosting many small client sites on a common setup. It is the wrong choice when sites need different plugins, different hosting or independent ownership, because every site in the network shares one database and one set of code. You enable it by adding define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php, after a full backup.

This guide explains how Multisite works, when to use it and when not to, how to set it up, and the limitations worth knowing before you commit.

How Multisite works

A normal WordPress install is one site. A Multisite network is one install that hosts many sites.

According to WordPress's documentation, sites in a network share the same core files and can share plugins and themes. Each site can activate plugins and themes, but individual sites cannot install them. Only the network's Super Admin can.

Roles in a network

This split is one of Multisite's main strengths. You can give a branch manager control of their own site without letting them install a plugin that affects the whole network.

Subdomains or subdirectories

When you create a network, you choose how site addresses work. WordPress calls these domain-based and path-based networks.

WordPress's documentation says your existing settings may restrict this choice, and that switching later "might not be easy". Decide before you build.

You can also map completely separate domains to sites in a network, such as chicagobakery.com for one site, using the site's address setting and a DNS record for each domain. Each mapped domain also needs an SSL certificate.

Which is better for SEO?

Search engines can rank both. Subdirectories keep all content under one domain, so every site benefits from links to the main domain. Subdomains behave a little more like separate sites. For location or department sites under one brand, subdirectories are usually the simpler choice. Internal Linking: How to Connect Your Pages covers how linking between related sites helps.

When Multisite is a good fit

The common thread: many sites that are similar in code and design, managed by one technical owner.

For multilingual setups, each language site still needs hreflang to tell search engines which version is for which audience. Hreflang Explained covers it.

When to avoid Multisite

The ownership point catches agencies out. If a client leaves and wants their site, you have to export it from the network into a standalone install. It is possible, but it is a migration project, not a button.

Plugin compatibility

Most popular plugins work on Multisite, but not all. Some need network activation, some only work per site, and some do not support it at all. Check each plugin's documentation before you rely on it. Backup, caching, security and SEO plugins in particular need to be Multisite-aware.

How to set up a Multisite network

Before you start

1. Take a full backup of the files and database. WordPress's documentation recommends backing up the database and files before enabling Multisite, and backing up wp-config.php and .htaccess too unless it is a fresh install. How to Back Up a WordPress Site covers how.
2. Use a staging copy for your first attempt if you are converting an existing site. How to Create a WordPress Staging Site explains how.
3. Check that permalinks work on the existing site.
4. Deactivate all plugins. WordPress's documentation advises deactivating them before creating the network and reactivating them afterward.

Step 1: Allow Multisite

Open wp-config.php and add this line above the one that says "That's all, stop editing!":

define( 'WP_ALLOW_MULTISITE', true );

Save the file and refresh your WordPress dashboard. A new Network Setup item appears under the Tools menu.

Step 2: Run Network Setup

1. Go to Tools, Network Setup.
2. Choose Sub-domains or Sub-directories, if WordPress offers the choice.
3. Enter the network title and the Network Admin email address.
4. Click Install.

Step 3: Add the configuration WordPress gives you

WordPress then shows two blocks of code.

The first goes in wp-config.php, below the line you added earlier. It looks like this, with your own domain:

define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', false );
define( 'DOMAIN_CURRENT_SITE', 'example.com' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );

The second replaces the WordPress rules in your .htaccess file on Apache. On Nginx, you need equivalent rewrite rules in the server block instead, since Nginx ignores .htaccess. Nginx vs Apache explains that difference.

Copy the code exactly as WordPress shows it for your site, rather than from a guide, since the values depend on your setup.

Step 4: Log in again

Save both files and log in again. You now have a My Sites, Network Admin menu with its own dashboard.

Step 5: Configure the network

In Network Admin, Settings, decide whether users can register and whether they can create their own sites. WordPress's documentation notes you can allow end users to create sites on demand, or restrict site creation to yourself. For most business networks, keep site creation to Super Admins.

Step 6: Add sites, plugins and themes

• Sites: Network Admin, Sites, Add New.
• Plugins: install under Network Admin, Plugins. Choose Network Activate to enable a plugin on every site, or leave it available for site administrators to activate individually.
• Themes: install under Network Admin, Themes, then Network Enable the themes each site may use.

Reactivate the plugins you deactivated before setup, checking each one works.

Running a network day to day

Updates

One update covers every site, which saves a lot of time. It also means one bad update affects every site at once. Test updates on a staging copy of the network before applying them to production.

Backups

Back up the whole network, files and the shared database together. Use a backup tool that supports Multisite, and check whether it can restore a single site or only the whole network. Restoring one site from a whole-network backup is harder than restoring a single install.

Security

A compromised plugin or a weak Super Admin password exposes every site. Limit Super Admin accounts to the people who truly need them, require two-factor authentication for them, and follow the rest of the WordPress security checklist.

Performance

All sites share one database and server. As the network grows, add page caching, an object cache, and enough server resources for the combined traffic. Watch for one site's traffic affecting the others. Why Is My WordPress Site Slow? covers caching, and Shared vs VPS vs Cloud Hosting covers when to move up.

Hosting

Some shared hosting plans do not support Multisite, or limit it. Check before you start. Managed WordPress hosts vary too, and some charge per site in the network. Best WordPress Hosting for Beginners compares the main plans.

Taking a site out of a network

If a site needs to leave, the general process is:

1. Export the site's content with Tools, Export, which produces an XML file of posts, pages and comments.
2. Create a new single WordPress install.
3. Import the XML file and copy the site's uploads folder.
4. Install the plugins and theme it used and recreate its settings.
5. Set up redirects if the address changes.

Dedicated migration tools can move a single site out of a network with more of its settings intact. Either way, plan for a few hours per site. How to Migrate a WordPress Site to a New Host covers the hosting side.

Alternatives to Multisite

For agencies, a management dashboard often gives most of the convenience of Multisite while keeping each client's site separate, which makes it far easier when clients come and go.

Frequently asked questions

What is WordPress Multisite?

WordPress Multisite is a built-in feature that lets one WordPress installation run a network of many websites. The sites share core files, plugins and themes, and a Super Admin manages them from a Network Admin dashboard while each site keeps its own content and settings.

How do I enable WordPress Multisite?

Back up your site, deactivate plugins, add define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php, then go to Tools, Network Setup. Choose subdomains or subdirectories, click Install, and add the code WordPress provides to wp-config.php and .htaccess.

Should I use subdomains or subdirectories for Multisite?

Subdirectories, such as example.com/chicago, need no extra DNS and keep all content under one domain. Subdomains, such as chicago.example.com, need wildcard DNS for on-demand sites. WordPress warns that switching later might not be easy, so choose before building.

Can each site in a network have its own plugins?

Each site can activate plugins, but only the Super Admin can install them. Plugins are installed once for the whole network and either network-activated for every site or made available for individual sites to activate.

Is WordPress Multisite good for agencies?

It can be for many similar client sites on one platform, since one update covers all of them. It is less suitable when clients need different plugins or may leave, because separating a site from a network is a migration project. Management dashboards are a common alternative.

Does Multisite affect SEO?

Not by itself. Each site can rank normally. Subdirectory networks keep content under one domain, which can help sites benefit from the main domain's links. Each site still needs unique content, correct canonical tags and, for multilingual networks, hreflang.

What are the downsides of WordPress Multisite?

All sites share one database, codebase and server, so a bad plugin update, a security issue or a traffic spike can affect every site. Some plugins do not support Multisite, some hosts limit it, and moving a single site out of the network takes work.

Sources

• WordPress.org: Create a network
• WordPress.org: Multisite administration
• WordPress.org: Roles and capabilities
• WordPress.org server requirements