keepcalculator

06 Numbers and Powers

WordPress Multisite Best Configuration Guide

Card No. 06·75341 · Updated · Standard formula, shown below

The best configuration for WordPress Multisite depends on your project size, but for most new installs, the top pick is a subdirectory network on a single server with an object cache and a dedicated CDN. This setup balances simplicity, performance, and cost, and it avoids the domain-mapping complexity that trips up many site owners.

What to Look For

Before you choose a configuration, focus on these criteria that actually affect how well Multisite works for you:

  • Network type: Subdirectory (yoursite.com/site1) vs. subdomain (site1.yoursite.com) vs. domain mapping (each site has its own domain). Subdirectory is easiest for SEO and maintenance; subdomains can be useful for separate brands; domain mapping requires extra setup and can be tricky with SSL.
  • Hosting environment: Shared, VPS, or dedicated server. Multisite needs more PHP memory and database connections than a single site, especially as the number of sites grows.
  • Storage and backups: All sites share the same WordPress core, plugins, and themes, but each has its own uploads folder and database tables. You need a backup solution that handles the entire network, not just individual sites.
  • Caching and performance: An object cache (like Redis) is almost mandatory for networks with more than a handful of sites. Page caching and a CDN help too, but they must be configured to work across all sites.
  • Plugin and theme compatibility: Not all plugins are Multisite-compatible. Check that the plugins you need support network activation and per-site settings.
  • Maintenance workflow: Updates are easier on Multisite (one core update for all sites), but you need a staging environment and a clear process for testing updates before pushing them live.

Option 1: Subdirectory Network on a Single VPS

Strengths: This is the simplest and most reliable setup. You get one WordPress installation, one core update, and shared plugins/themes. Subdirectory URLs are clean and easy for users to understand. A VPS gives you control over PHP memory, caching, and server settings, which you need for decent performance.

Trade-offs: You need to manage the server yourself (or use a managed VPS host). If one site gets a lot of traffic, it can affect all others. Backups must include the entire network.

Who it suits: Most users, including agencies managing client sites, universities with departments, and businesses with multiple product lines or regional sites.

Option 2: Subdomain Network on a VPS or Dedicated Server

Strengths: Subdomains (like shop.example.com and blog.example.com) can feel more distinct and allow for separate cookie domains, which can be useful for e-commerce. They also make it easier to scale by moving a high-traffic subdomain to a separate server later.

Trade-offs: Subdomains require more DNS setup and can be harder for users to remember. SEO best practices are debated, but subdirectories are generally easier to manage for SEO. SSL certificates need to cover all subdomains (wildcard or SAN).

Who it suits: Organizations that want clear separation between brands or functions, or that plan to scale specific sites independently.

Option 3: Domain Mapping (Multiple Domains) on a VPS

Strengths: Each site can have its own domain (e.g., site1.com, site2.com) while still running on one Multisite network. This is great for agencies running multiple client sites or for a company with multiple brands.

Trade-offs: Requires the WordPress MU Domain Mapping plugin (or similar) and careful DNS configuration. SSL can be a pain—you need a certificate for each domain. Performance can suffer if many domains point to the same server without proper caching.

Who it suits: Agencies or businesses that need each site to have a distinct, professional domain without managing separate WordPress installs.

Option 4: Managed WordPress Hosting with Multisite Support

Strengths: Providers like WP Engine, Kinsta, and Flywheel offer Multisite plans that handle server management, caching, staging, and backups for you. They often include a CDN and object caching out of the box. This is the easiest way to run Multisite if you don’t want to deal with server admin.

Trade-offs: Costs more than a DIY VPS. Some managed hosts have limits on the number of sites or traffic. You may have less control over server-level settings. Not all managed hosts support domain mapping, so check first.

Who it suits: Non-technical users, small businesses, and agencies that prefer to focus on content rather than infrastructure.

Option 5: Multisite with Redis Object Cache and CDN

Strengths: This is more of an enhancement than a standalone configuration. Adding Redis for object caching dramatically reduces database queries across all sites. A CDN (like Cloudflare) serves static assets (images, CSS, JS) from edge servers, speeding up page loads globally. This combo works with any of the above setups.

Trade-offs: You need to configure Redis on your server (or use a plugin like Redis Object Cache). CDN setup requires careful cache purging when you update content. Costs for CDN and Redis hosting can add up, though many VPS providers include Redis.

Who it suits: Any Multisite network with more than a few sites or with traffic that spikes. It’s essential for networks with many active users.

Option 6: Multisite on a Dedicated Server (High-Traffic Networks)

Strengths: For very large networks (hundreds of sites, heavy traffic), a dedicated server gives you full control over resources. You can allocate RAM and CPU as needed, and you can run advanced caching and load-balancing setups.

Trade-offs: Expensive and requires serious sysadmin skills. You must handle security, updates, and monitoring yourself. Overkill for most users.

Who it suits: Large enterprises, universities with many thousands of users, or networks that generate millions of page views per month.

How to Choose

Budget: If you’re on a tight budget, start with a subdirectory network on a shared host that supports Multisite (many do). But be aware that shared hosting can be slow and may not allow the PHP memory or caching you need. A low-cost VPS (like DigitalOcean or Linode) is a better balance of cost and control. Managed hosts are the most expensive but save time.

Use case: For a few internal sites or a small client portfolio, subdirectory on a VPS is perfect. For separate brands or domains, you need subdomain or domain mapping. For a large-scale network, consider a managed host or dedicated server with Redis and a CDN.

Common trade-offs: The main trade-off is simplicity vs. flexibility. Subdirectory is simplest but less flexible for branding. Subdomains and domain mapping are more flexible but require more setup. Managed hosting is easiest but costs more and limits control. Performance always requires some extra work—caching, CDN, and server tuning—regardless of which option you pick.

Frequently Asked Questions

Q: Can I convert an existing single-site WordPress to Multisite?
Yes, you can add define('WP_ALLOW_MULTISITE', true); to wp-config.php and follow the on-screen instructions. But it’s safer to do this on a staging site first, and be aware that some plugins may break.

Q: Do I need a separate database for each site?
No, Multisite uses one database with shared tables for users and separate tables for each site’s content. This is efficient but means a database backup backs up everything.

Q: How many sites can Multisite handle?
It depends on your server resources. With good caching and a decent VPS, you can handle dozens or even hundreds of low-traffic sites. For thousands, you’ll need a dedicated server or cluster.

Q: Is Multisite good for SEO?
Subdirectory networks are fine for SEO if you use proper permalinks and sitemaps. Subdomains are treated as separate domains by search engines, which can be good or bad depending on your strategy. Domain mapping works like separate sites.

Q: Can I use different themes and plugins on each site?
Yes, you can install themes and plugins at the network level and then activate them per site. You can also allow site admins to install their own, but that can become a security risk.

Q: How do I handle backups?
Use a plugin that supports Multisite, like UpdraftPlus or BackupBuddy. You need to back up the entire database and the wp-content/uploads folder (which contains all site uploads).

Bottom Line

For most people, the best configuration is a subdirectory Multisite network on a VPS with Redis object caching and a CDN. It’s affordable, flexible, and performant. If you want zero server maintenance, choose a managed host like WP Engine or Kinsta. If you need multiple domains or subdomains, adapt the network type accordingly. Start small, test thoroughly, and scale as your needs grow.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →