Technical SEO
How to Do a Website Migration Without Losing Traffic
By Shayan Ahmad · · 6 min read

A website migration can be a new design, a new CMS, a new domain, or a large change to your URL structure. It can also be the moment organic traffic falls off a cliff. The sites that come through it cleanly are not the ones that "hoped Google would catch up". They are the ones that mapped every important URL, redirected it, tested the launch, and watched the data afterwards. This is a before, during and after checklist for business owners who are redesigning a site or changing a domain, and who want to keep the traffic they already have.
It is written for any platform. The principles are the same whether you are replatforming, reskinning the current CMS, or moving from one domain to another.
Before: Know What You Have, and Where It Will Go
Start this work before the new templates are signed off, not the week of launch. Once design decisions have already changed every path, you are negotiating with a finished site rather than planning a move.
Inventory the URLs that matter
Collect the current URL list from a crawl, the XML sitemap, Google Search Console, and analytics. You need more than the main menu. Include ranking pages, pages with backlinks, campaign landing pages, PDFs you still share, and important parameter-free versions of category and article URLs. Note the title, the search demand, and whether the page is still useful.
Build a complete redirect map
For each current URL, decide the destination on the new site: the same content at a new path, a close replacement, or a genuine 404 if the content is retired and has no useful successor. Write this as a spreadsheet, with old URL, new URL, and redirect type. Almost every permanent move should be a 301 to the closest equivalent page, not to the homepage.
If the domain is changing, the map still starts with paths. Then you apply it on the new host, and you 301 the old domain across in one hop. Do not leave HTTP, HTTPS, www and the old domain pointing at each other in a chain.
Protect content, metadata and tracking
A redesign is not a reason to throw away title tags, headings and unique copy that already work. Take them across, then improve them. Set up Search Console and analytics on the new property or domain before launch, including any DNS or file verification you will need on the day. If a third party is building the site, put this list in the brief. Our web design and development work treats the URL map as a launch deliverable, not as an optional extra.
During: Launch With One Hop and a Working Site
On launch day, the redirect map has to be live before you send the public to the new site. Test a sample of old URLs by hand, including the homepage, a key service or category page, a blog post, a file, and a URL with a trailing-slash variation. Each should reach the right destination in a single permanent redirect, with the final page returning 200.
Also check the things that often break in the noise of a redesign:
- The XML sitemap lists only the new, canonical, indexable URLs, and it is submitted in Search Console.
- Robots.txt is not leftover from staging, and it does not block CSS, images or the new site.
- Canonical tags, hreflang if you use it, and internal links all use the new, final URLs.
- The staging site is no longer indexable, and noindex or password protection has been removed from the live site.
- Forms, pagination, language versions and important landing pages actually work on a phone.
If you are moving domain, add the new property in Search Console and use the change of address tool when it applies, after the redirects are already working. Keep the old domain live as a redirector for as long as you can reasonably afford to; taking it down early cuts off backlinks and bookmarks. A technical check at this stage is the core of a migration-focused SEO audit, and it is the kind of discipline we look at when comparing technical SEO approaches to large site changes.
After: Watch, Fix and Do Not Panic Too Early
In the first days, some fluctuation is normal. Google has to recrawl old URLs and learn the new ones. What you should not see is large numbers of important pages returning errors, chains, or soft 404s, or a sitemap that still lists the old host.
Set a short monitoring routine for the first few weeks:
- Search Console coverage and experience reports, including 404s, redirect errors and any sudden noindex or robots blocks.
- A recrawl of the old URL list, to catch missed redirects.
- Rankings and clicks for your most important pages, compared with the same pages or their replacements.
- Analytics for organic landing pages, so you can see whether traffic is landing on the new URLs or still hitting errors.
Fix gaps quickly. A missing redirect is cheaper to add in week one than after Google has already dropped the old URL. Update any leftover internal links you find, and ask partners to update important inbound links when you can. Do not start a second redesign, or strip content, because the graph dipped in the first fortnight. Give the recrawl time, unless the data shows a clear technical fault.
This aftercare is part of a wider technical SEO programme, not a one-day event. Owners who stay with the checklist through the first month usually keep more of the traffic they were afraid of losing.
A Note on Redesigns That "Keep the Same URLs"
Even if the paths stay the same, a redesign can still harm search. Titles can be reset to defaults, content can be shortened, heading structures can change, and JavaScript can hide text or links that used to be in the HTML. Treat a visual refresh as a migration of templates, and compare a sample of old and new pages before you launch. If the URL does stay the same, you may need fewer redirects, but you still need the content and technical checks.
FAQs
How long does traffic take to settle after a migration?
It varies with the size of the site and how clean the redirects are. Some sites settle in a few weeks; larger moves can take longer. A clean map and a tidy launch matter more than a precise timetable. A sharp drop with lots of errors is not something to wait out.
Do I need to redirect every old URL?
You should have a decision for every important URL, and for any address that still gets traffic or links. Low-value, unused parameter URLs can be left to 404 if they were never useful. The homepage should not be the default destination.
Is a redesign without a domain change still a migration?
Yes, if templates, content or paths change in a material way. The risk is often underestimated, because the address bar looks familiar while the underlying pages have changed.
Should I launch on a Friday?
I would not. Launch when your team can watch Search Console and fix redirects the same day, and the next day. A quiet mid-week window is easier than a weekend, when a missed rule can sit unnoticed.
Planning a Redesign or Domain Change?
If you already have a new site in progress and no URL map, or you have just launched and traffic looks wrong, a migration review will show what is missing. Start with a free SEO audit and we will tell you what to fix before, or immediately after, the move.
- website migration
- redirects
- redesign
- technical seo
- seo checklist
Have a question about this for your own site?
A 15-minute call is usually enough to tell whether it applies to you and what to do first.


