Website Migration SEO Checklist

The technical runbook for moving a site, from the URL map six weeks out to the redirects you keep for a year.

Updated 1 November 20265 min read

Short answer

For an SEO-safe website migration, map every old URL to a new one, use permanent server-side redirects with no chains and keep them for at least 1 year, remove test-site noindex tags on launch day, update sitemaps, canonicals and internal links, and monitor Search Console. Google says small and medium sites can take a few weeks or more to settle.

Which kind of migration are you doing?

Identify the type first, because it decides which of Google's two move guides applies and how much risk you carry. If you are still deciding what to keep, read how to redesign a website without losing SEO. This page is the technical sequence that follows those decisions.

Type Example What changes Extra step
Host or infrastructure only New hosting, a CDN Servers, not URLs Lower DNS TTL a week ahead, test on a hidden host, keep Search Console verification working
Secure address HTTP to HTTPS Every URL's prefix Redirect every URL, update canonicals and internal links
Platform Moving from one CMS to another Often the URL pattern Compare old and new URL lists before launch
URL structure Renaming sections or flattening paths Many URLs Full URL map and redirects
Domain New brand or domain name Every URL and the hostname URL map, redirects and a Change of Address

Google advises planning the move in smaller sections where you can, and changing only one thing at a time.

Six weeks out: inventory and URL map

  1. List every old URL. Combine your sitemap, analytics or server logs, Search Console's Links report and the CMS. Google lists all of these as places to find the URLs that matter.
  2. List the pages other sites link to. These are the ones you most need to redirect correctly.
  3. Decide what happens to each URL. Keep it, redirect it to a replacement or retire it with a 404 or 410.
  4. Build the map. An illustrative extract looks like this.
Old URL New URL Action Note
/services/seo-limassol /seo-limassol 301 redirect Same topic, shorter address
/blog/2021/10/review-tips /guides/seo/get-more-google-reviews 301 redirect Content merged into a better guide
/about-us /about 301 redirect
/old-offer-2019 none 410 Expired, no replacement
  1. List the places that refer to old URLs. Canonical tags, hreflang annotations, internal links, the sitemap, email footers and printed material all need updating.

Two weeks out: build and test the new site

  1. Hide the test site. Use noindex or a login. You must remove it on launch day, so put that on the checklist now.
  2. Set up certificates for HTTPS and check robots.txt and noindex rules on the new site.
  3. Verify both properties in Search Console, including every variant of the old and new domains (http, https, www and non-www).
  4. Test redirect rules on a sample from each section of the map, and confirm they are server-side.
  5. Check content parity. Titles, descriptions, headings, structured data and image alt text should match what ranks today unless you changed them on purpose.
  6. Check mobile. Content and metadata should match desktop, because Google indexes the mobile version.

Redirect rules that prevent most damage

Rule Why
Use 301 or 308 for permanent moves Google treats a permanent redirect as saying the new page replaces the old one
Prefer server-side redirects JavaScript redirects are a last resort because rendering can fail
One step only Chains slow users and can lose signals
Redirect to the closest equivalent Sending every old page to the home page is a poor match
Keep redirects for at least a year Google's stated minimum
Return 404 or 410 for pages with no replacement An honest status is better than a false redirect

Launch day, in order

  1. Take a last backup and a final export of the old URL list.
  2. Switch on the redirects.
  3. Remove any test-site noindex and any robots.txt block.
  4. Confirm canonical tags and robots meta rules point to the new URLs.
  5. For a domain move, submit a Change of Address in Search Console for each verified variant of the old domain.
  6. Submit the new sitemap and remove the old one.
  7. Update internal links on the new site, and ask important external sites to update theirs.
  8. Test the redirects by hand and a few key pages with URL Inspection.
  9. Test forms, phone links and analytics on a real phone.

Choose a quiet period for launch if you can, as Google suggests.

The first week and the first eight

When Check Look for
Daily for week one Server logs, Search Console crawl and indexing reports Errors, redirect loops, blocked pages
Weekly to week eight Impressions and clicks for pages in your old-URL list Old URLs falling and new URLs rising together
Weekly to week eight Enquiries from forms and calls Any drop that outlasts the move
Once at week four and eight A site: search for old and new domains Old pages still listed where they should have been replaced

Google also says its crawl rate can dip after a hosting move and then rise over several days. A sustained fall for pages that kept their content points to a fault, so investigate rather than wait. That reading is our rule of thumb, not a Google rule.

Failures that show up again and again

Failure How to catch it
noindex left on the new site URL Inspection on a key page, and a site: search after a week
A robots.txt block copied from the test site Read robots.txt on launch day
Everything redirected to the home page Test ten old URLs by hand
Chains and loops Run old URLs through a crawler or redirect checker
Canonicals still pointing to the old domain View source on five new pages
Sitemap listing old URLs Open the sitemap in a browser
Hreflang pointing to old addresses See the hreflang guide
Analytics and Search Console not carried over Check both on launch day

How long it takes

The technical steps are quick compared with the waiting. Google says it can take a few weeks or more for small and medium sites, and longer for large ones. Our timeline guide puts that in context.

Next step

Start the URL inventory today, even if the launch is months away. It is the longest task, and starting early takes the pressure off launch week. If you want help with the whole move, see our web design work and SEO service, or contact us with the size of your site.

Sources

  1. Google Search Central, site moves with URL changes
  2. Google Search Central, site moves without URL changes
  3. Google Search Central, redirects and Google Search
  4. Google Search Central, canonical URLs
  5. Google Search Central, localized versions of your pages

Frequently asked questions

What does website migration mean?

It means moving a site to a new place or structure: a new domain, platform, host, HTTPS or URL pattern. It is a search risk because Google must learn that old addresses are replaced. A new look on the same URLs carries far less risk.

How long does it take Google to reflect a migration?

Google says that for small and medium sites it can take a few weeks or more for new URLs to appear in place of the old ones. Larger sites take longer. Traffic to the old addresses should fall as traffic to the new ones rises.

Do I need to tell Google about a domain change?

Yes. For a domain move, Google advises submitting a Change of Address in Search Console for every verified variant of the old domain once redirects are live. Also submit the new sitemap and ask other sites to update their links.

Do I need redirects if only the design changes?

Not if every URL stays the same. If any URL changes, redirect it permanently to its closest replacement. Check by comparing an export of old URLs with the new site before launch.

How long should I keep redirects?

Google says at least one year, and keeping them longer is better for visitors who still use old links. Do not remove them just because traffic to the old URLs looks low.

Keep reading

Free audit

Let us tell you what to fix first.

Send us your website and we will send back a short, honest audit of what is holding it back.

Request a free audit