Running three client sites means three separate WordPress installs, three sets of plugin updates, and three logins to keep straight — unless you turn on Multisite. WordPress Multisite lets one WordPress install run a whole network of sites, sharing a single codebase, one set of plugins, and one wp-admin login for the network admin. It's a good fit for agencies, franchise sites with a shared theme, or a magazine with multiple regional editions. It's a bad fit if you just want two unrelated sites — for that, an addon domain is simpler and safer.
This guide walks through the one decision you can't easily undo later (subdomain vs subdirectory), the DNS and cPanel prep you need before touching wp-config.php, and the errors people hit most often right after flipping the switch.
What Multisite Actually Changes
Multisite doesn't install WordPress multiple times. It adds two new database tables per site (wp_2_options, wp_2_posts, and so on, numbered per site) on top of your existing tables, and it adds a Network Admin dashboard above your normal wp-admin. Themes and plugins live in one wp-content folder and get shared across every site on the network — you activate a plugin once per site, or network-activate it for all of them at once.
The upside is one WordPress core to update, one set of plugin files to patch for a vulnerability, and one login for you as the admin. The downside is that a bad plugin, a maxed-out PHP memory limit, or a crashed database table can take every site on the network down at once, not just one.
Subdomain vs Subdirectory: Pick Before You Enable
WordPress asks you to choose this during setup, and while it's technically possible to switch later, it involves rewriting URLs across the whole database — treat it as a one-way door and pick carefully up front.
| Subdomain | Subdirectory |
|---|---|
site1.example.com | example.com/site1 |
Needs a wildcard DNS record (*.example.com) | No DNS changes needed |
| Wildcard SSL cert covers all sites automatically | Single cert on the main domain covers everything |
| Google treats each subdomain as a separate property in Search Console | All sites share SEO authority under one domain |
| Good for: distinct brands/regions under one company | Good for: sections of one site (blog, docs, shop) |
One catch that trips people up: you must decide subdomain vs subdirectory before WordPress writes any site content, and if your WordPress install is already older than a few weeks with real posts and pages, WordPress will hide the subdirectory option and force subdomain mode. That's a WordPress core restriction, not a bug.
Before You Touch wp-config.php
Do these three things first, in this order:
- Take a full backup. Database and files, through cPanel's Backup Wizard or JetBackup if your SkyServer plan includes it. Multisite conversion is reversible in theory, but not something you want to debug live.
- Add a wildcard DNS record if you're going the subdomain route. In cPanel's Zone Editor, add an A record for
*pointing to your server's IP, same as your existingwwwrecord. Give it time to propagate before testing — DNS changes aren't instant. - Deactivate all plugins. Multisite conversion runs a database schema change, and a plugin hooking into that process mid-way is a common cause of a blank wp-admin afterward. Reactivate once the network is confirmed working.
Enabling the Network
Add this line to wp-config.php, above the line that says /* That's all, stop editing! */:
define( 'WP_ALLOW_MULTISITE', true );Save the file, reload wp-admin, and a new Network Setup option appears under Tools. Fill in the network title, pick subdomain or subdirectory, and click Install. WordPress will hand you two more blocks of code:
- A second block for
wp-config.php— defines likeMULTISITE,SUBDOMAIN_INSTALL,DOMAIN_CURRENT_SITE, andPATH_CURRENT_SITE. Paste these in exactly where WordPress shows them, replacing theWP_ALLOW_MULTISITEline you added earlier. - Rewrite rules for
.htaccess(or an equivalent block if you're on Nginx). On cPanel/Apache, paste these above the existing WordPress block in.htaccess, accessible via File Manager or FTP.
Log out and back in — Multisite requires a fresh session cookie. You should now see "My Sites" in the top admin bar instead of a single site name.
Common Errors Right After Enabling
Blank wp-admin or "Network Already Enabled"
Almost always a leftover or duplicated define in wp-config.php. Check for two MULTISITE lines, or a WP_ALLOW_MULTISITE line still sitting below the new network block — remove it, only the four network-setup constants should remain.
New Subdomain Site Shows DNS_PROBE_FINISHED_NXDOMAIN
The wildcard DNS record either hasn't propagated yet or wasn't added. Confirm it with:
dig site1.example.com +shortIf that returns nothing, go back to Zone Editor and check the * A record actually saved — a common mistake is adding it as *.example.com when cPanel's Zone Editor already appends the domain, which ends up creating *.example.com.example.com.
New Site Loads but Shows a 404 or the Wrong Site's Content
Usually stale rewrite rules. Regenerate permalinks from Network Admin → Sites → (select site) → Settings, or re-save the .htaccess block WordPress originally provided — a manual edit to it later often breaks the site-routing regex.
A Plugin Works on the Main Site but Not New Ones
Plugins activated on a single site before Multisite was enabled don't carry over automatically. Go to Network Admin → Plugins and either network-activate the plugin (turns it on everywhere) or activate it per-site under each site's own Plugins screen.
SSL on a Multisite Network
Subdirectory installs need nothing extra — one cert on the main domain covers every subdirectory site. Subdomain installs need a wildcard certificate. cPanel's AutoSSL can usually issue one automatically once the wildcard DNS record resolves correctly, but check under WHM > Manage AutoSSL that wildcard issuance is enabled for the account, since it's not on by default on every plan. If AutoSSL can't reach a wildcard cert, each new subdomain shows a certificate mismatch warning until you generate or renew one.
Prevention: Keep the Network Stable Long-Term
- Test plugin and theme updates on a staging site within the network before network-activating them everywhere — one incompatible update now affects every site, not one.
- Set a per-site upload storage limit under Network Admin → Settings if multiple people manage different sites, so one site can't fill the shared disk quota.
- Keep an eye on PHP memory_limit — a network with a dozen active sites and plugins needs more headroom than a single install; 256M is a safer floor than the WordPress default.
- Document which plugins are network-activated vs per-site somewhere outside WordPress itself. Six months in, nobody remembers.
Frequently Asked Questions
Can I convert an existing single WordPress site into the main site of a network?
Yes. Your current site becomes the primary site on the network (usually site ID 1), and its existing posts, pages, and media stay exactly where they are. Everything above still applies — back up first.
Do I need a separate cPanel account or hosting plan for each site on the network?
No. All sites in a Multisite network share one WordPress install, one database, and one hosting account. That's the whole point — if you need sites on entirely separate hosting resources, addon domains or separate accounts are the better fit, not Multisite.
Can I mix subdomain sites and completely separate custom domains on the same network?
Yes, with the Domain Mapping approach: point an external domain's DNS at your server, then add it as a mapped domain to a specific site in the network via a plugin like WordPress MU Domain Mapping, or natively in recent WordPress versions through the site's domain field in Network Admin. It needs its own SSL certificate since it's outside the wildcard.
Will my current theme and plugins work once Multisite is on?
Most will, but any plugin or theme that assumes a single wp_options table or hardcodes site_url() can misbehave. Deactivate everything before conversion, then reactivate one at a time so a problem plugin is easy to spot.
How do I remove a site from the network without deleting the whole network?
Go to Network Admin → Sites, hover over the site, and click Delete. This removes that site's database tables and uploaded files but leaves the rest of the network untouched. There's no undo, so export any content you want to keep first.
