How to Create a WordPress Multisite Network (2026 Guide)

Create WordPress multisite network — developer workspace with laptop and monitor showing a network of connected websites

If you run more than one WordPress site, you already know the pain: separate logins, separate plugin updates, and separate backups for every site. A WordPress multisite network fixes that by running many sites from one WordPress installation — one dashboard, one set of plugins and themes, and one update cycle. In this guide, you will learn how to create a WordPress multisite network step by step, and avoid the mistakes that break a network on day one.

What Is a WordPress Multisite Network?

Multisite is a built-in WordPress feature — part of core since WordPress 3.0 — that turns a standard single-site installation into a network of sites. All the sites share the same core files, database, and installed plugins and themes. Each site still keeps its own content, media library, settings, and user roles.

The best-known example is WordPress.com, which runs on Multisite. Universities run one site per department, franchises run one per location, and agencies run one per client — all managed from a Network Admin dashboard by a Super Admin, a role above the regular Administrator on every site. Multisite is not a plugin: there is nothing to install. You switch it on with a line of code, and WordPress walks you through the rest.

When Multisite Makes Sense — and When It Does Not

Multisite is the right call when your sites are related enough to share infrastructure: departments or branches of one organisation sharing the same brand and theme; regional or language versions of the same site; client sites built on the same stack, where you update one plugin once instead of twenty times; and networks of blogs where users hold different roles on different sites.

It is the wrong call when your sites have nothing in common: different plugin versions per site, heavy traffic spikes on one site, or different owners who should never see each other’s dashboards.

Before You Start: The Pre-Flight Checklist

Enabling Multisite rewrites wp-config.php and your rewrite rules, and there is no undo button — so prepare properly. If this is a live site you cannot afford to break, do the first run on a copy; my guide to setting up a WordPress staging site shows how.

  1. Take a full backup of your files and database, and confirm you can restore it. See my guide on how to back up your WordPress site if you do not have a backup routine yet.
  2. Check that pretty permalinks work. Go to Settings > Permalinks and make sure the structure is anything except Plain — Multisite depends on rewrite rules.
  3. Deactivate all plugins so a plugin conflict cannot lock you out mid-install. Reactivate them afterwards.
  4. Decide your URL structure now. You pick subdomains or subdirectories during setup, and changing it later means editing constants, rewrite rules, DNS, SSL, and every site URL by hand. The official Before You Create a Network doc lists the same checks.
  5. Confirm you have file access — SFTP or your host’s file manager — to edit wp-config.php and .htaccess directly.
  6. Make sure SSL is already working on the main domain. Fixing HTTPS after the network exists is harder than fixing it first.

How to Create a WordPress Multisite Network

With the checklist done, the setup takes about fifteen minutes on a clean install. Follow the steps in order.

Step 1: Enable Multisite in wp-config.php

Open wp-config.php in your site’s root folder and add this line directly above the comment that says “That’s all, stop editing!”:

define( 'WP_ALLOW_MULTISITE', true );

Save the file and refresh your dashboard. A new menu item appears under Tools > Network Setup. If it does not appear, clear your cache and check the line is above the “stop editing” comment — anything below it is ignored.

Step 2: Open Tools > Network Setup

Go to Tools > Network Setup, choose subdomains or subdirectories, enter a network title and the network admin email, then click Install.

Two things can surprise you here. The subdirectory option is missing if your site has any published post older than a month — WordPress hides it because existing post URLs could clash with new site paths. And the subdomain option is unavailable if your site address contains a path, uses localhost or an IP address, or runs on a port other than 80 or 443.

Step 3: Add the Generated Code to wp-config.php and .htaccess

After you click Install, WordPress shows two blocks of code. The first goes into wp-config.php, below the WP_ALLOW_MULTISITE line:

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 block replaces your existing .htaccess rewrite rules. Copy both blocks exactly as shown — a typo here will take the whole site down, which is why you made that backup. On Nginx there is no .htaccess file, so the same rules go into your server block configuration instead. One quirk: in a subdirectory network, your main site’s posts get a /blog/ prefix so post URLs can never clash with subsite paths. The official Create a Network documentation shows the same two code blocks.

Step 4: Log Back In and Open the Network Admin

Log out and log back in. You will see a new My Sites menu in the admin bar, and a Network Admin dashboard at yourdomain.com/wp-admin/network/ — the control room for the whole network.

Step 5: Set Up Wildcard DNS and SSL (Subdomain Networks Only)

If you chose subdomains, each subsite lives at an address like shop.example.com. Add a wildcard DNS record — an A record with the name * pointing at your server’s IP — and a wildcard SSL certificate (*.example.com) so every future subsite is covered by HTTPS. If your DNS runs through Cloudflare, add the wildcard record there — see my Cloudflare setup guide.

Step 6: Create Your First Subsite

Go to Network Admin > Sites > Add New, fill in the site address (the subdomain or subdirectory slug), the site title, and the admin email, then click Add Site. Visit the new address — your network is live.

Subdomains vs Subdirectories: Which Should You Pick?

This is the one decision you cannot easily reverse, so weigh it before you click Install. Subdirectories (example.com/site1/) are simpler — no DNS or SSL changes — and all sites share the main domain’s authority, which helps smaller sites rank. Subdomains (site1.example.com) give each site a stronger identity in the address bar, but they need wildcard DNS and a wildcard SSL certificate, and Google treats each subdomain as a separate site.

When in doubt, pick subdirectories. Choose subdomains only when each site genuinely needs its own identity — a publication, a franchise location, or a distinct brand.

Managing Your Network Day to Day

  • Plugins are installed once, network-wide. A Super Admin installs a plugin, then either network-activates it for every site or lets each site’s admin activate it individually. You cannot run two versions of the same plugin on different sites.
  • Themes work the same way. The Super Admin enables themes for the network, and each site picks its own from the enabled list. See my guide to creating a custom WordPress theme — one theme, many sites, is where Multisite pays off.
  • Users are shared across the network. One account can be an Administrator on one site and an Editor on another. Only Super Admins can add users to the network itself.
  • Updates happen once. Update WordPress core or a plugin in the Network Admin and every site gets it at the same time — the biggest time saving Multisite offers, and the biggest risk, so test updates on staging first.

Domain Mapping: Give a Subsite Its Own Domain

A subsite does not have to keep its network address. Since WordPress 4.5, domain mapping is built into core — no plugin required. Point the domain’s DNS at your server, install an SSL certificate for it, then change the site’s address under Network Admin > Sites > Edit. The subsite then runs entirely on its own domain while still being managed from your network.

Common Multisite Problems and Fixes

  • Network Setup does not appear: the WP_ALLOW_MULTISITE line is missing, saved in the wrong place, or cached. Check it sits above the “stop editing” comment and purge your cache.
  • The subdirectory option is missing: your site has a published post older than a month. Use a fresh install, or accept subdomains.
  • Subsites return 404 errors: the .htaccess rules were not replaced, or permalinks were set to Plain. Re-apply the generated rules and check Settings > Permalinks.

Final Thoughts

Learning how to create a WordPress multisite network is a small investment that pays off every time you add a site. One installation, one update cycle, and one dashboard for the whole network — that is the whole point. Just respect the two rules that cause most failures: back up before you touch wp-config.php, and decide on subdomains or subdirectories before you click Install.

Need help setting up a WordPress multisite network? I build and manage WordPress sites for clients — get in touch through my contact page.