WordPress Multisite: Quick Setup Guide

WordPress Multisite is a powerful feature that allows you to manage multiple WordPress sites from a single installation and dashboard. Instead of running separate WordPress instances, each consuming server resources and requiring individual updates, Multisite consolidates everything into one network. For South African agencies managing dozens of client sites, this translates to lower hosting bills, faster load times during peak hours, and unified security patching.

In this guide, I'll walk you through the exact steps to set up Multisite on your hosting, configure domain mapping, and manage plugins and themes across your network. Whether you're running an agency in Johannesburg, Cape Town, or Durban, this setup works seamlessly on HostWP WordPress plans with our LiteSpeed caching and Redis object cache already optimized for network performance.

Step 1: Enable Multisite on Your WordPress Installation

Enabling Multisite requires editing your wp-config.php file to add a single line of code. This tells WordPress to activate network mode and unlock the Multisite features in your dashboard. The process is straightforward but irreversible without a full backup—always back up your database and files before making any changes.

First, connect to your hosting via SFTP or use the file manager in cPanel/Plesk. Navigate to your WordPress root directory and download wp-config.php. Open it in a text editor and find the line that says /* That's all, stop editing! */. Just above that line, add:

define('WP_ALLOW_MULTISITE', true);

Save the file and upload it back to your server. You won't see any visible changes yet—Multisite is now enabled but not activated. At HostWP, we've guided over 150 SA agencies through this step, and the most common mistake is adding the define statement in the wrong location. Always place it above the final comment line, never below it. After uploading wp-config.php, log in to your WordPress admin and navigate to Tools → Network Setup. This menu only appears once WP_ALLOW_MULTISITE is true.

Faiq, Technical Support Lead at HostWP: "We've migrated over 500 WordPress sites to Multisite for SA agencies, and the most common setup issue is forgetting to flush permalinks after network creation. Always regenerate them immediately—it saves hours of troubleshooting 404 errors later."

Step 2: Complete the Network Setup

WordPress now displays the Network Setup form under Tools, which guides you through choosing a network structure and generating the required .htaccess rules and code snippets. You'll choose between Subdomains (client1.example.com, client2.example.com) or Subdirectories (example.com/client1, example.com/client2). For most SA agencies, subdomains are cleaner and easier to manage with domain mapping.

The setup form shows you exact code to add to wp-config.php and .htaccess. Copy these snippets carefully—they're critical for routing requests to the correct site. If you're using managed WordPress hosting like HostWP, your .htaccess is already configured for multisite-friendly rewrite rules, so the process is even faster. After adding the code, WordPress creates a new wp_signups table and wp_sitemeta tables in your database. The network site (usually example.com) becomes your primary site; all other sites are secondary networks.

Once setup completes, you're logged out automatically. Log back in—you'll notice your admin now shows a My Sites menu listing all sites in your network. You also see a new Network Admin section where you manage the entire network. This is your command centre for adding sites, managing users across the network, and controlling which plugins and themes are available to individual sites.

Step 3: Configure Domain Mapping for Multiple Sites

By default, Multisite uses subdomains or subdirectories. Domain mapping lets each site use its own separate domain (client1.co.za, client2.co.za). This is essential for agencies serving multiple clients who want their own branded domains. Domain mapping requires the Multisite Domain Mapping plugin and a wildcard DNS record pointing to your server.

First, set up DNS. In your hosting control panel, create a wildcard A record (*.yourdomain.com) pointing to your server's IP. This ensures all subdomains route to your WordPress installation. If clients are using their own domains (e.g., client.co.za registered elsewhere), they should update their DNS A record to point to your server's IP as well. For Johannesburg-based clients using Openserve or Vumatel fibre, DNS changes typically propagate within 1–4 hours.

Next, install the WordPress MU Domain Mapping plugin from the WordPress.org plugin directory. Activate it network-wide from Network Admin → Plugins. The plugin adds a Domains menu in Network Admin where you map each site to its custom domain. Add each domain, set one as primary, and the plugin handles rewriting URLs across the network. Always flush your site's cache (if using Redis, flush the Redis cache) after adding a new domain mapping—this prevents old URLs from being served to visitors.

Step 4: Manage Sites, Users, and Plugins Across Your Network

Your Network Admin dashboard is now your central hub. From Network Admin → Sites, you add, edit, or remove sites from the network. When you create a new site, WordPress assigns it a subdomain, language, admin email, and initial user. Each site has its own database tables (wp_2_posts, wp_2_postmeta, etc., where 2 is the site ID). Users are network-wide by default but can be assigned specific roles per site (editor, subscriber, etc.).

Plugin management is critical in Multisite. From Network Admin → Plugins, you can activate plugins network-wide (forcing all sites to use them) or let individual sites activate their own plugins. Network-wide plugins are ideal for security and caching plugins—you want all sites running the same firewall and cache layer. Individual plugins let each client customize their site. For example, you might network-activate a security plugin and caching layer, then let each client enable their own Gravity Forms or Yoast SEO licenses on their respective sites.

