Skip to main content
Hosting

Hosting a Multi-Site WordPress Network: Pros, Cons, and Setup Tips

MMercy Chepkemoi18 November 202617 min read17 views

If you manage several WordPress websites, you know the routine: log in to each one, update the same plugins again and again, keep track of different passwords and hope nothing falls behind. For a franchise with branch websites, a school with departmental sites, an agency with its own family of sites, or a business with country or language versions, that overhead adds up quickly.

WordPress has a built-in answer: Multisite, a feature that lets one WordPress installation run a whole network of websites. It can save a lot of time, but it is not right for every project, and the hosting it needs is different from a single-site setup.

This guide explains what Multisite is, compares its pros and cons honestly, shows when a network is the right choice and when separate installs are better, lists what your hosting must provide and walks you through setup and the tips that prevent the most common problems.

Key takeaways

  • WordPress Multisite runs many sites from one installation, with shared WordPress core, plugins and themes, a shared database and one network dashboard.

  • It shines when the sites are related, owned by one organisation and should share the same tools and standards.

  • Its biggest drawbacks are shared fate and shared resources: one bad plugin, one hacked admin account or one traffic spike can affect every site.

  • Subdomain networks need wildcard DNS and, for HTTPS, a plan for certificates. Subdirectory networks are simpler to host.

  • Choose hosting that lets you edit wp-config.php and .htaccess, gives you enough resources, offers reliable backups and staging, and has room to grow.

  • For unrelated client sites that need isolation, separate WordPress installs plus a central management tool are usually safer.

What Is WordPress Multisite?

A normal WordPress install runs one website. With Multisite switched on, a single install runs a network of sites. Each site in the network has its own content, menus, settings, users and, usually, its own address, but they all share:

  • One copy of the WordPress core files

  • One set of installed plugins and themes

  • One database (with separate tables for each site)

  • One network dashboard, controlled by a Super Admin

Sites in a network can use subdirectories (example.com/branch-one), subdomains (branch-one.example.com) or fully mapped custom domains (branchone.co.ke). Since WordPress 4.5, mapping a different domain to a site is built in.

Who Should Use Multisite?

Multisite works well when the sites are alike and managed by the same people. Typical examples:

  • Franchises and multi-branch businesses with one site per branch or region

  • Universities, schools and NGOs with departmental or programme sites

  • Language or country versions of the same company site

  • Publishers and blog networks under one brand

  • Communities where members can create their own sites

  • Agencies running a family of similar sites from one controlled platform

Pros of a Multisite Network

  • Update once, update everywhere. WordPress, plugins and themes are updated in one place, so every site stays current, which is good for security.

  • Less repeated work. Install a plugin or theme once and make it available to all sites.

  • Consistent branding and standards. The same themes and plugins make it easy to keep every site on-brand.

  • Central control. A Super Admin controls who can install code and which themes are available.

  • Shared users. A person can have one login and different roles on different sites.

  • Quick to launch new sites. Creating a new site takes a few clicks, with no new installation to configure.

  • Efficient resource use. One set of core files and one codebase is lighter than dozens of separate installs, which can help on a hosting plan with limits.

  • Easier governance. Network-wide settings, upload limits and policies apply across the board.

Cons of a Multisite Network

  • Shared fate. One broken plugin update, one fatal error or one outage can take down every site in the network at once.

  • Shared resources. A busy or badly built site can slow all the others. Hosting limits are measured for the whole account, not per site.

  • Security concentration. A compromised Super Admin account or a vulnerable network-activated plugin exposes the entire network.

  • Plugin and theme compatibility. Not every plugin supports Multisite, and some behave differently on a network.

  • Harder single-site backups and restores. Restoring one site means restoring that site's database tables and uploads, not just a simple file copy. Without a plan or the right tool, it is awkward.

  • Harder to move a site out. Selling a site, handing it to a client or migrating it elsewhere takes extra steps, such as exporting its content or its tables and uploads.

  • One database. Many sites mean many tables. Very large networks can hit database performance and backup size limits.

  • Less flexibility per site. Every site runs the same WordPress version, PHP version and core plugins. Site owners cannot normally install their own plugins or themes.

  • Privacy and isolation. Different clients' data sits in the same database, which can be a problem under client contracts or data protection rules.

  • A steeper learning curve. Network administration, domain mapping and wildcard configuration add complexity.

  • Licensing. Some premium plugins and themes count each site in the network separately, or do not allow network use at all. Check the terms.

