How to Move a Website Without Losing Your Rankings

There is a particular kind of email that arrives about ten days after a site relaunch. The new site looks wonderful. Inquiries have stopped. Nobody can work out why, and the agency is saying it takes time to settle.

It is not settling. Somebody skipped the redirects, and every page that used to rank is now returning a 404 to Google and to every link anyone ever built to it.

Why Traffic Disappears

Google does not rank websites. It ranks URLs. Fifteen years of accumulated signals attach to /services/drain-clearing/, not to your domain in the abstract. Change that address without telling anyone and the signals do not transfer — they are simply orphaned, and the page competing with you inherits the position.

A 301 redirect is the instruction that moves them. It says "this has permanently moved here", and it passes the accumulated value across. Without it, a redesign is indistinguishable from deleting your site and starting a new one.

Build the Redirect Map First

Not at launch. Before design, because it also tells you what the new site needs to contain.

1. Export every URL you have. Three sources, because none is complete on its own: your XML sitemap, a crawl of the live site, and Search Console's page report — which is the only one that includes pages you forgot existed but which still rank.
2. Add your top landing pages from analytics. Twelve months, so seasonal pages are included. A page that only matters in November is still worth keeping.
3. Deduplicate and sort by traffic. You will usually find that a few dozen URLs account for nearly all of it. Those get individual attention; the long tail gets sensible rules.
4. Map each one to its closest equivalent on the new site. Closest genuinely means closest, not the homepage.

Do not redirect everything to the homepage. It is the single most common shortcut and Google treats a mass redirect to the root as a soft 404, discarding the value you were trying to preserve. If there is genuinely no equivalent page, it is better to serve a real 404 than a lie.

The Launch Sequence

1. Build on staging, blocked from indexing. Check that it is actually blocked — an indexed staging site competing with your live one is its own problem.
2. Test the redirects on staging before anything moves. Every one should return a single 301 straight to a 200. Chains and loops leak value and are invisible unless you look.
3. Lower your DNS TTL a day ahead, so a rollback takes minutes rather than a day.
4. Launch at a quiet hour. Tuesday morning, not Friday afternoon: you want people available afterwards.
5. Remove the staging block. A launched site still carrying its staging noindex is the most catastrophic and most common launch error there is, and it looks exactly like a migration that failed.
6. Crawl the new site immediately and fix every 404 and every redirect chain.
7. Submit the new sitemap in Search Console. Leave the old one available for a while so Google rediscovers the old URLs and follows the redirects.
8. Keep the old host running for at least a week.

The Two Weeks After

Expect a wobble. A dip of ten to twenty percent for one to two weeks while Google recrawls and reassigns is normal even on a well-executed migration. What is not normal is a sustained drop, or a fall that deepens after week two.

Watch four things daily for two weeks:

• Search Console coverage — new 404s appearing is the alarm.
• Impressions, not just clicks. Impressions recover first; if they are flat, the problem is indexing rather than ranking.
• Your top twenty landing pages against the same period before.
• The contact form. Actually submit it. A migration that keeps every ranking and breaks the form has still cost you everything — and it fails silently, which is the subject of the small jobs that never get done.

The Mistakes That Cause Real Damage

• No redirects at all. Catastrophic and, remarkably, still common.
• Everything redirected to the homepage. Treated as soft 404s.
• Launching with noindex still on. Total disappearance within days.
• Changing URLs for no reason. If a URL works, keep it. A redesign does not require new addresses, and "tidier URLs" is not worth the risk.
• Dropping content. A 4,000-word page replaced with 300 words of brand copy will not rank for what the old one did. The new site can look different; it cannot say less.
• Forgetting images. If image URLs change without redirects, you lose image search traffic and every embed anyone made.
• Not reinstating analytics and Search Console. Then you cannot tell whether it worked.

What to Ask Before You Sign

Any competent supplier will have an immediate answer to all four:

1. Will you produce a redirect map, and can I see it before launch?
2. How are you testing redirects on staging?
3. What is the rollback plan if traffic drops?
4. What will you monitor afterwards, and for how long?

We map every old URL to its new equivalent before launch and watch Search Console afterwards as standard on every build — it is on our process page as step five, because losing rankings at launch is a preventable mistake rather than an inevitability. If you are still deciding whether to migrate at all, do you need a new website or just a better one is the more useful question first.

Common Questions

Why Did My Website Traffic Drop After a Redesign?

Almost always missing or incorrect redirects. Google ranks individual URLs, not domains, so the accumulated value attached to your old page addresses is orphaned unless each one 301-redirects to its closest new equivalent. The second most common cause is launching with the staging noindex tag still in place.

Should I Redirect Old Pages to My Homepage?

No. Google treats a mass redirect to the root as a soft 404 and discards the value you were trying to preserve. Redirect each URL to its genuinely closest equivalent, and where none exists, serving a real 404 is better than a misleading redirect.

How Long Does It Take for Rankings to Recover After a Site Migration?

A dip of ten to twenty percent for one to two weeks is normal even on a well-executed migration, while Google recrawls and reassigns. A sustained drop, or one that deepens after week two, is a problem rather than settling — check Search Console coverage for new 404s first.

Do I Need to Change My URLs When I Redesign?

No, and you generally should not. If a URL works, keep it. A redesign does not require new addresses, and tidier URLs are rarely worth the migration risk. Every URL you keep is one you cannot break.

What Should I Check Immediately After Launching a New Site?

That the staging noindex is removed, that a crawl returns no 404s or redirect chains, that the new sitemap is submitted in Search Console, and — actually submit it — that the contact form still delivers. A migration that preserves every ranking and breaks the form has cost you everything, and it fails silently.