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.
Some of our direct clients
Why Agencies Choose Us for Multisite
Seven years configuring multisite networks from the ground up, so wildcard SSL, subdomain routing and a shared database all hold up as sites multiply.
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.
The Servers We Build It On
Nginx or OpenLiteSpeed, configured with the multisite-specific rules a network of sites needs, on a VPS tuned for wildcard SSL, domain mapping and a shared database that scales.
Laravel & Bespoke Platforms
For systems and platforms that require bespoke processes, data handling complex integrations or internal business platforms with security at the forefront of the build.
WordPress & WooCommerce
For fast, reliable and easy to manage brochure based websites built following best practice with a bespoke theme powered by ACF Pro and supporting custom built plugins.
Shopify & Shopify Plus
For eCommerce and retail brands looking to grow revenue significantly online. Built using a bespoke theme specific to your brand and with a full seamless migration from legacy platforms.
Recently Completed Projects
Clintons Cards
A full migration from Magento 2 to Shopify Plus, with order, customer, product, stock and finance integrations kept live through the switch.
Ecommerce · Shopify Plus · IntegrationsQualityHive
A Laravel platform that web agencies use to capture, assign and close website bugs, taken from wireframe to launch, then handed over as clean, documented code.
SaaS platform · Laravel · API integrationsThe Sauce Foundry
A brand, a WooCommerce store and product photography for an artisan hot sauce startup, launched to a 3.8% conversion rate from day one.
Ecommerce · Branding · WooCommerceHave a project like these in mind?
Get in touchHere's What Our
Clients Say
Consistently rated 5* on Google by our full build clients and retainer clients.
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 us what you're looking for and we'll see how we can help. Quotes are typically provided within 2 working days of the initial call.