WordPress Multisite lets you run an entire network of WordPress sites from a single installation and a single dashboard, which is a genuinely different proposition from simply hosting several separate sites on one server. For agencies, developers and owners juggling a handful (or a few hundred) of related sites, it can slash maintenance to a single core update and one plugin library. The catch is that Multisite rewards control over your environment, and that is exactly what a UK VPS gives you. This guide walks through what Multisite actually is, when it is the right tool, and how to set it up and run it properly on your own server.
What Is WordPress Multisite?
WordPress Multisite is a native feature of WordPress core that turns one installation into a network capable of hosting many individual sites. Every site in the network shares the same WordPress files, the same plugin and theme directories, and the same database, but each gets its own content, users and settings. Instead of maintaining ten separate installs, you maintain one codebase. A new role, the Super Admin, sits above the usual site administrators and controls the network as a whole, while each site keeps its own day-to-day admin.
This is fundamentally different from running multiple standalone WordPress installations side by side. With separate installs, each site is fully independent, including its own version of WordPress. With Multisite, the network moves together: one update, one set of files, shared infrastructure.
When to Use Multisite (and When Not To)
Multisite shines when your sites are genuinely related and benefit from shared management. Think a university with departmental sites, a franchise with regional pages, a SaaS offering customer subdomains, or an agency running many client microsites that use the same curated set of themes and plugins. The shared codebase means a single security patch protects every site at once.
It is the wrong choice when sites need to be truly isolated. Because the network shares one database and one file tree, a fatal plugin conflict or a compromised site can affect everything. If each site needs different plugin versions, independent release cycles, separate backups you can restore in isolation, or the ability to be sold and migrated away on its own, you are better off with discrete installs. In that case, see our guide to hosting multiple separate websites on one VPS, which covers the Nginx, Docker and control-panel approaches to keeping sites fully independent on the same box.
Why a UK VPS Is Ideal for Multisite
Multisite leans on capabilities that restrictive shared hosting rarely grants. You need to edit wp-config.php and the web-server configuration, add wildcard DNS or per-domain SSL, and often bump PHP limits as the network grows. A VPS gives you root access to do all of this, plus the dedicated RAM and CPU a busy network demands rather than resources contended with strangers on an oversold server.
Running on a UK VPS adds data residency and low latency for British visitors, which helps both user experience and search performance for UK-focused sites. You also control the web server itself, so you can pick the stack that suits you best; our comparison of LiteSpeed, Nginx and Apache for WordPress is a useful starting point before you commit a network to one configuration.
Subdomains vs Subdirectories vs Mapped Domains
At setup you must choose how network sites are addressed, and the subdomain-versus-subdirectory decision is effectively permanent once content exists. Domain mapping, by contrast, has been part of core since WordPress 4.5, so you can attach real custom domains to any site regardless of the structure you pick.
| Approach | Example URL | DNS / server needs | Best for |
|---|---|---|---|
| Subdomains | site1.example.com | Wildcard DNS (*) and ideally wildcard SSL | Networks that add sites dynamically |
| Subdirectories | example.com/site1 | Nothing extra beyond the main domain | Content hubs under one brand |
| Mapped domains | site1.co.uk | Each domain pointed at the VPS plus its own SSL | Client sites needing their own brand |
A VPS makes the subdomain route painless because you can create a wildcard DNS record and provision a wildcard SSL certificate, so new sites work instantly without touching the server for each one.
How to Set Up WordPress Multisite on a UK VPS
Enabling the network is a controlled process rather than a single click. Work on a staging copy first if you can, and always take a full backup before you begin. Note that you cannot activate Multisite if any plugins are network-wide active, so deactivate plugins first.
Enabling WordPress Multisite Step by Step
- Back up your files and database in full, and deactivate all plugins.
- Add the allow-multisite constant to
wp-config.phpabove the “stop editing” line, then reload. - Go to Tools → Network Setup, choose subdomains or subdirectories, and run the installer.
- Add the generated network constants to
wp-config.phpand update your Apache.htaccessor Nginx rewrite rules as instructed. - Log back in, open the Network Admin dashboard, and configure settings, then add your first sites.
The first edit is the one that unlocks the Network Setup menu:
/* Enable Multisite */
define('WP_ALLOW_MULTISITE', true);After running Network Setup, WordPress generates a second block of constants (defining MULTISITE, SUBDOMAIN_INSTALL, the domain and path) to paste in. If you ever get stuck, the official WordPress Multisite documentation lists the exact values for both Apache and Nginx setups.
Mapping Custom Domains to Network Sites
Because domain mapping is built into core, giving a network site its own domain is straightforward. Point the domain’s A record (or CNAME) at your VPS, then in Network Admin edit the site and set its domain to the custom one. On the server, make sure the web server answers for that hostname and that a valid SSL certificate exists for it. With a VPS you can automate certificate issuance for each mapped domain using a tool like Certbot, so onboarding a new client domain is a couple of minutes rather than a support ticket.
Keep in mind that mapped domains still live inside the same network, so they share the codebase and database. The mapping changes only how visitors reach the site, not how it is maintained behind the scenes.
Managing and Securing Your Network
The Super Admin controls everything network-wide: which themes and plugins are available, who the users are, and when core updates run. Plugins and themes are installed once and then network-activated, or made available for individual site admins to switch on. This central control is the whole point, but it also concentrates risk, so good hygiene matters more, not less.
Be selective about plugins: some are simply not Multisite-compatible, and a poorly behaved one affects every site. Vet each addition on staging. For security, harden the single login surface with strong credentials and two-factor, keep the whole network patched promptly (one update covers all sites), and take regular backups that capture the shared database and the uploads tree, which splits into per-site folders under wp-content/uploads/sites/. Remember there is no built-in per-site resource cap, so one heavy site can consume the network’s RAM and CPU.
Performance and Scaling on a VPS
A network’s database grows quickly because WordPress creates a fresh set of tables for every site added, so the shared database can balloon into hundreds of tables. Plan for that. Page caching at the server level and a persistent object cache both make a big difference under load; our breakdown of object caching with Redis, Memcached and APCu explains which backend suits a busy network and how to wire it into Multisite.
Right-sizing the server is the other half. A few low-traffic brochure sites are happy on a modest plan, but a large or busy network needs headroom in RAM, CPU and fast NVMe storage. Use our VPS sizing guide to estimate requirements, and the buyer’s guide to choosing the right VPS plan to match that to a package you can grow into as the network expands.
Run your WordPress Multisite network on a UK VPS
UK Speed NVMe VPS plans give you full root access, dedicated AMD EPYC cores, enterprise NVMe and a UK data centre — everything a Multisite network needs for wildcard DNS/SSL, object caching and room to grow. Pick a plan and build your network with confidence.
Conclusion
WordPress Multisite is a powerful way to run a family of related sites from one installation, and a UK VPS gives it the root access, resources and DNS/SSL control it needs to run cleanly. Choose it when your sites genuinely benefit from shared management, and reach for separate installs when isolation matters more.
- Decide whether Multisite or separate installs fit your sites.
- Pick subdomains or subdirectories deliberately, since the choice is permanent.
- Back up, enable the network on staging, then go live.
- Size your VPS and add object caching before traffic grows.
