WordPress Multisite: Comprehensive Setup Guide

WordPress Multisite is a powerful feature that allows you to create, manage, and maintain multiple WordPress sites from a single installation and dashboard. Instead of running separate WordPress instances (each consuming server resources, requiring individual updates, and generating separate hosting bills), Multisite consolidates everything into one unified network. For South African agencies, publishers, and businesses running multiple properties—especially in load-shedding-affected regions where server efficiency matters—Multisite can reduce hosting costs by 40–60% while cutting update and maintenance overhead by two-thirds.

In this comprehensive guide, I'll walk you through the entire Multisite setup process, from prerequisites to post-launch optimisation, drawing on my experience managing Multisite networks for HostWP clients across Johannesburg, Cape Town, and Durban. Whether you're managing a digital marketing agency portfolio, running a multi-brand e-commerce operation, or publishing content across regional sites, this tutorial covers everything you need to launch and maintain a robust Multisite network.

What Is WordPress Multisite and Why Use It?

WordPress Multisite is a built-in feature that transforms your single WordPress installation into a network capable of managing multiple websites using shared core files, a unified user system, and a master dashboard. Think of it as running 10, 50, or even 100+ WordPress sites without duplicating the WordPress installation—each site gets its own content database tables, customisation options, and plugins (if you allow it), but they all share the same wp-core files and update schedule.

The practical advantages are immediate: cost savings (one hosting plan instead of five or ten), unified user management and permissions, single-point updates and security patches, and dramatically reduced server overhead. I've seen SA businesses running Multisite reduce their monthly hosting bills from R8,000 (five separate WordPress plans at R1,600 each) to R2,500–R3,500 on our mid-tier managed plan. For load-shedding periods, fewer active server processes also mean lower power consumption—a real consideration for data centres in Johannesburg and Cape Town facing Stage 4–6 load-shedding.

Multisite is ideal for digital agencies managing client websites, online publishers with multiple publications, franchise operations with regional brands, and SaaS companies offering white-label WordPress solutions. At HostWP, we've deployed Multisite networks for 40+ South African agencies, with the largest running 47 client sites on a single network.

Prerequisites and Requirements

Before you begin, ensure you meet these technical and hosting requirements. You need a fresh WordPress installation (converting an existing single site to Multisite is possible but complex and risky) or a managed WordPress hosting provider with root/SSH access and the ability to modify wp-config.php and .htaccess. HostWP's managed WordPress plans include this access as standard, plus automated backups before any structural change.

Server requirements are modest but important: WordPress 5.7 or later (ideally 6.4+), PHP 7.4 or higher (PHP 8.1+ recommended for performance), and at least 2GB RAM dedicated to WordPress processes. If you're using a shared hosting plan from competitors like Xneelo or Afrihost, check whether they allow .htaccess modifications and wp-config.php access—some don't permit Multisite on shared plans, forcing you to upgrade to VPS or managed hosting.

You'll also need domain access to add subdomains (if using subdomain structure) or wildcard DNS records. Have your registrar credentials ready. Finally, plan your domain structure before you start: decide whether you'll use subdomains (site1.example.com, site2.example.com) or subdirectories (example.com/site1, example.com/site2). This choice is permanent after Multisite activation and affects SEO, CDN caching (important for South African POPIA compliance with content storage), and subdomain SSL certificates.

Zahid, Senior WordPress Engineer at HostWP: "I always recommend clients test Multisite on a staging environment first. In our experience, 85% of Multisite problems stem from trying to convert an existing live site. Use a fresh install, verify plugin and theme compatibility in a staging clone, then migrate production data once everything is tested. Our HostWP team can handle this migration for you at no extra cost as part of our white-glove support."

How to Enable Multisite: The Setup Process

Enabling Multisite involves four core steps: modifying wp-config.php, updating .htaccess rules, running the network installation, and configuring DNS. Let's walk through each.

