Domains5 June 20266 min read

How to transfer your domain without losing your SEO

Done right, a domain transfer costs you almost nothing in search rankings. Done carelessly, it can wipe out your traffic overnight. The difference comes down to 301 redirects and a short checklist — here it is.

A domain transfer sounds scary because of one fear: losing the search rankings you've spent years building. The good news is that done correctly, a transfer costs you almost nothing in SEO. Done carelessly, it can wipe out your traffic overnight. The difference comes down to a handful of steps — here they are.

First, "transfer" means two different things

People use the word for two very different operations, and only one of them really threatens your SEO:

Moving the domain registration from one registrar to another (e.g. GoDaddy → OVH). Your URLs don't change, so this has essentially no SEO impact.
Changing the domain itself (e.g. old-name.com → new-name.com), or moving your content to a new site. This is where rankings are genuinely at risk and where redirects matter.

This guide covers both, with most of the care reserved for the second case.

Why a transfer can hurt SEO

Google ranks URLs, not businesses. Every page that ranks has accumulated authority tied to its exact address. When that address changes — or the site behind it disappears — Google has to rediscover everything, and any link or signal pointing at the old URL is lost unless you tell Google where the page went.

The number one cause of lost traffic during a transfer is simple: old URLs return a 404 instead of redirecting to their new equivalent. Avoid that and you avoid most of the damage.

Before you start

Export a full list of your current URLs. A crawl tool, your sitemap, or Google Search Console's page report all work.
Note your top pages. Know which URLs bring the most traffic — these are the ones you must redirect perfectly.
Unlock the domain and get the auth/EPP code from your current registrar (only needed when changing registrar).
Don't let the domain expire. Transfers can take a few days; never start one close to the renewal date.

301 redirects: the single most important step

A 301 redirectis a permanent "this page has moved" instruction. It sends visitors and search engines from the old URL to the new one, and it passes the large majority of the old page's ranking value across. If you change domains or URLs, this is non-negotiable.

The rules that matter

Redirect every old URL to its closest new equivalent — page by page, not all to the homepage.
Use 301 (permanent), not 302 (temporary), which doesn't pass authority the same way.
Avoid redirect chains (A → B → C). Point each old URL straight to its final destination.
Keep the redirects in place for at least a year — ideally permanently.

Mapping old URLs to new ones one-to-one is the work that protects your rankings. If a page has no equivalent, redirect it to the most relevant category — never to a dead end.

The transfer process

Moving registrar (same domain)

Unlock the domain at the current registrar and request the auth/EPP code.
Start the transfer at the new registrar and enter the code.
Approve the confirmation email. The transfer completes in a few days.
Re-check your DNS records afterwards — they sometimes need to be re-entered.

Changing domain or moving to a new site

Build the new site and keep the URL structure as close as possible to the old one.
Set up your 301 redirects from every old URL to the new one.
Point the new domain at the new site (see our DNS guide).
Go live, then immediately verify the redirects work.

After the transfer

Add the new domain to Google Search Console and submit your new sitemap.
If you changed domains, use the Change of Address tool in Search Console to tell Google explicitly.
Update internal links, your Google Business Profile, social profiles, and any backlinks you control.
Watch your coverage and traffic reports for a few weeks. A small temporary dip is normal; a cliff means a redirect is missing.

Final checklist

Full list of old URLs exported.
301 redirects mapped one-to-one and tested.
New domain pointed correctly via DNS, HTTPS active.
New sitemap submitted to Search Console.
Change of address declared (if the domain changed).
Internal links, profiles, and backlinks updated.

Moving to a Zapia site? HTTPS and the new sitemap are handled for you — you just point your domain and set up the redirects. Need a hand mapping them? Reach us at contact@zapia.fr.