Templates

SEO migration checklist template, before, during and after the move

Templates · updated on 19 November 2026 · 6 min read

Short answer

With an SEO migration checklist you go step by step through the move of your website to a new domain, a new URL structure or a new system. You work in three rounds, before, during and after launch. That way your visitors, your place in Google and your measurement data move with you. You fill in the 301 plan in the table.

The SEO migration checklist to tick off

Use the list for every move or relaunch of your website. Print it out or put it in a file of your own. Tick off each round with the date, so you can read back later what happened when.

SEO migration from [current address] to [new address]

Type of migration [new domain, new URL structure, new system or new design]. Launch on [date], final responsibility with [name].

1. Before the move

  • Collect all addresses of the current site from a crawl, the sitemaps and Search Console. Total [number] addresses.
  • Note the clicks, the main keywords and the incoming links for each address. Saved in [file].
  • Record a baseline of traffic, enquiries and rankings over [period].
  • Save the titles, descriptions and structured data of the current pages.
  • Link each old address to a new address in the 301 plan below.
  • Put the test environment behind a password, so search engines leave it alone.
  • Crawl the test environment and check titles, canonicals and internal links. Errors [number].

The 301 plan

Old addressNew addressCodeTested
/services/gutter-cleaning/gutters/cleaning301Yes, on 4 June
[old address][new address][301][date]
[old address][new address][301][date]
[old address][new address][301][date]

2. During launch

  • Put the redirects live as permanent 301s, one to one per address. Live on [date and time].
  • Test [number] old addresses from the 301 plan for code 301 and the right final address.
  • Remove the password and every noindex from the test phase.
  • Read through the robots.txt of the new site line by line.
  • Change internal links, canonicals and hreflang to the new addresses.
  • Add the tracking code to the new pages and test an enquiry via the form. Tested on [date].
  • New domain? Submit the change of address in Search Console. Submitted on [date].

3. After the move

  • Submit the new sitemap in Search Console on [date].
  • Track the indexing of the new site every week. Week 1 [number], week 4 [number] pages in the index.
  • Find old addresses that return a 404 and catch them with a 301. Caught [number].
  • Compare clicks and enquiries with the baseline. After 4 weeks [number], after 12 weeks [number].
  • Keep the redirects for at least a year and renew the old domain name. Renewed until [date].

Notes after the migration [what stood out and what you changed]

How to complete the migration

A migration succeeds in the preparation. The more you record before launch, the faster you see what is causing friction after the move.

  1. Complete the list of old addresses

    A crawl finds what can be reached via links. Add your sitemaps and the addresses from Search Console that get clicks. Google calls this mapping of old to new URLs an important step in its guide to site moves with URL changes.

  2. Choose the best-matching new page for each address

    Match each old page to the new page with the same content. A visitor looking for a product page gets little out of the homepage. Google recommends a permanent server-side redirect, because the crawler most often interprets it correctly, according to its explanation of redirects. A JavaScript redirect is only the last resort.

  3. Test everything on a protected test environment

    First build the new site on a test address behind a password. As Google explains, a rule in robots.txt alone still lets a test page appear in the search results. A password or noindex keeps it out. Remove that protection the moment the site goes live.

  4. Register a new domain with Google

    If you choose a different domain, use the change of address tool in Search Console. As Search Console Help explains, you need both the old and the new property verified in Search Console for this, plus a 301 from the old homepage to the new one. Never use this tool for a switch from http to https.

  5. Measure and give Google time

    For a small to medium-sized site, it takes a few weeks for most pages to move, according to Google. During those weeks, compare your figures with the baseline. Ideally, traffic to the old addresses falls while traffic to the new addresses rises.

Which kind of migration?

The list fits every move. How much work it is depends on what changes in your addresses.

The same addresses

You get a new design or different hosting and your URLs stay the same. Then the 301 plan is short and the focus is on round 2. Google describes this separately in a guide to site moves without URL changes.

New addresses or a new domain

If your URL structure changes or you choose a different domain, everything revolves around the 301 plan. Every old address that falls outside the plan returns a 404. Over time, Google drops such an address from the index.

Frequently asked questions about the SEO migration checklist

When do you start with the checklist?

As soon as the decision for a new site, a new domain or a new URL structure is made. Allow weeks rather than days for the inventory and the 301 plan, especially for a webshop with many product pages.

How long do you keep redirects in place?

For as long as possible. In its guide to site moves, Google generally advises at least a year. For the change of address in Search Console, a minimum of 180 days applies.

Can you merge old pages?

Yes, then redirect each old page to the new page that takes over its content. If a topic disappears completely, let the old address return a 404 or 410.

Should you keep the old sitemap?

Yes. According to Google, after the move you first submit the sitemaps based on your mapping, with the old and the new addresses. Then comes the new sitemap. You remove the old one later.

What if the migration is already behind you?

Then start at round 3. Find the old addresses that return a 404, compare your figures with the period before launch and add the addresses you missed to the 301 plan afterwards.

Have your migration guided

Next step

Planning a move or relaunch? In an SEO migration, our team creates the 301 plan, tests that plan on your test environment and tracks the figures after launch. Dominic goes through the plan with you beforehand. Is the problem mainly in the technical side of your site? Then read about technical SEO.

HOW SEO MIGRATION WORKS