WordPress multisite: a site factory for your brands and subsidiaries.

What WordPress Multisite actually enables

WordPress Multisite is an installation mode that lets you manage multiple independent sites from a single admin interface and a single codebase. Each site has its own content, its own users, and its own domain or subdomain, but they all share the same WordPress core, the same plugins, and the same base theme.

That shared infrastructure is where the value lies. Updating WordPress or a plugin across the entire network takes the same time as a single-site update. Deploying a new site for a subsidiary or a brand takes a few hours instead of several days. That is the central argument for what is often called a site factory: shared infrastructure, fixed maintenance cost, fast deployment.

Use cases: who needs WordPress Multisite

• Groups with multiple subsidiaries: each entity has its own site with its own brand and content, centralized governance
• Franchise networks: national site plus local pages managed by franchisees with limited editorial rights
• Holding companies with multiple brands: separate sites but shared technical infrastructure, maintenance savings
• Public or non-profit organizations: multiple themed portals under a single administration system
• Agencies managing their own clients on shared infrastructure
• Multilingual sites with a subdomain per language (fr.example.com, en.example.com)

Multisite network architecture: decisions to make from the start

WordPress Multisite is installed either in subdomain mode (site1.brand.com, site2.brand.com), subdirectory mode (brand.com/site1, brand.com/site2), or with independent domains via domain mapping. This choice is irreversible after installation: it determines SEO structure, SSL certificate management, and DNS configuration.

Domain mapping is the most flexible but most complex configuration to maintain: each domain requires its own SSL certificate and DNS configuration. For a network of ten sites, this is still manageable. Beyond twenty or thirty sites with manually managed certificates, automation via Let's Encrypt and a reverse proxy becomes essential.

Multisite limitations to understand before committing

Multisite is not suited to every multi-site scenario. The main limitations: plugins cannot be selectively activated per site in a granular way (a network-active plugin is active on all sites), performance issues on one site can affect the entire network if hosting is not properly configured, and migrating an individual site out of the network is technically complex.

• A plugin generating heavy load on one site can slow down the entire network
• Plugins activated at the network level apply to all sites: no per-site selective configuration without custom code
• Migrating an individual site out of the network requires a specific export (dedicated migration plugin)
• Some popular plugins are not Multisite-compatible or behave differently in network mode
• Media storage is shared or partitioned depending on configuration: this must be decided at the start of the project

Budget and return on investment of a site factory

Setting up a WordPress Multisite network for a group with 5 to 15 sites is a structural investment, priced according to design complexity and the level of editorial governance to put in place. The scope includes technical architecture, network theme development, configuration of the initial sites, and super-admin training.

The return on investment is measurable: centralized network maintenance costs significantly less than site-by-site maintenance. The initial investment is typically recovered in 2 to 3 years, not counting savings on the time to deploy new sites.