Multisite or separate installs: choosing for multi-brand WordPress

Organizations that run many WordPress sites eventually face the same question: should they live in one Multisite network or as separate installations? Universities, franchise groups, multi-brand retailers and agencies with many regional sites all hit it. Both approaches work at scale, and both fail in predictable ways when chosen for the wrong reasons. This is how we make the call with clients.

What Multisite actually shares

A WordPress Multisite network runs many sites from a single codebase and a single database, with some tables shared across the network and others created per site. In practice that means:

• One set of core, themes and plugins. Updates happen once for every site, and a network administrator controls what is available.
• Shared users. A person has one account and can be given roles on any number of sites.
• Central administration. Creating a new site takes minutes, with default settings, themes and content applied automatically.
• Shared infrastructure. One hosting environment, one backup routine, one monitoring setup.

Separate installs share nothing by default. Each site has its own codebase, database, users and update cycle, even if they are built from the same starter theme and deployed by the same pipeline.

When Multisite is the right call

Multisite shines when sites are genuinely similar and centrally governed. We recommend it when most of the following are true:

1. The sites share a design system and a common set of features, with differences mostly in content and branding tokens.
2. A central team owns the platform, controls which plugins are available, and has the authority to say no.
3. New sites are created regularly, such as for new locations, departments or campaigns, and speed of launch matters.
4. Users often work across several sites and benefit from a single account.
5. Traffic levels are broadly comparable, without one site dwarfing the others.

A franchise group we work with runs over 140 location sites on a single network. New locations launch the same day they are approved, every site gets security fixes at the same time, and the central marketing team can push a new pattern or promotion across the network in one release.

Multisite is a governance decision disguised as a technical one. If nobody has the authority to standardize, the network will not stay standard.

Governance is worth writing down before the first site launches. We usually produce a one-page platform charter covering who can request a new site, who approves new plugins, how often updates ship, what individual site administrators may and may not change, and how a site is archived when a location closes or a campaign ends. Networks that skip this step tend to accumulate dozens of half-used plugins requested by individual sites, which erodes the very efficiency that justified Multisite in the first place.

When separate installs are safer

Separate installs are the better choice when sites diverge or when isolation matters more than efficiency:

• Different feature needs. One brand runs WooCommerce, another runs a membership platform, a third is a simple brochure site. Forcing them into one network means every site carries the plugin weight and risk of all the others.
• Independent teams. Brands with their own developers and release schedules will fight over shared updates.
• Uneven traffic. A high-traffic site in a network competes for database and cache resources with everything else, and scaling it independently is harder.
• Risk isolation. In a network, a bad plugin update or a compromised site can affect every site. For businesses where one brand's outage must not touch another, separation is worth the overhead.
• Likely divestment. If a brand might be sold or spun off, extracting it from a network is a real migration project. Separate installs make that trivial.

The operational trade-offs

Separate installs used to mean multiplying maintenance work by the number of sites. That is much less true with modern tooling. With a shared starter theme, Composer-managed dependencies and a single deployment pipeline that targets many sites, updating 30 separate installs is a scripted operation rather than 30 manual ones.

Multisite, meanwhile, has costs that are easy to underestimate:

• Some plugins do not support Multisite well, or license per site in ways that get expensive.
• Database tables multiply with every site, and very large networks need careful database tuning.
• Backups and restores are network-wide by default; restoring a single site requires tooling.
• Domain mapping, SSL and caching configuration need more thought than for a single site.

We have also seen hybrid setups work well: a Multisite network for many similar small sites, alongside separate installs for the flagship site and any site with unusual requirements. Content can still be shared between them through syndication or the REST API.

Cost is rarely the deciding factor, but it is worth modeling honestly. For a network of 50 small, similar sites, Multisite typically reduces hosting and maintenance effort by half or more compared with separate installs. For ten large, divergent sites, the savings largely disappear, and the shared risk becomes the dominant consideration.

Migrating between the two

Organizations sometimes need to change direction. Moving a site out of a network into its own install involves exporting its tables, remapping users, copying uploads and rewriting URLs, and it is very manageable with planning. Consolidating many separate sites into a network is a larger project, because themes and plugins need to be standardized first. In both cases we plan migrations in waves, starting with the simplest sites to prove the process before touching high-traffic ones.

Our Multisite setup work covers new networks and the governance model around them, and our WordPress migration team handles consolidations and extractions. For either approach, a shared custom theme with brand-level tokens keeps sites consistent without copying code.

Get help choosing

List your sites, their traffic and who manages each one, and we will recommend a structure. Send us the details for a fixed-price quote within 24 hours.