Convert a Standalone WordPress Instance into a WordPress Multisite

Transforming an existing WordPress install into a multisite is rather straightforward, but there are a few steps involved. Let’s do this:

Edit wp-config.php to Allow Multisite

You’ll need to start first by editing the local wp-config.php file for the install. This can be done straight from File Manager by going to the install directory, selecting wp-config.php and clicking edit.

Copy/Paste the following lines into the wp-config.php file above the line that begins with “require_once(”:

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


Once you’ve added the lines, click save. You will want to keep this window open, as we will be returning to it later.

Deactivate Plugins and Create Network

Now log into your WP dashboard, and deactivate all plugins. Plugins can be reactivated after the multisite switch has been made.

Go to Tools > Network Setup.


Edit the Network Title & Admin Email address if need be, and then click install. You’ll then be given a set of instructions that are pretty self-explanatory, but I’ll go ahead and walk them through here as well!

Editing .htaccess + wp-config.php

Go back to the editing window of your wp-config.php file. Copy/Paste the following code above the line that says / That’s all, stop editing! Happy blogging. / Replace with your domain.

define('MULTISITE', true); 
define('SUBDOMAIN_INSTALL', true); 
define('DOMAIN_CURRENT_SITE', ' **** ');
define('PATH_CURRENT_SITE', '/'); 
define('SITE_ID_CURRENT_SITE', 1); 
define('BLOG_ID_CURRENT_SITE', 1);

Once you’ve added the lines, click save .

We’re now going to edit the local .htaccess file. This file is considered a hidden file in your File Manager, so if you’re not seeing it right off the bat, go to Settings in the top right corner, check Show Hidden Files, and click save.


Now open the editing window of the .htaccess file in the corresponding directory of the domain you’re working with. Add the following code, replacing all existing WordPress rules.

RewriteEngine On 
RewriteBase / 
RewriteRule ^index\.php$ - [L] 

# add a trailing slash to /wp-admin 
RewriteRule ^wp-admin$ wp-admin/ [R=301,L] 

RewriteCond %{REQUEST_FILENAME} -f [OR] 
RewriteCond %{REQUEST_FILENAME} -d 
RewriteRule ^ - [L] 
RewriteRule ^(wp-(content|admin|includes).*) $1 [L] 
RewriteRule ^(.*\.php)$ $1 [L] 
RewriteRule . index.php [L]

Once you’ve added the lines, click save .

Adding a Wildcard Subdomain

In a non-Multisite scenario, creating an additional WordPress site involves installing the WP app, but also making sure that the location (i.e. subdomain or addon domain) has been created beforehand. There’s that extra step where you have to tell your cPanel where you’ll be installing WordPress before you actually do it.

A WordPress Multisite is self-service in the sense that you can create a WordPress site straight from the WP Multisite dashboard without dealing with other aspects of the cPanel. To achieve this, however, you have to tell your cPanel right from the get go: “ Hey, I’ll be adding subdomains. I’m not sure what they are yet, so just accept all future subdomains that I create. ” This is accomplished by creating a wildcard subdomain in your account. 

Keep in mind that wildcard SSL certificates will only work in shared hosting if the domain is using Reclaim Hosting's nameservers.

From your cPanel,go to the Domains section and click on Subdomains.

  1. In the subdomain section, type an asterisk (*).
  2. In the domain section, select from the drop-down menu.
  3. Change the document root to match the directory of
  4. Click create .


The Last Step

We’re almost there! You’ll need to Log out/Log back into your WP Multisite. Reactivate your plugins. You should be all set!

Was this article helpful?
0 out of 1 found this helpful

Articles in this section

Reclaim Hosting Support Hours
8:00 am - 5:00 pm ET, Monday through Friday
Submit a Ticket
Get a quick and helpful response from the pros.
Need Extra Support?
No problem, we're here to help! Talk to us about Professional Services or custom Service Level Agreements.