How to Enable and Configure WordPress Multisite

What WordPress Multisite is

WordPress Multisite lets you manage a network of sites from a single WordPress install. Every site shares the core files, the theme and plugin installs, one database (though each site uses its own tables), one network admin area, and one superadmin user. Each site can still have its own content, settings, users, and media files.

Multisite is different from multi-domain hosting, which lets you host several independent domains on the same hosting account without sharing a WordPress install — here we’re talking about the network feature built into WordPress itself.

It’s useful for networks of branches, chapters, brands, education projects, franchises, or related sites that need centralized management.

When Multisite isn’t the right choice

It’s not the best option when the sites are unrelated, need different versions of WordPress, PHP, or plugins, each client needs full, independent control of the server, you want to isolate security risks between projects, an essential plugin isn’t Multisite-compatible, or each site needs a fully separate database.

Multisite simplifies some tasks, but it also creates dependency: a failure in the core, the server, or a network-activated plugin can affect several sites at once.

Before enabling Multisite

Take a full backup of the files and database (see WordPress backup and restore), update WordPress, plugins, and themes, confirm permalinks work, deactivate all plugins, verify you have access to wp-config.php and .htaccess, decide between subdomains and subfolders, and check that your essential plugins are compatible.

Choosing between subdomains and subfolders

Subdomain-based network (site1.yourdomain.com): creating subdomains on demand usually requires a wildcard DNS record (*.yourdomain.com) pointing to the right server, and the SSL certificate needs to cover those subdomains.

Subfolder-based network (yourdomain.com/site1/): usually simpler since it doesn’t need a wildcard DNS record, though it shares the main domain’s path structure.

Changing the network type later is possible, but can require complex changes, so choose carefully from the start.

Step 1: allow Multisite configuration

Open wp-config.php and add this line before the final comment:

/* Multisite */
define( 'WP_ALLOW_MULTISITE', true );

Step 2: open the network setup

Go to Tools > Network Setup, choose subdomains or subfolders, enter the network title, confirm the network admin email, and click Install. WordPress will generate instructions specific to your domain — use exactly the code shown on your screen.

Step 3: add the configuration to wp-config.php

WordPress will show a block similar to this:

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

Copy it into the position the wizard indicates. Don’t copy values from another site — they need to match your own network.

Step 4: add the server rules

On Apache, WordPress will show rules for .htaccess — back up the file and replace the existing WordPress rules with the new ones. On Nginx, which doesn’t use .htaccess, you’ll need to add the corresponding rules to the server configuration or ask your administrator. If you use a proxy or CDN, check that it recognizes every domain or path in the network.

Step 5: log back in

Log out, clear the domain’s cookies if you hit a loop, and log in again. My Sites > Network Admin should appear in the top bar.

Step 6: set up DNS for subdomains

This is only needed for on-demand subdomain-based networks. Create a wildcard A record (* pointing to the server’s IP) or a CNAME, depending on the service’s architecture. The main domain must point correctly, the server must accept *.yourdomain.com, and SSL must cover the subdomains.

Step 7: create a site on the network

Go to Network Admin > Sites > Add New, enter the site’s address, a title, and the admin’s email, and click Add Site.

How plugins and themes work

Only the superadmin can install plugins. You can network-activate them (they stay active on every site and local admins can’t deactivate them), leave them available (each site can activate them if the network allows it), or deactivate them. Don’t network-activate a plugin without testing it first — a bug can affect every site.

The superadmin installs themes and decides which ones are enabled for the network or for specific sites; each site’s admin can activate the enabled ones, but can’t install others.

Users and roles

A user account can belong to one or several sites. The superadmin controls the whole network; a site admin manages one specific site with fewer privileges than on a standalone install; editor, author, contributor, and subscriber work within each site. Only grant the superadmin role to people you fully trust.

Important network settings

Under Network Admin > Settings, review user and site registration, welcome emails, allowed file types, the maximum upload size per site, and the site-creation policy. Don’t set limits higher than what PHP or your hosting allows.

Custom domains on Multisite

WordPress lets you map different domains to network sites in modern setups. Before doing so, add the domain to your hosting, configure its DNS, activate SSL, edit the site’s address from the network admin area, and check cookies, redirects, and caching (see how to change the WordPress URL).

Backups on Multisite

A backup needs to include every file, the entire database, wp-config.php, .htaccess, the media files from every site, and the DNS configuration documented separately. Restoring a single site within a network is more complex than restoring a standalone install, since users and some tables are shared — test the procedure before you actually need it.

Common issues

”Network Setup” doesn’t appear

Check that WP_ALLOW_MULTISITE is defined correctly, that you saved wp-config.php, and that you have admin permissions.

Subdomains don’t load

Check the wildcard DNS, the virtual host, SSL, and propagation.

There’s a login loop

Check HTTPS, the domain, cookies, any reverse proxy, and DOMAIN_CURRENT_SITE. Clear caches and cookies.

A plugin works on a regular site, but not on Multisite

Not every plugin is compatible with networks or global activation. Check its documentation and test in staging.

Frequently asked questions

Does every site have a different database?

They usually share one database, but each site has several tables of its own. Some tables, like users, are shared across the network.

Can I convert an existing site into Multisite?

Yes, but you need a full backup, a review of your plugins, and a carefully chosen structure.

Does Multisite use fewer resources?

It can reduce file duplication and simplify updates, but each site still generates its own queries, visits, and tasks.

Do I need a VPS?

Not always. A small network can run on compatible hosting, but networks with many sites or heavy traffic may need extra resources.

Conclusion

WordPress Multisite centralizes management of several related sites, but it requires planning around DNS, SSL, plugins, backups, and resources. Only enable it after choosing between subdomains and subfolders, taking a full backup, and checking compatibility.