Site Migration Checklist: Keep Your Backlinks Intact

A site migration is one of the few moments where you can wipe out years of link building in a single afternoon. A rebrand, a domain change, a CMS replatform, or a URL restructure all touch the exact pages that hold your most valuable referring domains. Do site migration without losing backlinks and you keep your rankings. Botch the redirect map and you watch traffic bleed out for months. This checklist walks you through protecting the link equity you already paid for, step by step.

Key takeaways

• Most post-migration traffic drops are not a Google penalty. They are broken or missing redirects severing the path between your backlinks and your content.
• Build a complete URL-to-URL redirect map before launch, and prioritize the URLs that carry the most referring domains.
• Use permanent 301 redirects, avoid redirect chains, and never point everything to the homepage.
• For domain changes and rebrands, pair whole-domain 301s with the Search Console Change of Address tool.
• Crawl staging, QA every redirect before go-live, then monitor Search Console for crawl errors and lost links for at least 90 days after.

Why migrations destroy backlink equity

Here is the part most teams miss. When another site links to your /old-pricing page, that link's value flows to a specific URL. Change the URL without a redirect and the link now points at a 404. Google sees a dead end, the equity stops flowing, and the page that used to rank quietly disappears.

This is why the classic "we migrated and traffic tanked" story is almost never a penalty. It is plumbing. The links are still out there on those referring domains, but the pipe connecting them to your content got cut. Google's own documentation on site moves with URL changes is blunt about this: combining a move with a content or URL redesign means Google has to relearn the pages, and you will probably see some traffic loss in the process.

The good news is that 301 and other permanent redirects do not cause a loss in PageRank, per Google Search Central. So the equity is preservable. You just have to route it correctly. If the difference between redirect types is fuzzy to you, read our breakdown of 301 vs 302 redirects and backlink value before you start, because picking the wrong status code is a common and expensive mistake.

To preserve link value, you first have to understand how it moves. Our link equity guide for SaaS covers how authority passes from page to page, and that mental model makes the rest of this checklist click into place.

Step 1: Audit your backlink profile before you touch anything

You cannot protect what you have not measured. Before a single URL changes, pull a full export of your backlink profile so you know exactly which pages carry weight.

Open Ahrefs, Semrush, or Google Search Console's Links report and export your linked pages sorted by number of referring domains. According to Ahrefs' research on the link-rankings relationship, the count of unique referring domains correlates strongly with rankings, so referring domains, not raw link count, is the metric to sort by.

Now build a simple priority list:

Priority	Page type	What to do
Critical	Top 20 pages by referring domains	Map a 1:1 redirect to the closest matching new URL, QA twice
High	Pages with editorial links from DR 40+ sites	Map 1:1, verify the anchor context still makes sense
Medium	Pages with a handful of links	Map 1:1 or to the nearest relevant page
Low	Pages with zero backlinks and no traffic	Consolidate or retire deliberately

The point of this exercise is focus. If you only have time to manually verify a subset of redirects, verify the critical and high rows first. Those are the pages that move the revenue. While you are in there, flag any broken or orphaned pages already wasting link equity so you can fix them during the move instead of carrying the problem across.

Step 2: Build a complete URL-to-URL redirect map

This is the heart of the whole job. A redirect map is a spreadsheet with two columns: every old URL and the single new URL it should point to.

Start by crawling your existing site with Screaming Frog or Sitebulb to get the complete list of live URLs. Do not rely on your sitemap alone, since it often misses old pages that still hold links. Then for every old URL, assign the most relevant new destination.

A few hard rules that separate clean migrations from disasters:

• Map one-to-one wherever possible. Send /blog/old-slug to /blog/new-slug, not to /blog. A redirect to a loosely related page passes far less value, and a redirect to the homepage is treated by Google much like a soft 404, which means the equity mostly evaporates.
• Avoid redirect chains. Googlebot will follow a chain, but Google recommends keeping chains short and redirecting straight to the final destination. If you have migrated before, you may already have an /v1 to /v2 hop. Collapse it so the old URL jumps directly to the final live page.
• Cover the URLs nobody remembers. Old campaign landing pages, retired feature pages, and that one viral post from three years ago often carry your best links. The crawl from Step 1 catches them.
• Account for parameters, trailing slashes, and case. These tiny inconsistencies generate the broken redirects that bite you on launch night.

