Website Migration Without Losing SEO: The Full Checklist

Migrating a website is one of the riskiest operations in SEO. Changing domains, switching platforms or restructuring URLs can wipe out years of built-up authority in a matter of days if the migration is done without method. On the other hand, a well-planned migration transfers practically all of the old site’s strength to the new one, with minimal, temporary fluctuation. The difference between the two scenarios lies in planning, the redirect map and monitoring after the switch.

This guide presents the complete website migration checklist: the URL inventory, the redirect map, pre-launch testing and follow-up. All anchored in Google’s official guidance, so your next migration happens without losing what you’ve built.

Quick answer: to migrate a site without losing SEO, map every old URL to its new one in a one-to-one relationship, apply server-side 301 redirects, update the sitemap and internal links, and use Google Search Console’s Change of Address tool if you’re changing domains. According to Google’s official documentation, 301 redirects don’t cause PageRank loss and should be kept for at least 180 days, ideally longer. Monitoring Search Console in the following weeks confirms whether the transfer went well.

What Counts as a Website Migration

Website migration is a broad term covering several different situations, each with its own particulars. Knowing which type you’re dealing with is the first step to planning correctly.

According to Google Search Central’s documentation on site moves, there are distinct scenarios that change URLs, including protocol changes (HTTP to HTTPS), domain changes, subdomain or subdirectory changes, URL architecture restructuring and content management system changes. Each of these changes page addresses and therefore requires redirects.

There’s also migration without URL changes, like a platform switch that keeps the same addresses. It’s less risky but still requires care to preserve content and technical structure. Technical SEO work is what ensures that, in any of these scenarios, Google keeps finding and understanding your site after the switch.

Why Migrations Go Wrong

When a migration tanks traffic, the cause is almost always one of three avoidable mistakes.

The first is not having a complete redirect map. When some old URLs are left without redirects, they become error pages, and all their traffic and authority is lost. In large migrations with thousands of pages, missing part of the inventory is a real risk.

The second is redirecting everything to the homepage. In a hurry, some people simply point every old URL to the new site’s homepage. Google may treat that as an error, because it doesn’t deliver content equivalent to what the person was looking for, wasting the authority of every page redirected generically.

The third is removing redirects too soon. Many people remove redirects a few weeks after migrating, thinking the job is done. That reopens the hole, because Google and external links still point to the old addresses for a long time.

The URL Inventory: Your Starting Point

No serious migration starts without a complete inventory of the current site’s pages. That inventory is what ensures no URL gets left behind.

It should gather every indexed URL on the site, cross-referencing several sources so nothing is missed. The current sitemap, Google Search Console’s pages report, traffic data from analytics tools and a full site crawl with an audit tool make up the most faithful list possible. Pages that get traffic or have backlinks are the top priority.

Before migrating, record current metrics for every important page: how much traffic it gets, which terms it ranks for, how many links point to it. Without that baseline, it’s impossible to measure afterward whether the migration preserved or hurt performance. This initial diagnosis is part of what an SEO audit delivers before any high-risk operation.

The Redirect Map: The Heart of the Migration

With the inventory in hand, the central step is building the redirect map, which pairs every old URL with its counterpart on the new site in a one-to-one relationship.

The fundamental rule is direct correspondence. Each old page should point to the most equivalent page on the new site, not the homepage or a generic category. An old product goes to the new product, an old article to the new article, a category to its matching category. The more faithful the match, the more complete the authority transfer.

The right tool for these redirects is the permanent 301. According to Google’s documentation, 301 permanent redirects don’t cause PageRank loss, which dispels one of the biggest fears about migrating. Google itself recommends server-side permanent redirects, like 301 and 308, whenever technically possible, because they’re more reliable than application-level redirects. Each type is covered in detail in our guide to 301 redirects.

Two precautions complete the map. First, avoid redirect chains: the old URL should point straight to the final destination with no intermediate hops, because, according to Google, long chains add latency and not all browsers handle them well. Second, align redirects with the new site’s canonical tags, so both signals point to the same version of each page.

Testing Before Launch

A migration should never go live without testing. Fixing a mistake after launch costs far more than preventing it in a test environment.

