WordPress Multisite lets one installation serve many sites, but the initial network configuration controls far more than the dashboard name. It determines site URL patterns, registration rules, upload limits, and the tools available to individual site administrators. Because changing a subdomain network to subdirectories later can require a full URL migration, plan these settings before public sites are created.
Plan Before Enabling the Network
Network setup modifies wp-config.php and the rules used by the web server. On an existing WordPress site, review custom permalinks, redirects, security rules, and plugins that depend on a fixed site address. A staging copy is the safest place to test the complete setup.
- Hosting: Confirm support for wildcard DNS, subdomains, SSL certificates, and the required web server configuration.
- Address policy: Decide if sites should use paths, subdomains, or separately mapped custom domains.
- Administration: Limit super administrator access and choose an email address monitored by more than one responsible person.
- Content: Check whether existing media, links, and internal references use absolute URLs that may need updating.
Before activating the network, back up the database, configuration files, web server rules, themes, plugins, and uploads. If the site is already receiving traffic, schedule a short maintenance window and prepare a rollback plan.
Choose Subdirectories or Subdomains
The Network Setup screen asks for a network title, network admin email, and address structure. This is one of the most consequential choices in the process.
| Option | Example address | Typical use | Main requirement |
|---|---|---|---|
| Subdirectories | example.com/campus | Departments, regional branches, or a controlled group of sites | Working rewrite rules under the main domain |
| Subdomains | campus.example.com | Distinct brands, schools, franchises, or user-created sites | Wildcard DNS, SSL coverage, and server routing |
Subdirectories are often simpler to host because every site remains under one domain. They can also make the relationship between sites obvious to visitors. Their shared address may be less suitable when each site needs a distinct brand or cookie and security policies must be separated by hostname.
Subdomains look more independent, but the host must direct requests for new subdomains to the same WordPress installation. Arrange a wildcard DNS record such as *.example.com, configure the web server, and provide valid SSL certificates for generated subdomains. A custom domain is a further step: it needs DNS records, domain mapping supported by the host or WordPress, and its own valid certificate.
Complete Network Activation Correctly
WordPress generates configuration lines using the address entered during setup. Copy the supplied values exactly rather than adapting examples found elsewhere.
- Add the multisite constant requested by WordPress to wp-config.php.
- Open Tools, then Network Setup, and complete the title, email, and address options.
- Add the generated network constants to wp-config.php and the rewrite rules to .htaccess where the installer directs.
- Log in again, open the Network Admin, and visit Settings, then Network Settings.
The generated rewrite rules are for Apache. An Nginx server needs equivalent location and rewrite directives, so do not paste Apache rules into an Nginx configuration. After activation, resave the permalink settings, clear any server or plugin cache, and test the main site, the network dashboard, and a newly created test site.
Configure the Core Network Settings
Operational Details
The network name appears in network administration screens and registration messages. The network admin email receives system notices, so use a stable role mailbox rather than an address tied to one employee. Send a test message after setup because a correct address does not guarantee that hosting can deliver mail.
Registration Controls
Registration settings should match the network’s actual administrative capacity. Public signups create moderation work and can attract spam, while a fully closed network requires staff to provision every account and site.
- Allow new registrations: Enable only the intended options for user accounts, new sites, or both. Disabling public registration does not prevent a super administrator from creating sites manually.
- Add New Users: Permit site administrators to add users only when they can manage invitations and remove access promptly.
- Notification email: Direct signup notices to a mailbox that is checked regularly. This can differ from the network admin email.
- Registration and welcome messages: Explain the network name, account status, site address, and the correct route for support requests.
- Banned Names and email restrictions: Reserve confusing site slugs or usernames and limit public signups to approved email domains when appropriate.
Domain restrictions apply to public registration; they are not a replacement for reviewing administrator roles. WordPress core also does not turn every registration form into a full approval workflow, so an organization with formal review steps may need a suitable plugin or manual provisioning process.
Upload Defaults
The maximum upload size sets a network default in kilobytes, but PHP and hosting limits can impose a lower ceiling. The file-type list acts as a whitelist. Keep it narrow, and do not add executable files or SVG uploads unless the server and WordPress environment include appropriate sanitization.
Leave the upload path blank unless there is a documented storage requirement. Multisite normally separates media under wp-content/uploads/sites by site ID. Changing this path after files exist can leave old media URLs broken and requires a planned migration.
Menus and Languages
Menu Settings controls access to built-in features such as Links, Post Formats, Trackbacks, Custom Backgrounds, and Custom Headers. The available options vary by WordPress version. Enabling a menu makes the feature available in supported site dashboards, but it does not force a theme to display it or override user capabilities.
Default language settings reduce repeated configuration for new sites. Confirm that the installed language files are available and that site administrators understand where they can change the setting.
Match the Settings to the Network
An association offering sites to local chapters might permit logged-in members to create sites, restrict addresses to approved chapter names, and use subdirectories for a consistent brand. A private company network would usually disable public registration, allow administrators to add staff, and keep upload types limited to normal documents and images.
Neither policy is universally correct. The useful configuration is the one that reflects who owns the content, how sites are approved, how much storage they need, and who responds when access or email problems occur.
Common Configuration Mistakes
- Choosing an address structure because it looks cleaner, without testing DNS, SSL, and server routing.
- Raising the network upload limit while leaving lower PHP or hosting limits unchanged.
- Changing the upload directory after media has been added, then discovering broken file paths.
- Leaving open registration active without monitoring new accounts, site names, and storage use.
- Assuming every network setting overrides a site-level setting. Many values are defaults that site administrators can later change.
- Copying domain constants or rewrite rules from staging into production without replacing environment-specific values.
Frequently Asked Questions (FAQs)
Can I switch between subdirectories and subdomains later?
Yes, but WordPress does not provide a risk-free one-click switch. The migration must update stored site URLs, rewrite rules, links, media paths, DNS, and redirects. Test the process on a full copy before changing a live network.
What can a network administrator change that a site administrator cannot?
A network administrator manages network-wide settings, creates sites, installs themes and plugins, and can activate them across the network. Site administrators manage their own content and permitted site settings. Network defaults do not automatically lock every corresponding site-level option.
Can each Multisite site use a different custom domain?
It can. Each domain needs DNS records that reach the WordPress installation, supported domain mapping, and valid HTTPS coverage. Hosting controls and plugin requirements vary, so test certificate renewal and redirects before launch.
Why are users unable to register a new account or site?
Check that registration is enabled, the selected signup type is allowed, and the visitor’s email domain is not restricted. A requested site name may also match a banned name. If the settings look correct, test with a new browser session and review caching or security plugins.
How do I allow larger media uploads?
Raise the Network Settings upload limit and the relevant PHP limits, such as upload and post sizes. The hosting account may impose another ceiling. Test the complete upload after changing all applicable limits.
Does every site in the network have a separate database?
No. A standard Multisite installation stores sites in one database, using separate tables or prefixed table groups for each site. Backups and migrations must include the full database, not only the main site’s tables.
Do Network Settings changes take effect immediately?
Most saved settings apply after the update, but some are defaults for sites created afterward. Existing sites may retain their own values. Clear caches and inspect both a current site and a test site to confirm the result.
