Preparing and setting up WordPress Multisite on NabWP

A network shares core code, installed themes and plugins, with a Super Admin controlling network-wide operations. It is useful when sites have a common administration model. Separate installations are often easier when clients need independent plugins, upgrades, backups or ownership.

Confirm resource requirements and how backups, staging, AI tools and restoration will apply to the network. Do not assume an operation designed for one normal WordPress site safely targets an individual network subsite. Agree on the scope with us before using automated management actions.

• Choose subdirectories or subdomains before enabling the network. Existing installations can have restrictions on available structures.
• For subdomains or mapped domains, arrange the required DNS, hosting-domain routing and HTTPS certificates. WordPress configuration alone does not create them.
• Back up files and the entire database. Test the conversion on a suitable copy and review plugin compatibility with Multisite.
• Record existing redirects, permalink settings and any custom code that assumes a single site.

1. Use an authorised administrator and the official network preparation procedure, including the documented temporary plugin deactivation where required.
2. Add define('WP_ALLOW_MULTISITE', true); to the correct wp-config.php before the stop-editing comment, without duplicating the setting.
3. Open Tools > Network Setup, review the structure offered, and enter the network title and administrator email.
4. Apply the exact configuration and rewrite instructions generated for that installation. Apache and NGINX use different routing mechanisms; ask us to apply server-level rules where your account cannot.
5. Sign in again, open My Sites > Network Admin and create a small test subsite through Sites, Add New.

Check the main site and test subsite, media uploads, permalinks, HTTPS, email and user permissions. Network-enable a theme to make it available; this does not automatically activate it on every site. Network-activated plugins affect the network, while permitted site-level activation depends on network settings.

Keep the test network private until routing and recovery are confirmed. Converting back to separate sites is a migration task, not simply removing the configuration line. If a management tool cannot safely identify the intended site, stop and ask us to review the scope.

• Installing and administering WordPress Multisite through cPanel and Softaculous
• Choosing separate WordPress websites or a Multisite network
• Planning and checking your WordPress backups
• Securing a WordPress website with practical maintenance and access controls

• Preparing a Multisite network
• Creating a Multisite network
• Network administration