Keep the map in one shared sheet, version it, and treat it as the source of truth your developers implement against.

Step 3: Handle domain changes and rebrands specifically

A rebrand or domain change is the highest-stakes version of this work, because you are moving the authority of an entire domain at once. The mechanics differ from a simple URL restructure.

First, implement whole-domain 301 redirects from every old URL to its new equivalent, preserving the path structure where you can. Keeping the same site architecture in the new location, as Google advises for site moves, lets signals pass more directly because Google does not have to relearn a brand-new structure on top of a new domain.

Second, file a request in the Search Console Change of Address tool. This explicitly tells Google the whole site has moved permanently, prioritizes crawling of the new domain, forwards signals from the old one, and helps Google pick your new URLs as canonical. Both the old and new domains must be verified in Search Console first.

Third, do not chain site moves. If you redirect domain A to domain B, you cannot immediately file another change of address from B to C. Google needs time to process the first move, so settle on your final domain before you start.

A few rebrand-specific reminders:

• Update your anchor text expectations. After a rebrand, new links will naturally use the new brand name, but your historical branded anchor text still points at the old name. That is fine, but factor it into your anchor profile reviews.
• Email the handful of sites linking to your most valuable pages and ask them to update the URL directly. A live editorial link beats a redirected one, and a polite note often works.
• Keep the old domain registered and the redirects live. Letting the old domain lapse hands your equity to whoever buys it next.

Step 4: Stage, crawl, and QA before go-live

Never push a migration straight to production and hope. Stand up the new site or structure on a staging environment first, then test the redirect map against it.

Run through this pre-launch QA:

1. Block staging from indexing. Use HTTP authentication or a noindex, since a robots.txt block alone can still let staging URLs get indexed. You do not want a duplicate of your site competing with itself.
2. Crawl the staging redirects. Point Screaming Frog at your old-URL list and confirm each one returns a single 301 to the correct new URL, not a 302, not a chain, not a 404.
3. Spot-check your critical pages by hand. For the top 20 pages from Step 1, click through the redirect in a browser and confirm you land on the right content.
4. Check internal links. Make sure your own site does not link to the old URLs, because internal links to redirects waste a little equity on every hop. Update them to point at the final destinations.
5. Prepare the new XML sitemap with the new URLs ready to submit the moment you launch.

This crawl-and-verify pass is the single highest-leverage hour in the entire project. A study of common migration failures by Search Engine Journal repeatedly traces traffic loss back to redirect errors that a pre-launch crawl would have caught.

Step 5: Monitor after launch and recover fast

Go-live is the start of monitoring, not the end of the project. The first 90 days decide whether your equity transfers cleanly.

In the days right after launch:

• Submit the new sitemap in Search Console and, for a domain move, confirm the Change of Address request is filed.
• Watch the Page Indexing report for a spike in 404 errors or Page with redirect issues. A surge of 404s means redirects are missing.
• Re-crawl the old URL list weekly for the first month to confirm redirects still resolve correctly.
• Track your top pages in the Performance report, comparing clicks and impressions against the four weeks before launch. A small dip that recovers within a few weeks is normal. A sustained drop on a specific page set signals a redirect problem there.
• Keep redirects live long-term. Google says to maintain redirects for at least a year, and longer if any traffic still hits them, so it can reassign the external links pointing at your old URLs. For deeper post-launch analytics, our guide to tracking backlink-driven traffic in GA4 and GSC shows how to isolate referral and organic shifts page by page.

Recovering equity from a past migration

If you are reading this after a migration already broke something, you can still recover. Pull your linked-pages export and cross-reference it against your live URLs. Any page with backlinks that now returns a 404 is leaking equity. Build a redirect from that dead URL to the closest live page, even if the migration was a year ago. Google will pick the link signals back up on the next crawl. Then chase the highest-value referring domains and ask them to update the link directly. Recovery is slower than prevention, but the equity is rarely gone for good.

Bringing it together

A clean migration is unglamorous work: a thorough audit, a complete redirect map, a careful staging crawl, and patient monitoring. Get those four right and your backlinks keep working through a rebrand, a replatform, or a full domain change. Skip them and you spend the next quarter trying to recover what you already had.

Once your equity is preserved and stable, the next move is growth. If you are ready to add high-quality, real-traffic backlinks to the pages that matter most, you can browse vetted inventory on Saaslinks or start at the homepage to see how the marketplace works.