WordPress Multisite lets you run multiple WordPress sites from a single installation. One dashboard manages all sites, plugins, themes, and users — instead of maintaining separate WordPress installs for each site. For agencies managing client sites, businesses with multiple brands, universities with department sites, or any organization running multiple WordPress properties, Multisite simplifies operations dramatically.
Here’s the complete guide to setting up, configuring, and managing WordPress Multisite in 2026.
What Is WordPress Multisite?
WordPress Multisite is a built-in feature (not a plugin) that converts a single WordPress installation into a network of sites. Each site in the network has its own content, users, and settings, but they all share the same WordPress core files, plugins, and themes.
Key concepts:
- Network — The entire Multisite installation containing all sites
- Super Admin — The administrator who manages the entire network (installs plugins/themes, creates sites, manages network settings)
- Site Admin — Administrators of individual sites within the network (manages content, users, and site-specific settings)
- Network-activated plugins — Plugins enabled across all sites by the Super Admin
- Site-activated plugins — Plugins enabled on individual sites (if allowed by Super Admin)
When to Use Multisite (and When Not To)
Use Multisite when:
- You manage 5+ related sites — University departments, franchise locations, regional offices, multilingual versions
- Sites share the same plugins and themes — Update once, apply everywhere
- You need centralized user management — Users can have accounts across multiple sites with different roles
- You’re building a blog network — Like WordPress.com, where users create their own sites on your platform
- You run an agency — Manage all client sites from one dashboard
Don’t use Multisite when:
- Sites need different plugins — Multisite shares all plugins. If Site A needs WooCommerce but Site B shouldn’t have it, separate installs are cleaner.
- Sites have vastly different traffic — One high-traffic site can affect performance of all sites in the network since they share a database.
- You need different hosting for different sites — All Multisite sites run on the same server.
- You only have 2-3 sites — The overhead of Multisite management isn’t worth it for a small number of sites.
Step 1: Prerequisites
Before enabling Multisite:
- Fresh WordPress install (recommended) — While you can convert an existing site, starting fresh avoids complications with existing plugins and content.
- Deactivate all plugins — Required during the conversion process. Re-activate after Multisite is enabled.
- FTP/SSH access — You’ll need to edit wp-config.php and .htaccess (or Nginx config).
- Decide: Subdomains or Subdirectories
- Subdirectories: example.com/site1, example.com/site2 (easier setup, no DNS changes)
- Subdomains: site1.example.com, site2.example.com (requires wildcard DNS)
Step 2: Enable Multisite in wp-config.php
Add this line to wp-config.php, above the “That’s all, stop editing!” comment:
define( 'WP_ALLOW_MULTISITE', true );
Save the file and refresh your WordPress admin. You’ll see a new menu item under Tools > Network Setup.
Step 3: Network Setup
Go to Tools > Network Setup. WordPress will ask you to choose between subdomains and subdirectories, and to provide a network title and admin email.
After submitting, WordPress generates two blocks of code:
- wp-config.php additions — Network configuration constants (MULTISITE, SUBDOMAIN_INSTALL, etc.)
- .htaccess rules — URL rewriting rules for the network (Apache) or Nginx configuration block
Add these to their respective files exactly as shown.
Step 4: Configure the Network
After adding the code and logging back in, you’ll see a new My Sites > Network Admin menu. Key settings:
- Settings > Network Settings — Registration (allow new sites, user registration), upload limits, menu settings
- Sites > Add New — Create new sites in the network
- Themes — Enable/disable themes for the network. Site admins can only use themes enabled by the Super Admin.
- Plugins — Network-activate plugins (applies to all sites) or allow per-site activation.
Domain Mapping
Want each site to have its own domain (site1.com, site2.com) instead of subdirectories or subdomains? WordPress 4.5+ includes native domain mapping.
Setup:
- Point the custom domain’s DNS A record to your server’s IP address
- Add the domain to your server configuration (Apache virtual host or Nginx server block)
- In Network Admin > Sites > Edit Site, change the site URL to the custom domain
- Install an SSL certificate for each mapped domain (Let’s Encrypt handles this automatically on most hosts)
Managing Plugins Across the Network
Plugin management in Multisite has nuances:
- Network Activate — Activates the plugin on ALL sites. Use for essential plugins every site needs (security, caching, SEO).
- Per-site activation — Super Admin installs plugins; site admins activate on their individual sites. Use for optional functionality.
- Must-Use Plugins (mu-plugins) — Plugins in wp-content/mu-plugins/ are automatically active on all sites. No activation needed. Use for custom code that must run everywhere.
Theme Management
Themes work differently in Multisite:
- Network Enable — Makes a theme available for site admins to choose. It doesn’t activate it on any site.
- Per-site activation — Each site admin selects their theme from network-enabled options.
- Default theme — Set in Network Settings. New sites use this theme automatically.
User Management
Multisite user management is powerful:
- Global users — A user account exists once and can be added to multiple sites with different roles (admin on Site A, editor on Site B).
- Super Admin — Has access to all sites and the network admin dashboard.
- Registration settings — Allow user registration, allow site creation, or both.
- User limits — Control how many sites a user can create.
Performance Considerations
Multisite performance requires attention since all sites share resources:
- Object caching — Redis or Memcached is essential for Multisite. Each site generates its own database queries; object caching reduces database load dramatically.
- CDN — Use Cloudflare or a CDN plugin that supports Multisite to serve static assets from edge servers.
- Database optimization — Each site creates 10+ database tables. A 50-site network has 500+ tables. Regular database optimization (WP-Optimize or similar) keeps queries fast.
- Managed WordPress hosting — Hosts like Cloudways, GridPane, and SpinupWP support Multisite well and handle server-level caching.
Multisite Hosting Recommendations
Not all hosts support Multisite well. Recommended options for 2026:
- Cloudways — Excellent Multisite support with server-level caching, staging, and scalable resources. Best balance of performance and price.
- GridPane — Server management panel with full Multisite support, automatic SSL for mapped domains, and Redis object caching.
- SpinupWP — Modern WordPress server management with Multisite support, Nginx, and automated deployments.
- WP Engine — Managed WordPress hosting with Multisite support on Growth plans and above.
WordPress Multisite is a powerful tool when used for the right scenarios. It simplifies management of related sites, centralizes updates and security, and provides a unified user system. Plan your network structure carefully, invest in proper hosting and caching, and your Multisite network will run efficiently at scale.
Interesting Reads:
WooCommerce Fashion Store Setup Guide