Themes work similarly. From Network Admin → Themes, you enable themes network-wide, then each site admin can choose which enabled theme to use. This prevents sites from accidentally using unsupported or unsecured themes. Many SA agencies create a single custom theme and enable it for all sites, ensuring consistent branding and faster development—you update once and all clients benefit immediately.

Step 5: Optimize Network Performance for South African Infrastructure

Multisite consolidates your infrastructure, but it also means one server serves multiple sites. To maintain fast load times, especially during South Africa's load shedding windows when server resources are precious, you must optimize network-wide caching and database queries. HostWP's LiteSpeed Web Server and Redis cache are already configured for Multisite; however, you need to enable persistent object caching in your code.

First, install the Redis Object Cache Pro or WP Redis plugin on your network. This caches database queries, reducing load on your database server—critical when serving 20+ sites from one database. Redis is especially valuable during peak traffic hours when load shedding makes server resources expensive. We've seen Multisite networks without Redis increase database query time by 300% under load; with Redis, queries drop to near-instantaneous speeds.

Next, configure your wp-config.php for Multisite-specific optimizations. Add these constants to improve performance:

• define('WP_CACHE', true); — Enables object caching
• define('EMPTY_TRASH_DAYS', 30); — Prevents trash from accumulating across all sites
• define('AUTOSAVE_INTERVAL', 120); — Reduces database writes by spacing autosaves to 2 minutes

Monitor database performance using Query Monitor (activate network-wide). Sites with slow queries stand out immediately. For example, one poorly-configured WooCommerce site in your network can slow queries for all other sites if it's running heavy product queries. Isolate and optimize problem sites quickly.

Finally, enable Cloudflare or another CDN at the network level. Cloudflare's free plan is ideal for SA sites, reducing bandwidth costs during load shedding and serving static assets from edge servers worldwide. For clients with heavy traffic, Cloudflare's ZAR pricing plans offer DDoS protection and advanced caching rules—important for protecting all your client sites from a single attack.

Faiq, Technical Support Lead at HostWP: "In our experience, 78% of SA Multisite networks we audit have no Redis cache active. Adding Redis typically cuts database load by 60–70%, translating to 2–3 second faster page loads across all sites. It's the single biggest performance win for Multisite."

Frequently Asked Questions

Q: Can I convert an existing WordPress site to Multisite?

A: Yes, but it's risky. Your existing site becomes the network's primary site. All posts, pages, and data remain intact, but you need to recreate user roles and plugin settings across the new network structure. Backup thoroughly before starting. For critical client sites, hire a managed WordPress provider like HostWP to handle the migration—we migrate 20+ sites monthly and ensure zero downtime.

Q: What's the difference between Multisite Subdomains and Subdirectories?

A: Subdomains (client1.example.com) are cleaner, work better with SSL certificates and domain mapping, and are easier for search engines to treat as separate sites. Subdirectories (example.com/client1) are simpler to set up but complicate SEO and domain mapping. Most SA agencies prefer subdomains for professional separation of client sites.

Q: Does Multisite slow down WordPress?

A: Not if optimized. A single database and shared caching layer actually reduce overhead compared to 10 separate WordPress installations. However, poorly configured Multisite networks with slow plugins and no caching perform worse than separate sites. Use Redis, CDN, and disable slow plugins on individual sites to maintain speed.

Q: Can I migrate individual sites out of Multisite later?

A: Yes, but it's complex. You'd export the site's database and files, install WordPress separately, and import the content. Plugins like Multisite Clone Duplicator automate part of this process. Plan Multisite as a long-term strategy, not a temporary setup.

Q: What hosting features does Multisite require?

A: Multisite needs SFTP access to edit wp-config.php, wildcard DNS support for domain mapping, and .htaccess write permissions. Most managed WordPress hosting (including HostWP) supports all of these. Avoid cheap shared hosting—Multisite's database load requires proper server resources and caching infrastructure.

Sources

• WordPress.org – Create a Network Documentation
• Web.dev – Why Speed Matters (Performance Best Practices)
• Google Search – WordPress Multisite Domain Mapping Best Practices

WordPress Multisite transforms how SA agencies manage client websites. Instead of maintaining separate hosting accounts, updates, and security patches, you consolidate everything into one manageable network. The setup takes 20–30 minutes, and the long-term time savings—combined with reduced hosting costs and unified security—make it essential for any agency managing 5+ sites.

The next step is testing your network thoroughly. Create a test site within the network, enable domain mapping, activate plugins, and verify all sites load correctly. Once confident, migrate your first client site and monitor its performance over a week. If you're managing load shedding challenges or traffic spikes during South African peak hours, enable Redis caching immediately—it's the difference between a responsive network and one that times out under load.

Ready to set up Multisite but unsure about configuration? Contact our white-glove support team—we've guided 150+ SA agencies through Multisite setup and can handle the entire process for you, including domain mapping and performance optimization.