WordPress Multisite vs Separate Sites: Which Should You Use?

Use WordPress Multisite when you run several similar websites with one team and want to update, secure and design them in one place. Use separate WordPress installations when the sites belong to different brands or owners, need different plugins, or might one day go their own way.

This guide is for business owners, marketing leads and agency teams who have been told they need “a network” and want to know whether that is true before paying for it. It covers how Multisite really works, a decision table, the hidden costs, the URL choice you cannot easily undo, and a simpler option many teams overlook.

How WordPress Multisite works, in plain terms

A Multisite network is one WordPress installation that serves many websites. The official WordPress documentation describes the sites as virtual: they share the core files and can share plugins and themes, but each one gets its own database tables and its own folder for uploaded media.

Four things change compared with a normal site:

• A new top role. The Super Admin manages the whole network. Each site still has its own administrators, editors and authors.
• Plugins and themes are installed once. Only the Super Admin can install them. Site administrators can switch on what is already installed, but cannot add anything new.
• User accounts are shared. There is one list of people for the whole network, and each site decides who has a role on it. One person can be an editor on three sites with one login.
• Updates happen together. Updating WordPress, a plugin or a theme updates it for every site in the network on the same click.

That last point is the whole trade-off in one line. Central updates save hours when everything works, and spread a problem to every site when something breaks.

WordPress Multisite vs separate installations: the decision table

Most decisions come down to how alike the sites are and who controls them. Read across the rows that matter to you. If most of your answers land in the right-hand column, separate sites will cost you less trouble over the years.

Question	Multisite fits	Separate installs fit
How similar are the sites?	Same design, same features, different content	Different designs, features or audiences
Who runs them?	One team or one company	Different owners, clients or departments with their own budgets
Do they need different plugins?	Rarely; one shared toolkit is fine	Often; one site needs a store, another a booking system
Could a site be sold or handed over?	No, they stay together	Yes, or you are not sure
How bad is shared downtime?	Acceptable for the whole group	One site’s problem must never touch the others
Hosting	A host that supports Multisite on your plan	Any WordPress host, chosen per site
Number of sites	Many, with new ones added regularly	A few, added rarely

The WordPress documentation itself asks “Do you really need a network?” before explaining setup. Its point is worth repeating: if you only want different sections to look different, or different groups of people to see different things, a single site with the right theme or permissions setup can usually do it.

When Multisite is the right call

Multisite earns its extra setup when you have many sites that are close copies of each other and one team looking after all of them. Typical good fits:

• Franchise and multi-location groups where each location needs its own site with local staff editing it, but head office must control the design, the legal pages and the brand. Our franchise and multi-location website work starts from this question.
• Universities, schools and membership bodies with dozens of department or chapter sites that follow one template.
• Language or country versions run as separate sites on one network, when each market has its own editor and content that is not a straight translation.
• Groups that add new sites often. Creating a site in a network takes minutes, with the theme and plugins already in place.

In each case, the value comes from sameness. The more each site needs its own design, plugins or rules, the more of Multisite’s advantage disappears.

When separate WordPress sites are better

Separate installations are safer whenever the sites have different owners, different futures or different technical needs. Choose them when:

• The sites are different businesses or brands. If you might sell one brand, its website should be able to leave with it on the day of the sale.
• You are an agency hosting client sites. Putting several clients on one network ties their uptime, security and update schedules together, and makes it hard to hand a site back when a client leaves. Our checks for choosing a white-label WordPress partner include who owns each site, for the same reason.
• One site needs heavy or unusual plugins. A large WooCommerce store, a learning platform or a membership system is easier to run, cache and back up on its own.
• Security or compliance rules differ. A network shares one database and one list of user accounts. If one site handles health, legal or payment data with stricter rules, keep it apart.
• Different people need full admin rights. On a network, only the Super Admin can install a plugin. Teams used to adding their own tools find this frustrating quickly.

Running several separate sites does not mean logging in to each one every day. Management dashboards such as MainWP or ManageWP let one person update and back up many independent sites from one screen, without joining them into a network.

The option most teams miss: one site with sections

For many multi-location and multi-brand businesses, the best answer is neither a network nor several sites. It is one normal WordPress website with a section for each location or brand.

One site means one domain building search strength, one place to update, one care plan and one set of analytics. Each location still gets its own page with its address, team, services and reviews, and local editors can be limited to their own pages with user roles. This is also the setup Google handles most easily for local search, as long as every location page is genuinely different and not the same text with a new town name.

From our projects: For Norske, an industrial tool brand, we built a custom multi-brand system with structured product management inside one WordPress and WooCommerce site. It was a Figma-to-WordPress build delivered in 4 to 6 weeks. The project shows that several brands do not automatically mean several WordPress installations: when the brands share one catalog, one checkout and one team, a single site keeps all of that in one place.

