Redesigning Your Website Without Losing Google Rankings - The 301 Redirect Map and Migration Checklist

Why a new website is "dangerous" for rankings at all

Every URL on the old site that carries value - organic traffic, indexation, inbound links from other sites - needs a 301 redirect to its equivalent on the new site. Without one, Google simply finds a 404 where a good answer used to be, and drops the URL from its index. This isn't a rare glitch - it's the natural outcome of a project where the team designing the new structure and the team responsible for SEO never sat down together before launch.

A real example of the scale of the damage

SISTRIX documented the migration of the UK brand Topshop into the ASOS website, and found the domain lost roughly 80% of its search visibility as a result of the merger. This isn't a theoretical worst case - it's what happens when a large platform migration runs without a complete, accurate redirect map between the old structure and the new one (source: sistrix.com).

What Google itself says about this

In its official documentation on site moves, Google explicitly recommends using permanent server-side redirects - status codes 301 or 308 - for any URL change, and states that these redirects don't cause a loss of PageRank (source: developers.google.com). Another point Google repeats: keep redirects live for at least a year from launch, even if rankings appear to stabilize much sooner - removing them too early is a common mistake that causes a second, later, confusing drop in traffic (source: searchenginejournal.com).

The redirect map - how to build it properly

• Pull a complete list of every URL on the old site that gets organic traffic, ranks for keywords, or has inbound links - not just the pages that look "important" on the surface.
• Assign each old URL a specific destination on the new site - not a blanket redirect of everything to the homepage, which preserves only a fraction of the value.
• Check for redirect chains (URL A redirects to B, which redirects to C) - every chain adds crawl friction and increases the risk of losing value along the way.
• Run the entire mapping on a staging environment before the actual launch, not after.

Checklist for the migration itself

1. Update sitemap.xml with the new URLs and resubmit it in Google Search Console.
2. Verify robots.txt isn't accidentally blocking crawlers from the new site.
3. Keep the URL structure identical wherever there's no business reason to change it - every unnecessary change is another point of failure.
4. Monitor Search Console daily in the first weeks after launch - crawl errors, a sharp drop in impressions, or a spike in 404s.

This applies to AI visibility too

The same problem exists with ChatGPT, Perplexity, and Gemini, not just Google. If content built specifically to be cited moves to a new URL without a redirect, it simply disappears from the index these AI services rely on. A study covered by Search Engine Land found that 44.2% of ChatGPT citations come from the first 30% of a document - meaning even a page that survives the move correctly, but whose internal structure gets scrambled along the way, stops being a citable source (source: searchengineland.com).