How to Move Your Website with Zero SEO Loss

What “zero SEO loss” realistically means

No one can promise that a site move will cause no change at all in rankings. When you change domains, Google has to recrawl your pages, follow the redirects and transfer signals from old URLs to new ones. During that period, positions often wobble. What you can achieve is a move where rankings and traffic settle back to the previous level, and where no pages, links or signals are lost along the way.

This guide covers moving to a new domain, which is the hardest case, and also applies to HTTP to HTTPS moves, merging subdomains and restructuring URLs. The principles are the same: map everything, redirect permanently, tell Google, and monitor.

Types of site moves and their risk

Where possible, avoid combining a domain change with a redesign, a CMS switch and a content rewrite. Each change makes it harder for Google to match old pages to new ones and harder for you to diagnose problems. Moving first and redesigning later is usually safer.

Phase 1: preparation before you touch DNS

Secure and check the new domain

• Register the new domain, enable a transfer lock and turn on auto-renew.
• Check its history in web archives and with a WHOIS lookup. A name with a spam past may carry problems; look in Search Console for manual actions once you verify it.
• Verify the new domain in Google Search Console, ideally as a Domain property using a DNS TXT record so all protocols and subdomains are covered.

Build a complete URL inventory

Collect every URL that matters from several sources, because no single source is complete:

• A full crawl of the current site.
• Your XML sitemaps.
• Search Console performance and indexing reports.
• Analytics landing pages over the last year.
• Backlink reports, so you do not miss old URLs that still receive links.

Create the redirect map

Map each old URL to the single most relevant new URL. Keep it one-to-one wherever possible. Avoid redirecting everything to the homepage: Google tends to treat mass homepage redirects as soft 404s, so the signals from those pages are not passed on.

Phase 2: set up 301 redirects correctly

A permanent redirect (HTTP 301, or 308) tells search engines that the content has moved for good and that the new URL should replace the old one in the index. Temporary redirects (302, 307) signal that the old URL should stay, which is the wrong message for a migration. Our article on 301 versus 302 redirects explains the differences in detail.

For a domain change where the paths stay the same, a single rule can redirect everything while preserving the path and query string. On Nginx:

server {
    listen 443 ssl;
    server_name old.example www.old.example;
    # ssl_certificate lines for the old domain go here
    return 301 https://new.example$request_uri;
}

On Apache with mod_rewrite in an .htaccess file:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www.)?old.example$ [NC]
RewriteRule ^(.*)$ https://new.example/$1 [R=301,L]

Redirect rules that prevent common mistakes

• Keep a valid SSL certificate on the old domain. Visitors and crawlers reach old HTTPS URLs first; if the certificate has expired, many will never see the redirect.
• Avoid chains. Redirect old URLs straight to the final destination, not through http, then www, then the new domain.
• Return 404 or 410 for content you have intentionally removed rather than sending it somewhere irrelevant.
• Do not block the old domain in robots.txt. Googlebot has to crawl the old URLs to see the redirects.

Phase 3: update everything on the new site

• Change internal links to point directly at new URLs rather than relying on redirects.
• Update canonical tags, hreflang annotations and structured data so they reference the new domain.
• Publish a fresh XML sitemap for the new domain and submit it in Search Console. It can also help to keep a sitemap of the old URLs available for a while so Google discovers the redirects faster.
• Update profiles you control: social accounts, business listings, email signatures, ad campaigns and any partner links you can edit.
• Check analytics, tag manager and consent tools so tracking continues on the new domain.

Phase 4: use the Search Console Change of Address tool

After redirects are live, tell Google about the move with the Change of Address tool in Google Search Console. It is found under Settings for the old property.

1. Make sure you are a verified owner of both the old and new properties.
2. Open the old property, go to Settings, then Change of address.
3. Select the new property. The tool runs checks, such as testing that the old homepage and some sampled URLs return 301 redirects to the new site.
4. Submit the request once the checks pass.

Important limits to know:

• The tool works at domain level. It is meant for moves such as old.example to new.example, not for moving a subfolder or for http to https changes on the same domain.
• Google says the change of address request stays in effect for 180 days, during which it prioritises crawling and indexing the new site. Redirects must stay in place well beyond that.
• The tool does not replace redirects. Without working 301s, it will refuse the request or do little good.

Bing Webmaster Tools offers a similar site move feature, so repeat the process there if Bing traffic matters to you.

Phase 5: monitor after launch

Monitoring is where most problems are caught early. In the first days and weeks, check:

• Redirect status. Crawl your list of old URLs and confirm each returns a single 301 to the expected destination with a 200 at the end.
• Search Console reports for both properties: Page indexing, crawl stats and any spikes in 404 or server errors.
• Traffic and rankings for your most important pages, comparing like-for-like periods.
• DNS and SSL on both domains, including renewal dates.

You can spot-check a redirect from the command line:

curl -sI https://old.example/some-page | grep -i -E "HTTP/|location"

A gradual shift where the old domain’s impressions fall as the new one rises is normal. Sudden drops in both usually point to a technical issue such as blocked crawling, broken redirects or missing pages.

Phase 6: what to keep after the move

Google recommends keeping redirects in place for as long as possible, and generally for at least one year. In practice, keep them indefinitely: links from other sites, old bookmarks and emails will keep sending visitors for years.

• Keep the old domain registered with auto-renew. If it expires, all redirects stop and someone else can register it. Add both domains to TLDix monitoring so neither lapses unnoticed.
• Keep the old SSL certificate renewed for as long as the redirects run.
• Keep the old Search Console property verified so you can watch for issues.

Before the switch, lowering DNS TTL values can make the cutover faster; see the role of DNS TTL settings for details.

Handling links you do not control

Redirects pass signals from existing backlinks, but updating the most valuable links directly is still worthwhile. Contact partners, suppliers, associations and publications that link to you prominently and ask them to change the URL to the new domain. A direct link avoids an extra hop for users and removes dependence on the old domain over the long term. Prioritise sites that send real referral traffic rather than trying to update every link.

Pre-launch checklist

1. Both domains verified in Search Console.
2. Full URL inventory and one-to-one redirect map completed.
3. Redirects tested on staging, with no chains or loops.
4. Internal links, canonicals, hreflang and sitemaps updated.
5. Valid SSL on old and new domains.
6. Change of Address submitted right after launch.
7. Old domain renewal secured for years ahead.