A single site stops being the right fit when each location needs its own domain, its own design or its own store and checkout. That is the point where Multisite or separate sites become worth the extra running cost.

Subdomains, subfolders or separate domains

Every network must choose how its sites are addressed, and changing it later is hard. There are two network types, plus domain mapping on top:

Setup	Example address	Good for	Watch out for
Subfolder (path-based)	example.com/boston	Locations or departments under one brand	On an existing site, blog post URLs on the main site gain a /blog/ prefix
Subdomain (domain-based)	boston.example.com	Clearly separate sections under one brand	WordPress must sit at the root of the domain; open sign-ups need wildcard DNS
Mapped domain	bostonplumbing.com	Separate brands or countries run by one team	DNS and an SSL certificate for every domain; login cookies may need extra settings

Two rules from the WordPress documentation surprise people who convert an existing site. First, you cannot choose the subfolder type if your WordPress site has been set up for more than a month, because of conflicts with existing permalinks. Second, on a subfolder network the main site’s posts move to a /blog/ path, and removing it needs manual configuration that WordPress does not recommend.

If your current site already ranks, that second rule matters. Changed post addresses need a careful move with every old URL redirected, or you risk losing the search traffic you have built. Since WordPress 4.5, domain mapping is built in, so separate domains no longer need a plugin.

What a WordPress Multisite really costs to run

The software is free, so the cost sits in work and services around it. Plan for these before you commit:

1. Setup. Server rules for rewrites, DNS and SSL for each domain, and choosing plugins that work network-wide. A theme or plugin that works on a single site can still misbehave on a network.
2. Hosting. The host must support the network type you choose. Shared and budget plans may limit it, and a busy network concentrates all your traffic on one installation.
3. Plugin licences. Premium plugins are often priced by the number of sites, and a subsite usually counts as a site. Read each licence before you build twenty locations on it.
4. Backups and restores. Restoring one subsite without rolling back the others needs a backup tool that understands networks. Test a single-site restore before you need one.
5. Updates. Every update should be tested on a staging copy of the whole network first, because a fault reaches every site at the same time.

For comparison, separate sites have a simple, visible cost. Our WordPress care plans start at $49 a month and are priced per website, so four separate location sites on the Essential plan cost 4 × $49 = $196 a month for updates, daily backups, security scans and uptime monitoring. One site with four location sections needs one plan. There is no separate Multisite plan on our pricing page; a network is quoted in writing once we know how many sites it holds and how different they are.

Build costs for the three routes

Here is how the three routes compare for a business with four locations, using our published WordPress prices. These are build prices only; hosting, domains and premium plugins are paid by you directly.

Route	What you build	Published starting price
One site with location sections	Growing Business plan: up to 12 individually designed main pages, so room for four location pages	$1,690
Separate sites	Four Small Business sites, each with up to 6 main pages	$890 per site
Multisite network	One shared design, network setup, one site per location	Quoted on your site list
Larger groups	25 or more pages, several languages or bookings	Large Site plan from $2,990

If you are still choosing a platform for the whole group, our guide to WordPress.com vs WordPress.org explains why a self-hosted install is needed for Multisite in the first place, and our WordPress development packages list exactly what each plan includes.

WooCommerce on a Multisite network

WooCommerce works on Multisite, but each site runs its own store. Products, orders, settings and payment accounts are separate per site, and adding a product to one store does not add it to the others.

WooCommerce’s own article on running multiple stores on one installation notes that shared inventory or shared product data needs a separate connection, and that each store needs its own WooPayments account. If what you want is one catalog shown in several countries or currencies, a single store with currency and language tools is often simpler than a network of stores.

Questions to settle before anyone builds a network

Ask these on your first call with a developer. Clear answers prevent the most expensive mistakes.

1. Which plugins will every site need, and has each been tested on a network?
2. Will the sites use subfolders, subdomains or their own domains, and what happens to any existing URLs?
3. Who is the Super Admin, and what can each site’s own team change without asking?
4. How will one site be restored from backup without affecting the others?
5. If one site ever has to leave the network, what does that move involve and who pays for it?
6. Does our hosting plan support Multisite, and what happens when traffic grows?

Sources checked on November 6, 2026: WordPress Advanced Administration Handbook pages Before You Create A Network, Create A Network and Multisite Domain Mapping (last updated October 14, 2026); WooCommerce.com article on building multiple stores on a single WordPress installation; current WordPress release 7.1.4 from the WordPress.org version API. Attors prices from our pricing page on the same date.

Get the structure right before the first site goes live

Attors Technologies is a web development agency that builds and maintains WordPress websites for businesses and agencies in the US, UK and Europe. Send us your list of sites, who edits each one and what they need to do, and we will tell you whether a network, separate sites or one site with sections fits best, with a fixed written quote before any work starts.

Plan your WordPress sites with us