WordPress Multisite: Ultimate Setup Guide

WordPress Multisite is a powerful feature that lets you run multiple WordPress sites from a single codebase and dashboard. Instead of managing separate WordPress installations for each site—which means separate updates, backups, and user accounts—Multisite consolidates everything into one network. This is especially valuable for South African agencies managing client portfolios, corporate groups running multiple regional sites, or publishers maintaining niche publications under one umbrella.

In this guide, I'll walk you through the complete Multisite setup process, from network activation through subdomain configuration and day-to-day management. I'll also share what we've learned at HostWP after hosting over 500 WordPress networks for SA-based agencies and enterprises.

What Is WordPress Multisite and Why Use It?

WordPress Multisite is a native WordPress feature that transforms a single WordPress installation into a network capable of hosting dozens—or even hundreds—of sites. Each site in the network has its own content, users, and settings, but they share one WordPress codebase, one database (with prefixed tables), and one set of core files.

The primary benefit for South African agencies is operational efficiency. Instead of managing five separate WordPress installations with five different update schedules, five backup routines, and five login dashboards, you manage one network. A single plugin update deployed from the network dashboard automatically applies to all sites—or just the ones you choose. This is crucial when you're managing client sites across multiple time zones, especially during South Africa's load shedding periods when updates need to be coordinated carefully.

At HostWP, we've found that agencies managing 5 or more client sites see an average 40% reduction in monthly maintenance time after migrating to Multisite. That translates to real cost savings and faster response times when urgent updates are needed. However, Multisite isn't suitable for every scenario—single large sites, sites requiring completely different hosting environments, or sites needing full isolation for security reasons are better served by separate installations.

Faiq, Technical Support Lead at HostWP: "In our experience, the sweet spot for Multisite is 3–25 sites per network. Beyond that, you run into database scaling issues and admin dashboard complexity. We've migrated over 50 SA digital agencies to Multisite, and the ones who benefit most are those managing similar site types—e.g., multiple e-commerce stores, multiple service-based business sites, or multiple franchise locations."

Before You Start: Planning and Backups

Setting up Multisite is irreversible without significant database work. Once you enable the network feature and create additional sites, converting back to a standard WordPress installation is complex and risky. This is why proper planning and backups are non-negotiable.

First, take a full backup of your WordPress installation. At HostWP, all managed WordPress plans include daily automated backups stored separately from your Johannesburg data centre, so if you're on our platform, you're already protected. If you're self-hosted, use a plugin like UpdraftPlus or BackWPup to create a complete backup before proceeding.

Next, decide on your Multisite architecture: Will you use subdomains (site1.yourdomain.com, site2.yourdomain.com), subfolders (yourdomain.com/site1, yourdomain.com/site2), or a mix of domain mapping? Subdomains require wildcard DNS records and are more scalable; subfolders are simpler but less flexible. For most SA agencies, subdomains work best because they're easier to brand and distribute as separate client sites.

Finally, audit your current plugins. Not all plugins are Multisite-compatible. Some may work network-wide (one license covers all sites), while others must be activated per site. This is a critical step—incompatible plugins can break your network or force you into costly licensing negotiations. Common issues we see include WooCommerce plugins that weren't tested for Multisite, security plugins with conflicting rules, and form builders that don't support network activation.

Enabling the Network Feature

Once you've backed up your site and planned your architecture, enabling Multisite is straightforward. Here's the step-by-step process.

Step 1: Add Network Constants to wp-config.php
Access your site via SFTP or your hosting control panel's file manager and edit wp-config.php. Before the line that reads "/* That's all, stop editing! */", add these lines:

