Frequently Asked Questions

What Is Multi-Site CMS Management?

Multi-site CMS management refers to the technical and operational model by which a single agency manages multiple client websites from a centralised infrastructure and governance framework. Rather than treating each client website as an entirely separate, siloed entity — with its own hosting account, its own update process, its own security monitoring, and its own support workflow — a multi-site management model consolidates these functions into a shared system that the agency (or its white label development partner) operates at scale.

This model is distinct from WordPress Multisite, which is a specific WordPress feature that hosts multiple websites within a single WordPress installation sharing a single database and codebase. Multi-site CMS management, as a broader concept, can apply to any CMS platform and simply means that the agency has implemented standardised infrastructure, tooling, and processes for managing a portfolio of websites rather than managing each one in isolation.

For agencies, multi-site management is a significant commercial opportunity. Done well, it converts what would otherwise be disconnected, low-margin project work into a high-margin, recurring revenue model — one where the cost of management decreases as the portfolio grows, while the revenue per site remains constant or increases.

Multi-Site Architecture

The architecture underpinning multi-site CMS management varies depending on the platform, the scale of the portfolio, and the level of site isolation required by clients. However, the core architectural elements are consistent across most implementations.

WordPress Multisite

WordPress Multisite is a native feature that enables a single WordPress installation to host multiple sites, each with its own domain, admin dashboard, content, and theme. All sites share the same WordPress core installation, plugin codebase, and database (with separate table prefixes per site). A network administrator manages the overall installation, can activate themes and plugins for specific sites, and can apply updates across the entire network simultaneously.

WordPress Multisite suits agencies that manage a large portfolio of similar sites — franchise websites, regional microsites, or sites built on a shared template. It is not appropriate for sites that require different plugin sets, fundamentally different architectures, or strict data isolation between clients.

Managed Hosting With Centralised Tooling

The more flexible and commonly recommended approach for agency portfolios is to host each site separately — ideally on a managed WordPress hosting platform such as WP Engine, Kinsta, or GridPane — and use a centralised management tool to administer the portfolio. Tools such as MainWP, ManageWP, or WP Umbrella allow agencies to monitor uptime, manage updates, run security scans, and create backups across hundreds of sites from a single dashboard.

This approach preserves full site isolation — a problem on one site cannot cascade to others — while still delivering the operational efficiency of centralised management. It is the architecture most commonly recommended for agency multi-site management.

Headless Multi-Site

For agencies operating headless CMS portfolios, multi-site management takes a different form. Multiple front-end sites may share a single headless CMS back end (for example, a single Contentful or Sanity organisation with multiple spaces or projects), or each client may have their own CMS instance. The front-end applications are typically deployed via Vercel or Netlify, which provide their own portfolio management and deployment infrastructure.

Governance in a Multi-Site Model

Governance is the most critical success factor in multi-site CMS management. Without consistent governance, a growing portfolio becomes increasingly difficult to manage — update failures, security vulnerabilities, and performance degradation compound across sites. With strong governance, the portfolio becomes more efficient and more profitable as it scales.

Core governance requirements include a documented update policy that specifies when and how WordPress core, plugin, and theme updates are applied; a staging environment requirement so that updates are tested before being deployed to production; a backup policy with defined retention periods and tested restoration procedures; a security monitoring protocol covering malware scanning, failed login alerting, and vulnerability tracking; and an incident response process for handling site outages, hacks, or data loss events.

Agencies that white label their multi-site management to a development partner should require that the partner operates within this governance framework and provides monthly reporting against the agreed standards.

Technical Requirements

From a technical perspective, running a well-managed multi-site CMS portfolio requires investment in several key systems.

•       Centralised Monitoring: A real-time monitoring system that alerts the agency or development partner when any site goes down, returns a server error, or experiences a significant performance degradation. Tools like Better Uptime, Pingdom, or the monitoring features built into managed hosting platforms serve this function.
•       Automated Backup Infrastructure: Automated daily or hourly backups for each site, stored off-server, with a tested restoration process. Backups are the safety net that makes all other maintenance work less risky.
•       Staging Environments: Every managed site should have a staging environment that mirrors production. Updates, code changes, and new feature builds should always go through staging before being pushed to live.
•       Security Scanning: Regular automated scans for malware, file integrity violations, and known vulnerabilities. On WordPress, tools like Wordfence, Sucuri, or hosting-level security scanning provide this capability.
•       Update Management Tooling: A centralised tool that can identify outdated plugins, themes, or CMS cores across the portfolio and manage updates in bulk with rollback capability.
•       Access Management: Centralised management of admin credentials, with MFA enforced across all sites. Password management tools and single-sign-on solutions are valuable at portfolio scale.

The Commercial Opportunity

The commercial opportunity of multi-site CMS management for agencies is substantial. Consider the economics: a single web developer who manages 50 sites on a maintenance retainer at £200 per month per site generates £10,000 per month in revenue for work that, with the right tooling, requires 20-30 hours per month of actual technical time. Much of that time is automated.

The margin profile improves further when this work is fulfilled by a white label development partner. The agency sells the retainer to the client, retains a margin, and passes the fulfilment to the partner. The agency’s role becomes account management and reporting — low-cost activities that can be handled by non-technical staff.

At scale, agencies with 100 or more sites under management benefit from what might be called portfolio economics. The fixed cost of infrastructure, tooling, and management processes is spread across a larger base of revenue-generating sites. The incremental cost of adding a new site to the managed portfolio is very low, because the systems are already in place. This makes multi-site management one of the highest-margin revenue lines available to a digital agency.

Packaging is important in the commercial strategy. Agencies should offer tiered maintenance plans — for example, Basic (core updates, backups, uptime monitoring), Standard (all Basic plus plugin updates, security scanning, and monthly reporting), and Premium (all Standard plus performance monitoring, priority support, and a small development hours allowance). Tiered pricing allows clients to self-select based on their risk tolerance and budget, and gives the agency a clear upsell path.

Agencies that build a sizeable managed hosting portfolio also create a significant asset. A predictable, contracted recurring revenue stream is valuable not only operationally but commercially — it improves agency valuation multiples if the business is ever sold or acquires investment.