Multisite
A WordPress feature that lets you run multiple websites from a single WordPress installation, sharing one database and codebase.
Think of WordPress Multisite as running an apartment building instead of a single house. You have one foundation (your WordPress installation), but each tenant (website) gets their own space, their own keys, and their own front door. The landlord — that’s you, the Super Admin — manages the whole building from one control panel.
Multisite has been part of WordPress core since version 3.0. You don’t need a plugin to enable it, just a few lines in your config files and a fresh install or an existing single-site setup.
How It Works
Enabling Multisite requires editing two core files. First, add this line to wp-config.php above the “That’s all, stop editing!” comment:
define( 'WP_ALLOW_MULTISITE', true );After saving, go to Tools → Network Setup in your WordPress dashboard. WordPress will ask you to choose between subdomains or subdirectories:
- Subdirectories:
yoursite.com/blog1,yoursite.com/blog2 - Subdomains:
blog1.yoursite.com,blog2.yoursite.com
WordPress then gives you additional code to paste into wp-config.php and .htaccess. Once that’s done, you’ll see a new My Sites menu in the admin bar and a Network Admin dashboard where you manage every site in the network.
Each site in the network shares the same WordPress core files and the same database, but gets its own set of database tables (prefixed like wp_2_posts, wp_3_posts, and so on). Plugins and themes are installed once by the Super Admin and then activated per site or network-wide.
Common Use Cases
University or school departments. A university runs one Multisite network with a site for each department — English, Biology, Admissions — all sharing the same theme and branding. The IT team manages updates in one place instead of maintaining 30 separate installs.
Client hosting for agencies. Freelancers and agencies spin up a new site for each client on their Multisite network. Every client gets their own dashboard, but the agency handles core updates, security patches, and plugin licensing centrally. This cuts maintenance time dramatically.
Multilingual content networks. A media company publishes in English, Spanish, and French. Each language gets its own site (en.example.com, es.example.com) with its own editorial team, while the network admin controls shared assets and global settings.
Corporate intranets and microsites. A company launches campaign-specific microsites — product launches, events, seasonal promos — without provisioning new servers or installations each time. Spin one up, use it, archive it.
Why It Matters
Here’s the thing — managing five separate WordPress installations means five sets of updates, five security audits, five hosting configurations. Multisite collapses all of that into one. You patch a vulnerability once and every site in the network is protected.
From a performance standpoint, Multisite is efficient because all sites share one set of core files and one object cache pool. Pair it with a hosting provider that supports Multisite well — Cloudways and WP Engine both handle it cleanly — and you get solid performance without multiplying your infrastructure.
The tradeoff is real, though. If one site in the network gets compromised or a plugin conflict takes down the network admin, every site feels it. And not all plugins play nicely with Multisite — always check compatibility before activating network-wide.
For agencies and organizations managing more than three or four WordPress sites, Multisite is worth serious consideration. The upfront setup takes about 15 minutes. The ongoing time savings compound every single month.