Skip to content
MinniHost Guides

Website Migration SEO Checklist: Keep Your Rankings

By Posted Topic: Moving a Site

A migration that keeps the same URLs carries little SEO risk if the new host is reachable and unblocked. A migration that changes URLs needs a complete old-to-new URL map, server-side 301 redirects kept for at least a year, updated internal links and sitemap, and monitoring in Search Console. Rankings may take a few weeks or more to settle.

Blank clipboard and pen beside a laptop on a wooden desk

Part of our guide: Website Migration: How to Move a Site to a New Host

This checklist covers the search side of a move and follows Google’s own site-move documentation. It is a support page for the host-to-host moving guide, which explains the host-to-host process; for WordPress specifics see how to migrate a WordPress site. No SEO outcome is guaranteed.

Which migrations carry SEO risk

  • Same URLs, new host: low risk, if the new site is reachable and unblocked.
  • Changed URLs, same domain (new paths or platform): moderate to high risk, so you need a URL map and redirects.
  • New domain: the same, plus a change of address in Search Console, which Google says applies only to domain or subdomain changes. It is not needed for HTTP-to-HTTPS moves, www changes or path changes.

Before: crawl, benchmark, URL map

  1. Crawl the old site and list every URL, using your sitemaps, server logs and the CMS. Save the list.
  2. Benchmark search queries, indexed pages and traffic from Search Console and analytics, to compare later.
  3. Build the URL map from each old URL to its new URL if URLs change. Update canonical tags, hreflang annotations and internal links on the new site to the new URLs.
  4. Verify all variants of the old and new sites in Search Console, and confirm your server can handle extra Googlebot traffic.
  5. Lower the DNS TTL at least a week ahead for a same-URL host move.

During: 301 redirects, robots.txt, canonicals, sitemap

  • Redirects: use server-side permanent redirects (301 or 308), direct to the final destination, with chains ideally no more than 3 hops and fewer than 5. Do not send many old URLs to an unrelated page such as the new home page.
  • Test the redirects with the URL Inspection Tool or a script for large batches.
  • robots.txt and noindex: remove any disallow rules and noindex tags used during testing.
  • Canonicals: make them point to the new URLs.
  • Sitemap: submit the new sitemap and remove the old one.
  • Content you are not moving: return 404 or 410.

After: Search Console checks, crawl errors, index coverage

Watch the sitemap indexing counts, index coverage and query data in Search Console, plus server logs on both hosts. For a same-URL move, expect a temporary drop in crawl rate that rises again over a few days. Use the URL Inspection Tool on key pages. Update internal and external links to the new URLs, and ask sites that link to you to update theirs.

Timeline: what to monitor and for how long

When What to do
A week before Lower DNS TTL, finish the URL map, verify Search Console properties
Launch day Remove test blocks, switch, run the URL Inspection Tool, submit the sitemap
First days Watch crawl rate, logs on both servers, index coverage
Weeks Compare queries and indexed pages with your benchmark; rankings may take a few weeks or more
At least 1 year Keep redirects; keep the old host until its traffic is zero

Common mistakes

  • Leaving a noindex rule or a robots.txt disallow from the test copy.
  • Redirecting everything to the home page.
  • Redirect chains that run past Google’s advised 3 hops or reach 5.
  • Forgetting to carry over Search Console verification.
  • Letting the new server block Googlebot with a firewall.
  • Removing redirects within months.
  • Skipping HTTPS on the new host: see what an SSL certificate is.

Printable checklist

  • Old URLs listed from sitemap, logs and CMS
  • Benchmark saved
  • URL map built (if URLs change)
  • Canonicals and internal links updated
  • Redirects tested
  • robots.txt and noindex test rules removed
  • New sitemap submitted, old removed
  • Search Console monitoring set
  • Redirects kept at least a year

Sources re-opened and compared with this text by the MinniHost Guides team on 2026-11-17. MinniHost Guides is an independent editorial site and does not sell hosting.

Your questions answered

Will changing hosts affect SEO?

A host change with the same URLs should not hurt rankings if the new site is reachable, loads correctly and is not blocked. Google expects a temporary dip in crawl rate after launch that recovers over a few days. The risk comes from mistakes: leftover noindex or robots.txt blocks, broken pages or a server that cannot handle Googlebot.

How long do rankings take to recover after a migration?

Google says that for medium-sized sites rankings may take a few weeks or more to shift to the new URLs, and larger sites take longer, because Googlebot has to visit every old and new URL at least once. For a same-URL host move the crawl rate usually recovers within days, so monitor both.

Do I need 301 redirects if the URLs stay the same?

No. If every URL stays exactly the same, no redirects are needed. You need server-side 301 or 308 redirects only when URLs change, for example a new domain or new paths. Check that redirects point to the matching new page, and keep them for at least a year as Google advises.

Should I update the sitemap after a migration?

Yes, when URLs change. Google advises submitting a sitemap of the new URLs and removing the old one. For a move with no URL changes, make sure your existing sitemap still lists the correct URLs and loads from the new host without errors.

What should I check in Search Console?

Check the sitemap indexing counts, the index coverage report and search query data, and compare them with server logs and analytics to see traffic shifting from old to new URLs. Use the URL Inspection Tool on individual pages to confirm that Googlebot can reach the new host. Submit a change of address only for domain or subdomain changes.

Where this comes from

  1. Google Search Central: Site move with URL changes (developers.google.com)
  2. Google Search Central: Site move without URL changes (developers.google.com)

More on this topic

Top of page