Glossary · Corporate & Marketing Websites

WordPress multisite

A WordPress multisite is a single WordPress installation that runs multiple distinct websites, each with its own content, users, and sometimes its own domain, from one shared core and one shared database. The feature is built into WordPress as a network of sites, and it lets multiple brands, countries, or subsidiaries share maintenance, themes, and plugins. It differs from a standard multilingual site: each site in the network stays an independent content entity, with its own pages and its own editorial team.

Updated on July 10, 2026 · Bertrand Dumast

How a WordPress multisite network works

Multisite is switched on in the WordPress configuration file and creates a network managed by a super admin account. Each site in the network has its own content, its own settings, and usually its own database tables, but every site shares the same WordPress core, the same installed themes, and the same plugins. The super admin activates themes and plugins at the network level, then each site admin picks which ones to use on their own site.

When it makes sense

  • Several brands under one group that share a maintenance team and a technical foundation, without necessarily sharing editorial content.
  • Country or language versions of the same site, when the content structure stays similar across markets.
  • A network of agencies or subsidiaries that each need a site, built on a shared template with centralized control over security updates.
  • Event or temporary microsites that get spun up and retired often, without provisioning new hosting every time.

When separate sites are the better call

Multisite also pools the risk. A vulnerable or poorly coded plugin exposes the whole network, not just the one site running it. A theme update validated on one site can break the display on another once their needs have drifted apart. If the brands do not share the same governance or the same update cadence, or if one of them may need to move to a different host independently down the line, separate WordPress installations, possibly built on a shared custom WordPress theme, avoid that coupling.

Governance to put in place

  • Decide who holds the super admin role and who manages each site in the network day to day.
  • Set a shared update policy for plugins and WordPress core, tested before it rolls out network-wide.
  • Scope access rights per site so a local admin cannot change settings for the whole network.

Smartshift scopes the technical architecture and governance of your WordPress multisite before the first line of code gets written.

Questions
Does a WordPress multisite cost more to maintain than a standard site?

Not necessarily. Maintenance runs on a single WordPress core installation instead of several, which cuts the time spent on security updates. On the other hand, governance overhead grows with the number of sites in the network and how different their needs are.

Can an existing site be migrated into a multisite network?

Yes, but the move requires merging content into a network structure and checking that existing plugins are compatible with a multisite setup. It should be planned as its own project, with a staging environment before going live.

What happens if one site in the network needs to move to a different host?

That is the structural limit of multisite: every site in the network shares the same hosting and the same WordPress core. Splitting one site out of the network means a full technical migration, not a simple settings change.

A project where WordPress multisite comes into play?

Send us your context. We tell you where to start, with a concrete first opinion and no commitment.

Get advice on my project