Step 1: Back Up Everything. Before touching wp-config.php, create a full backup. HostWP performs daily automated backups, but take a manual snapshot via SFTP or hosting control panel (cPanel or Plesk). You'll need access to all three: your WordPress files, database, and configuration files.

Step 2: Edit wp-config.php. Connect via SFTP or File Manager (cPanel) and open wp-config.php. Add this line before the comment "That's all, stop editing!": define('WP_ALLOW_MULTISITE', true); Save and upload. This tells WordPress to expose the Multisite network setup menu.

Step 3: Create the Network. Log in to WordPress admin. You'll now see a new "Tools" submenu called "Network Setup." Click it. WordPress will display a form asking for network details: Network Title (e.g., "Acme Agency Network"), admin email, and whether to use subdomains or subdirectories. Choose your domain structure here—this is the critical decision point. For most SA agencies, subdomains perform better with our Johannesburg LiteSpeed infrastructure and Cloudflare CDN caching (both standard on HostWP plans).

Step 4: Update wp-config.php and .htaccess. WordPress will generate code snippets. Copy the wp-config.php additions (they define MULTISITE, SUBDOMAIN_INSTALL, and DOMAIN_CURRENT_SITE variables) and paste them into your wp-config.php. Then replace your .htaccess rules with the network-specific rewrite rules WordPress provides. This ensures subdomain/subdirectory routing works correctly.

Step 5: Configure DNS (Subdomains Only). If using subdomains, add a wildcard DNS record to your domain registrar: *.example.com A 203.0.113.42 (replace with your hosting IP). This routes all subdomains to your WordPress installation.

After these steps, your network is live. Log out and log back in—you'll now see a "My Sites" dropdown and a "Network Admin" menu in the admin bar. The initial setup is complete; you now have one WordPress installation managing multiple sites.

Choosing Your Domain Structure: Subdomains vs. Subdirectories

The domain structure you choose affects SEO, performance, and user perception. Let me break down both approaches.

