WordPress Multisite is a powerful feature that lets you run multiple sites from a single WordPress installation. It’s used by universities for campus sites, agencies for client sites, media companies for network blogs, and enterprises for multi-brand deployments.
But Multisite comes with tradeoffs. It requires careful planning, a compatible hosting environment, and an understanding of which plugins and themes work in a networked context. This guide covers everything you need to know to set up, manage, and develop for WordPress Multisite.
When to Use Multisite
Multisite is the right choice when you need to manage multiple sites that share plugins, themes, and users. Common use cases include a university with department sites that all need the same event calendar plugin, an agency managing client sites from a central dashboard, or a company with multiple brand sites that share a user database.
Multisite is the wrong choice when sites need completely independent plugin sets, custom server configurations, or isolated user databases. In those cases, separate WordPress installations or a WordPress management platform like MainWP are better options.
Setting Up a Multisite Network
Enable Multisite by adding a constant to wp-config.php, then running the network setup through the WordPress admin. The process adds new tables to your database — wp_blogs, wp_blogmeta, wp_site, wp_sitemeta — and modifies your .htaccess or nginx configuration for subdirectory or subdomain sites.
Choose between subdirectory and subdomain URLs. Subdirectory — site.com/site1 — is simpler and works with standard hosting. Subdomain — site1.site.com — requires wildcard DNS configuration. Both are equally capable from a technical standpoint.
Network Administration
The Network Admin panel is your central command center. From here you can add and remove sites, manage users across the network, install plugins and themes for all sites, and configure network-wide settings.
Plugins and themes can be activated network-wide (active on every site) or site-specific (each site admin chooses what to activate). Use network-wide activation for essential plugins that every site needs. Use site-specific activation for optional functionality that sites can opt into.
Plugin and Theme Compatibility
Not all plugins and themes work correctly in Multisite. Testing is essential before deploying to production. Common Multisite compatibility issues include hardcoded table prefixes, assumptions about site URLs, and caching mechanisms that don’t account for multiple sites.
When developing plugins for Multisite, use get_current_blog_id() to get the current site’s ID, switch_to_blog() to access another site’s data, and restore_current_blog() to return to the original context. Use get_site_option() and update_site_option() for network-wide settings.
Performance in Multisite
A Multisite network with 100 sites under a single WordPress installation handles traffic differently than 100 separate installations. The database is shared across all sites, so a slow query on one site can affect all sites.
Object caching with Redis is essential for Multisite performance. It caches database queries on a per-site basis and dramatically reduces database load. Use a network-wide caching plugin that’s Multisite-aware. Consider separating the database server from the web server for larger networks.
User Management Across Sites
Users in Multisite are global — a user registered on one site can be added to any other site in the network. This is useful for networks that share user bases but can be confusing for users who expect separate accounts for separate sites.
Sites: 10 Users: 500 Shared plugins: 15 Monthly visits: 500k
Use the Network Admin’s Users screen to manage users across all sites. You can add, remove, and change roles for any user on any site. For networks with thousands of users, use the user querying APIs to find and manage users programmatically.
The Bottom Line
WordPress Multisite is a powerful tool for managing multiple sites efficiently. It reduces maintenance overhead, centralizes plugin and theme management, and enables workflows that are impossible with separate installations. Approach Multisite with a clear understanding of your requirements, test thoroughly before migrating, and invest in performance optimization from the start. For the right use cases, Multisite is transformative.
