WordPress Multisite: When and How to Use It

What WordPress Multisite Actually Does

Multisite converts a standard WordPress installation into a network. The network has one Super Admin who controls themes, plugins and user access across all sites. Individual site admins manage content and settings for their specific site.

All sites share one WordPress codebase and one database (with separate tables per site). This means a single WordPress update, a single plugin update and a single security patch cover every site on the network.

Sites on a Multisite network can use subdomains (blog.example.com, store.example.com) or subdirectories (example.com/blog, example.com/store). With domain mapping, each site can even use a completely separate domain name (example.com, differentbrand.com).

For broader web development guidance, see our web development services page.

When Multisite Makes Sense

Franchise and Multi-Location Businesses

A franchise with 20 locations needs consistent branding with localized content. Multisite lets the corporate team control the theme and core plugins while each location manages their own pages, blog posts and contact information. This balance between control and autonomy fits the franchise model perfectly.

Our franchise SEO guide explains the search optimization considerations for multi-location businesses.

Universities and Large Organizations

Universities run dozens of department websites. Multisite gives the IT department centralized control over security and updates while each department manages their own content. WordPress.com and many university networks run on Multisite at scale.

Agencies Managing Client Sites

Agencies that build multiple client sites on WordPress can reduce server costs and maintenance time by running them on one Multisite network. Each client gets their own site with separate admin access while the agency handles infrastructure from a single dashboard.

Multilingual Sites

Businesses that need completely separate sites per language (not just translated pages) can use Multisite to run example.com/en, example.com/fr and example.com/es as independent sites with shared infrastructure.

When Multisite Is the Wrong Choice

Sites with Different Hosting Needs

If one site gets 500,000 monthly visitors and another gets 5,000, they have fundamentally different performance requirements. Multisite puts them on the same server with shared resources. The high-traffic site’s spikes affect every other site on the network.

Sites Needing Different Plugins

Multisite activates plugins network-wide or per-site, but all sites must use the same plugin version. If Site A needs WooCommerce 8.0 and Site B needs WooCommerce 7.5 due to a compatibility issue, Multisite cannot accommodate both.

Small Number of Unrelated Sites

Two or three sites with no shared branding, users or content gain nothing from Multisite. The added complexity of network administration outweighs the marginal maintenance savings. Separate WordPress installations are simpler.

Client Sites You Will Hand Off

If you build a client site that the client will eventually self-manage or migrate to their own hosting, Multisite creates a dependency. Extracting a single site from a Multisite network requires more effort than migrating a standalone installation.

How to Set Up WordPress Multisite

Prerequisites

• A fresh WordPress installation (converting an existing site is possible but riskier)
• FTP or SSH access to your server
• Access to wp-config.php and .htaccess files
• All plugins deactivated during setup

Step 1: Enable Multisite in wp-config.php

Add this line above the “That’s all, stop editing” comment:

define( 'WP_ALLOW_MULTISITE', true );

Step 2: Install the Network

After saving wp-config.php, go to Tools > Network Setup in your WordPress dashboard. Choose between subdomains or subdirectories. WordPress generates code snippets for your wp-config.php and .htaccess files.

Step 3: Update Configuration Files

Add the generated code to wp-config.php and replace your .htaccess rules with the provided snippet. Log out and log back in. The dashboard now shows a “My Sites” menu and a “Network Admin” option.

Step 4: Create Sites

Navigate to Network Admin > Sites > Add New. Enter the site address, title and admin email. WordPress creates the site with its own set of database tables instantly.

Step 5: Configure Network Settings

Set network-wide defaults for registration, upload limits and menu settings. Install and network-activate plugins that every site needs. Install themes that site admins can choose from.

Domain Mapping for Multisite

Domain mapping lets each site on the network use its own unique domain instead of a subdomain or subdirectory. Since WordPress 4.5, domain mapping is built into core.

To map a domain, point the external domain’s DNS A record to your server’s IP address. Then in Network Admin > Sites, edit the site and change its URL to the external domain. WordPress handles the routing automatically.

Domain mapping requires wildcard SSL certificates or individual certificates per domain. Let’s Encrypt supports both options at no cost.

Multisite Performance Considerations

Database Growth

Each site adds 9-12 database tables. A network with 50 sites creates 450-600 tables in one database. This does not cause performance issues for most hosting environments, but shared hosting with limited database connections may struggle. Use managed WordPress hosting or a VPS for networks larger than 10 sites.

Caching

Object caching (Redis or Memcached) benefits Multisite networks significantly because multiple sites share the same cache layer. Page caching requires per-site configuration since each site serves different content. WP Super Cache and W3 Total Cache both support Multisite.

Media Storage

Each site stores media in its own uploads subdirectory (wp-content/uploads/sites/2, sites/3, etc.). Plan storage capacity based on total media volume across all sites, not just the primary site.

Security for Multisite Networks

The shared codebase means one vulnerability affects every site. Apply these security measures:

• Restrict Super Admin access to a maximum of 2-3 trusted users
• Use a security plugin like Wordfence or Sucuri that supports network-wide scanning
• Apply updates immediately since one outdated plugin exposes all sites
• Disable plugin and theme installation for individual site admins
• Monitor user registrations if you allow open registration on any site
• Keep automated backups of the entire network including the shared database

Migrating to or From Multisite

Converting a Standalone Site to Multisite

Converting an existing WordPress installation to Multisite is possible but requires careful execution. Back up your database and files completely before starting. Deactivate all plugins, enable Multisite through wp-config.php and run the network installation. Reactivate plugins one at a time to identify compatibility issues.

Extracting a Site from Multisite

Moving a single site out of a Multisite network requires exporting content, recreating the site as a standalone installation and importing the content. Media files need manual migration because Multisite stores them in a unique directory structure. Plugins like WP Migrate handle this process but require testing to verify nothing breaks.

Need help determining the right WordPress architecture for your business? Request a free audit and our team will evaluate your requirements.

Frequently Asked Questions