Changing a Domain Name Without Losing SEO: A Site Move Plan

To change domain name SEO-safely, set up server-side permanent redirects from every old URL to its matching page on the new domain. When those redirects work, submit a Change of Address in Search Console for the old site. This guide is for site owners who are rebranding or merging several domains into one and don’t want to lose their search traffic. It covers moves where the URLs change. Only switching servers, with the addresses staying put? Then you want the guide on changing IPs instead of domains.

What Counts as a Site Move with URL Changes?

Going from example.com to example.net is a site move with URL changes. So is merging several domains or hostnames into one. Google’s guide to moving a site with URL changes uses exactly these examples. A new hosting provider or CDN is a different story, because visitors and crawlers still see the same addresses. HTTP to HTTPS? That changes URLs too, but it has its own, simpler rules. And if you registered the new domain a while back, or bought it with some past attached, look into domains with existing history before you send any traffic its way.

Why Change One Thing at a Time When You Change Domain Name for SEO

Move to the new domain first. The new CMS, the redesign, the new site structure: all of that can wait and come later, one at a time. Why so strict? Diagnosis. If traffic drops after one change, you know the cause. Change five things on the same day and you’re guessing. Google gives this exact order as an example: move to the new domain, then change the layout. Also, settle the domain structure before the move (switching again later means a second migration, and nobody wants that). If you target several countries, make the ccTLD or subfolder choice first.

Domain Migration Checklist: Prepare the New Site

No redirect goes live until the new domain serves the full site and your URL mapping is done. Work through these steps in order:

1. Register the new domain and point its DNS at the server that will host the site.
2. If the site runs on HTTPS, install TLS certificates for the new domain on your own server. Keep the old domain’s certificate valid as well, so redirects from its HTTPS URLs don’t break.
3. Verify both the old and the new domain in Search Console.
4. Build a mapping that pairs each old URL with its new equivalent.
5. On the new domain, check that internal links, canonical tags and XML sitemaps use the new host. Not the old one.

If every path stays the same and only the host changes, one wildcard server-side redirect can stand in for a full URL list. Nice shortcut. You can also keep hosting and change IPs, pointing both domains to your existing origin through a panel, so the domain switch doesn’t quietly turn into a server move as well.

How to Redirect the Old Domain Without Breaking Rankings

Set up a server-side permanent redirect from each old URL to the new URL in your mapping. On Apache these rules usually live in .htaccess. On your own NGINX they go in a server block. Most CMSs have redirect functions built in, too. Google’s advice on redirect strategy suggests asking your server admin or host which options you can actually use. On NGINX, 301 redirects for a domain change that keep the path and query string look like this:

server {
    server_name example.com www.example.com;
    return 301 https://example.net$request_uri;
}

The $request_uri variable carries the full path and query string, so /pricing?plan=team lands on the same page on the new host. Now, two classic mistakes. Don’t dump every old URL on the new homepage. And don’t build redirect chains. Each old address should point straight at its equivalent, one hop, done. Keep the old domain registered and the redirects running. And never, ever let the old domain expire.

When and How to Use the Change of Address Tool

Submit a Change of Address in Search Console for the old site once the move is live and the redirects work. Google’s help page for the Change of Address tool says it tells Google about the move and helps shift search results from the old site to the new one. It only covers moves between domains or subdomains, like example.com to example.net or a.example.com to b.example.com. So it’s not for an HTTP to HTTPS switch, not for www vs. non-www, and not for moving paths inside one domain. One more catch: it only works on domain-level properties, which means a path-level property like example.com/petstore/ can’t be moved with it.

What to Check After the Move

After launch, confirm that old URLs return a permanent redirect to the right page and that Google is crawling and indexing the new domain. Then keep an eye on these:

• Test a sample of redirects from your mapping, including deep pages and URLs with query strings.
• Watch crawl errors and indexing reports in both Search Console properties.
• Update social profiles, business listings and any important backlinks you control so they point to the new domain.
• Keep the sitemap for the new domain submitted and up to date.

How fast does traffic settle? Honestly, nobody can promise that, and every site moves at its own pace. If you hit a problem the plan doesn’t cover, the Google Search Central help pages and user forums have answers for a lot of oddly specific cases.

The order is the same for every migration: prepare the new site, map the URLs, redirect the old domain, submit the Change of Address, then monitor both properties. Stick to that order, change nothing else during the switch, and you can change domain name SEO-safely and trace any problem back to its cause. Planning a rebrand or a merger of domains? talk to us before moving.

FAQ