Website migration: how to move without losing your Google rankings

A step-by-step plan for changing your website platform, design or domain while protecting the search traffic you've built up.

By the UK Technology Hub teamPublished 4 minute read

The short answer

To protect rankings during a migration, list every important URL on your old site, decide where each one will live on the new site, set up permanent 301 redirects for anything that changes, keep your best content, and check everything before and after launch in Google Search Console. Most traffic losses come from missing redirects and deleted content.

A website migration is any major change that affects how search engines see your site: a new platform, a redesign that changes page addresses, a move to a new domain, or switching from HTTP to HTTPS. Done carefully, rankings stay stable or improve. Done carelessly, traffic can drop sharply and take months to recover.

Why migrations lose traffic

Google has learned which of your pages answer which searches. If those pages disappear or move without telling Google, the links it holds lead to errors. Visitors arriving from search, bookmarks or other websites hit "page not found", and the value of links pointing to you is lost. The fix is planning.

Step 1: Take an inventory

Before changing anything, collect a full list of your current URLs. Use:

  • Your XML sitemap.
  • A crawl with a tool such as Screaming Frog.
  • Google Search Console's performance report, to see which pages get clicks.
  • Google Analytics, to find pages that bring visitors and conversions.
  • Backlink data, to see which pages other sites link to.

Mark your most valuable pages. These must be protected above all.

Step 2: Map old URLs to new ones

Create a spreadsheet with every old URL and its new destination. Keep URLs the same where you can. Where they change, point each old page to the closest equivalent new page, not just the home page. Redirecting everything to the home page is treated much like deleting the pages.

Step 3: Set up 301 redirects

A 301 redirect tells browsers and search engines that a page has moved permanently. Set these up at server or platform level. Avoid chains, where one redirect leads to another, as they slow things down and dilute signals.

Step 4: Keep your content

Pages rank because of their content. If the new design trims text heavily or merges pages without care, rankings can fall even with perfect redirects. Carry over headings, body copy, titles and meta descriptions for important pages, improving them where you can.

Step 5: Check the technical details

On the staging site, before launch, check:

  • Page titles, meta descriptions and headings.
  • Canonical tags pointing to the right URLs.
  • Structured data. Our guide to schema markup explains what to include.
  • Internal links pointing to new URLs, not redirects.
  • Image alt text and file names.
  • That the staging site is blocked from search engines, and that the block is removed at launch.

Step 6: Launch carefully

  • Launch at a quiet time for your business.
  • Remove any "noindex" settings left over from staging.
  • Submit the new XML sitemap in Google Search Console. Our Search Console guide shows how.
  • If you're changing domain, use Search Console's change of address tool.
  • Test a sample of old URLs to confirm the redirects work.

Step 7: Monitor for several weeks

Some fluctuation is normal while Google processes the changes. Watch Search Console for crawl errors and pages not indexed, check analytics for traffic drops on key pages, and fix any missed redirects quickly. Keep redirects in place for at least a year, and ideally permanently.

Common migration mistakes

  • Leaving the staging site's "noindex" setting switched on after launch, which tells Google to drop every page.
  • Forgetting image, PDF and blog category URLs that also receive traffic.
  • Changing the domain, platform and content all at once, which makes problems harder to diagnose.
  • Not keeping a copy of the old site's URL list, so missed redirects can't be traced later.

Special cases

Moving to Shopify: Shopify uses fixed URL patterns for products and collections, so redirects are essential. See our guide to migrating to Shopify and our Shopify development service.

Changing CMS: moving from one content management system to another often changes URL structures. Our CMS development service includes content migration and redirect mapping.

Get help with the risky bits

Every website we build as a replacement for an existing site includes redirect mapping and launch checks, because protecting existing rankings is part of the job.

Frequently asked questions

How long does it take rankings to settle after a migration?

Often a few weeks for a well-planned migration, sometimes longer for large sites or domain changes. Missing redirects can extend this considerably.

Should redirects ever be removed?

Keep them for at least a year. There's usually no harm in keeping them permanently, especially for pages with backlinks.

Can a migration improve rankings?

Yes, if the new site is faster, better structured and has stronger content. That's the goal of a well-planned rebuild.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

How much does a website cost in the UK?

What drives the price of a business website, typical UK market ranges, the ongoing costs people forget, and how to get a quote you can rely on.

All websites & web design guides