A company with offices in several cities. A franchise network. A holding group with multiple brands. A university with separate faculty websites. An agency maintaining sites for its clients. Each of these organizations faces the same challenge: how to manage several or dozens of websites without maintaining a separate WordPress installation for each one. The answer is WordPress Multisite. One installation, one Super Admin dashboard, shared updates, plugins, and themes, yet separate content, media, and users for every site in the network.
At WebOptimo we deploy, maintain, and optimize Multisite networks containing dozens of sites. We handle configurations with subdirectories, subdomains, and custom domain mapping. You can read more about the technology itself in our WordPress Multisite knowledge base article.
A set of features we configure as standard in every Multisite deployment. Each element is designed with network security, performance across multiple sites, and ease of daily management in mind.
Multisite introduces an additional management layer: the Super Admin role, which governs the entire network, alongside individual site administrators with restricted permissions. We configure granular access so that a branch administrator can manage the content of their own site but cannot access network settings, install plugins, or view content belonging to other sites. For larger organizations we also create custom roles with precisely defined capabilities.
Plugins and themes in Multisite can be activated globally (for the whole network) or individually (for selected sites). The Super Admin controls which plugins are available to site administrators and which are reserved at the network level. We test every plugin for Multisite compatibility before deployment, because not all WordPress extensions handle the Multisite architecture correctly.
Every site in the Multisite network has its own technical SEO settings: unique meta tags, a separate XML sitemap, its own schema.org structured data, and an independent indexing configuration. We set up correct canonical URLs and hreflang tags for multilingual sites so that search engines treat each site in the network as a standalone entity with its own SEO profile.
Multisite security requires a specific approach because a vulnerability in a single plugin can affect every site in the network. We deploy a network-level WAF firewall, brute-force login protection, isolation of upload directories between sites, daily malware file scanning, two-factor authentication for the Super Admin, and separate backups of individual sites with the ability to restore a single site without impacting the rest of the network.
A Multisite network with dozens of sites generates far heavier database load than a single WordPress installation. InnoDB buffer pool tuning, Redis object cache configuration, PHP-FPM process pool optimization, image compression to WebP/AVIF, and Core Web Vitals configuration are a standard part of our deployment. Every site in the network must load quickly regardless of traffic on the other sites.
We configure separate Google Analytics 4 properties and Google Tag Manager containers for each site in the network, or a single GA4 property with separate data streams. Each site gets its own conversion, goal, and event tracking. For networks running advertising campaigns, we deploy ad pixels (Meta, Google Ads, LinkedIn) assigned to specific sites so that conversion data never bleeds between them.
Each site in a Multisite network may collect personal data from different user groups and be subject to different privacy policies. We configure a GDPR-compliant cookie banner, separate privacy policies and data-processing notices for each site, forms for exercising data-subject rights (access, deletion, portability), and consent collection in contact forms. Sites in the network remain legally independent from one another.
Multisite is a natural solution for organizations that need websites in several languages. Each language version operates as a separate site in the network with its own content, SEO meta tags, and hreflang configuration. Unlike multilingual plugins (WPML, Polylang) installed on a single site, the Multisite approach provides full content isolation between language versions and greater flexibility in configuring each one.
WordPress Multisite is an architecture that demands server-side experience. Smaller networks run well on properly configured shared hosting, but larger installations with dozens of sites and heavy traffic require a dedicated server with full control over the environment. Regardless of scale, it is the infrastructure configuration that determines whether Multisite becomes a convenient management tool or a daily source of performance headaches.
Larger installations with dozens of sites and significant traffic run on dedicated servers or VPS instances where we have full control over the infrastructure. When performance requirements are highest, we configure a stack built on Nginx + PHP-FPM + MariaDB + Redis, which we describe in our article on efficient server stack architecture. Redis as an object cache eliminates repetitive database queries generated by dozens of sites simultaneously, while PHP-FPM is tuned with enough worker processes to handle multiple sites in parallel.
Every site in a Multisite network creates its own set of database tables. With dozens of sites the database holds hundreds of tables, which calls for careful tuning. We configure InnoDB buffer pool sized to the database, optimize indexes, clean revisions and transients across all sites, and monitor slow queries through the slow query log. More on MySQL and MariaDB administration on the dedicated page.
Linux server administration for Multisite covers Apache VirtualHost configuration for every domain in the network, SSL certificate management (automated Let's Encrypt renewals for dozens of domains), firewall configuration, SSH hardening, task automation (cron, WP-CLI), and resource monitoring. On FreeBSD servers we work with an analogous setup adapted to that platform.
Updating a plugin in Multisite affects every site at once. That is why we test every update on a staging environment that mirrors the production network. We verify plugin compatibility with the Multisite architecture, check the performance impact, and confirm that no site in the network has lost functionality. Only after successful testing do we deploy the change to production.
Multisite is not a one-size-fits-all solution. It works very well in certain scenarios but falls short in others. Below we describe situations where Multisite delivers real benefits, and those where a different architecture is the better path.
An organization running several or a dozen websites for regional offices, brands, or product lines. Centralized update management, a shared visual and security standard, and at the same time full content independence for each branch. Every site can run on its own domain while preserving brand identity.
A university with separate sites for faculties, departments, research projects, and administration. Local government bodies with sites for subordinate institutions. Multisite lets you maintain a uniform technical standard and meet GDPR and accessibility (WCAG) requirements at the network level, rather than configuring each installation separately.
An agency managing client websites can maintain them in a single Multisite network with centralized update and security management. The administrative time savings across dozens of sites are substantial. Each client has a separate site with its own content, while the agency controls the infrastructure from one Super Admin dashboard.
Multisite is not a good choice when each site requires a completely different set of plugins or a different PHP version. It is also not the right solution when sites have fundamentally different technical requirements, or when the teams managing individual sites need full independence including the ability to install their own plugins. In such cases, separate WordPress installations with independent technical care for each site work better.
WordPress Multisite is an architecture that, when deployed correctly, radically simplifies the management of multiple websites. We manage Multisite networks containing dozens of sites. From initial analysis, through deployment and migration, to daily technical care and server administration. A single Multisite deployment can replace dozens of separate WordPress installations, and the time spent on administration drops by an order of magnitude.
WordPress Multisite is a built-in WordPress feature that lets you run and manage multiple websites from a single installation. All sites in the network share the WordPress core, plugins, and themes, while each site maintains its own content, media, users, and database tables. Everything is managed from a single Super Admin dashboard.
Multisite is a strong fit for organizations managing multiple websites: companies with regional branches, franchise networks, holding groups with several brands, universities with separate faculty sites, agencies maintaining client websites, and publishers running multiple themed portals. The common thread is the need to manage several or dozens of sites from a single place.
There is no hard technical limit on the number of sites. We manage Multisite networks with dozens of sites. The key factor is matching the server infrastructure to the scale of the network: sufficient RAM, CPU power, properly configured MySQL/MariaDB, Redis object cache, and PHP-FPM tuned for concurrent handling of multiple sites.
Yes. WordPress Multisite supports three addressing modes: subdirectories (example.com/site), subdomains (site.example.com), and custom domain mapping (site.com). We configure domain mapping, SSL certificates for each domain, and the appropriate DNS records so that every site in the network operates under its own address.
Not all WordPress plugins are compatible with Multisite. Updating a shared plugin affects every site at once, which makes staging tests essential. A failure at the core or database level impacts the entire network. Migrating a single site out of the network is more complex than with a standard installation. Server requirements also grow with the number of sites.
Yes. We migrate standalone WordPress installations into Multisite networks, bringing over content, media, users, plugin configurations, and SEO settings. We also handle the reverse: extracting a site from a Multisite network into an independent WordPress installation. In both cases we ensure continuity of service and full data integrity.
Yes. Multisite places higher demands on server resources than a standard WordPress installation. With dozens of sites you need more RAM, a higher-performance database, properly configured PHP-FPM (more worker processes), Redis object cache, and often a VPS or dedicated server instead of shared hosting. We advise on hosting selection and configure the server to meet Multisite requirements.
Yes. We offer WebOptimo WordPress Care plans tailored to the specifics of Multisite: core and plugin updates tested on staging first, daily backups of the entire network and individual sites, uptime monitoring for every site, security scanning, and technical support. Networks deployed by WebOptimo receive a 50% discount on care for the first year.
Managing multiple WordPress sites and considering consolidation? Planning a Multisite deployment from scratch? Tell us about your needs. We will prepare a proposal tailored to the scale and specifics of your organization.
VAT ID: PL6391758393
