A website owner planning several WordPress sites from one content management system

Editorial illustration; it does not show a real WordPress network or server.

Published on October 21, 2026.

Running several related websites can become repetitive. You update the same WordPress core files, install the same security tools, check several dashboards and then repeat the process for the next site. WordPress Multisite can reduce that duplication by letting multiple sites share one WordPress installation.

That does not mean Multisite turns several sites into one website. Each site can have its own content, settings, users and URL. The network shares the WordPress core and can share themes and plugins, while a network administrator controls the parts that individual site administrators are allowed to use.

This guide explains how to enable WordPress Multisite on a self-hosted WordPress installation. It is written for a site where you can edit server files such as wp-config.php and .htaccess or the equivalent web-server configuration.

Quick Answer

To enable WordPress Multisite:

  1. Confirm that a network is the right architecture and make a complete backup.
  2. Deactivate active plugins and confirm that pretty permalinks work.
  3. Add define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php.
  4. Open Tools > Network Setup in the WordPress dashboard.
  5. Choose a subdomain or subdirectory network and enter the network details.
  6. Click Install, then copy the exact wp-config.php and rewrite rules WordPress provides.
  7. Log in again and confirm that My Sites > Network Admin is available.
  8. Add a test site and verify its URL, dashboard, theme and login behaviour.

The configuration shown by your own WordPress installation takes priority over copied examples. WordPress generates different rewrite rules depending on your URL, network type and server setup.

Before You Enable Multisite

Make sure you actually need a network

Multisite is useful when several sites should be administered together: a company may have a main site, regional sites and campaign sites; a school may have separate sites for departments; or an organisation may manage many related publications.

It is less suitable when the sites need completely separate hosting, release schedules, administrators or databases. A network can share infrastructure, but it also creates a shared operational dependency. A mistake in a network-wide plugin or update can affect every site.

If you only need different layouts or restricted sections inside one website, a single WordPress installation may be simpler. WordPress’s own preparation guide recommends deciding this before creating the network.

Understand the two URL models

You must choose how additional sites will be addressed:

  • Subdirectory network: example.com/shop and example.com/news
  • Subdomain network: shop.example.com and news.example.com

Subdirectories are often easier to start with because they use the same domain and do not require wildcard DNS. However, WordPress notes that an existing installation may not be able to choose subdirectories if it has already been running for more than a month, because existing permalink structures can conflict with the new paths.

Subdomains require DNS and server support. If you want users to create subdomain sites on demand, you normally need a wildcard DNS record such as *.example.com pointing to the appropriate server, plus a web-server configuration that sends those hostnames to the WordPress installation.

Do not select a network type just because the option looks familiar. Check the current WordPress URL, hosting control panel and DNS setup first.

Prepare access and a rollback plan

You normally need:

  • Administrator access to the existing WordPress site
  • Access to the server’s files through SSH, SFTP or a hosting file manager
  • Permission to edit wp-config.php
  • Permission to edit .htaccess, nginx.conf or the equivalent server rules
  • A database backup and a copy of the WordPress files
  • A maintenance window if the site is important or heavily used

Store the backup somewhere separate from the server. Before changing anything, confirm that you know how to restore the database and files. A backup that has never been tested is only an assumption.

Step 1: Check the Existing WordPress Installation

Log in to the current WordPress dashboard and check Settings > Permalinks. Pretty permalinks should work before you create a network. Open a few posts and pages in a private browser window and confirm that their URLs return the expected content.

Also check whether WordPress Address (URL) and Site Address (URL) are configured as expected. WordPress cannot create some network types when the URL uses a non-standard port. A local setup using localhost or an IP address has additional restrictions, especially for subdomain testing.

If WordPress is installed in a subdirectory, decide whether you want the network URLs to follow that structure. Moving WordPress during the same change increases the number of variables, so complete the move and test it first if a move is necessary.

Step 2: Back Up and Deactivate Active Plugins

Create a database backup and copy the WordPress files, including wp-config.php and the existing rewrite configuration. Record the active themes and plugins so you can restore the previous state if something goes wrong.

From the dashboard, go to Plugins > Installed Plugins and deactivate the active plugins temporarily. This does not delete them. It reduces the chance that a plugin interferes with network creation or changes the configuration screen.

Do not reactivate everything immediately after installation. Bring plugins back in a controlled order and test the main site and a new test site after each important change.

Step 3: Enable the Network Setup Menu

Open wp-config.php in a backup-aware editor. Add the following line above the comment that says That's all, stop editing! Happy publishing.:

/* Multisite */
define( 'WP_ALLOW_MULTISITE', true );

If the comment is not present, add the setting above the first line that begins with require or include, as described in the official WordPress instructions. Keep the spelling, punctuation and quotes exactly as shown.

Save the file and return to the WordPress dashboard. Refresh the page. You should now see Network Setup under the Tools menu.

