Changing your domain name without losing SEO: a checklist
Keep rankings through a domain change: redirect every URL to the same path on the new domain, file a Change of Address, and keep the old domain for years.
By Sohail Hussain21 November 20265 min read
To change your domain name without losing SEO, redirect every URL on the old domain to the same path on the new one with a 301, verify both domains in Search Console and submit a Change of Address, update everything that still points at the old domain, and keep the old domain registered and redirecting for years. Expect a few weeks of movement in rankings while Google processes the move. Done this way, the new domain inherits the old one's standing.
The authority here is Google's guide to site moves with URL changes and its help page on the Change of Address tool. This checklist follows both, in the order we run domain changes as part of our website redesign and migration work.
Should you change your domain at all?
A domain change is the riskiest kind of migration, because every URL on the site changes at once. Good reasons to accept that risk: a rebrand, a trademark dispute, a merger, or a domain that genuinely confuses customers. Weak reasons: a keyword-rich domain (it does not help rankings), a shorter name for its own sake, or moving from a country extension to .com without evidence that the extension is costing you. .com vs .in vs .ae covers that last case.
Do not combine a domain change with a redesign or platform change if you can avoid it. Google's guide advises making changes one after the other, not all at once. If a rebrand forces both, launch the new site on the old domain first, let it settle for a few weeks, then move the domain.
What do you do before the move?
1. Decide the new domain and check its history
Register the new domain in the company's name, not an employee's or agency's. If it was previously owned, look at its history in the Internet Archive and, once it is verified in Search Console, check the Manual actions report. Google's guide recommends cleaning up any manual action on a purchased domain before moving to it. How to choose a domain name covers registration.
2. Verify both domains in Search Console
Add both as Domain properties, which cover www, non-www, HTTP and HTTPS in one. Keep your verification method working on both. If you ever uploaded a disavow file for the old domain, upload it again to the new property; Google's guide says this explicitly.
3. Keep SSL and email working on the old domain
This step is easy to miss. A visitor who types https://old-domain.com connects to the old domain before any redirect happens, so the old domain needs a valid certificate for as long as it redirects. Without one, browsers show a security warning instead of following the redirect.
If email runs on the old domain, leave its MX records alone. Mailboxes on the old domain should keep receiving, or forward to the new addresses, for at least a year.
4. Prepare the new site with new-domain URLs
On the new domain, before the switch:
- Canonical tags point at the new domain. The canonical tag generator shows the correct form.
- Internal links use the new domain, or relative paths.
- Hreflang annotations and structured data (organisation URL, logo, breadcrumbs) use the new domain.
- The XML sitemap lists new-domain URLs only.
- Analytics is ready. In GA4 you can keep the same property and update the data stream, so history stays in one place.
What do you do on the day of the move?
5. Turn on path-preserving 301 redirects
Every old URL should go to the same path on the new domain in a single hop: old-domain.com/services/audit to new-domain.com/services/audit, not to the new homepage. One server rule handles the whole site. On Nginx:
server {
listen 80;
listen 443 ssl;
server_name old-domain.com www.old-domain.com;
# ssl_certificate and ssl_certificate_key for the old domain go here
return 301 https://www.new-domain.com$request_uri;
}
On Apache, in the old domain's .htaccess:
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?old-domain\.com$ [NC]
RewriteRule ^(.*)$ https://www.new-domain.com/$1 [R=301,L]
On Vercel or Netlify, add the old domain to the project and set it to redirect to the new one in the dashboard; then confirm with a test that the path is kept. If paths are changing as well, add those rules from your redirect map so each old URL still reaches its final page in one hop. The redirect generator writes them.
Test with curl -I on a dozen old URLs, including http:// and www variants. Each should return one 301 to the matching new URL.
6. Submit the Change of Address
In Search Console, open the old domain's property, then Settings, then Change of Address, and choose the new property. The tool checks that the old homepage redirects to the new one before it lets you continue. Google's help page says to run it for every verified variant of the old domain. Then submit the new sitemap in the new property.
The tool is only for domain and subdomain changes. You do not need it for HTTP to HTTPS, for www to non-www, or for path changes on the same domain.
What do you update after the move?
7. Update external references
Redirects catch old links, but each hop you remove helps visitors and speeds up the move. In rough order of value:
| What | Where |
|---|---|
| Google Business Profile website link | Business Profile manager |
| Social profiles | LinkedIn, Instagram, X, YouTube, Facebook |
| Your top backlinks | Search Console's Links report; ask those sites to update |
| Payment, login and webhook callback URLs | Payment gateway, OAuth apps, integrations |
| Email signatures, invoices, quote templates | Email client, accounting software |
| Directory and association listings | Each listing's admin |
| Printed materials | Update at the next print run; the redirects cover the old ones |
Callback URLs deserve a check on the day itself. A payment gateway that still returns customers to the old domain may work through the redirect or may fail outright, depending on the provider.
8. Keep the old domain and redirects
Google's site move guide recommends keeping redirects for as long as possible, generally at least a year. The Change of Address tool asks for at least 180 days. Our advice is simpler: keep renewing the old domain and leave the redirects running indefinitely. Old links never stop arriving, and a lapsed domain can be registered by anyone.
For the weeks after the switch, follow the week after a migration, and compare clicks in the new property with the old one's last month. If you are also redesigning, the full sequence is in the website redesign process.
Was this guide useful?