How to Set Up WordPress Multisite

WordPress Multisite allows you to run multiple WordPress websites from a single WordPress installation. Instead of installing and maintaining WordPress separately for every website, you can create a network where multiple sites share the same WordPress core, themes, and plugins.

Multisite is useful for businesses, educational institutions, agencies, franchises, membership organizations, and developers who need to manage several related websites from one dashboard.

In this guide, you will learn how to enable WordPress Multisite, configure the network, create additional sites, manage users, install themes and plugins, and avoid common Multisite problems.

What Is WordPress Multisite?

WordPress Multisite is a built-in WordPress feature that lets you create and manage a network of websites using one WordPress installation.

For example, a company could have:

• example.com — Main company website
• example.com/blog — Blog
• example.com/support — Support website
• example.com/store — Store website

Alternatively, each website can use a subdomain:

• site1.example.com
• site2.example.com
• shop.example.com

All sites are managed from the same WordPress installation.

How Multisite Works

A normal WordPress installation generally contains one website. With Multisite, one WordPress installation can contain multiple sites.

The sites share:

• WordPress core files
• Installed themes
• Installed plugins
• User accounts
• Server resources

However, individual sites can have their own:

• Posts and pages
• Media library
• Settings
• Menus
• Widgets
• Content
• Site administrators

WordPress Multisite vs Multiple WordPress Installations

Feature	WordPress Multisite	Separate WordPress Sites
WordPress core	Shared	Separate
Management	Centralized	Individual
Themes	Network-controlled	Installed separately
Plugins	Network-controlled	Installed separately
Updates	Easier to manage centrally	Managed separately
Database	Shared database structure	Separate databases
Site independence	Lower	Higher
Best for	Related websites	Completely independent websites

Multisite is convenient, but it is not always the right solution. If every website needs completely independent hosting, plugins, users, or server configurations, separate WordPress installations may be more appropriate.

---

Requirements for WordPress Multisite

Before enabling Multisite, make sure your hosting environment meets the normal WordPress requirements.

You should have:

• A working WordPress installation
• Administrator access
• Access to wp-config.php
• Access to the WordPress files
• Database access
• HTTPS configured
• Sufficient server storage and memory
• A hosting environment that supports Multisite

For production websites, it is strongly recommended to create a complete backup before making configuration changes.

Subdomain or Subdirectory?

During Multisite setup, you can generally choose between two network structures.

Subdomain Structure

Example:

example.com
site1.example.com
site2.example.com

This structure is useful when each site should appear as a separate subdomain.

Subdirectory Structure

Example:

example.com
example.com/site1
example.com/site2

This can be convenient when all sites are closely related and you want to keep them under the main domain.

Which Structure Should You Choose?

Structure	Example	Suitable For
Subdomain	site1.example.com	Separate brands, departments, locations
Subdirectory	example.com/site1	Related sections or projects

The choice should be made carefully because changing the network structure later can require additional migration work.

---

Step 1: Create a Complete Backup

Before enabling Multisite, create backups of:

• WordPress files
• Database
• wp-config.php
• .htaccess
• Uploaded media
• Themes
• Plugins

A backup gives you a recovery option if configuration changes cause problems.

If your hosting provider offers automated backups, verify that the backup completed successfully before proceeding.

---

Step 2: Disable Your Plugins Temporarily

Go to:

WordPress Dashboard → Plugins → Installed Plugins

Deactivate your plugins before enabling Multisite.

This can help prevent plugin conflicts during the network configuration process.

After the Multisite setup is complete, you can reactivate compatible plugins.

---

Step 3: Enable Multisite in wp-config.php

Locate the WordPress installation’s wp-config.php file.

You can usually find it in the main WordPress directory.

Open the file and locate:

/* That's all, stop editing! Happy publishing. */

Add the following line immediately above it:

define( 'WP_ALLOW_MULTISITE', true );

Save the file.

Your configuration should look similar to:

define( 'WP_ALLOW_MULTISITE', true );

/* That's all, stop editing! Happy publishing. */

---

Step 4: Open the Network Setup Screen

Log in to your WordPress administrator dashboard.

Go to:

Tools → Network Setup

WordPress will display the Multisite network configuration screen.

You may be asked to choose between:

• Subdomains
• Subdirectories

Select the structure that matches your planned network.

You will also need to provide:

• Network Title
• Network Admin Email

Review the settings and click:

Install

---

Step 5: Add Multisite Configuration to wp-config.php

WordPress will provide configuration instructions after you click Install.

It will normally provide code that needs to be added to wp-config.php.

The configuration can look similar to:

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 );