If the menu does not appear, check that you edited the wp-config.php used by this installation, that the line is outside another PHP statement, and that the file remained valid PHP. Check the PHP error log before making additional changes.

Step 4: Open Network Setup and Choose the Structure

Go to Tools > Network Setup. WordPress will display the Create a Network of WordPress Sites screen.

Choose Sub-domains or Sub-directories. Think about the examples shown on the screen and the restrictions discussed earlier. The choice affects the URLs of new sites and can be difficult to change safely later.

Then review the network details:

  • Network Title: the name used for the network as a whole
  • Network Admin Email: the address used for network administration and support notifications
  • Server Address: the domain currently serving the WordPress installation

Read the warnings on the page. A warning about wildcard subdomains may not apply if you plan to add sites manually or use a subdirectory network, but do not ignore a warning about your actual hosting setup.

When the details are correct, click Install.

Step 5: Apply the Generated Configuration

After installation, WordPress displays two sets of instructions. One set adds network constants to wp-config.php; the other adds rewrite rules to .htaccess or the equivalent web-server configuration.

Copy the exact snippets shown for your installation. Do not replace them with a generic snippet from a different WordPress version or URL model. The generated rules may differ for subdomains, subdirectories and installations with WordPress in a separate directory.

Before editing, make another copy of wp-config.php and .htaccess. Add the new wp-config.php lines immediately after the WP_ALLOW_MULTISITE line, unless WordPress shows a different placement. If an existing .htaccess contains old WordPress rewrite rules, follow the screen’s instruction about replacing those WordPress lines while preserving unrelated server rules.

If the server uses Nginx, there may be no .htaccess file. You will need to apply the equivalent rules in the Nginx configuration and reload Nginx. If you do not control the server configuration, ask the hosting provider whether WordPress Multisite and the chosen network type are supported.

Step 6: Log In Again as the Network Administrator

Return to the login screen using the link WordPress provides and sign in again. The new configuration changes the dashboard menus and cookies, so logging in again is expected. If the browser behaves strangely, clear cookies for the site or test in a private window.

After logging in, open My Sites in the admin toolbar. You should see Network Admin. The Network Admin area is available to a Super Admin, not automatically to every administrator of an individual site.

Open Network Admin > Dashboard and then Network Admin > Settings. Review the network name, administrator email, registration settings, upload limits and default language. Leave user and site registration disabled unless you have a clear moderation and support process.

Step 7: Create and Test a Site

Go to Network Admin > Sites > Add New. Enter:

  1. The site address, such as news or department
  2. The site title
  3. The site language
  4. The administrator email

Click Add Site. Visit the new site and open its dashboard. Check that the URL resolves, the dashboard loads, media uploads work and the intended theme is available.

Remember that a site administrator can manage content and site settings but may not be allowed to install plugins or themes. Network administrators install those resources and can network-activate a plugin for every site. WordPress documents network activation as a separate administrative action, so decide carefully which tools should be available everywhere.

Test the original site as well. Open an existing post, submit a form if the site has one, upload a small image and sign in from a separate browser session. A network setup is not complete until both the original site and the new site behave correctly.

Common Problems

Network Admin does not appear

Confirm that the final wp-config.php constants are present and that you logged in again. Check that the account is a Super Admin. On an existing network, the link is normally under My Sites > Network Admin rather than the regular site dashboard.

New subdomain returns a DNS error

Check the DNS record and whether the web server accepts the hostname. A wildcard subdomain is useful for on-demand subdomain sites, but it must point to the server and be covered by the site’s TLS certificate. A DNS record alone is not enough if the web server routes the hostname elsewhere.

New site returns a 404

Check the rewrite rules, pretty permalinks and web-server configuration. For subdomains, verify that the hostname reaches the same WordPress document root. For Nginx, confirm that the equivalent Multisite rules were applied and the configuration was reloaded.

Plugins or themes are missing

This may be normal. Network Admin controls installation and network activation. Review Network Admin > Themes and Network Admin > Plugins, then enable only the resources that every site should use. Test plugin compatibility before network-activating it.

My Take

WordPress Multisite is most valuable when the shared administration is a real advantage, not merely because the feature exists. The network can reduce repeated maintenance, but it also raises the impact of configuration mistakes and plugin failures. Start with one test site, keep registration closed, document who can act as Super Admin and make backups part of the routine.

The safest implementation is deliberately unexciting: choose the URL model first, copy the configuration WordPress generates, verify DNS and rewrites, then test one site at a time.

Bottom Line

To enable WordPress Multisite, add WP_ALLOW_MULTISITE, use Tools > Network Setup, select subdomains or subdirectories, apply the generated configuration and log in again as a Super Admin. The technical steps are straightforward, but the preparation matters more than the checkbox: make a backup, understand your URLs and confirm that your host supports the required rewrite and DNS behaviour.

Sources