Editorial illustration.
Originally published 20 June 2023; rewritten and reviewed on 15 October 2026.
Several websites need the same platform, and a single WordPress network looks easier to maintain than separate installations. The convenience is real only when the sites can share the operational decisions that Multisite centralises. I would decide that relationship before editing configuration.
Establish what the network will share
Confirm the proposed site addresses, administrators, themes and plugins. Decide whether the sites should use subdirectories or subdomains, and check the DNS and certificate requirements. Existing content, hosting restrictions and domain mapping can affect the plan.
Review plugin compatibility and ownership of updates. A network-wide change can affect several sites, so a shared installation needs an agreed maintenance and recovery process.
Enable through the supported procedure
Back up the database and files, and test the restore before starting. Follow the WordPress network-creation documentation for the installed version and hosting setup.
The familiar configuration switch is only the beginning:
define('WP_ALLOW_MULTISITE', true);
Place it according to the documented configuration procedure. Use Network Setup to obtain the settings generated for your specific network, then apply those settings and the correct web-server rewrite rules. Do not copy Apache .htaccess rules into an unrelated Nginx or IIS configuration.
Test site boundaries and administration
Check sign-in, site creation, media uploads, permalink handling and access for a normal site administrator. Verify that one site’s users and editors receive only the privileges intended for them.
Keep a representative restore test that includes the network configuration and content. Multisite is a platform decision with a larger shared failure boundary; it is ready when the team understands that boundary and can operate it deliberately.