SEO Migration Checklist: How to Move a Website Without Losing Rankings

Most traffic losses after a website migration are not caused by Google. They are caused by decisions made months earlier: URLs changed without a reason, a redirect map built from the sitemap instead of from real data, a staging "noindex" tag that went live with the new site. This SEO migration checklist is organised in the order those decisions happen, with the reason behind each step, so you know what to protect and why.

What counts as a website migration?

Any change that affects how search engines find, read or understand your pages. The level of risk depends on what changes.

Several of these often happen at once. A new CMS with a new URL structure and a redesign is three migrations, and should be planned as such.

Phase 1: Before you start

Most of the SEO work in a migration happens before a line of code is written. This is also when SEO has the most influence on the new site, so it needs to be in the project from the design brief, not brought in two weeks before launch.

1. Decide what changes and what does not

Every URL you keep is a redirect you do not need and a ranking you do not put at risk. Challenge each URL change: is there a real reason (a clearer structure, a new offer, a rebrand), or is it a side effect of the new platform's defaults? Many platforms can be configured to keep existing URLs.

2. Take a full benchmark

• Export Search Console data for the longest period available: queries, pages, clicks, impressions and average position.
• Export landing pages from analytics by channel, with conversions or revenue.
• Record rankings for your priority keywords.
• Export backlinks by target page.
• Crawl the full site: status codes, titles, meta descriptions, headings, canonicals, hreflang, structured data and internal links.
• Record Core Web Vitals for your main templates.

This is your reference point. Without it, you cannot tell after launch whether a change is a problem or normal movement.

3. Rank the pages that matter

Not every URL deserves the same care. Score pages on organic traffic, conversions or revenue, number of linking domains, and their role in the site structure. The top group gets manual checks at every stage. This is where most checklists fall short: 88 equal steps are hard to prioritise when the launch date is fixed.

4. Inventory everything that points to the site, not just Google

Redirects protect search traffic, but plenty of other links point to your old URLs. List them before launch so each one can be updated rather than left to a redirect:

• Final URLs in paid search, shopping feeds and paid social ads.
• Links in email templates, automated journeys and CRM sequences.
• QR codes on packaging, print, events and point of sale.
• Social profile links and pinned posts.
• Retailer, distributor and partner listings.
• Links inside PDFs, apps and help centres.

A redirect will usually catch these, but ad platforms can reject or penalise URLs that redirect, tracking parameters are sometimes lost, and a QR code printed on packaging cannot be changed later.

5. Decide what happens to each piece of content

For each page: keep, merge or remove. Merged pages redirect to the page that now covers the topic. Removed pages with no equivalent and no links can return a 410 or 404. Redirecting them all to the homepage is not a solution: Google may treat a redirect to an irrelevant page as a soft 404.

6. Write SEO requirements into the design and development brief

• Editable titles, meta descriptions and H1s on every template.
• One H1 per page and a logical heading structure.
• Breadcrumbs and internal linking modules (related content, category links).
• Clean, readable URLs and a single version of each page (canonical tags).
• Structured data at least equal to what exists today.
• Performance budgets for images, scripts and fonts.

7. Agree success criteria and a go or no-go list

Decide before launch what "ready" means: redirect map complete and tested, priority pages checked, tracking verified, performance within target. If any item on the list fails, the launch moves. It is far cheaper to delay a launch by a week than to spend three months recovering lost traffic. Agree also what counts as success afterwards, for example organic traffic to priority pages back within a set margin of the benchmark after two months, so everyone judges the result the same way.

Phase 2: Building the redirect map

The redirect map is the single most important document in the migration. It lists every old URL and where it goes.

• Build it from data, not from the sitemap. Combine URLs from your crawl, Search Console, analytics landing pages and backlink exports. Sitemaps often miss old pages that still carry links and traffic.
• Redirect one to one, to the closest equivalent. Each old URL should point to the new page that best matches its content.
• Use permanent, server-side redirects (301 or 308). Avoid JavaScript or meta refresh redirects for this.
• No chains. If older redirects already exist, update them so they point straight to the final destination.
• Include files and images with traffic or links: PDFs, downloadable resources, key images.
• Handle variations: trailing slashes, upper case, www and non-www, http and https, and URL parameters.

