Key Takeaways
- Multisite runs multiple sites from one WordPress installation — shared database, shared plugins and themes, centralised admin.
- The right use cases: franchise systems, multi-campus institutions, news networks with regional sites, agencies managing many similar client sites.
- The wrong use cases: unrelated sites with different performance requirements, sites managed by independent teams, or sites requiring security isolation from each other.
- Multisite's main risk: all sites share a single failure point — a bad plugin update or server issue affects all sites simultaneously.
- Domain mapping allows each site in a Multisite network to have its own independent domain — the subdirectory default is not required.
WordPress Multisite is one of those features that's genuinely powerful in the right context and a source of complexity and frustration in the wrong one. It's been part of WordPress since version 3.0 in 2010 (when it absorbed WordPress MU — 'multi-user'), and organisations that use it correctly — typically networks of related sites with shared infrastructure — benefit significantly from centralised management. Organisations that use it incorrectly — lumping together unrelated sites simply to save on hosting — create a single point of failure and maintenance overhead that outweighs any savings. This guide explains how Multisite works, when it's the right architecture, and when separate WordPress installations are the better answer.
Definition: Super Admin and Site Admin in WordPress Multisite
WordPress Multisite introduces a two-tier admin structure. Super Admin is a role that exists only in Multisite — it has access to the Network Admin dashboard, which manages the entire network: activating/deactivating plugins and themes for the network, creating and deleting sites, managing the list of network users, and configuring network-wide settings. A Super Admin can access any site's wp-admin dashboard. Site Admin is the standard WordPress Administrator role scoped to a single site — they can manage content, users, and settings for their specific site, but cannot install new plugins (only activate plugins the Super Admin has already made available to the network) or access other sites. This permission hierarchy is what makes Multisite suitable for franchise or multi-department scenarios — site-level teams have control over their content and settings, while the network team controls the shared infrastructure.
When WordPress Multisite Makes Sense
Multisite's efficiency advantages appear when multiple sites share enough infrastructure, theme, and plugin code that centralised management reduces work relative to separate installations.
Franchise and multi-location business websites are the classic Multisite use case. A franchise system with 50 franchise locations — each needing a site with the same brand design, same plugins (booking system, SEO tools, contact forms), and the same content structure (about page, services, team, contact) but with location-specific content — benefits enormously from Multisite. The franchisor manages the theme and plugins centrally; each franchise location gets a site admin login to update their own content. When a plugin needs updating or a theme change is rolled out to all locations, the Super Admin does it once and all 50 sites receive the update.
University and education network sites are another strong Multisite fit. A university with 30 faculty departments, each needing a website with the same brand identity but department-specific content, is well-suited to Multisite. Central IT manages the WordPress installation, theme, and core plugins; department administrators manage their site's content. A content editor in the Economics department can't accidentally break the Business School's site. The IT team only manages one WordPress installation and one set of plugin updates rather than 30 separate installations.
Media and publishing networks benefit from Multisite when multiple publications share editorial tools (editorial calendar plugins, paywall management, subscriber management) and a common design framework while maintaining editorial independence per publication. A regional news organisation with sites for each region — same editorial workflow tools, different mastheads and content — is a natural Multisite candidate. The shared infrastructure reduces cost while each regional editor maintains editorial control over their site.
- Franchise systems — shared brand and plugins, location-specific content and site admins
- University and education networks — central IT management, department-level content editing
- Media/publishing networks — shared editorial tools, distinct mastheads and content
- Agencies managing similar client sites — shared infrastructure reduces per-site overhead
- Government departments — shared security management and compliance tools, departmental content autonomy
When Separate WordPress Installations Are Better
Separate WordPress installations are better when sites have significantly different requirements, need independent risk profiles, or are managed by teams with no shared governance.
The risk profile argument for separate installs: in Multisite, a plugin update that introduces a fatal error takes down all sites simultaneously. In separate installs, the same error affects only one site. For organisations where each site represents independent business risk — a law firm managing both their own website and a client's site, or an agency hosting client sites — the shared failure risk of Multisite is unacceptable. Separate installs with separate staging environments allow testing updates on one site before deploying to others.
Performance requirements vary by site: a high-traffic news site needs different server resources and caching configuration than a low-traffic informational site. In Multisite, all sites share the same server environment. A traffic spike on the highest-traffic site can degrade performance for all network sites. Sites with materially different performance profiles — in terms of traffic volume or traffic patterns (burst traffic for event-driven sites versus steady traffic for information sites) — are better on separate hosting environments that can be scaled independently.
Unrelated sites managed by unrelated teams are a bad fit for Multisite. The efficiency of centralised management only applies when there's someone at the Super Admin level responsible for the network. Multisite doesn't make sense as a way to bundle together a personal blog and a client site to share a hosting account — the complexity outweighs any savings, and the governance model (Super Admin has access to all sites) creates privacy concerns between unrelated site owners.
Key Setup Considerations for WordPress Multisite
Setting up Multisite correctly from the start — subdomain vs subdirectory structure, hosting environment, user management — prevents migration pain later.
The most important setup decision is subdomain versus subdirectory structure. Subdomains (site2.yournetwork.com) require wildcard DNS configuration — a DNS record for *.yournetwork.com pointing to your server. Subdirectories (yournetwork.com/site2) are simpler to set up and don't require wildcard DNS. The choice affects how domain mapping works and how SSL certificates are structured — wildcard SSL certificates cover all subdomains, while subdirectory sites can use the same certificate as the main domain. For networks where each site will eventually use its own domain (via domain mapping), the subdomain/subdirectory choice is less critical — mapped domains override the default structure.
Hosting for Multisite should be on a plan that explicitly supports it. Shared hosting accounts sometimes restrict Multisite due to the database and file system load it creates. Managed WordPress hosting plans (WP Engine, Kinsta, Flywheel) all support Multisite explicitly and often include staging environments per site and network-level performance optimisation. For networks with more than 10–15 sites or sites with significant traffic, a VPS or dedicated managed WordPress environment is appropriate.
Plan the plugin and theme strategy before launch. In Multisite, only Super Admins can install plugins; site admins can only activate plugins the Super Admin has made network-available. This means decisions about which plugins are available to all sites must be made deliberately, and sites with unique plugin needs may need Super Admin involvement for one-off activations. Establish a process for site admins to request additional plugins and a review process for the Super Admin to evaluate and approve requests.
Experience Signal
The Multisite decisions that go wrong most often are driven by cost optimisation rather than architectural fit — 'we can run all these sites on one WordPress install to save on hosting'. The saving is real; the hidden cost is centralised risk. When the shared installation has a problem, every site is affected. We typically recommend Multisite for organisations with genuine shared governance requirements (franchise systems, university networks) and separate installs for everything else — the independence and isolation of separate installs is worth the slightly higher hosting and maintenance overhead in most situations.
Frequently Asked Questions
Yes. WordPress Multisite is a built-in feature of WordPress core — no additional plugin or license is required. Enabling it requires adding a few lines to your wp-config.php and .htaccess files, which any developer can do in under an hour. The hosting cost scales with the number of sites and their combined traffic — you're running multiple websites on the same server infrastructure, so adequate hosting (typically a VPS or managed WordPress hosting plan that supports Multisite) is important. Plugins and themes used across the network are licensed per the standard terms — a plugin licensed for one site typically needs a multi-site license (or a license per site count) to be used across a Multisite network.
Yes, with domain mapping. By default, WordPress Multisite sites are accessed as subdirectories (yoursite.com/site2) or subdomains (site2.yoursite.com) of the main network URL. Domain mapping allows each site to use its own independent domain (site2.com) — the request is routed to the correct Multisite site transparently. WordPress 4.5+ has domain mapping built into core (the WordPress MU Domain Mapping plugin is no longer needed). Each mapped domain requires a DNS record pointing to your hosting server and a server-level virtual host configuration for the domain.
Main disadvantages: (1) All sites share the same WordPress core and plugin versions — an update that breaks one site can break all sites, removing the ability to update each site independently; (2) If the server goes down, all sites in the network go down — single point of failure versus separate hosting environments; (3) Resource contention — a traffic spike on one site can affect performance for all sites on the same server; (4) Plugin and theme availability — a plugin that works in single-site mode may have Multisite compatibility issues; (5) Complexity — managing Super Admin vs Site Admin roles and per-site plugin activation adds administrative complexity; (6) Database — all sites share the same database, which grows large and can affect backup and restore times. These disadvantages are manageable with appropriate hosting and maintenance practices, but they make Multisite inappropriate for sites with very different performance or security requirements.
Sources
Managing Multiple WordPress Sites and Considering Multisite?
Webnixon designs and builds WordPress Multisite networks — from architecture planning through to setup, theme development, and ongoing Super Admin management. We'll help you decide whether Multisite is right for your situation.
Book a WordPress Architecture ConsultationAbout the author
Jim Yang
Marketing Manager
Jim oversees paid media and growth marketing at Webnixon, specializing in Google Ads, Meta advertising, and conversion rate optimization across B2B and B2C categories. He has managed multi-channel campaigns for businesses ranging from professional services to ecommerce retailers, consistently delivering cost-efficient lead generation against competitive benchmarks. He writes about paid advertising strategy, marketing measurement, and growth tactics for businesses.
Related Articles
Web Design
WordPress Security: A Practical Guide to Protecting Your Business Website
WordPress is the most popular CMS in the world — and consequently the most targeted. Automated bots scan for outdated plugins, weak passwords, and exposed login pages constantly. Most WordPress security breaches are preventable with a straightforward set of practices. This guide covers them in order of priority.
Web Design
How to Speed Up a WordPress Website: A Practical Performance Guide
Page speed is a confirmed Google ranking factor, and 53% of mobile users abandon sites that take longer than three seconds to load. For WordPress sites — which power over 40% of the web — performance is often degraded by plugin bloat, unoptimised images, and inadequate hosting. This guide covers every layer of the problem.
Web Design
Drupal vs WordPress: Which CMS Is Right for Your Organisation?
WordPress and Drupal are the two most widely deployed open-source CMS platforms in the world. WordPress powers over 33% of all websites. Drupal is the CMS of choice for governments, universities, and enterprise organisations with complex content requirements. Here's how to choose between them.