WordPress Multisite Needs a Server That Is Set Up for It
WordPress multisite server setup is the full configuration of your VPS to run a network of sites from one install, covering wildcard SSL, web server routing, DNS, domain mapping, database tuning and caching. Built as a solid foundation so every new sub-site works reliably.
Wildcard SSL for Subdomain Networks
Let's Encrypt wildcard SSL certificates configured via DNS challenge so every new sub-site in your network gets HTTPS automatically.
Web Server Configuration for Multisite
Nginx or OpenLiteSpeed configured with multisite-specific rules covering subdomain routing, upload directories, and dynamic sub-site handling.
Wildcard DNS Setup Guidance
We configure or guide you through wildcard DNS records so subdomain-based multisite sites resolve correctly without individual DNS entries for each.
Domain Mapping Configuration
Server-level setup for custom domain mapping so individual sites in your network can use their own domains rather than subdomains.
Database Tuning for Multisite Scale
MySQL or MariaDB configured with appropriate InnoDB settings, query optimisation, and connection handling for multi-site database structures.
Multisite-Compatible Caching
Page caching and object caching configured correctly for multisite, with separate cache partitions per site and no cross-site cache collisions.
Some of our direct clients
WordPress Multisite on a Server Built for It
Wildcard SSL, correct Nginx or OpenLiteSpeed rules, DNS configuration, and caching set up for multi-site environments. Every sub-site on your network gets HTTPS automatically from day one.
- 7+
- Years of WordPress multisite work
- 100%
- Wildcard SSL for every sub-site
- 0
- Certificate errors on new sub-sites
- 24hr
- Multisite setup consultation
Why Agencies Choose Zestcode for WordPress Multisite
We configure the complete server environment for WordPress multisite: wildcard SSL, web server rules, DNS guidance, domain mapping, database tuning, and caching. A properly built foundation for your network.
- Wildcard SSL and DNS configuration
- Nginx or OpenLiteSpeed multisite rules
- Domain mapping server setup
- Multisite-compatible caching and database tuning
How a Multisite Setup Works With Us
We understand your network
We start with a short call to learn how many sites you expect, whether you want subdomains, subdirectories or mapped domains, and what your current hosting looks like. No jargon and no commitment, just a clear read on whether your environment suits multisite and what the setup involves.
We plan the architecture and quote
We decide the network model, the web server, the SSL and DNS approach and the database and caching setup, then set it out in a fixed-price proposal with a clear scope and timeline. You know exactly what is being configured and why before any work begins.
We configure the server
We build the environment: web server rules for multisite routing, wildcard SSL and DNS, domain mapping, tuned database and partitioned caching. We test by adding real sub-sites and confirming each resolves, serves over HTTPS and caches without collisions, rather than assuming it will.
We hand over and keep it running
We migrate any existing network, launch, and confirm certificates renew and new sites can be spun up with no manual server work. You get documentation of what was configured, and optional ongoing support so the network stays patched and monitored without you thinking about it.
Ready to build your multisite network?
Tell us how your network is structured and where it needs to run, and we will come back with a fixed quote and a realistic timeline, usually within 24 hours. NDA first, no obligation.
Here's What Our Partners Say
Agencies, direct clients and long-term retainers. Rated 5* on Google.
Zestcode really have proven to be “website design & development specialists” whilst maintaining the very best customer service. Not easy to find a well-rounded company like Zest these days that tick all the boxes. 5*
Head of Marketing, Masterclip
After working with Zestcode for over 2 years I wouldn’t trust any other web developers. An agency that are committed to getting the project right and going above and beyond expectations.
Director, Novus Digital
Harry and his team have just finished producing our new website, his team have done an amazing job producing our website and their continuous communication throughout made the process a lot easier.
Director, JL Phillips
Zestcode Digital have just finished my website and I am beyond thrilled with it! I highly recommend their services not only are they professional and proficient but incredibly helpful.
Director, Select Art Gallery
It's an easy and enjoyable process working with Zestcode Digital, highly recommended.
Director, Whoisvisiting
Their team is highly responsive, especially in time-sensitive situations, and their ability to deliver reliable solutions quickly has been a huge asset. I wouldn’t hesitate to recommend them to anyone looking for dependable web development support.
Marketing Manager, Slick Gorilla
Having close communication with Harry throughout the whole project has been invaluable. He always makes sure to explain things thoroughly and helped me understand all the different aspects of the project that I needed to know.
Director, All Abroad
WordPress Multisite Server FAQs
WordPress Multisite Server Setup Done Properly
Multisite is easy to switch on and hard to run well. Before you enable the network flag, the server underneath it has to be configured for wildcard SSL, subdomain routing, domain mapping and a shared database that will not buckle as sites multiply. Here is what that setup actually involves and how we approach it.
What multisite actually needs from a server
A multisite network is one WordPress install serving many sites from a shared codebase and database. That single detail changes almost everything about how the server has to be configured, because a rule written for one site now has to hold true for sites that do not exist yet.
The web server needs to route requests for any sub-site, current or future, to the same install without you touching config each time a site is added. SSL has to cover hostnames nobody has created yet. Uploads, caching and the database all have to stay cleanly separated per site while sharing the same infrastructure.
This is why multisite rarely works well on shared hosting, and why a plain single-site setup does not simply scale up. It is a different job, and it is worth doing properly at the start rather than patching it later.
Subdomain versus subdirectory networks
The choice between subdomain networks (site.example.com) and subdirectory networks (example.com/site) is made once, early, and it shapes the server config that follows. Subdirectory is simpler at the DNS and SSL level because everything lives under one hostname. Subdomain is more flexible for genuinely separate sites but needs wildcard DNS and wildcard SSL to work without manual steps per site.
We will talk through which fits what you are building rather than defaulting to one. A network of near-identical regional sites has different needs from a network of distinct brands that may later want their own domains.
Once the model is chosen, the web server rules, certificate strategy and routing all follow from it, so getting this decision right up front saves reconfiguration down the line.
Wildcard SSL and wildcard DNS
For a subdomain network, you cannot issue a certificate for every sub-site by hand, because new ones appear over time. The answer is a wildcard certificate covering *.example.com, so any subdomain is served over HTTPS the moment it exists.
We configure Let's Encrypt wildcard certificates via the DNS-01 challenge, which proves control of the domain through a DNS record rather than a file on a specific host. That is set up to renew automatically, so certificates do not lapse and take sites down. Alongside it we configure or guide you through the wildcard DNS record that makes every subdomain resolve to your server without a separate entry per site.
Both pieces work together: wildcard DNS gets the request to your server, wildcard SSL secures it once it arrives. Handled correctly, adding a sub-site needs no DNS or certificate work at all.
Not sure your server is ready for multisite?
Send us your hosting details and how you plan to structure the network. We will tell you plainly whether the environment can support it and what it would take to get there.
Web server configuration for the network
The web server is where multisite routing lives. We configure Nginx or OpenLiteSpeed with the specific rules multisite requires: rewriting requests so any sub-site reaches the shared install, handling the per-site uploads directory correctly, and dealing with the dynamic files multisite generates rather than serving stale or missing assets.
Which server we reach for depends on your stack and preferences. If you are set on OpenLiteSpeed for its built-in caching, our OpenLiteSpeed WordPress setup work covers that ground in more detail. Nginx remains a solid, well-understood choice and we configure either to the same standard.
The test of a good config is that it keeps working as the network grows. You should be able to spin up a new sub-site through the WordPress admin and have it served correctly without anyone editing server files.
Domain mapping for individual sites
Often a sub-site needs its own domain rather than a subdomain, so client-one.com serves a site that technically lives inside your network. Modern WordPress handles the application side of domain mapping natively, but the server still has to accept and route those domains and, ideally, secure them.
We configure the server so mapped domains resolve to the correct site in the network, and we set up SSL for them so each mapped domain is served over HTTPS rather than throwing a certificate warning. Where a client points their domain at your server, we guide the DNS side so it lands cleanly.
This is what lets a single network present as many independent websites, each on its own domain, while you maintain one install, one codebase and one set of updates.
Database, caching and keeping it running
Multisite adds a set of shared and per-site tables to a single database, and under load that database is usually the first thing to feel the strain. We tune MySQL or MariaDB with sensible InnoDB settings, connection handling and query optimisation suited to the multi-site structure rather than leaving defaults in place.
Caching needs care too, because a network makes cross-site cache collisions a real risk: one site serving another's cached page is a genuine failure mode if object and page caching are not partitioned correctly. We configure caching so each site has its own space and nothing bleeds across. If raw speed is the priority, our WordPress speed optimisation work goes deeper on that front.
We can also migrate an existing network onto new infrastructure, moving files, the database and the mapping config so nothing breaks in the move. For ongoing peace of mind, WordPress support retainers keep the network patched, monitored and looked after once it is live.
Partner with Zestcode for Industry Leading Quality and Reliability
Tell what you're looking for and we'll see you how we can help. Quotes are typically provided within 2 working days of the initial call.