Ideally, build the new site in a staging environment closed to the public and Google, where you can validate everything before the switch. There, check that every redirect in the map works and lands on the right destination, that no important page returns an error, that canonical tags point to the new addresses and that the new sitemap is correct and complete.

Also confirm the staging environment is blocked from Google during the build, to prevent premature indexing, and, crucially, remember to remove that block at launch. Forgetting an active block is one of the most common and serious mistakes, because it keeps the new site invisible to Google exactly when it should be crawled.

What to Do at Launch and Afterward

At launch and in the following weeks, a few actions help Google recognize the change as quickly as possible.

Activate all redirects at the same moment the new site goes live. Then submit the new sitemap through Google Search Console and, if you’re changing domains, use Search Console’s Change of Address tool, which formally tells Google the site moved from one domain to another, speeding up the index update. The tool applies to moves between domains or hosts, not to protocol or path changes within the same domain.

After launch, monitoring is ongoing. Follow Search Console’s coverage report to catch errors, check that Google is crawling the new addresses and watch traffic behavior. According to Google, crawling of the new site is usually more intense than normal after a migration, so your server needs enough capacity to handle the extra load without going down.

On how long to keep redirects, the official guidance is clear: Google’s Change of Address tool recommends keeping redirects for at least 180 days, and longer while any traffic still arrives at the old addresses. In practice, the safest choice is keeping them permanently, since external links and user bookmarks can point to old URLs for years.

Proof That It Works

A well-executed migration preserves results, and there’s a public example from Google itself. According to the official Google Search Central blog, when the team migrated its own documentation hub, three months after the move the new blog recorded a 159% increase in clicks and 23% in impressions compared with the previous address, following exactly the migration checklist they recommend to others: keyword research, redirect mapping, 301 quality control and a post-migration monitoring dashboard.

The point isn’t to expect a traffic increase from every migration, since that gain also came from a content restructuring. The point is that, done with method, migration preserves and can even improve performance instead of destroying it.

Frequently Asked Questions About Website Migration

Will I lose rankings when I migrate my site?

If the migration is done well, the loss is minimal and temporary. According to Google’s documentation, 301 redirects don’t cause PageRank loss, so authority is transferred. A small fluctuation while Google reindexes the new addresses is normal, but results stabilize once the process completes.

Should I use a 301 or a 302 for a migration?

Use a 301, the permanent redirect. A 302 is temporary and signals to Google that the change isn’t final, which prevents full authority transfer. For a migration, which is permanent by nature, the 301 is the correct choice, per Google’s own guidelines.

How long do I need to keep the redirects?

Google’s official guidance is to keep redirects for at least 180 days, and longer while traffic still arrives at the old addresses. In practice, the safest approach is keeping them permanently, because external links and user bookmarks keep pointing to old URLs for a long time.

Do I need to use the Change of Address tool?

It depends on the type of migration. Search Console’s Change of Address tool is for moves between domains or hosts. For protocol changes, like HTTP to HTTPS, or path changes within the same domain, it isn’t used: in those cases, correct redirects and canonical tags are enough, and Google detects the change on its own.

Can I migrate the site gradually, or does it have to happen all at once?

Both approaches exist and depend on the site’s size and complexity. Phased migrations reduce risk on very large sites, letting you validate each stage before moving on. Whichever approach you choose, the principle is the same: every old URL needs a redirect to its new one the moment its section is migrated.

How do I know if the migration worked?

By monitoring Google Search Console in the following weeks. Compare traffic with the metrics you recorded before the migration, check the coverage report for errors, confirm the new addresses are being indexed and see whether Googlebot is still crawling old URLs in high volume after 30 days, which would indicate internal links that weren’t updated.

Migrate With Method, Not Luck

A botched migration wipes out years of work in a few days, and recovery is slow and uncertain. A well-planned migration transfers nearly all of the old site’s authority to the new one, with minimal, temporary fluctuation. The difference lies in a complete inventory, a faithful redirect map and monitoring after launch.

If you’re planning to change domains, switch platforms or restructure your site’s URLs, talk to Malamute Digital before taking the first step. We map every redirect and follow the transition closely through our SEO consulting, or start with a complete SEO audit of your current site, with the rigor of a team that treats every migration as a high-risk operation that demands planning.