Multisite or Separate Installs? A Decision Guide

Your situation

Better choice

Many similar sites for one organisation, with shared standards

Multisite

Unrelated client sites, each needing its own plugins and settings

Separate installs

Clients who may leave and take their site with them

Separate installs

Sites that need strong data isolation

Separate installs

One very high-traffic site plus several small ones

Separate installs, with the busy site on its own resources

A franchise or branch network that must look and work the same

Multisite

Heavy WooCommerce stores per site

Usually separate installs, because multisite stores add complexity

You want one dashboard but need isolation

Separate installs with a central management tool

If you want the convenience of one dashboard without sharing an installation, central management tools such as MainWP and ManageWP let you update, back up and monitor many separate WordPress sites from one place. For agencies, that is often a safer middle path.

Subdomains, Subdirectories or Mapped Domains?

Subdirectory

Subdomain

Mapped domain

Example

example.com/branch

branch.example.com

branchname.co.ke

DNS setup

Simple, one domain

A wildcard DNS record (*.example.com) or a record per site

Each domain pointed to the server

HTTPS

One certificate covers the site

Needs a wildcard certificate or one per subdomain

One certificate per domain

Best for

Related sections under one brand

Separate sections with their own identity

Sites that need their own brand and address

Watch out for

Permalink clashes with existing pages

Wildcard DNS and certificates

Many certificates, DNS and renewals to manage

WordPress may limit the subdirectory option on an established site, because of possible clashes with existing page addresses, so planning the structure before you convert an old site matters.

What Your Hosting Needs to Support Multisite

Requirement

Why it matters

Ability to edit wp-config.php and .htaccess

Multisite setup adds configuration to both files

A current PHP version and a supported database

WordPress recommends PHP 8.3 or greater, and a current MySQL or MariaDB. Check WordPress.org's requirements

Enough memory and CPU for the whole network

Resources are shared by every site, so size for the total, with headroom

Fast storage and sensible file limits

Every site adds uploads, cache files and database tables

Wildcard DNS and a certificate plan (subdomain networks)

Subdomains need DNS entries and valid HTTPS certificates

DNS control for mapped domains

Each custom domain must point to the server

Caching, including object caching if possible

Network-wide performance depends on caching

Daily backups and a tested restore process

A network failure affects every site

Staging

Test updates before they reach every site

Security: firewall and malware scanning

One weak point exposes the network

Monitoring and clear resource limits

You need early warning of problems

An upgrade path

Networks grow, and you may need a VPS later

Always check with your host that WordPress Multisite is supported on your plan, since some managed WordPress environments restrict it.

Step-by-Step: Set Up a WordPress Multisite Network

Step 1: Plan the network

Decide how many sites you expect, whether they will use subdirectories, subdomains or mapped domains, who will be Super Admins, which themes and plugins all sites will share and how you will handle backups. Changing structure later is much harder than choosing well now.

Step 2: Prepare your hosting and your site

  • Take a full backup of your files and database.

  • Update WordPress, your theme and all plugins.

  • Deactivate your plugins temporarily, since WordPress asks for this before network setup.

  • Make sure pretty permalinks work, and that your site runs over HTTPS.

  • For subdomain networks, add a wildcard DNS record, and make a plan for HTTPS certificates. See managed DNS and the SSL certificates options, or ask SteboHost support what your plan allows.

Step 3: Allow the network setup

Open wp-config.php and add this line above the comment that says "That's all, stop editing":

define( 'WP_ALLOW_MULTISITE', true );

Save the file, then reload your WordPress dashboard.

Step 4: Run the network installer

Go to Tools > Network Setup. Choose subdomains or subdirectories if WordPress offers the choice, give the network a title and a Super Admin email address, and click Install. WordPress then shows two pieces of code, one for wp-config.php and one for .htaccess. Copy exactly what it shows you, because the code is generated for your own site. The wp-config.php part looks like this:

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

Add these lines to wp-config.php (above the "stop editing" comment), and replace the existing WordPress rewrite rules in .htaccess with the rules WordPress provides. Log in again.

Step 5: Configure the network settings

