Skip to content

Book a call

AHL Technologies logo

Cloud & deployment

How to migrate a website without losing your Google rankings

Redesigns and platform moves are a common cause of lost search traffic, and most of it is avoidable. A practical migration plan, from URL inventory to post-launch checks.

Published: 3 min readAHL Technologies team

Moving to a new platform, redesigning your site or changing your domain is often the right decision. It is also one of the most common reasons a site loses search traffic. The good news is that most of the risk comes from a handful of avoidable mistakes: missing redirects, lost content, and new pages that search engines can't crawl.

1. Build a complete URL inventory

Before you change anything, list every URL that matters on the old site. Combine your XML sitemap, a crawl of the site, the pages that receive search traffic in Search Console, the pages with backlinks, and your analytics landing pages. Old PDFs, images and campaign pages often have links pointing to them, so include them too.

2. Map every old URL to its best new page

  • Use permanent (301 or 308) redirects from each old URL to the most relevant new page.
  • Redirect one to one wherever possible. Sending everything to the home page throws away relevance.
  • Avoid chains (A → B → C) and loops; redirect straight to the final URL.
  • Keep the redirects in place long term, not just for a few weeks.

3. Carry over what ranks

Pages rank because of their content, headings and metadata. Keep the substance of pages that perform well, keep or improve their titles and descriptions, and make sure internal links point directly to the new URLs instead of relying on redirects. Structured data, image alt text and hreflang (for multilingual sites) need to come across as well.

4. Test on a staging site that search engines can't see

Build and test the new site on a staging URL that is blocked from indexing. Crawl it to find broken links and missing pages, test the redirect map against the inventory, and check performance and mobile layouts. Before launch, remove the staging blocks; a forgotten noindex tag on a live site is a classic migration failure.

5. Launch-day checks

  1. Redirects work for a sample of important old URLs, including old file URLs.
  2. Robots.txt allows crawling, and no live page carries a noindex tag by mistake.
  3. Canonical tags point to the new URLs, on the new domain if it changed.
  4. The new XML sitemap is live and submitted in Search Console.
  5. Analytics and conversion tracking are working on the new site.
  6. Forms and checkout are tested end to end.

If you are changing domains, also verify the new domain in Search Console and use its change-of-address tool once redirects are in place.

6. Monitor for the following weeks

Some fluctuation after a migration is normal while search engines recrawl the site. Watch Search Console for crawl errors, pages not indexed and 404s, and compare traffic to key pages against the weeks before launch. Fix missing redirects as soon as they appear; the sooner they are fixed, the less ranking signal is lost.

Changing the technology underneath

Many migrations are really technology upgrades, such as moving an old PHP site to a modern framework like Next.js. That is a good moment to improve speed and Core Web Vitals, which helps both users and search. Automate the release process too, so future changes are tested before they go live; see our migration, CI/CD and DevOps service.

More insights

All insights