WordPress Multisite Different Domains: Complete Setup & Management Guide

Setting up a WordPress network with different domains under one install gives you something no collection of separate sites can match: one place to update, one user database, and one codebase serving every branded property you run. WordPress Multisite makes this possible, but domain mapping, DNS, SSL, and server configuration all have to work together before a single subsite goes live. This guide breaks down each piece so you know what to set up, in what order, and why it matters.

Key Takeaways

• Domain mapping has been built into WordPress core since version 4.5, so each subsite can carry its own domain without a third-party plugin.
• Before your first subsite goes live, you need wildcard DNS, per-domain SSL certificates, and the right server block configuration in place.
• The Network Admin dashboard controls every site on the network, but SEO, canonical URLs, and database growth each require attention as the network scales.
• Multisite with domain mapping works well for media portfolios, agency client rosters, and WooCommerce storefront networks, but only when the architecture fits the workload.
• Redirect loops, SSL mismatches, and cookie-based login failures each trace back to specific configuration errors with clear fixes.

Domain Mapping and How WordPress Multisite Handles Different Domains

Domain mapping in WordPress Multisite lets each subsite appear under its own fully independent domain. Instead of visiting network.com/site1 or site1.network.com, a visitor goes directly to site1.com. The underlying network address stays invisible.

( [URL pending editorial input])

WordPress Multisite, sometimes called WPMU, runs multiple websites from a single WordPress install. You share one codebase, one plugin library, one theme library, and one database server across every site on the network. Updates apply once and reach every subsite. User accounts can span multiple sites without separate logins.

What Is the Difference Between a Subdomain Network and a Subdirectory Network?

A subdomain network places each subsite at a subdomain, such as site1.network.com. A subdirectory network places each subsite at a path, such as network.com/site1. You pick one structure when you first activate Multisite. Switching later is not a simple process.

Domain mapping works on top of either structure. You can point an external domain at any subsite regardless of how the network organizes its internal addresses.

Before WordPress 4.5, domain mapping required a plugin. That plugin ran a sunrise routine, which is an early-loading process that reads the incoming domain and routes the request to the right subsite. WordPress 4.5 folded this into core. You still need correct server and DNS settings, but the plugin dependency is gone.

Two constants in wp-config.php still matter. The COOKIE_DOMAIN constant sets which domain WordPress uses when it writes authentication cookies. Get this wrong and users get logged out every time they move between sites. The SUNRISE constant, set to true, tells WordPress to run domain routing before anything else loads. Both are required in a domain-mapped network.

Plugins are still worth considering for bulk domain management. If you're assigning and reassigning domains across dozens of subsites, a plugin adds a management layer that core alone doesn't provide. Core handles the routing; plugins handle the workflow.

How to Set Up WordPress Multisite with Multiple Domains

Multiple domains in a Multisite network need deliberate preparation before you write a single line of configuration. Three things must be ready first: a hosting environment that supports Multisite, correct DNS records, and SSL certificates for every domain you plan to map.

( [URL pending editorial input])

Shared hosting is often the wrong choice here. Many shared hosts restrict Multisite or block domain mapping at the server level. A VPS or dedicated server gives you direct control over server blocks and rewrite rules. Managed WordPress hosts vary. Some have Multisite support with domain mapping workflows built in; others require a support request or don't support it at all. Confirm this before you start building.

Wildcard DNS is required for subdomain-based networks. A wildcard A record, written as *.network.com, points every subdomain to your server IP. New subsites resolve automatically without a new DNS entry each time. Subdirectory networks don't need a wildcard, but every externally mapped domain still needs its own A record or CNAME pointing to your server.

Do You Need a Plugin to Map Domains in WordPress Multisite?

No. WordPress 4.5 added domain mapping to core. You set it up inside the Network Admin dashboard. Plugins can help with bulk management across large networks but aren't required to make mapping work.

Here's the setup sequence once your prerequisites are ready.

Add define('WP_ALLOW_MULTISITE', true); to wp-config.php. Save and reload the admin. A Network Setup menu appears under Tools. Choose your network type, subdomain or subdirectory, and WordPress generates the additional constants and .htaccess rules you paste into place.

Add a new site from the Network Admin under Sites, then Add New. Assign its internal address based on your network structure. Then open the site's settings and enter the external domain in the domain field. WordPress routes requests for that domain to the correct subsite.

