When an agency starts managing several WordPress sites for different clients, the question of consolidation eventually comes up: rather than multiplying separate installations, wouldn't it be better to group everything under a single technical structure? WordPress actually offers a native feature for this, called Multisite, which lets several sites run from a single installation, sharing the same core software, the same database, and a common pool of plugins and themes.
What Multisite actually changes
With Multisite enabled, a network dashboard oversees every site, while each site keeps its own content, settings, and users. A plugin update applied at the network level automatically rolls out to every site using it, which is the main argument in its favor: instead of updating twenty separate installations one by one, a single action covers the whole network.
Why this advantage sometimes backfires
This centralization, which at first glance looks like an obvious time saver, becomes a risk as soon as the managed sites do not share exactly the same needs. An incompatible or buggy plugin can affect the entire network rather than a single isolated site, turning a minor incident into a widespread outage hitting several clients at once. WooCommerce in particular remains known for compatibility issues in a Multisite context, which strongly limits this architecture for an agency where some clients run an online shop.
The real obstacle: how different client needs actually are
The main problem is not technical but organizational. Multisite works well when the managed sites closely resemble each other, with the same plugins, the same type of theme, and similar functional needs. An agency whose clients run very different businesses, a craftsman with a simple showcase site, a medical practice with an appointment booking system, a merchant with an online shop, quickly ends up managing exceptions and diverging configurations within an architecture designed for uniformity, which cancels out much of the initial benefit.
The client's loss of autonomy
A client whose site is part of a Multisite network cannot simply take their site and hand it to another provider or a different host without a non trivial technical migration, unlike a standard, independent WordPress installation. This dependency deserves to be clearly anticipated and acknowledged in the contractual relationship with the client, since it limits their future freedom in a way that may not be obvious at setup time.
The widely recommended alternative today
For the vast majority of agencies managing client sites with varied needs, the generally recommended approach is to keep fully separate, independent WordPress installations, while centralizing their oversight through a dedicated multi site management tool, such as ManageWP, MainWP, or equivalent alternatives. These tools let you monitor updates, backups, and security across several sites from a single dashboard, without sharing code, database, or plugins between sites, which preserves each client's technical isolation and autonomy while keeping most of the sought after time savings.
The cases where Multisite still makes sense
Multisite remains relevant in specific contexts: a network of regional microsites for a single brand, a franchise with several locations sharing an identical identity and features, or an internal structure managing several departmental sites within a single organization. In these cases, the uniformity of needs fully justifies pooling resources, provided the technical resources needed to properly administer this more demanding architecture than a simple installation are available.
Points to verify before publishing: confirm that compatibility issues between WooCommerce and Multisite remain current for recent versions of both software at the time of publication, and check that the multi site management tools mentioned (ManageWP, MainWP) remain commonly used market references.