In Network Admin > Settings, review:

  • Registration: keep new registrations off unless you really want people to create sites.

  • Upload limits and file types for the whole network

  • Welcome emails and new-site defaults

  • Menu options, which control whether site admins can see the Plugins menu

Step 6: Add themes and plugins

Install themes and plugins in the network admin. Network Activate a plugin if every site needs it (a security or caching plugin, for example), or leave it available for individual sites to activate. Enable themes for the network, then choose which themes each site may use. Keep the list short, because every extra plugin affects every site.

Step 7: Create your sites

In Network Admin > Sites > Add New, enter the site address, title and admin email. Repeat for each site. Create a model site with your standard pages and settings, and use it as a pattern for new ones, with a cloning plugin if needed.

Step 8: Map custom domains (if needed)

To give a site its own address:

  1. Register or choose the domain, and point it to your server using DNS records. See our guide to pointing a domain to your hosting.

  2. In Network Admin > Sites, edit the site and change its Site Address (URL) to the new domain.

  3. Make sure the new domain has a valid HTTPS certificate.

  4. Check redirects from the old address, and update internal links.

You can register your domain names for the sites that need them and manage them alongside your hosting.

Step 9: Set up users and roles

A Super Admin controls the whole network, including plugins, themes and all sites. A site Administrator controls only their own site. Keep the number of Super Admins very small, give each person their own login, and turn on two-factor authentication for every Super Admin.

Step 10: Add caching and performance tuning

Use a page caching plugin that supports Multisite, and add object caching (such as Redis) if your hosting offers it. Optimise images across the network, keep the plugin list lean and watch how resource use grows as sites are added. Our guide to image optimization and our guide to reading your cPanel resource usage explain two of the biggest levers.

Step 11: Secure the network

  • Disable the theme and plugin file editor in wp-config.php with define( 'DISALLOW_FILE_EDIT', true );

  • Keep WordPress, plugins and themes updated, and remove the ones you do not use

  • Use strong passwords and two-factor authentication

  • Run a firewall and malware scanning. See website security

  • Review Super Admins and administrators regularly

Step 12: Back up, stage and monitor

Keep daily backups and test restoring, including how you would restore a single site. Use a staging copy of the network to test updates before they reach every site. Our guide to staging environments explains the safe way to move changes live. Set up uptime monitoring that checks more than one site in the network.

Working With a Network: Practical Tips

  • Test every plugin update on staging first, since a failure affects everyone.

  • Search and replace across the network carefully. With WP-CLI, the network flag applies a change to every site's tables, and a dry run first shows what would change. See our guide to SSH and command-line tools.

  • Export a site from Tools, Export when you need to move one site's content out, and keep a copy of its uploads.

  • Document the network: which sites exist, who owns them, which domains map to them and how to restore each one.

  • Retire unused sites instead of letting them age, since forgotten sites are security and storage risks.

  • Watch the database, because a network creates many tables. Clean up revisions, spam and expired data regularly.

  • Plan for growth: when the network needs more resources, move to dedicated capacity instead of squeezing more into a shared plan.

Common Problems and Fixes

  • After enabling Multisite, the site shows a database error or redirects in a loop. The wp-config.php constants or .htaccess rules are wrong or incomplete. Compare them with what WordPress generated, and check for duplicate definitions.

  • Subsites show the main site, or give 404 errors. The rewrite rules are missing or not working. Re-save permalinks and check that .htaccess contains the multisite rules.

  • Subdomains do not load. Wildcard DNS is missing or has not spread yet. Check the DNS record.

  • Certificate warnings on subdomains or mapped domains. The certificate does not cover that address. Use a wildcard certificate or one certificate per domain.

  • Cannot log in to a mapped domain. Cookie or address settings do not match the new domain. Check the site address and any cookie domain setting.

  • A plugin works on one site but breaks others. It is not fully compatible with Multisite or conflicts with another plugin. Test on staging, update it or replace it.

  • Uploads or images missing. Network uploads are stored per site under the uploads folder. Check file paths, permissions and any URL replacements.

  • The whole network slows down. One site or plugin is using too many resources. Check resource usage and logs to find the cause.

Is Multisite Right for You? A Quick Checklist

  • Are all the sites owned or controlled by the same organisation?

  • Will they share the same themes and plugins?

  • Do you want central updates and governance?

  • Are you comfortable with one site's problems potentially affecting others?

  • Do you have a plan for backups, restores and moving a site out?

  • Does your hosting support Multisite, with the resources to match?