Every mapped domain needs its own SSL certificate. A wildcard certificate covers subdomains of one domain but won't cover site1.com and site2.com as separate mapped domains. Use per-domain certificates for those. Let's Encrypt handles this well and renews automatically, but your server needs to provision and renew each certificate on its own schedule.

Apache uses .htaccess rewrite rules that WordPress generates during setup. Nginx doesn't read .htaccess, so you write server block configurations manually. Each mapped domain on Nginx typically gets its own server block pointing to the WordPress root, or you use a catch-all block that passes every incoming domain to WordPress for routing.

Managing Your Multisite Network Admin, SEO, and Performance

The Network Admin dashboard sits above every individual site dashboard on your network. Only Super Admins can access it. From here you create sites, edit settings, assign domains, manage network-wide plugins and themes, and set user permissions across the entire installation.

( [URL pending editorial input])

User roles split into two tiers. A Super Admin controls the full network. A Site Admin controls a single subsite but can't install plugins or themes network-wide. For agencies or media companies with multiple editors, this separation keeps individual contributors from touching infrastructure they shouldn't.

Changing a domain after a site goes live requires more than updating the domain field in the Network Admin. Any URLs hardcoded in post content, metadata, or option values still point to the old domain. A database search-and-replace updates those records. Skip this step and you'll have broken links across the site.

How Does WordPress Multisite Affect SEO Across Mapped Domains?

Search engines treat each mapped domain as a separate website. Google sees site1.com and site2.com as two distinct properties, not two parts of one WordPress install. That's an advantage when each site covers a different topic for a different audience. It becomes a liability when the same content appears at both the internal network address and the mapped domain.

Canonical tags fix the duplicate content problem. Each subsite should declare its mapped domain as the canonical URL. Most SEO plugins set this automatically after domain mapping is configured, but you should check the output rather than assume it's correct.

Sitemaps work the same way. Each subsite needs its own sitemap, submitted separately to search engines. There's no network-wide sitemap by default.

Database growth is the performance trade-off that catches networks off guard. Every new subsite adds its own set of database tables. At ten sites this is manageable. At a hundred sites, query performance and maintenance overhead become real concerns. A traffic spike on one subsite also draws from the same server resources as every other site on the network.

Security follows the same logic. One vulnerability in the core installation puts every site on the network at risk at the same time. Keeping WordPress, plugins, and themes current isn't optional when you're running multiple public-facing domains from one install.

The Bottom Line

WordPress Multisite with domain mapping is a practical architecture for anyone running multiple branded properties from one WordPress install, whether that's a media company with several editorial sites, an agency managing client properties, or an operator running multiple WooCommerce storefronts. Native core support means you're not relying on plugins for the routing, but the trade-offs are real: per-domain SSL management, shared security exposure, and database growth at scale all add work that a single-site install doesn't require. If the use case fits, the architecture holds up well. To read further about related WordPress hosting configurations and network setups,.

Related reading

• managed WordPress hosting
• 303 Redirect Explained

FAQs

Can WordPress Multisite use completely different domains for each subsite?

Yes. Each subsite can carry its own independent domain through domain mapping. This has been part of WordPress core since version 4.5. You configure it through the Network Admin dashboard without a third-party plugin.

Why does my WordPress Multisite domain mapping cause a redirect loop?

Redirect loops after domain mapping usually come from a misconfigured server rewrite rule or a wrong constant in wp-config.php. Check your COOKIE_DOMAIN and SUNRISE settings first, then verify your Nginx server block or Apache .htaccess rules match the Multisite configuration WordPress expects.

How do I get an SSL certificate for each domain in a WordPress Multisite network?

Each mapped domain needs its own certificate. A wildcard certificate covers subdomains of one domain but won't cover separate mapped domains like site1.com and site2.com. Let's Encrypt issues free per-domain certificates with automated renewal. Your server needs to handle provisioning for each domain on its own schedule.

Why do I get logged out when switching between sites in my Multisite network?

This is a cookie domain conflict. WordPress scopes authentication cookies to a specific domain. If the COOKIE_DOMAIN constant in wp-config.php doesn't match the domain a user is visiting, the browser drops the cookie and the session ends.

Does WordPress Multisite hurt SEO?

It doesn't, as long as you manage canonical URLs correctly. Search engines treat each mapped domain as a separate site. That works in your favor when each site has a distinct topic. The risk is duplicate content appearing at both the internal network address and the mapped domain. Canonical tags on every subsite prevent that.