Insights · Nov 9, 2026 · 4 min read · FAQ

Should your brands and regional sites share one WordPress multisite?

A multisite network shares one install, database and plugin set across your brands. What that gives you, what it ties together, and when to keep sites apart.

MULTISITE OR NOTSeveral brands on WordPress SELLWRIGHT

Once a business runs several brands, or a site for each region, the WordPress question arrives: one multisite network, or a separate install for every site? A network turns many sets of updates and logins into one, but it also ties the sites together in ways that are slow to undo, so know what is shared before switching it on.

What does a multisite network share?

A network shares one set of WordPress core files, one database and one pool of user accounts, while each site keeps its own content. Each site gets its own database tables and its own uploads folder. Themes and plugins are installed once for the whole network: a plugin can be network activated, which turns it on everywhere, or activated site by site, and each site picks its own theme from the ones made available to it.

Content is not shared by default. WordPress describes the sites as separate, much like separate blogs on WordPress.com, so publishing one article on several brand sites needs a plugin or a copy.

Who is in charge of what on a network?

The Super Admin runs the network, and each site's Administrator runs only that site. On a network, site Administrators cannot install themes or plugins, run core, theme or plugin updates, or edit their users' profiles. They can only switch plugins on or off if the Super Admin enables the Plugins menu for them in Network Settings.

So a regional marketing lead still asks the Super Admin for every new plugin. That is good governance when someone owns the network, and a bottleneck when nobody does. For who should get which role, see WordPress user roles for a marketing team.

Subdomains, subdirectories or a domain for each brand?

Every network is either domain-based or path-based, and any site can also be mapped to its own domain. Mapping has been built in since WordPress 4.5, though WordPress's planning guide still suggests a plugin for it. A domain-based network (a sub-domain install) gives sites like uk.example.com; a path-based one (a sub-directory install) gives example.com/uk/. To map a brand's domain, point it at the server in DNS, then enter the full URL as that site's address in Network Admin. WordPress says every mapped domain should have SSL, so admin logins stay encrypted.

Converting an existing site has two catches. If the main site has published content older than a month, WordPress normally requires a domain-based network. And in a path-based network, posts on the main site gain an extra /blog/ in their URLs. Switching types later is, in WordPress's words, an advanced operation. If the regional sites are language versions of each other, plan their hreflang tags as a separate job.

What should you check before choosing multisite?

Check four things before any setup work.

  • Plugins: WordPress warns that not every plugin in its directory works on a network, so check each plugin's page or ask its developer. Whether a plugin keeps its settings network-wide or per site depends on how it is written.
  • Hosting: multisite needs URL rewriting. WordPress generates the rules for Apache and IIS but not for Nginx, and shared hosting may rule out some network types.
  • Updates: core, theme and plugin updates run once from the Network Admin Updates screen and reach every site using that code at the same time.
  • Shared code: edit a theme's code and you change it for every site using that theme. Style changes made in the Site Editor stay on one site.

Back up the database and files, then try the conversion on a copy first. WordPress notes that a test site on your production server is sometimes more useful than a development server, which cannot always match production exactly.

When does multisite fit, and when are separate installs better?

Multisite fits sites that one team runs on a shared theme and plugin set; separate installs fit brands that change on their own schedule. Multisite tends to fit when:

  • One team or agency manages every site and updates them together.
  • The sites share a theme and most plugins but carry different content, the regional use case WordPress itself describes.
  • You often launch regional or campaign sites from the same setup.

Separate installs tend to fit when:

  • One brand runs a much heavier plugin stack, such as a full online store, or must hold back an update.
  • The brands have different owners, agencies or hosts, or one may be sold later.
  • A failure on one brand's site must never reach the others.

For one brand with a few regional sections, a single ordinary site may be enough. WordPress's own guide says a network might not be the best solution for sites that are strongly interconnected or share data.

Can a site leave the network later?

Yes, but it is a migration project, not a setting. The site's content sits in its own tables and its media in its own uploads folder, while its user accounts, plugins and themes belong to the network. Moving out means a new install, then content, media, users, plugins, settings and redirects. WordPress notes that widget configuration and plugin settings are not included when you export a site from Tools, Export, so those are rebuilt and checked by hand.

Where to start

List every site with its owner, theme, plugins, host and update routine. If the lists mostly match and one team runs them all, a network is worth testing on a copy; if they differ, separate installs will be easier to live with. Our WordPress development team can review your sites and plan either route, or start with a website review.

FAQ

Frequently asked questions

Can each site on a multisite network have a different theme?

Yes. Themes are installed once for the network, and the Super Admin decides which ones each site may use, either network-wide or site by site. Each site then activates its own. Making a theme available to the network does not switch it on anywhere, and a site keeps its active theme even if the Super Admin later disables that theme for the network.

Does each person need a separate login for every site on the network?

No. User accounts are stored once for the whole network, so one person can have a single login and a role on several sites, for example Editor on one brand and Author on another. A new network account has no access to any site until it is given a role on that site, and each site sets its own roles.

Can we merge our existing WordPress sites into one network?

Yes. WordPress documents a route: create the network, add a site for each brand, export each old site's posts and pages from Tools, Export, and import the file into the matching new site, mapping authors to users. Widget configuration and plugin settings are not included in that export, so note them down before the old sites are switched off.

Do all sites on a network run the same WordPress version?

Yes, because they share the same core files. After a core update, the Super Admin runs Upgrade Network, which steps through the sites five at a time and applies any database changes. Sites that are deactivated, archived or marked as spam are skipped, and each is upgraded when an admin logs in to its dashboard after it is restored.

Can we take one regional site offline without deleting it?

Yes. On the Network Admin Sites screen, a Super Admin can deactivate or archive a site, which WordPress treats as effectively the same thing, and activate it again later. Delete is a separate action that removes the site, so choose deactivate or archive when a market is paused rather than closed for good.

Next step

Ready for a website that sells?

Book a short call. We will look at your current site, agree what matters most and send a written scope with a fixed quote.

Book a callOr write to hello@sellwrightstudio.com