How to Move Your Website Without Losing Rankings

Almost all the traffic lost in a website redesign is lost in a single afternoon, by a single decision, and it is nearly always the same one: nobody built a proper redirect map. The new site goes live, a few hundred old URLs stop existing, and every link and ranking pointing at them evaporates. Six weeks later somebody notices enquiries have halved. This is the checklist that prevents it, in the order the work actually happens, whether you are redesigning, changing platform, changing domain, or moving to https.

First, Know Which Kind of Migration This Is

The risk is not equal across these, and knowing which one you are doing tells you how careful to be.

• Redesign only, same URLs. Lowest risk. Content and addresses stay, appearance changes. Still capable of losing rankings if content gets cut or page speed collapses.
• Platform change, same domain. Moderate risk. URL patterns usually change because the new system builds addresses differently. This is where redirect maps matter most.
• Domain change. High risk. Everything moves and you are asking Google to transfer years of accumulated authority to a new address.
• Http to https, or www to non-www. Technically a migration and routinely treated as a five-minute job. Handled badly it creates duplicate versions of every page on your site.

Doing more than one at once multiplies the risk rather than adding to it. If you can separate a platform change from a domain change by a few months, do. If you cannot, plan for a longer recovery.

Before You Change Anything

This stage is the whole game. Skip it and the rest of the checklist cannot be completed, because the information you need will no longer exist.

1. Crawl your existing site and export every URL. Screaming Frog's free tier covers up to 500 URLs, which is enough for most business sites. Save the export somewhere permanent. This file is the basis of everything that follows.
2. Export your top pages from Search Console. Sixteen months of data, sorted by clicks and impressions. These are the pages that must not break, and this list is often surprising. Pages nobody in the business thinks about are frequently doing the heavy lifting.
3. Export your backlinks. Any tool will do. You need to know which specific pages have external links pointing at them, because those are the pages where a broken redirect costs the most.
4. Record your baseline. Organic sessions, enquiries, rankings for your main terms, and Core Web Vitals. Without a baseline you cannot tell in eight weeks whether you have a problem or a normal dip.
5. Save a full backup of the old site. Files and database. Not the hosting company's automatic one, your own copy, downloaded and stored somewhere you control.

Building the Redirect Map

A redirect map is a spreadsheet with two columns: every old URL, and the new URL it should send visitors to. That is the entire concept, and it is where migrations are won or lost.

Four rules.

1. Use 301 redirects, not 302. A 301 says moved permanently and passes authority. A 302 says temporary and does not, at least not reliably. Plenty of platforms default to 302 and nobody checks.
2. Send each old URL to its closest equivalent, not to the homepage. If a page genuinely has no equivalent, send it to the most relevant category or section. Redirecting a hundred product pages to the homepage tells Google those pages are gone, and it treats them accordingly.
3. Redirect in one hop. Old URL straight to final URL. Chains of three or four redirects, which accumulate when a site has been migrated twice before, leak authority and slow everything down.
4. Cover every variation. With and without www, with and without trailing slash, http and https, and any uppercase versions if your server treats them as distinct.

For a site under a few hundred pages this is a manual afternoon and worth every minute. For large catalogues you can pattern-match most of it and hand-check the rest, but the top hundred pages by traffic and by backlinks should always be checked individually.

While the New Site Is Being Built

• Keep staging out of the index. Password protect it, or block it in robots.txt with a noindex header. A staging site that gets indexed becomes a duplicate of your real site and confuses everything.
• Do not lose content. This is the second biggest cause of ranking loss after redirects. A redesign trims a 900 word service page to 200 words because the new layout looks cleaner with less text, and the page stops ranking. If the old page ranked, the new one needs at least as much substance.
• Carry over titles and meta descriptions deliberately. Not automatically regenerated by the new theme. Your existing ones earned their rankings.
• Rebuild the internal linking. New templates frequently drop the contextual links that were in the old body content, and internal links are how authority moves around your site.
• Keep your schema markup. Organization, LocalBusiness, breadcrumbs and product markup all need to be reimplemented rather than assumed to survive.

Launch Day

1. Launch on a Tuesday or Wednesday morning. Never on a Thursday afternoon in this region, and never before a public holiday. When something breaks, and something usually does, you want everyone available.
2. Immediately confirm the noindex setting is off. On WordPress, Settings then Reading. This one line has cost more businesses more traffic than any other single mistake in web development.
3. Test 20 to 30 redirects by hand, including your top five pages by traffic and your top five by backlinks. Confirm each lands on the right page in one hop.
4. Check robots.txt is the live version, not the staging version.
5. Submit the new sitemap in Search Console. If the domain changed, use the Change of Address tool and keep the old property verified.
6. Confirm analytics and conversion tracking are firing. Forms, WhatsApp buttons, phone links, all of it. Losing three weeks of data because a tag did not carry over is avoidable and irritating.
7. Run your top pages through PageSpeed Insights. A new design that is dramatically slower than the old one will cost you regardless of how good the redirects are.

The First Eight Weeks

Expect a dip. Google has to recrawl everything, follow every redirect and reassess every page. A drop of 10 to 20 percent for somewhere between two and six weeks is normal on a well-executed migration and is not a sign of failure.

What to watch, weekly:

• Search Console's Pages report. Indexed page count should climb back towards the old number. If it stalls well below, something structural is wrong.
• The 404 report. Every 404 with real traffic is a redirect you missed. Fix them as they appear rather than in one batch at the end.
• Your top pages by clicks. Compare against the export you saved before launch, page by page. A site-wide average hides the fact that three important pages died while everything else was fine.
• Enquiries, not just traffic. The number that matters is the one that pays.

Keep the Old Domain

If you changed domains, do not let the old one expire. Renew it for years. Those 301 redirects need to keep working, because links pointing at your old address will still exist a decade from now, and every one of them stops passing anything the moment the domain lapses.

Expired domains also get bought by people who noticed they had links, and having your old address turn into something you would not want associated with your business is a bad and entirely preventable surprise. The renewal costs less than a lunch.

There is a version of this that goes fine and a version that costs a year of traffic, and the difference is decided weeks before launch, in a spreadsheet nobody enjoys making. If you are about to rebuild, the single most valuable thing you can do today is crawl the site you already have and save the file. Everything else on this list can be recovered. That one cannot.