define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
define('DOMAIN_CURRENT_SITE', 'yourdomain.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

Set SUBDOMAIN_INSTALL to 'true' for subdomains or 'false' for subfolders.

Step 2: Create the wp-content/blogs.dir Directory
Some Multisite configurations need this directory for uploaded media. Via SFTP, create /wp-content/blogs.dir/ and set its permissions to 755.

Step 3: Configure Your Wildcard DNS Record
If using subdomains, log into your domain registrar (e.g., Openserve if your domain uses ZA infrastructure) and add a wildcard DNS record: *.yourdomain.com → your.hosting.ip.address. This allows any subdomain to point to your Multisite installation.

Step 4: Run the Network Setup Wizard
Go to your WordPress admin dashboard. You'll see a new message: "To set up a WordPress network, please enable the multisite feature." Click the link, fill in the network title and admin email, then submit. WordPress will generate the necessary .htaccess rules and database modifications.

Step 5: Update wp-config.php and .htaccess Again
WordPress will provide additional code to paste into wp-config.php and .htaccess. Copy it exactly—typos here will break your network. Save both files and test by visiting your dashboard. If you see a "Network Admin" menu, you've succeeded.

Configuring Subdomains vs. Subfolders

The subdomain vs. subfolder choice has lasting implications for your network's usability and SEO. Understanding the tradeoffs is essential before you commit to one approach.

Subdomains (site1.yourdomain.com)
Subdomains are treated as separate domains by search engines and analytics tools. This means each site builds its own domain authority separately—good for client branding and SEO isolation, but each site starts from zero in Google's eyes. Subdomains require wildcard DNS records and are slightly more complex to configure, but they feel like entirely separate websites to users and search engines.

Subfolders (yourdomain.com/site1)
Subfolders are treated as part of the parent domain, so they inherit some domain authority from the main site. This can boost SEO ranking speed for new subsites, but it also means weaker content isolation—if one subsite gets hacked, the parent domain is at higher risk. Subfolders are simpler to configure (no DNS changes needed) but less scalable for large networks or complex client setups.

For SA agencies, we typically recommend subdomains. They're cleaner for client handover, better for brand separation, and they avoid the perception of affiliate networks or subdirectory spam. However, if you're building regional variations of a single brand (e.g., a national retailer with regional microsites), subfolders may work better because they keep the parent domain's authority.

Once configured, changing from subdomains to subfolders requires database work and isn't recommended. Choose now and commit.

Managing Plugins and Themes Across Your Network

One of Multisite's biggest advantages is centralised plugin and theme management. However, this requires careful planning to avoid licensing conflicts and compatibility issues.

Network-Activated vs. Per-Site Plugins
When you activate a plugin on the Network Admin page, it activates on all sites. This is useful for security plugins, caching plugins, and site-wide tools that every site needs. However, you lose the flexibility for individual sites to use their own plugins.

Most agencies use a hybrid approach: network-activate essential plugins (security, caching, performance optimisation), then allow individual site admins to activate optional plugins specific to their site (WooCommerce, job boards, booking systems). This balances control with flexibility.

The catch? Check plugin licensing first. Some premium plugins charge per-site or charge a flat network fee. WooCommerce Pro, for example, typically requires separate licences per site even on Multisite. Budget for this before rollout.

Theme Management
Themes on Multisite can be network-activated (all sites use the same theme) or made available to individual sites. Most agencies choose the latter: upload a parent theme to the network, then allow each site admin to activate it or choose from a curated list of child themes.

A practical tip from our experience at HostWP: use a child theme for all custom work. This keeps theme updates separate from core customisation, making updates safer. We've seen too many agencies lose custom CSS when they updated their parent theme without a child theme in place.

Security and Performance for Multisite Networks

Multisite networks are higher-value targets for hackers—compromise the network, and you compromise dozens of sites. Performance also becomes trickier because all sites share database and server resources. Here's how to protect both.

Security Best Practices for Multisite
First, use a security plugin that understands Multisite architecture. Wordfence and Sucuri both have Multisite-specific modes. Avoid security plugins that aren't Multisite-aware; they can block legitimate admin traffic or create conflicting rules across sites.

Second, enforce strong user permissions. Limit site administrators' access to core settings (they shouldn't be able to edit wp-config.php or .htaccess). Use the "Super Admin" role sparingly—usually only for you or your most trusted manager. Document role permissions clearly, especially if you're handing over admin access to clients.

Third, isolate compromised sites quickly. In a traditional WordPress setup, one hacked site is one problem. In Multisite, it's one problem you need to contain before it spreads to others. Regular backups and monitoring are essential. At HostWP, our Multisite clients benefit from automated daily backups and proactive malware scanning included in our managed plans.

Performance Optimisation
Multisite networks can slow down if not configured properly. Here's our performance checklist:

• Enable object caching: Redis or Memcached dramatically speeds up Multisite by caching database queries across all sites. HostWP includes Redis on all plans, so this is already optimised for our customers.
• Use a page caching plugin: WP Super Cache or LiteSpeed Cache (native to our platform) caches entire HTML pages, reducing server load.
• Optimise the database: Run WP-Optimize monthly to clean up post revisions, transients, and spam comments that accumulate across dozens of sites.
• Lazy-load images: Use Lazy Load by WP Rocket or a similar plugin to defer off-screen image loading, speeding up initial page loads.
• Monitor with a tool: New Relic or Kinsta APM (if using their hosting) help you identify which sites are bottlenecks and why.

Load shedding in South Africa adds another layer of complexity. Ensure your host has backup power and a reliable UPS system. HostWP's Johannesburg data centre includes backup generators to keep your network online during Eskom blackouts—a critical feature for agencies managing client SLAs.

Frequently Asked Questions

Q: Can I convert a standard WordPress site to Multisite without losing content?
A: Yes, but it's complex. You'll need to export content, enable Multisite, then import content into a new subsite. For sites with significant customisation or user data, it's safer to hire a developer. At HostWP, our migration team can handle this—contact us for a quote on your specific setup.

Q: What's the maximum number of sites I can run on a single Multisite network?
A: Technically, hundreds. Practically, database and server performance start degrading around 50–100 sites depending on traffic and plugin complexity. Beyond that, consider splitting into multiple networks or upgrading your hosting tier.

Q: Do Multisite sites need separate SSL certificates?
A: No. A wildcard SSL certificate (*.yourdomain.com) or a multi-domain certificate covers all subdomains. HostWP includes free Let's Encrypt SSL on all plans, automatically renewed, so this is handled for you.

Q: Can I use domain mapping to point different domains to Multisite subsites?
A: Yes, with the Domain Mapping plugin or a custom solution. This lets site1.com, site2.com, and site3.com all run under one Multisite network behind the scenes. It's complex but powerful for agencies managing client domains.

Q: How do I handle POPIA compliance across a Multisite network?
A: Ensure your privacy policy, cookie consent, and data handling meet South Africa's Protection of Personal Information Act. Use a network-wide privacy plugin (e.g., MonsterInsights with GDPR/POPIA settings) and document how user data flows across sites. If sites have different data controllers, consider separate networks instead.

Sources

• WordPress.org: Create a Network
• WordPress.org Developer Handbook: Multisite
• Google Search: Multisite WordPress Performance Optimisation

WordPress Multisite is a game-changer for agencies managing multiple client sites, but it demands careful planning and ongoing maintenance. The setup process itself is straightforward—most agencies complete it in an afternoon—but success depends on choosing the right architecture upfront, managing plugins intelligently, and investing in proper security and caching from day one.

If you're considering Multisite for your agency or running one already and facing performance or security issues, HostWP's managed WordPress hosting is purpose-built for networks. Our LiteSpeed caching, Redis object cache, and 24/7 South African support eliminate the technical friction so you can focus on client work. Ready to move forward? Contact our team for a free audit of your current setup and a proposal tailored to your network's size and needs.