A Website Migration Checklist That Protects Your Rankings

Redesigns lose traffic for boring reasons

When organic traffic falls after a relaunch, the cause is almost never the design. It is a missing redirect, a staging site that shipped with indexing disabled, a page that quietly lost the content that made it rank, or analytics that stopped recording on launch night so nobody noticed for three weeks.

All of those are preventable with a checklist and the discipline to work through it in order.

Before you build: record what you have

You cannot protect what you have not measured. Capture all of this while the old site is still live:

• A full crawl of every existing URL, including PDFs and images that earn traffic
• Your top pages by organic traffic and by conversions over the last twelve months
• Every page with external backlinks pointing at it
• Current rankings for your priority keywords
• Baseline Core Web Vitals from field data
• A copy of the existing metadata for every page

Twelve months matters — six months of data will hide anything seasonal, and seasonal pages are exactly the ones that get quietly dropped.

Map every old URL to a new one

This is the step that actually prevents traffic loss. Every URL from your crawl needs a decision: keep the same address, redirect to the closest equivalent, or deliberately retire.

Redirect to the most relevant specific page, not the homepage. A mass redirect to the homepage is treated as a soft 404 and the ranking value evaporates. If there is genuinely no equivalent page, letting the URL return 404 is more honest and less damaging than a misleading redirect.

Watch for redirect chains when URLs have moved before. Each hop dilutes the signal, so collapse chains into a single 301 that points straight at the destination.

Protect the content that earns the rankings

Redesigns tend to cut copy for aesthetic reasons. If a page ranks because it answers a question thoroughly, cutting it to two elegant sentences will cost you the ranking. Keep the substance; restructure how it looks.

Preserve heading structure and internal links to your important pages too. Internal linking is a large part of why some pages rank better than others on the same site, and it is easy to lose when navigation is redesigned.

Before launch

• Confirm the staging site was blocked from indexing — and that the block will be removed at launch
• Test every redirect against the mapping file, not by spot-checking a few
• Verify titles, descriptions and canonical tags on every template
• Check structured data validates
• Confirm analytics and conversion tracking fire on the new site
• Test forms end to end, including that the email actually arrives
• Run Lighthouse on mobile for each template

That first item causes more catastrophes than everything else combined. A noindex tag left in place at launch will remove you from search results within days, and recovery takes far longer than the mistake did.

Launch day

Launch mid-week and in the morning, never on a Friday afternoon — you want your whole team available if something surfaces. Immediately after DNS switches: confirm indexing is allowed, submit the new sitemap in Search Console, spot-check redirects on live URLs, and confirm analytics is recording.

The first month

Watch Search Console daily for the first fortnight. Coverage errors and a spike in 404s are the early warnings that something in the mapping was missed. Some ranking fluctuation in the first few weeks is normal as pages are recrawled; a sustained decline after three weeks is a problem to diagnose, not to wait out.

Compare traffic against the baseline you captured, segmented by landing page. Aggregate traffic can look stable while your most valuable pages quietly collapse.

Keep the old data

Hold onto the pre-launch crawl, analytics export and redirect map for at least a year. When a question comes up about a page nobody remembers, that archive is the only way to answer it.