The exact values generated by WordPress may differ depending on your domain and network configuration.

Use the code generated by your own WordPress installation rather than copying values from another website.

---

Step 6: Update .htaccess

WordPress will also provide rules that need to be added to your .htaccess file.

For example, a Multisite installation using subdirectories may contain rewrite rules similar to:

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

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]

The exact rules depend on your WordPress configuration.

Again, use the .htaccess instructions generated by WordPress.

---

Step 7: Log In Again

After modifying wp-config.php and .htaccess, log out of WordPress and log in again.

You should now see a new menu at the top of the WordPress dashboard called:

My Sites

From there, you can access the Network Admin dashboard.

---

Step 8: Open Network Admin

Go to:

My Sites → Network Admin → Dashboard

The Network Admin area provides centralized control over the entire Multisite network.

You can manage:

• Sites
• Users
• Themes
• Plugins
• Network settings
• Updates
• Network-wide configuration

The normal WordPress dashboard manages an individual website, while Network Admin manages the entire network.

---

Step 9: Configure Network Settings

Go to:

Network Admin → Settings → Network Settings

Here you can configure options such as:

• Network title
• Network administrator email
• Registration settings
• New site settings
• Upload settings
• Language
• Registration restrictions

For example, you can decide whether users are allowed to register new accounts or whether existing users can create websites.

For a private business network, it is usually better to restrict public registration unless you specifically need it.

---

Step 10: Create Your First Additional Website

Go to:

My Sites → Network Admin → Sites → Add New

You will see fields such as:

• Site Address
• Site Title
• Site Language
• Admin Email

For example:

Site Address: support
Site Title: Support Center
Site Language: English

Depending on your network structure, WordPress may create:

example.com/support

or:

support.example.com

Click:

Add Site

Your new WordPress site is now part of the network.

---

Step 11: Configure the New Site

Go to:

Network Admin → Sites → All Sites

Find the new website and select:

Dashboard

You can then configure its:

• General settings
• Permalinks
• Reading settings
• Discussion settings
• Users
• Themes
• Content

Each site can have its own website-specific configuration.

---

Step 12: Understand Network Administrators

One of the most important concepts in Multisite is the difference between a Network Administrator and a Site Administrator.

Network Administrator

A Network Administrator can manage the entire network.

They can generally:

• Create sites
• Delete sites
• Manage network users
• Install themes
• Activate themes
• Install plugins
• Network-activate plugins
• Change network settings

Site Administrator

A Site Administrator manages an individual website.

Depending on network settings, they may not be able to:

• Install plugins
• Install themes
• Change network-wide settings
• Create new network sites

This separation is useful when multiple teams manage different websites.

---

Step 13: Install Themes for the Network

Go to:

Network Admin → Themes

You can install WordPress themes from the network administration area.

After installing a theme, you can choose whether to:

• Network Enable it
• Enable it for a particular site

Network activation makes the theme available across the network.

However, availability and activation behavior can depend on the network configuration and WordPress theme type.

---

Step 14: Install Plugins for Multisite

Go to:

Network Admin → Plugins → Add New

Install the required plugin.

After installation, you can choose:

Network Activate

This activates the plugin across the network.

Some plugins allow individual site administrators to control activation, while others are intended to be controlled by the network administrator.

Always check whether a plugin explicitly supports WordPress Multisite before deploying it across a production network.

---

Step 15: Configure Permalinks

For each website, check:

Settings → Permalinks

Choose an appropriate permalink structure.

A commonly used structure is:

/%postname%/

Save the settings.

If you experience unexpected 404 errors after configuring Multisite, saving the permalink settings again can sometimes refresh the rewrite configuration.

---

Step 16: Configure HTTPS

Every site in a production Multisite network should use HTTPS.

For example:

https://example.com
https://site1.example.com
https://site2.example.com

For subdomain-based networks, make sure the SSL certificate covers the required subdomains.

A wildcard certificate such as:

*.example.com

can cover many subdomains, subject to the certificate’s scope and hosting configuration.

For subdirectory networks, the main domain’s certificate is generally sufficient because the sites use paths under the same hostname.

---

Step 17: Configure DNS for Subdomain Multisite

If you use subdomains, DNS must be configured correctly.

For example:

site1.example.com
site2.example.com
site3.example.com

Your DNS configuration needs to direct these hostnames to the WordPress server.

A wildcard DNS record is often used:

*.example.com

The exact DNS record depends on your hosting environment.

After changing DNS, allow sufficient time for DNS propagation.

---

Step 18: Configure Wildcard Subdomains

