Yes. WordPress Multisite can give each subsite its own top-level domain. Since WordPress 4.5, ordinary domain mapping is built into core, so a subsite can use a complete address such as https://brand-example.com instead of the network’s original subdomain or directory. The WordPress setting is only one part of the job, however: every domain must resolve in DNS, your web server must send each hostname to the same WordPress installation, and each hostname needs valid HTTPS coverage.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
This guide lays out the infrastructure, setup sequence, testing checks and operating practices that keep a multi-domain network reliable.
As an Amazon Associate I earn from qualifying purchases.
What “different domains” means in WordPress Multisite
A Multisite network has one WordPress codebase and database structure with multiple subsites. Each subsite can have its own content, administrators, theme settings and site address while the super administrator controls the network.
Domain mapping changes the public address used by one of those subsites. For example, a network might be installed at network.example.com, while a subsite is presented publicly as https://brand-example.com. Visitors, login pages, canonical links and media URLs should all use the mapped hostname after configuration is complete.
#1 Best Overall
WordPress Developer Resources states that “In WordPress 4.5+, domain mapping is a native feature.” A plugin is therefore not required for standard one-domain-per-subsite mapping. Plugins can still add alias or microsite behavior, but they introduce another compatibility layer and should be treated as an optional, version-checked enhancement.
Choose the network model before you install
Multisite can organize its original site addresses by hostnames or by paths. A mapped top-level domain can be attached to a subsite in either model, but the routing work differs.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →| Network model | Example native address | Infrastructure implications | When it fits |
|---|---|---|---|
| Domain-based | site1.example.com |
Often uses wildcard DNS or explicit virtual-host/add-on-domain routing. The server must accept multiple hostnames and deliver them to the same document root. | Networks that already treat each subsite as a separate hostname and may later map many public domains. |
| Path-based | example.com/site1 |
Usually starts with one hostname and directory-style URLs. Each mapped domain still needs its own DNS record, server routing and certificate. | Networks that want simple initial setup or branded paths for sites that do not need separate public domains. |
Changing from one model to the other later is an operational project, not a cosmetic switch. Decide whether every subsite needs a distinct public domain or whether a branded path is sufficient. Also consider who controls DNS, how certificates will renew, how caches identify hosts, and how you will stage or migrate the network.
Prerequisites to verify before activation
Do these checks before creating the network. They prevent the common mistake of entering a new URL in WordPress while the surrounding infrastructure still points somewhere else.
- A working WordPress installation: the installation must load correctly at its current primary address, with permalinks and rewrites functioning.
- Server control: you or your host must be able to create virtual hosts, add-on domains, aliases or equivalent hostname routes that point to the WordPress document root.
- DNS control: each domain owner must be able to create the required records. WordPress Developer Resources says, “Make sure all the domains you want to use are already mapped to your DNS server.”
- HTTPS capability: certificates must cover the primary network hostname and every mapped hostname. Multiple domains can require SNI-capable server configuration.
- Backups: take a database and file backup before enabling Multisite or changing site addresses.
- Rewrite support: the web server must pass requests to WordPress’s rewrite rules so front-end URLs, administration and REST requests resolve correctly.
- Operational ownership: document who renews certificates, edits DNS, changes server routes and restores backups.
WordPress Developer Resources summarizes the boundary clearly: “Whichever methods you use, you will need to configure your DNS (to map the domain name to the server’s IP address) and server (to map the domain name to the WordPress installation directory).” The WordPress URL field cannot perform either task.
Build the Multisite network
If Multisite is not enabled yet, use the standard WordPress network-setup flow while the installation is still at its intended primary domain. The exact controls can vary with the WordPress version and hosting panel, but the sequence is consistent.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Back up the site. Save the database and the entire WordPress files directory. Record the current site URL, database credentials and web-server document root.
- Enable network setup. In the WordPress administration area, open the network-setup screen under the administration tools and choose either subdomains (domain-based) or subdirectories (path-based), subject to the options WordPress presents for the existing installation.
- Apply the generated configuration. WordPress displays the required
wp-config.phpand rewrite changes. Copy them exactly, keep a backup of the original files, and confirm that the resulting configuration still loads the main site. - Sign in again. Network activation normally requires a fresh login. Confirm that Network Admin is available before adding public domains.
- Create a test subsite. Add one subsite using the network’s native hostname or path. Test it internally first so you know the network itself works before introducing DNS and certificate variables.
Do not point production domains at an untested network. A mapping problem is much easier to diagnose when the original network address still works as a control.
Point DNS for every domain
For each public domain, create DNS records that resolve to the server hosting the Multisite installation. The record type and value depend on your provider and whether you use a dedicated address, a shared address or a proxy, but the result must be the same: a request for the mapped hostname reaches the WordPress server.
Rank #2
Domain-based networks
A domain-based network commonly uses wildcard DNS for subdomains such as site1.example.com, or explicit records for each hostname. Wildcards simplify creation of new subsites but do not replace server-side hostname routing. If you later map brand-example.com, that top-level domain still needs its own DNS record; a wildcard under example.com does not cover an unrelated domain.
Path-based networks
A path-based network may begin with only the primary domain. Every newly mapped top-level domain must still be added to DNS and directed to the same installation. The fact that the network uses paths internally does not make external domains automatic.
Recommended Free Tools
Allow time for DNS changes
Verify DNS from more than one resolver or network before troubleshooting WordPress. Cached records can make one location show the old destination while another reaches the new server. Keep the old routing in place until the new address is confirmed, especially for a live site.
Route hostnames at the web server or hosting panel
DNS only gets a request to an IP address. The web server must then recognize the requested hostname and serve the WordPress document root. Depending on your platform, this may be called a virtual host, server block, parked domain, alias, add-on domain or domain pointer.
Create a route for the primary network address and for each mapped domain. The routes should use the same WordPress files, PHP configuration and rewrite behavior. A domain that resolves correctly but lands on a default hosting page, another application or a directory listing is a server-routing failure, not a WordPress mapping failure.
Check the host header and rewrites
Requests must retain the original hostname through the web server and any reverse proxy. Confirm that:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- the hostname is listed in the server’s accepted names;
- the document root is the Multisite installation directory;
- PHP requests are passed to the same runtime used by the primary site;
- rewrite rules send unknown paths to WordPress rather than returning a server-level 404; and
- HTTP-to-HTTPS redirects preserve the requested hostname instead of redirecting every domain to the network’s original address.
These checks are especially important on managed platforms where adding a domain in a dashboard may create a separate site rather than an alias to the existing installation.
Install SSL/TLS coverage before sending visitors
Every mapped domain needs a valid certificate whose names cover that hostname. Install certificates for the primary network domain and each mapped domain, then configure the web server to present the appropriate certificate during the TLS handshake. The official guidance calls out SNI for multiple domains so that administration remains encrypted when several hostnames share one server address.
Test both the bare domain and the www form only if you intend to support both. Decide which form is canonical, issue certificates for the forms you actually serve, and redirect the other form consistently. A certificate that covers only the primary network address will not make a mapped subsite secure.
Automated renewal is preferable, but automation must include every mapped hostname. Record renewal ownership and test a renewal or expiry warning before launch. An expired certificate can make an otherwise healthy subsite appear offline.
Free tools Windows power users keep installed
One-click scans. No signup required.
Map a subsite in Network Admin
Once DNS, routing and HTTPS are ready, save the public address in WordPress:
- Sign in as a super administrator.
- Open Network Admin → Sites.
- Find the subsite and choose Edit.
- In the site address field, replace the network hostname or path with the complete mapped URL, such as
https://brand-example.com. - Save the change.
- Open the mapped address in a private browser window and test the front end and administration.
Use the complete canonical scheme and hostname you intend visitors to use. If the site should be HTTPS, save the HTTPS address rather than relying on a later redirect to correct an HTTP value.
Mapping one subsite does not automatically map every other subsite. Repeat the infrastructure and Network Admin work for each domain, keeping a written inventory of the site ID, public hostname, DNS record, certificate and server route.
Test behavior on the mapped host
A successful home-page load is not enough. Host-specific URLs are generated by WordPress, themes, plugins, caches and APIs, so test the complete visitor and administrator journey.
- Front-end navigation: open menus, archive pages, search results and pagination. Links should stay on the mapped hostname.
- Canonical and redirect behavior: confirm that HTTP, alternate hostnames and trailing-slash variants resolve to the chosen canonical URL without loops.
- Login and logout: sign in, sign out and open an authenticated page in a new tab. Check that the browser receives cookies for the intended host.
- Media: upload an image and inspect its public URL. Existing media should not unexpectedly point to the old network address.
- REST and other APIs: test the REST API, block editor requests, XML-RPC if enabled, webhooks and any external integrations used by the subsite.
- Forms and email: submit a form and verify that callbacks, return URLs and notification links use the mapped domain.
- Caching: purge page and object caches, then confirm that one domain’s cached response is not served to another domain.
- Robots and sitemap files: inspect
robots.txt, XML sitemaps and canonical tags for the correct hostname. - Administration: check Network Admin, the subsite dashboard, updates and user management over HTTPS.
Run these checks from an unauthenticated browser and from a logged-in account. A cache or cookie issue can be invisible in one state and obvious in the other.
Fix login-cookie problems carefully
When the front end works but login repeatedly returns to the login screen, inspect cookie scope, HTTPS redirects, proxy headers and cache rules before changing code. A cookie issued for the old network hostname will not authenticate a browser on a different host.
Rank #4
The official domain-mapping guidance documents this troubleshooting setting:
define( 'COOKIE_DOMAIN', $_SERVER['HTTP_HOST'] );Apply it only after confirming that the deployment actually requires host-specific cookie handling. Test every subsite, the network administration area and logout afterward. A broad cookie change can create the opposite problem by sharing authentication across hosts that should remain isolated.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsAlso exclude login, administration, REST and personalized responses from page caches. Ensure that a reverse proxy does not strip the Host header or convert secure cookies into an HTTP context.
Canonical URLs, media and database references
Changing the site address in Network Admin controls how WordPress identifies the subsite, but themes, plugins and stored content may contain absolute URLs created under the previous address. Search for the old hostname in settings, navigation menus, widgets, custom fields, serialized options and integration callbacks before performing a bulk replacement.
Use a serialization-aware migration method rather than a plain text replacement on the database. Make a backup and test the replacement on a staging copy. Afterward, inspect source HTML, redirects, Open Graph metadata, feeds, sitemaps and uploaded files. Do not delete the original network address until you know it is no longer needed for administration, redirects or recovery.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Operate many domains as one system
Multi-domain Multisite is reliable when the surrounding services are managed as a single inventory.
Maintain a domain register
For each subsite, record the site ID, public URL, DNS records, server route, certificate names and renewal owner. Include the original network domain and any staging hostname. This documentation shortens incident response when a domain expires or a server is replaced.
Coordinate renewals and redirects
DNS, certificates, web-server routes and WordPress settings must change in a planned order. Add and validate the new route and certificate before changing the canonical URL. During retirement, keep a redirect and certificate in place long enough to handle bookmarks, search indexes and cached links.
Back up all network layers
Backups must include the database, uploads, themes, plugins, configuration files and the routing information that is not stored in WordPress. A database-only backup cannot recreate DNS records, virtual hosts or certificates.
Plan migrations as network projects
Moving a Multisite installation is more complicated than moving a single site because one codebase serves multiple hostnames and the database stores network relationships. Record the original network domain and routing configuration before migration. Lower DNS time-to-live values ahead of a planned move, copy the files and database, recreate every hostname route and certificate on the destination, then test one mapped site before switching the rest.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When a plugin is appropriate
Core mapping is the normal choice for ordinary domain-per-subsite setups. A plugin may be justified when you need additional aliases, specialized microsite behavior or compatibility with an established legacy workflow. The WordPress.org Domain Mapping System listing advertises multiple-domain and Multisite support but requires a custom sunrise.php integration.
Treat that path as an advanced or legacy option. Verify compatibility with the current WordPress release, PHP version, web server, cache layer and login configuration in a staging environment. Do not install a plugin merely because DNS or server routing has not been configured; no plugin can substitute for those prerequisites.
Troubleshooting by symptom
| Symptom | Likely layer | Checks and correction |
|---|---|---|
| The domain shows a registrar or hosting placeholder | DNS or server routing | Confirm the DNS record reaches the intended IP, then verify the hostname is configured as a virtual host or alias for the WordPress document root. |
| The domain opens another website | Server routing | Inspect hostnames on the server block, add-on domain or proxy. The request is reaching the server but being assigned to the wrong application. |
| WordPress redirects to the old network URL | Site settings, stored URLs or redirect rules | Recheck the value saved under Network Admin → Sites, then inspect hard-coded links, canonical settings, web-server redirects and cache entries. |
| HTTPS works on the network but warns on the mapped domain | Certificate or TLS routing | Issue a certificate containing the mapped hostname and confirm SNI selects it for that host. Renew and install it on every relevant server. |
| Login loops or immediately logs out | Cookies, proxy or cache | Test in a private window, inspect cookie domain and secure flags, bypass cached responses, preserve the host header and consider the documented COOKIE_DOMAIN setting only after diagnosis. |
| Images or API calls still use another domain | Stored URLs or application configuration | Inspect media URLs, REST endpoints, plugin settings, webhook callbacks and serialized database values. Correct them with a backup and serialization-safe process. |
| Pretty links return 404 errors | Rewrite configuration | Verify the web server’s rewrite rules and document root, then resave permalinks after confirming the request reaches WordPress. |
| One site displays another site’s cached page | Cache key configuration | Make the cache vary by hostname, purge old objects and exclude authenticated or host-sensitive responses. |
A practical decision checklist
Use this sequence when deciding whether to map a domain and when reviewing a production change:
- Does the subsite genuinely need its own public top-level domain, or would a path meet the branding and navigation requirement?
- Can you control DNS for the domain and route it to the same WordPress installation?
- Can your server or hosting panel accept the hostname without creating a separate WordPress instance?
- Can you issue and renew HTTPS certificates for every public hostname?
- Have you selected a canonical scheme and hostname and tested redirects?
- Have you tested login, cookies, media, REST requests, sitemaps, caches and integrations on the mapped host?
- Is the domain, certificate, route and subsite URL recorded for future migration and recovery?
If any answer is no, resolve that infrastructure gap before changing the WordPress URL. The native feature is straightforward; the reliability of the result depends on the systems around it.
The Bottom Line
WordPress 4.5 and later can map a different top-level domain to each Multisite subsite without a domain-mapping plugin. Configure DNS, web-server routing and HTTPS first, save the complete URL under Network Admin → Sites, then test cookies, redirects, media, APIs and caching on every hostname. Treat the domains, certificates and routing records as one managed network when operating or migrating the installation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