If you answered yes to most of these, Multisite is a strong candidate. If not, separate installs with a central management tool may suit you better.

Why Host Your WordPress Network With SteboHost

A network puts more weight on your hosting than a single site does, so the platform matters:

  • Fast WordPress hosting. LiteSpeed web servers, NVMe storage and cPanel on SteboHost web hosting, with managed WordPress hosting adding staging, automatic core and plugin updates and LiteSpeed caching. Check that your chosen plan supports Multisite, and ask SteboHost support if you are unsure.

  • Clear resource limits. Each plan's limits are published, so you can size a network sensibly. See the plan limits.

  • Control when you need it. VPS and cloud hosting gives you dedicated CPU and RAM, full root access, Ubuntu, Debian and AlmaLinux images and snapshot backups for larger networks and custom setups. See also Developer Hosting for developer-focused options.

  • Domain and DNS tools in one place. Manage your records with managed DNS, and ask about certificate options for subdomains and mapped domains on the SSL certificates page.

  • Security on every plan. A web application firewall, Imunify360 malware scanning and DDoS mitigation, plus 24/7 infrastructure monitoring and a 99.9% uptime SLA.

  • Daily backups on shared hosting plans, with 7-day retention and one-click restore. See backup and disaster recovery, and ask how single-site restores work for a network.

  • Migration help on annual plans. Terms are shown on the pricing page and at checkout.

  • Local support on +254 703 610 464 during East Africa Time business hours, with 24/7 urgent monitoring, and billing in KES by M-Pesa, card or bank transfer.

Current plan and renewal prices are shown on the pricing page before you buy. You can also browse the knowledge base for more WordPress guides.

Conclusion

WordPress Multisite can turn a pile of separate websites into one well-managed network, with central updates, consistent branding and quick site creation. It can also concentrate risk, so it suits related sites under one owner much better than unrelated client work. Decide your structure first, choose hosting that supports it and has room to grow, set up carefully, secure and back up the network from day one and test your updates on staging.

Planning a network and want a second opinion on the hosting? Contact the team or call +254 703 610 464, and SteboHost will help you choose the right setup.

Frequently Asked Questions

What is WordPress Multisite?

WordPress Multisite is a built-in feature that lets one WordPress installation run a network of websites. The sites share the same WordPress core files, plugins and themes and one database, and they are managed from a single network dashboard by a Super Admin.

Is WordPress Multisite good for agencies with client websites?

Usually not for unrelated clients. Clients often need their own plugins, isolation, independent backups and the option to take their site with them, which are easier with separate installs. A central management tool lets you update and monitor separate sites from one place. Multisite suits agencies better when running a family of similar sites for one organisation.

Can each site in a multisite network have its own domain?

Yes. WordPress supports mapping a custom domain to a site in the network. You point the domain to your server, change the site's address in the network admin and make sure the domain has a valid HTTPS certificate.

Is Multisite slower than separate WordPress sites?

Not by itself, because it shares one codebase. But all sites share the same server resources and database, so a busy site or a heavy plugin can slow everything down. Good hosting, caching, object caching and a lean plugin list matter even more on a network.

Do I need wildcard SSL for a subdomain network?

To serve every subdomain over HTTPS with one certificate, you generally need a wildcard certificate, or you need a separate certificate for each subdomain. Subdirectory networks avoid this problem, since one certificate covers the main domain. Ask your host what certificate options your plan supports.

Can I back up and restore one site in a multisite network?

It is possible, but harder than with a single site, because each site has its own database tables and uploads inside a shared installation. Use a backup approach or plugin that supports per-site restores, test it before you need it and keep a full network backup too.

Can I convert an existing WordPress site to Multisite?

Yes, but back up first and plan carefully. WordPress may limit the subdirectory option on an established site, and some plugins need to be deactivated during the setup. Test the conversion on a staging copy before doing it on a live site.

#WordPress#Multisite#Hosting#WordPress Network#Setup#Developer#Agencies
M

Written by Mercy Chepkemoi

SteboHost engineering and operations team. We write practical guides on hosting, domains, email and security for African businesses — based on what we see in the field, not marketing copy.

Ready to get started?

Browse our hosting plans or contact our team for help choosing the right one.