WordPress Multisite Setup: Network and Domain Mapping
WordPress Multisite lets you run several websites from one WordPress installation. The sites share WordPress core, installed plugins and themes, but have their own content tables and upload directories. It is useful for related sites managed by one organization; it is usually the wrong fit for unrelated client websites that need independent hosting, updates, ownership or recovery.
Before you click Network Setup
Choose subdomains (team.example.com) or subdirectories (example.com/team), check DNS and your host’s web-server support, and back up both your database and files. An existing installation over a month old may not offer the subdirectory option. On-demand subdomain creation requires wildcard DNS and a matching server configuration.
Go to the installation steps, DNS and mapped domains, plugin and theme controls or troubleshooting FAQs.
Test recovery and isolation before growing the network
Multisite shares core code and installed plugins, so an update or operational failure can affect several sites. Confirm whether your backup process can restore one site without rolling back unrelated sites.
- Test the intended subdomain or subdirectory structure.
- Check mapped-domain DNS and HTTPS separately.
- Verify site administrators cannot access network-only controls.
- Test uploads, email and scheduled tasks on more than one site.
- Document network-wide plugin decisions and an update rollback.
Domain mapping changes routing; it does not automatically transfer a domain’s registration or email service. For unrelated client sites needing independent ownership and recovery, compare separate installations before committing. Our cloning guide covers a separate-site migration workflow.
Should you use WordPress Multisite or separate installations?
Multisite is an administration model, not a performance upgrade. It centralizes the software stack while keeping sites’ content separate. A school with department sites or one company with regional microsites may benefit; independent businesses with different developers or compliance requirements generally gain more control with separate installations.
| Question | Multisite | Separate installs |
|---|---|---|
| Core updates | One shared installation | Each installation updated independently |
| Plugin versions | Shared plugin files, network or site activation | Each site can run its own stack |
| Content and media | Separate content tables and subsite upload folders | Separate databases and files |
| Outage or compromise | Shared server and software increase the potential blast radius | Failures can be isolated if hosting and credentials are separated |
| Moving one site away | Requires extracting the relevant content and media | Usually simpler to move an entire independent install |
There is no minimum number of sites required for Multisite. The old rule that you need dozens of sites before it makes sense is not a WordPress requirement; two closely related sites may share enough infrastructure to justify it, while a hundred independent clients may not.
Requirements before creating a network
WordPress’s network preparation guide requires access to WordPress administration and the site files. Verify that clean permalinks work, take a complete backup and deactivate active plugins before converting an existing site. Decide on the URL model before activating Multisite: later changes can affect permalinks, login cookies and domain mapping.
For subdomain networks, the host must route the subdomains to the same WordPress document root. Wildcard DNS is required when visitors or users can create new subdomains on demand; manually created sites can be configured individually instead. All publicly accessible domains also need appropriate HTTPS certificates. For a path-based network, ensure the host handles WordPress rewrite rules; Apache uses .htaccess, while Nginx uses its own server configuration.
Compare hosting before consolidating sites →
How to install WordPress Multisite in six steps
Step 1. Back up the site and check the URL options
Download a verified backup of the WordPress files and database, including wp-content/uploads. Test the restore if this is a live business site. Check whether your existing WordPress address uses localhost, an IP address, a nonstandard port or a subdirectory. WordPress restricts which network types you can select under those circumstances. An established site older than a month generally cannot select a new path-based network through the normal wizard.
Step 2. Allow Multisite in wp-config.php
Open wp-config.php in your WordPress installation and insert this line above the final “stop editing” comment or, if absent, before the main require or include line:
define( 'WP_ALLOW_MULTISITE', true );Save the file and reload WordPress administration. This switch enables the installer menu; it does not by itself create a network. If you cannot safely edit the file, ask your host or developer to do it instead of editing a production configuration blindly.
Step 3. Choose subdomains or subdirectories
In the WordPress dashboard, open Tools → Network Setup. Select the available URL structure, supply a network title and check the administrator email. A domain-based structure creates addresses such as shop.example.com; a path-based network creates example.com/shop. If the choice is missing, consult WordPress’s published restrictions rather than assuming your installation is broken.
Click Install only after confirming the network type. A path-based network may place a /blog/ prefix before posts on the main site to avoid collisions with subsite paths, so check the impact on existing URLs and redirects.
Step 4. Add the configuration WordPress generates
The Network Setup screen prints installation-specific lines for wp-config.php and, on Apache, rewrite rules for .htaccess. Back up those files separately, copy the generated lines into their indicated locations, and preserve unrelated web-server rules. Do not paste a random Multisite rewrite block from an older tutorial: subdomain, subdirectory and hosting configurations differ.
If you use Nginx, ask your host to implement the equivalent routing in its configuration because Nginx does not use Apache’s .htaccess file. Sign out and sign back in as directed by the installer.
Step 5. Configure Network Admin and create a subsite
Open My Sites → Network Admin → Sites → Add New. Enter the site’s address, title and administrator email. The new site has its own posts, settings and media, while its plugins and themes are installed in the shared WordPress directory. Review Network Admin → Settings for user registration, site creation and upload policies; do not allow public site signups unless that is intentional.
Step 6. Test each hostname, TLS certificate and the recovery plan
Open the main site and every subsite in a fresh browser session. Confirm HTTPS, working links, media uploads, a site administrator’s limited permissions and plugin behavior on each site. Take a new network-wide backup and test restoring it to staging; a backup that only contains the main site’s content is insufficient for recovering the network.
Subdomain DNS and domain mapping explained
Subdomains: create an individual DNS record for each planned hostname, or configure a wildcard record such as *.example.com when your network needs on-demand subdomains. The web server must also recognize the hostnames and send them to the same WordPress installation. DNS alone cannot enable Multisite routing.
Separate custom domains: WordPress has supported native Multisite domain mapping since version 4.5. For a site that should appear at example-two.com, point that domain’s DNS to the correct hosting destination, configure web-server routing and its TLS certificate, then update the subsite’s domain in Network Admin. Follow WordPress’s domain-mapping documentation. A wildcard certificate for *.example.com does not cover a completely different custom domain.
Existing-site caveat: moving an established standalone site into a network is not the same as clicking Add New. Its users, media paths, table prefixes, URLs and SEO redirects require a deliberate migration plan.
Installing themes and plugins in WordPress Multisite
The super administrator installs plugins and themes centrally. A regular site administrator manages that site’s content and activates only items made available to it, subject to network policy.
Plugins: Network Activate makes a plugin active across the network. If you install it without network activation, a subsite can activate it only where the network’s settings and that plugin permit. Test compatibility: a plugin might write a single global settings table, assume the original uploads path, or be licensed per site even though its files are installed once.
Themes: Network Enable makes a theme available to sites; it does not force every subsite to use it. You can enable a particular theme for a specific subsite from the network site’s settings. Check each vendor’s licence terms before assuming a single-site commercial licence covers all mapped domains.
SEO and monetization: each site still needs appropriate titles, canonicals, sitemap inclusion, analytics and any applicable affiliate settings. A shared Rank Math installation does not make every subsite’s metadata correct automatically. Avoid publishing near-identical articles across regional sites merely because they share a theme.
Multisite hosting and backup buying checklist
Before choosing a hosting plan, establish how many sites share traffic spikes, whether it supports your DNS and TLS layout, and whether support will help with network-specific restore and domain-mapping problems. Ask how a backup can restore one subsite separately, not just the entire shared installation. Many ordinary backup plugins have plan limits or extra steps for Multisite; inspect those requirements before buying.
A multisite network does not automatically provide stronger isolation. A vulnerable network-activated plugin or exhausted shared server can affect more than one site. Maintain least-privilege administrator accounts, test upgrades on staging and store recoverable backups away from the server.
Frequently asked questions
How do I enable WordPress Multisite?
Add define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php, visit Tools → Network Setup, choose an allowed network type, and follow the installer-generated configuration steps for your server. Back up the existing site first.
Can WordPress Multisite use different domain names?
Yes. Native domain mapping is available in WordPress; each mapped domain also needs DNS routing, web-server configuration and an appropriate HTTPS certificate.
Does Multisite require at least 50 websites?
No. WordPress has no such minimum. Choose it when shared governance and software are useful, not simply because your site count crosses a threshold.
Why can’t I choose subdirectories on an old WordPress installation?
WordPress restricts path-based network creation through the standard installer when an existing site has been established for more than a month, to avoid permalink collisions. Review the official network-preparation guide and plan any conversion carefully.
Do plugins and themes work on every subsite automatically?
No. The super administrator installs them centrally, but availability, site activation and network activation differ. Compatibility and commercial licensing need to be checked for each plugin or theme.
Is a multisite network faster or cheaper than separate sites?
Not necessarily. It centralizes maintenance and shared software, but sites still consume CPU, storage and bandwidth, and some backups, migrations or plugin licences may become more complex. Compare actual hosting and operational requirements instead of assuming savings.
Next step: verify your network prerequisites and hosting options, then follow the official Create a Network procedure on a staging copy before enabling it on a live site.
