WordPress Multisite: When You Need It and How to Set It Up

WordPress Multisite lets you run dozens — or hundreds — of websites from a single WordPress installation. One login. One set of core files. One hosting bill. If you’re managing multiple sites and manually updating the same plugins across ten different dashboards, that’s not workflow. That’s punishment.

This guide shows you exactly how to create a WordPress Multisite network from scratch, covers the real gotchas nobody else warns you about, and tells you honestly when Multisite is the wrong tool for the job.

What Is WordPress Multisite (And Why Most People Never Need It)

WordPress Multisite is a network architecture baked into WordPress core since version 3.0. It lets one WordPress installation host multiple websites — each with its own URL, content, users, and settings — while sharing the same codebase, plugin files, and database.

Originally built to power WordPress.com’s infrastructure, it was folded into self-hosted WordPress so enterprises, universities, and agencies could replicate that scale. Harvard, BBC America, and The New Yorker have all run on WordPress Multisite. These are not small operations.

But here’s what the cheerleader posts won’t tell you: Multisite is a force multiplier, not a convenience feature. It solves specific organizational problems at scale. It is not the answer to “I have two websites and updating them separately is annoying.”

Multisite vs. Separate Installs: The Honest Comparison

Separate WordPress installs give every site full independence — its own database, its own plugin choices, its own update schedule. Nothing that breaks on Site A touches Site B. Multisite trades that independence for centralized control: one update covers all sites, one admin panel governs everything, and one corrupted database table can take down your entire fleet.

Choose Multisite when centralized control is a feature, not a liability. Choose separate installs when site independence matters more than management convenience.

When to Use WordPress Multisite (And When to Walk Away)

Before you learn how to create a WordPress Multisite network, make sure it’s actually the right tool for your situation.

Use Multisite if you are:

• An agency managing 10+ client sites that use the same plugins and theme framework
• A university or large organization running department subsites under one domain
• A media company managing multiple editorial brands from one content team
• A SaaS product that spins up a new WordPress site per customer (the WordPress.com model)
• A developer who wants to update plugins and core once and have it propagate everywhere

Do NOT use Multisite if you are:

• Managing 2-4 sites with different plugin stacks or wildly different designs
• A solo freelancer who just wants less admin overhead
• On shared hosting where your host doesn’t support wildcard subdomains
• Planning to sell or hand off individual subsites to independent owners
• Running sites that need completely different user permission models

“WordPress Multisite is ideal for companies, universities, or developers that need to manage multiple websites with the same set of plugins and themes.” — Kinsta Engineering Blog

Before You Start: Prerequisites and Warnings

Before you learn how to create a WordPress Multisite network on your live server, lock these things down:

• Back up everything. Enabling Multisite modifies your wp-config.php and .htaccess. A backup is not optional — it is your escape hatch if something goes sideways.
• Confirm your host supports Multisite. Some managed hosts restrict wildcard subdomains or have Multisite-specific limitations. WP Engine, for example, has documented restrictions. Check with your host before you start.
• Know your URL structure decision upfront. Subdomains (site2.example.com) or subdirectories (example.com/site2). You cannot easily switch after the network is live.
• Your WordPress installation must have no existing content if possible. Technically you can enable Multisite on an existing site, but the original site becomes “Site 1” of the network.
• You need FTP or server file access. This is not a GUI-only operation.

If you want to test Multisite before touching your live server, set up a staging environment first. Multisite staging is more complex than single-site staging, but the principle is the same — our WordPress staging guide walks you through the process.

How to Create a WordPress Multisite Network: Step by Step

The official reference for this process is the WordPress.org Create a Network documentation — bookmark it. Here’s the full process for how to create a WordPress Multisite network broken down into clear steps.

Step 1 — Deactivate All Active Plugins

Before enabling Multisite, deactivate every active plugin. Go to Plugins → Installed Plugins, select all, and bulk deactivate. This prevents plugin conflicts during the network conversion. You’ll reactivate them through the Network Admin panel after setup.

Step 2 — Enable Multisite in wp-config.php

Open your wp-config.php file via FTP or your host’s file manager. Find this line:

/* That's all, stop editing! Happy publishing. */

Add this line directly above it:

define( 'WP_ALLOW_MULTISITE', true );

