A “custom domain alias” can mean three different WordPress setups: assigning a domain to an entire WordPress.com site, mapping a domain to a WordPress Multisite subsite, or showing one landing page from a self-hosted single-site installation at another domain. The correct procedure depends on that scope. DNS, web-server routing and SSL are prerequisites in every self-hosted arrangement; WordPress.com uses its hosted domain tools.
Choose the setup that matches your goal
| What you want | Where it applies | Normal method |
|---|---|---|
| Use a new domain for the whole site | WordPress.com | Connect the domain in the Hosting Dashboard, then separately make it the primary address. |
| Give one Multisite subsite its own domain | Self-hosted WordPress Multisite | Point DNS to the network, route the hostname on the server, install SSL, then set the subsite’s Site Address (URL). |
| Show one landing page at a separate domain | Self-hosted single-site WordPress | Route the domain to the installation, then use a page-level mapping plugin or custom server/application configuration. |
Connecting a domain to WordPress.com does not automatically make that domain an alias for one page. Likewise, Multisite domain mapping is not the same feature as page-level mapping on a single site.
Before you change anything
- Decide whether the alias should stay visible in the browser or redirect visitors to a canonical URL.
- Confirm who controls the domain’s DNS and whether existing email, verification, CDN or other records must remain intact.
- Make sure the domain will have a valid SSL certificate. A DNS record by itself does not configure HTTPS.
- Back up DNS records and the WordPress site before changing nameservers, server configuration or URL settings.
- Check whether the page is published and whether forms, analytics, internal links and canonical tags need host-specific testing.
WordPress.com: connect a domain for the whole site
Use this route when the new domain should be the public address of the entire WordPress.com site, not just one landing page. WordPress.com says the domain remains registered with the external registrar. Connecting it and selecting it as the site’s primary address are separate actions, and current support guidance requires an eligible paid plan for custom-domain connection and primary use.
Connect the domain
- Open your WordPress.com Hosting Dashboard and choose the option to add or connect an existing domain.
- Follow the displayed verification and DNS instructions. The exact labels and eligibility can change, so use the current guide at WordPress.com’s domain-connection instructions.
- If you use WordPress.com nameservers, WordPress.com manages DNS for the domain. If you must keep DNS at your registrar, use the A/CNAME alternative method and create the records shown there.
Set the connected domain as primary
After the connection is complete, separately select the domain as the site’s primary address using WordPress.com’s primary-address guidance. The old free .wordpress.com address and redirect behavior depend on the current plan and configuration; verify the result in the live dashboard rather than assuming a universal rule.
#1 Best Overall
- Used Book in Good Condition
When to keep external DNS
The A/CNAME method is useful when you cannot change nameservers or when email and other services must continue using the registrar’s DNS. DNS remains at that registrar, so future web, email and verification-record changes must also be made there. Do not replace nameservers blindly: first inventory the existing records.
WordPress Multisite: map a domain to one subsite
WordPress has native Multisite domain mapping from version 4.5 onward. This is appropriate when the landing page is actually a separate subsite in a network. It is not a page-level alias for an ordinary single-site installation.
Prepare DNS, the server and SSL
- Create the required DNS record for the mapped domain so it points to the network server.
- Configure the web server or hosting control panel to accept that hostname and route it to the existing WordPress installation. DNS pointing at an IP is not enough if the server does not recognize the host.
- Install and activate an SSL certificate covering the mapped domain, then confirm that the HTTPS hostname reaches the network without certificate warnings.
- Review the network preparation requirements in the WordPress Multisite preparation handbook.
Enter the mapped URL in Network Admin
- Sign in as a network administrator and open the target subsite’s settings in Network Admin.
- In the Site Address (URL) field, enter the complete HTTPS address, such as
https://example.com. - Save the change, then test the homepage, the landing page, administrator login and any forms in a private browser window.
WordPress Developer Resources gives the instruction this way: “In the Site Address (URL) field, enter the full URL to the domain name you’re mapping – https://example.com – and click save.” Read the complete Multisite Domain Mapping handbook, including its cookie guidance, if login or session behavior breaks.
Older networks may contain legacy domain-mapping plugins or configuration. Do not mix an old plugin setup with native mapping until you understand which component currently owns the URLs.
Recommended Free Tools
Rank #3
Self-hosted single site: show one landing page at another domain
A single-site page alias requires two layers: infrastructure that delivers the domain to WordPress, and a page-level mechanism that decides which published page to display. WordPress’s native Multisite instructions do not, by themselves, map a second domain to one page.
Route the domain to WordPress
- At the registrar or DNS provider, point the domain or subdomain to the server hosting WordPress.
- Configure the web server, reverse proxy or hosting panel to accept that hostname and send it to the correct WordPress installation.
- Issue an SSL certificate for the alias and force HTTPS only after the certificate works.
Use the network and server fundamentals in the WordPress preparation documentation as a reminder that DNS and server routing are separate tasks.
Choose a page-level mapping method
A plugin or custom server/application configuration must associate the incoming host with the intended page. The WordPress.org listing for Domain Mapping System specifically describes mapping a domain to a page or group and displaying one page’s content at another domain. That listing is a vendor claim, not a guarantee for every hosting stack. Before enabling it, check the plugin’s current compatibility, documentation, update history and supported WordPress/PHP versions.
Test the behavior you actually want
- Open the alias over HTTPS and confirm that the intended landing page, not the site homepage or a 404, appears.
- Check whether the alias remains in the address bar or redirects to the site’s canonical URL.
- Test navigation, images, downloadable files, forms, embedded content and login links for hard-coded URLs.
- Inspect canonical tags, redirects, sitemap output and analytics host reporting. The available setup guidance does not establish a universal SEO benefit, so do not promise one.
- Test both the alias and the original site URL on desktop and mobile, including a private window with cached redirects cleared.
Redirect or keep the alias visible?
A redirect sends visitors to a chosen canonical address; host mapping keeps the alias visible while the mapped page is served. The right choice is a product and URL-architecture decision, not an automatic WordPress setting. Decide before launch, then verify links, forms, analytics and canonical metadata under the selected behavior.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Troubleshooting checklist
The domain shows a DNS error
Confirm the record points to the intended provider, that the hostname is spelled correctly, and that the authoritative nameservers are the ones you edited. If email or third-party services use the domain, restore any missing records from your backup.
The server displays the wrong site
DNS may be correct while the web server’s virtual-host or proxy rule is not. Add the alias to the hosting configuration and route it to the same WordPress installation before changing page settings.
HTTPS fails
Issue a certificate for the exact domain, including a www variant if you intend to serve it, and ensure the server presents that certificate. Do not treat an HTTP-only test as a completed launch.
The wrong page, a redirect loop or a 404 appears
Check which layer is handling the host: WordPress.com dashboard, native Multisite mapping, or the single-site mapping plugin/custom rule. Remove conflicting legacy mappings, review redirect and canonical settings, and retest with caches bypassed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Multisite users cannot stay logged in
Review the cookie and domain guidance in the official Multisite mapping handbook instead of applying an unrelated single-site fix.
Quick Recap
Decision summary
- Whole WordPress.com site: connect the domain, then set it as primary; choose nameservers or the A/CNAME method based on DNS and email needs.
- Multisite subsite: prepare DNS, server routing and SSL, then enter the full HTTPS mapped URL in Network Admin.
- One page on a single site: prepare DNS, server routing and SSL, then use a maintained page-level mapping mechanism and test every URL-dependent feature.
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.