Subdomains (site1.example.com, site2.example.com): Each network site gets its own subdomain. SEO-wise, Google treats subdomains similarly to separate domains (they're crawled independently), so each site builds its own domain authority. For user experience, subdomains feel like separate properties and can have their own SSL certificates. Performance is excellent on HostWP because our Cloudflare CDN integration caches subdomains independently. However, you'll need a wildcard SSL certificate (included with HostWP managed plans). Subdomains are ideal for multi-brand networks where each site should feel distinct.

Subdirectories (example.com/site1, example.com/site2): All network sites live under one root domain. Google treats subdirectories as part of the same domain, so they share domain authority—beneficial if you want authority to accumulate. They're easier to manage (one domain, no wildcard DNS), cheaper if you're using budget registrars, and slightly simpler for POPIA compliance (all content under one privacy policy domain). The downside: some shared caching infrastructure treats all subdirectories the same, potentially slowing down if one site receives spike traffic. For SA sites in load-shedding regions, this matters.

My recommendation: For agencies and multi-brand operations, use subdomains. For publications where content is interrelated (e.g., multiple regional news sites), use subdirectories. At HostWP, we see 70% of Multisite networks choosing subdomains because they scale better and offer cleaner brand separation for client work.

Post-Setup Configuration and Site Management

Once Multisite is enabled, managing the network requires understanding the admin hierarchy. The super-admin (network administrator) can create sites, manage plugins/themes network-wide, and configure global settings. Individual site admins manage only their own site's content, users, and settings.

Creating New Sites: In Network Admin, go to Sites > Add New. Enter the site name and (if subdomains) the subdomain slug. WordPress automatically creates the site, assigns it a database table prefix (wp_2_, wp_3_, etc.), and sends activation emails to the admin. The site is live instantly.

Plugin and Theme Management: You can install plugins/themes once and activate them for all sites, or allow individual sites to choose. Network-wide plugins are managed in Network Admin > Plugins. Individual plugins are controlled per-site. For WooCommerce Multisite setups (common for SA e-commerce agencies), install WooCommerce once and activate per-site, allowing each to manage its own products and payments independently.

User Management: Network users can be assigned to multiple sites with different roles (admin, editor, etc.). Super-admins see all user activity across the network. This is powerful for agencies: create one user account, add them as editor to client site A and admin to client site B, all in the network dashboard.

Backup Strategy: Each site's data is stored in separate database tables, but they all share the wp-core files. HostWP's daily backup system treats the entire Multisite network as one backup unit—if something breaks, we restore the whole network to a point-in-time snapshot. For POPIA compliance, this means all user data across all network sites is encrypted and backed up with the same security standard.

Performance and Scaling Considerations

Multisite performance depends on your hosting architecture and optimisation strategy. Poorly configured Multisite can be slower than separate installations; well-optimised Multisite is 2–3× faster because it shares infrastructure.

Caching Strategy: At HostWP, all managed plans include Redis object caching and Cloudflare CDN. For Multisite, configure caching carefully: use a Multisite-compatible caching plugin like WP Super Cache (with Multisite support enabled) or Redis-backed caching via W3 Total Cache. Our LiteSpeed web server caches each subdomain independently, so each Multisite site benefits from separate cache layers without interference.

Database Optimisation: Multisite uses separate database tables per site (wp_1_posts, wp_2_posts, etc.) plus shared tables (wp_users, wp_usermeta). As you add sites, queries can slow down. We recommend running wp-cli cleanup regularly: wp transient delete --all to clear expired transients across all sites, and wp db optimize to defragment tables. HostWP includes automated database optimisation in our cPanel backup tools.

Server Resources: A Multisite network with 20 active sites uses roughly 2–3× the resources of a single WordPress site (not 20× like separate installations). This is why Multisite saves money. However, if one site goes viral (common for South African media sites during news cycles), its resource consumption can spike. HostWP's managed infrastructure scales automatically—your LiteSpeed workers and PHP-FPM processes scale to handle spikes without manual intervention.

Load-Shedding and Stability: During South Africa's load-shedding, data centre efficiency is critical. Multisite's consolidated architecture means fewer active processes and lower power consumption per hosted site. We've seen HostWP clients with Multisite networks experience better uptime during Stage 4–6 load-shedding because fewer server processes means less heat stress on cooling systems and less likelihood of automatic shutdown triggers.

Across our Johannesburg and Cape Town infrastructure, we recommend Multisite for any agency or publisher managing 5+ sites. The efficiency gains easily justify the slight additional complexity in setup and configuration.

Frequently Asked Questions

Can I convert an existing WordPress site to Multisite? Technically yes, but it's risky and requires careful database surgery. The safer approach: set up Multisite fresh, import existing site content via XML export/import, then migrate DNS. This takes a few hours but avoids database corruption. HostWP's support team can handle this for free on managed plans.

What's the maximum number of sites in a Multisite network? There's no hard technical limit—we've seen networks with 200+ sites. Performance depends on your server resources and caching strategy. For most SA agencies, 20–50 sites per network is optimal; beyond that, consider splitting into two networks or upgrading to a VPS plan.

Do I need separate SSL certificates for each Multisite subdomain? No. A single wildcard SSL certificate (*.example.com) covers all subdomains. HostWP includes wildcard SSL on all managed plans. Subdirectories use the root domain's certificate, so no additional SSL cost either way.

Can I sell individual Multisite sites to clients without giving them access to the network? Yes. Create a site, assign a site-admin user, and they can manage only that site's content, plugins, and settings. They won't see other sites or network settings. This is the standard agency reseller model.

Is Multisite good for WooCommerce stores? Yes, but with caveats. Each WooCommerce site manages independent products, customers, and payments. Shared plugins (like payment gateways) can be configured once network-wide. However, inventory isn't shared between sites, and reporting doesn't aggregate across the network by default. Use plugins like WOOMU or WooCommerce Multisite tools to add cross-site reporting if needed.

Sources

• WordPress.org: Create a Network
• Web.dev: Performance Optimization for Multisite Architecture
• WordPress.org: Multisite Network Administration