The example above shows the columns worth keeping. The "Tested" column matters: every redirect should be checked against the staging site before launch.

Phase 3: Testing on staging

• Keep staging out of the index, the right way. Password or IP protection is safer than relying on robots.txt alone. If a noindex tag or a disallow rule is used, make sure removing it is on the launch checklist.
• Crawl staging and compare it with the live site. Titles, H1s, meta descriptions, canonical tags (pointing to the live domain, not staging), hreflang, structured data and internal links.
• Check internal links point to new URLs directly, not through redirects.
• Test the redirect map by running the full list of old URLs through a crawler against staging.
• Check performance. Google's "good" thresholds for Core Web Vitals are a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less.
• Check tracking. Analytics tags, consent banner behaviour, conversion events, ad platform tags and Search Console verification (DNS verification survives a redesign best).

Phase 4: Launch day

1. Launch at a quiet time for your business, early in the week, with the people who can fix things available.
2. Deploy redirects at the same moment as the new site, not afterwards.
3. Remove any noindex tags and staging disallow rules, then check robots.txt on the live site.
4. Submit the new XML sitemap in Search Console.
5. For a domain change, use the Change of Address tool in Search Console once redirects are live.
6. Manually check your priority pages, forms, checkout and key conversion paths.
7. Update the external inventory from Phase 1: ads, emails, QR code destinations where possible, profiles and partner links.

Phase 5: The first weeks after launch

• Daily for the first week: Search Console page indexing and crawl stats, server errors, and 404s appearing in logs or crawl reports.
• Compare with the benchmark by page group, not only sitewide. A stable total can hide a section that has collapsed.
• Fix 404s that have traffic or links first, then clean up any redirect chains.
• Expect some movement. Google notes that a medium-sized site can take a few weeks for most pages to move in its index, and larger sites longer.
• Keep redirects in place for at least a year, as Google recommends, and indefinitely for URLs with valuable backlinks.
• Ask the sites linking to your most important old URLs to update their links. A direct link is stronger than one through a redirect.

Special cases that need extra steps

Domain change or rebrand

A new domain starts without the history of the old one, so every signal has to be passed on through redirects. Keep control of the old domain for as long as it has links pointing to it, and do not let it expire: redirects stop working the day the domain lapses. Announce the new name clearly on the site, since visitors arriving from old links need to understand why the brand looks different.

Changing CMS or ecommerce platform

Some platforms impose their own URL patterns. Shopify, for example, places products under /products/ and categories under /collections/, so a move to it almost always means a URL change for the whole catalogue. Check early what the new platform can and cannot control: URL structure, title and meta fields, canonical tags, redirect limits, and how it handles pagination and filters.

International sites

If the site serves several countries or languages, every hreflang annotation must point to the new URLs, and each language version must reference the others correctly. A broken hreflang setup can send visitors to the wrong country version for weeks.

Ecommerce catalogues

Product and category pages usually carry the most revenue and the most links. Map them one to one, including discontinued products (to the closest replacement or the parent category), and keep the same product names and key attributes in titles so search engines recognise them.

Who needs to be involved

The most common failure is not technical. It is a migration where nobody owns the redirect map, or where SEO is consulted after the templates are built.

Why traffic drops after a migration, and how to find the cause

Do not forget AI search

AI assistants and AI search features build their picture of your brand from many sources. After a migration, update your brand details wherever they appear (business profiles, directories, social bios), keep structured data consistent with the old site, and make sure old URLs that AI tools may still cite redirect to the right place. It is part of the same job as protecting your SEO, and increasingly part of GEO.

The SEO migration checklist at a glance

A migration is also the best moment to improve the site rather than simply move it: new templates, faster pages and a clearer structure. That is where web design and SEO need to work as one team from the start, and on platform moves, with your ecommerce team too.

FAQ