Subdomain-based Multisite installations often require wildcard subdomain handling.

Depending on your server, you may configure a wildcard DNS record and corresponding web server configuration.

For example:

*.example.com

This allows requests such as:

blog.example.com
shop.example.com
support.example.com

to reach the appropriate server.

The exact configuration differs between Apache, Nginx, managed hosting platforms, and control panels.

---

Step 19: Add Users to Individual Sites

Go to:

Network Admin → Users

You can create users centrally and assign them to sites.

For example:

User: editor1
Site: example.com/blog
Role: Editor

The same user can also have access to another website:

example.com/store
Role: Author

This is one of the major benefits of Multisite because a single account can access multiple websites in the network.

---

Step 20: Manage Media and Storage

Each Multisite website maintains its own media content.

For example:

Site A → Media
Site B → Media
Site C → Media

The media libraries are generally separate from the user’s perspective.

However, all sites share the server’s available storage.

If your network contains hundreds of websites, monitor:

• Disk usage
• Inode usage
• Database size
• CPU usage
• RAM usage
• Backup size

---

Step 21: Understand the Multisite Database

WordPress Multisite stores information using multiple database tables.

For example, the main site may use tables such as:

wp_posts
wp_postmeta
wp_options

Additional sites can have site-specific tables using IDs:

wp_2_posts
wp_2_postmeta
wp_2_options

wp_3_posts
wp_3_postmeta
wp_3_options

The exact table prefix depends on your WordPress configuration.

Because multiple websites depend on the same database, database backups are especially important.

---

Step 22: Back Up the Entire Network

Do not treat Multisite as a collection of unrelated websites.

A complete backup should include:

• WordPress core files
• wp-content
• Plugins
• Themes
• Uploads
• Database
• wp-config.php
• Server configuration where appropriate
• DNS configuration information

Test your backups periodically.

A backup that has never been restored should not be considered fully tested.

---

Step 23: Protect the Network

Multisite can increase the impact of a security problem because multiple websites share the same WordPress installation.

Use security practices such as:

• Keep WordPress updated
• Keep plugins updated
• Keep themes updated
• Remove unused plugins
• Use strong passwords
• Enable appropriate administrator protection
• Use HTTPS
• Restrict administrator access
• Monitor login activity
• Maintain regular backups
• Use reputable plugins
• Review user permissions

A compromised network-level administrator account can affect multiple websites, so administrator accounts deserve particular protection.

---

Step 24: Prevent Unwanted Site Registration

If you do not want visitors to create websites, configure registration restrictions.

Go to:

Network Admin → Settings → Network Settings

Review the registration options.

You can disable site registration and user registration when they are not required.

This is particularly important for private corporate networks.

---

Step 25: Use Multisite for Staging or Development

Multisite can be useful for development environments.

For example:

client1.example.com
client2.example.com
client3.example.com

Each website can contain a separate development project while sharing the same WordPress installation.

However, avoid treating Multisite as a replacement for proper staging and backup systems.

---

Common WordPress Multisite Problems

1. Network Setup Option Is Missing

If Tools → Network Setup does not appear, check that:

define( 'WP_ALLOW_MULTISITE', true );

has been added correctly to wp-config.php.

Also make sure you are logged in as an administrator.

---

2. Subdomain Sites Do Not Load

Check:

• DNS records
• Wildcard DNS configuration
• SSL certificate
• Apache/Nginx configuration
• WordPress Multisite settings
• Domain configuration

For example, verify that:

site.example.com

actually resolves to the correct server.

---

3. 404 Errors After Enabling Multisite

Check the .htaccess rules or web server rewrite configuration.

Then visit:

Settings → Permalinks

and save the permalink settings again.

---

4. CSS or JavaScript Is Not Loading

Check the browser developer console.

Look for:

• 404 errors
• Mixed-content warnings
• Incorrect URLs
• HTTP/HTTPS conflicts
• Cached files

Make sure the website and WordPress URLs use HTTPS consistently.

---

5. Plugins Do Not Appear for Site Administrators

The network administrator may have control over plugin activation.

Check:

Network Admin → Settings → Network Settings

and review the plugin-related configuration.

Some plugins are designed to be controlled only at the network level.

---

6. Login Redirect Problems

Login redirects can occur because of:

• Incorrect domain configuration
• Incorrect HTTPS settings
• Reverse proxy configuration
• Cached redirects
• Incorrect WordPress URL settings
• Cookie/domain problems

Clear browser and server caches after correcting the configuration.

---

WordPress Multisite Best Practices

For a stable Multisite network:

1. Plan Your URL Structure