Save the file and reload your WordPress admin. If you’re not familiar with editing this file safely, our wp-config.php guide covers what to touch and what to leave alone.

Step 3 — Run the Network Setup Wizard

After saving wp-config.php, go to Tools → Network Setup in your WordPress admin. You’ll see the Multisite setup wizard.

Here you make the permanent decision: Subdomains or Subdirectories. Fill in your Network Title and admin email, then click Install.

Step 4 — Add the Required Code to wp-config.php and .htaccess

After clicking Install, WordPress shows you two code blocks. Copy them exactly. The first block goes into wp-config.php. The second block replaces your entire .htaccess file content.

The code blocks look similar to this (your values will differ):

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 );

Do not edit these values manually. Copy exactly what WordPress generates for your installation.

Step 5 — Log Back In and Access Network Admin

After updating both files, WordPress will log you out. Log back in. You now have a new menu item: My Sites → Network Admin. This is the Super Admin control panel for your entire network. That’s it — you now know how to create a WordPress Multisite network.

Step 6 — Reactivate Plugins Network-Wide

Go to Network Admin → Plugins. Here you can Network Activate plugins, which makes them active on every site in the network. Or leave them unactivated at the network level and let individual site admins activate them for their own sites.

Individual site admins cannot install new plugins. They can only activate or deactivate plugins the Super Admin has already uploaded. This is the #1 misunderstanding that causes friction between agencies and their clients.

Understanding the Super Admin Role

In a Multisite network, the Super Admin is God. Every site in the network has its own Administrator, but that site Admin cannot install plugins, install themes, or touch network-level settings. Only the Super Admin can.

This is powerful for agencies — you control the plugin stack, your clients can’t accidentally install something malicious or incompatible. But it creates a support relationship you need to manage. Set that expectation before onboarding.

For a full breakdown of WordPress’s permission hierarchy beyond Multisite, our WordPress user roles guide explains every role from Subscriber to Super Admin.

The Honest Problems With WordPress Multisite

Every other article glosses over this. We won’t. Knowing how to create a WordPress Multisite network is only half the picture — you also need to understand what can go wrong.

One Database, One Point of Failure

Every site in your Multisite network shares a single MySQL database. A corrupted table, a runaway query from a bad plugin, or a botched site migration can affect every site simultaneously. With separate installs, a broken Site A has zero impact on Site B. With Multisite, one breach in the hull can sink the fleet.

Domain Mapping Is Non-Trivial

If you want a subsite to have its own branded domain — clientsite.com instead of youragency.com/clientsite — you need domain mapping. WordPress 4.5+ has basic domain mapping built in, but getting it working with SSL for each mapped domain requires configuration at the DNS level and sometimes server-level config. Most articles treat this as a footnote. It is not.

Not All Plugins Are Multisite Compatible

Some plugins are built for single-site and behave unexpectedly in a network. WooCommerce on Multisite, for example, requires specific configuration. eCommerce, membership, and LMS plugins especially — verify Multisite compatibility before building your architecture around them.

Staging a Multisite Network Is More Complex

Staging a single WordPress site is straightforward. Staging a Multisite network requires replicating the network structure and updating all site URLs across multiple WordPress database tables. Our staging guide covers the single-site process — Multisite staging adds a layer of database table management on top of that.

Adding New Sites to Your Network

Once you’ve learned how to create a WordPress Multisite network and your setup is live, adding new subsites is genuinely fast. Go to Network Admin → Sites → Add New. Fill in the site address, title, admin email, and click Add Site. The new site is live immediately.

Each subsite can have its own theme — even if it’s a network-activated theme, individual site admins can customize it. If you want truly independent designs per subsite, child themes per subsite give each site its own customizations without touching the parent theme.

Permalink structures can also be set per subsite under Settings → Permalinks. For the best SEO structure, follow the same rules as any WordPress install — our permalink best practices guide applies site-by-site within a Multisite network.

Frequently Asked Questions

Set Sail or Stay in Port?

Now that you know how to create a WordPress Multisite network, the harder question is whether it’s right for your specific operation. If you’re managing 5+ related sites that share a common plugin stack and you’re the one responsible for keeping all of them running, Multisite will save you real time. If you’re not there yet, separate installs and a solid update routine serve you better.

Got a Multisite setup running — or a horror story from one that went sideways? Drop it in the comments below. The fleet learns from every sinking.