Decide between subdomains and subdirectories before creating many sites.

2. Use Reliable Hosting

Multisite can consume significant resources as the number of websites increases.

3. Keep Everything Updated

Regularly update:

• WordPress
• Themes
• Plugins
• PHP
• Server software

4. Limit Administrator Access

Only trusted users should have network administrator privileges.

5. Monitor Resources

Track:

• CPU
• RAM
• Disk space
• Database usage
• PHP workers
• Traffic

6. Test Plugins Before Network Activation

A plugin that works on one site can potentially affect the entire network when network-activated.

7. Maintain Multiple Backup Copies

Keep backups in separate locations when possible.

8. Test Restores

Regularly verify that your backups can actually be restored.

9. Use HTTPS Everywhere

Avoid running network sites over plain HTTP.

10. Document Network Configuration

Keep records of:

• Domains
• DNS
• SSL
• Hosting
• Administrator accounts
• Plugins
• Themes
• Backup procedures

This makes troubleshooting and future migrations much easier.

---

When Should You Use WordPress Multisite?

Multisite is a good fit when multiple websites share a common management environment.

Examples include:

Corporate Networks

A company could manage:

company.com
news.company.com
support.company.com
careers.company.com

Educational Institutions

A university could create sites for:

university.example
engineering.example
business.example
library.example

Agencies

An agency can manage multiple client or project websites from one installation when the technical and operational requirements are compatible.

Franchise Businesses

Each branch can have its own website while the organization maintains centralized control.

---

When Should You Avoid WordPress Multisite?

Multisite may not be appropriate when websites need completely independent environments.

Consider separate WordPress installations if:

• Sites have unrelated owners
• Sites require different server configurations
• Sites need completely independent databases
• Different PHP versions are required
• Sites need different plugin stacks
• Sites have very different traffic requirements
• Each site must be migrated independently
• A failure in one installation must be isolated from the others

In these cases, separate installations may provide greater isolation.

---

WordPress Multisite vs WordPress Staging

Multisite and staging solve different problems.

Feature	Multisite	Staging
Purpose	Manage multiple websites	Test changes safely
Multiple sites	Yes	Usually one copy per environment
Production use	Yes	Usually not public
Testing updates	Possible	Primary purpose
Shared WordPress core	Yes	Depends on setup
Search indexing	Can be enabled	Usually disabled

A Multisite network can contain a staging site, but Multisite itself is not a staging system.

---

WordPress Multisite Security Checklist

Before launching a Multisite network, verify:

• HTTPS is enabled
• Strong administrator passwords are used
• Unused plugins are removed
• Unused themes are removed
• WordPress is updated
• PHP is supported and updated
• Network registration is restricted if unnecessary
• Administrator privileges are limited
• Backups are configured
• Backup restoration has been tested
• DNS is configured correctly
• SSL certificates cover required domains
• Subdomain configuration has been tested
• All websites have been checked for broken links
• Email functionality has been tested

---

Frequently Asked Questions

Can WordPress Multisite manage unlimited websites?

There is no simple fixed number of sites that applies to every installation. The practical limit depends on your hosting resources, database performance, traffic, plugins, and server configuration.

Can each Multisite website have its own domain?

Yes. A Multisite network can be configured to use custom domains, but domain mapping and DNS/SSL configuration may be required.

Can each site have a different theme?

Yes. Network administrators can make themes available to individual sites, and sites can use different themes when permitted.

Can each site use different plugins?

Yes, depending on how the network administrator configures plugin management. Some plugins may be network-activated.

Can I convert a normal WordPress site into Multisite?

Yes. WordPress provides a built-in process for enabling Multisite on an existing installation. However, always create a complete backup first and test the conversion carefully.

Can I disable Multisite later?

Yes, but converting a Multisite network back into independent WordPress installations is more involved than simply switching off one setting. Each site’s database content, files, URLs, and configuration may need to be separated.

Does Multisite improve website performance?

Not automatically. Multisite mainly improves centralized management. Performance depends on server resources, database configuration, caching, plugins, themes, traffic, and site architecture.

---

Final Thoughts

WordPress Multisite is a powerful feature for managing multiple related websites from one WordPress installation. It provides centralized control over sites, users, themes, plugins, and network settings while allowing each website to maintain its own content and configuration.

The most important part of a successful Multisite setup is planning. Decide whether you need subdomains or subdirectories, configure DNS and SSL correctly, limit network administrator access, test plugins before deploying them across the network, and maintain reliable backups.

When the websites share a common management model, Multisite can significantly simplify administration. When they require strong technical or operational independence, separate WordPress installations may be a better architecture.