Skip to content
MrKeyword
Technical SEO

Website migration SEO checklist: move without losing rankings unnecessarily

Map every old URL to its closest new URL, use permanent 301 or 308 redirects one hop deep, and update canonicals, internal links and sitemaps. For a domain move, tell Google with the Change of Address tool after the redirects are live, then watch Search Console as Google recrawls both sites.

A technical website audit checklist on a dashboard
The short version
  • Map every old URL to its closest relevant new URL; do not send unrelated pages to the home page.
  • Use server-side 301 or 308 redirects that lead directly to the final destination.
  • Make new canonicals, hreflang annotations, internal links and XML sitemaps agree on the new URLs.
  • Use Search Console's Change of Address tool only for domain or subdomain moves, not for an HTTPS-only or same-domain path move.
  • Expect temporary ranking fluctuation while Google recrawls and reindexes; processing happens URL by URL.

What counts as a website migration?

For SEO, a website migration with URL changes includes moving to another domain or subdomain, changing URL paths, merging hosts, or switching from HTTP to HTTPS. Google's site-move guidance groups these changes together because Google must discover the new URLs and connect them with the old ones.

A hosting or CDN change with no user-visible URL change follows a different process: there are no old page addresses to redirect. Similarly, a redesign that keeps every URL unchanged is not the URL-mapping exercise described here. If a domain move, CMS change and redesign are all planned, Google recommends making one change at a time rather than combining them.

The checklist below covers the three common URL-changing cases:

  • Domain or subdomain move: the host changes, with or without path changes.
  • URL restructuring: paths, parameters, file extensions or directory names change on the same host.
  • HTTP to HTTPS: every HTTP URL needs its preferred HTTPS equivalent, a valid TLS configuration and the same careful signal updates.

For the redirect code decision itself, read the guide to 301 vs 302 redirects. This page turns that decision into a complete migration workflow.

Before the move

Before launch, create a complete URL inventory, choose a relevant destination for every URL and test the new site without letting staging directives leak into production. The redirect map is the central record for development, launch checks and later troubleshooting.

  1. Crawl and inventory the old site

    Crawl the old site and combine the result with its XML sitemaps, CMS URL list, analytics or server logs. A crawl only finds URLs it can reach, so the other sources help include orphaned and rarely linked pages. Export Search Console's top pages and its top linked pages so important search landing pages and backlinked URLs are not missed.

    Include images, videos, PDFs, JavaScript and CSS where their URLs will change. Google explicitly includes embedded resources in its URL-mapping guidance; moving only the HTML can leave new pages requesting assets at obsolete addresses.

  2. Build the redirect map

    Give each old URL one closest relevant new URL. Use exact mappings where page relationships differ and server-side pattern rules where a whole directory changes predictably. Do not redirect a collection of unrelated old URLs to the home page: Google says that can confuse users and may be treated as a soft 404.

Redirect map with generic URL patterns

Old URL patternNew URL patternRedirect type
/blog/<slug>/articles/<slug>301 or 308
/category/<name>/<slug>/guides/<slug>301 or 308
/page.php?id=<id>/resources/<slug>301 or 308
Replace each placeholder with the site's real matching value. Keep the old and new identifiers aligned in the mapping.

If content is deliberately removed or merged, record that decision too. A removed page with no relevant replacement should return 404 or 410 on the new site rather than redirect to an irrelevant page. When several old pages genuinely become one consolidated page, redirect them to that consolidated resource.

  1. Prepare and test the new site

    Configure the CMS, content, TLS certificates for HTTPS, analytics and server capacity. Verify the old and new sites in Search Console and make sure the verification file, meta tag or other verification method will still work after launch. Review manual actions and URL removals on a newly acquired domain before moving to it.

    If staging uses a blanket robots.txt block or noindex rules, keep a launch list of every directive that must be removed. Test representative pages from every template, the redirect rules, navigation, resources and canonical annotations before the switch. Google recommends moving a small or medium site all at once; a large site can move in sections so problems are easier to isolate.

During the move

Activate direct server-side permanent redirects and make every signal on the new site point to the new canonical URLs. Then test old and new URLs immediately, including host and protocol variants.

  1. Turn on 301 or 308 redirects without chains

    Implement the mapping with server-side 301 or 308 permanent redirects. Each old URL should redirect directly to its final new URL, one hop deep. Do not route an old address through an intermediate URL and then another rule. Google recommends avoiding chains because they add latency and not every user agent handles long chains reliably.

    Use client-side redirects only as a last resort when server-side redirects are not technically possible. Test the response's status and location, and confirm the final page returns 200 with the expected content. The redirect checker can inspect the response path for an individual URL.

  2. Update canonicals and hreflang

    Every new indexable page should have a self-referencing rel="canonical" using its new URL. Remove any staging canonical that points elsewhere. If the site has language or regional alternatives, update every hreflang annotation to the corresponding new URLs and retain reciprocal references between the alternatives.

  3. Open crawling and publish the new sitemap

    Remove temporary robots.txt blocks and noindex rules from pages intended for search. Check both the robots meta tag and the HTTP response where rules may be set. Publish an XML sitemap containing the new canonical URLs, not the redirected old addresses. Update internal links, navigation, breadcrumbs and resource references to those same final URLs.

  4. Check launch responses and server load

    Test each redirect pattern and representative exact mappings. Look for incorrect destinations, loops, unexpected 404 or 5xx responses, leftover noindex directives and canonicals that still use old URLs. Google's guidance notes that crawling can temporarily increase after a migration, so the new server must have enough capacity for both normal traffic and redirected crawler requests.

After the move

After the redirects work, submit the domain change where applicable, submit the new sitemap and monitor old and new URLs until indexing and traffic shift to the new site. Do not treat launch day as the end of the migration.

  1. Use Change of Address for a domain move

    In Google Search Console, open the old domain-level property and use the Change of Address tool after the move and redirects are in place. You must own both properties with the same Google account. Submit requests for all verified variants of the old domain that are moving, including relevant subdomains and www/non-www variants.

    Do not use the tool for an HTTP-to-HTTPS-only move, path changes within the same domain, or a switch between www and non-www on that domain. Those moves use redirects, canonicals and sitemaps without Change of Address. The tool also does not apply to a hosting move with no URL change.

  2. Submit sitemaps and update links

    Submit the new XML sitemap in Search Console. Google says the old sitemap can then be removed because the new sitemap will be used going forward. Update your own internal links immediately, and ask sites linking to important old URLs to update them where practical. Also update profiles and advertising destinations that still send visitors through a redirect.

  3. Monitor indexing, errors and traffic

    Use the Search Console Page indexing report guide to review indexed and not-indexed URLs on both properties. Old-site indexing should decline as new URLs are discovered and indexed, but the transition happens per URL. Check the Performance report for new URLs gaining impressions and clicks, and inspect server logs for crawler activity and unexpected errors.

    Investigate chains, loops and invalid destinations with the guide to fixing a Search Console redirect error. Old URLs appearing under Page with redirect can be expected when their redirects are intentional; read what the Page with redirect status means before trying to remove them from that report. Warnings about redirected URLs in an old sitemap are also expected during the transition.

  4. Keep the redirects in place

    Google's site-move guide says to keep redirects for as long as possible, generally at least one year, and suggests considering indefinite redirects for users. Its Change of Address help separately requires maintaining them for at least 180 days and longer if Google Search still sends traffic to them. Keeping the old domain and redirects avoids breaking old links while signals and visits move.

How long do rankings take to recover?

Google gives no fixed ranking-recovery deadline: temporary fluctuation is normal, and the move is processed URL by URL. For a medium-sized site, Google says it can take a few weeks or more for new URLs to gradually replace old ones in search; larger sites can take longer.

Discovery and processing speed depend largely on the number of URLs and server speed. Googlebot needs to visit the old and new URLs, and there is no fixed crawl frequency. Submitting a sitemap can help discovery, but neither a sitemap nor Change of Address guarantees a ranking outcome or a completion date.

Judge progress through the Page indexing and Performance reports rather than expecting every URL to change at once. If old URLs remain indexed where equivalent new pages exist, check that the redirects work, canonical tags agree and the new pages are crawlable. Google's guidance says permanent redirects do not cause a loss of PageRank, but that is not a promise that rankings will never fluctuate during a significant site change.

What MrKeyword does not do

MrKeyword does not move websites, change DNS or server settings, edit a CMS, implement redirects or submit Change of Address requests. The site owner or developer must make and verify those changes.

MrKeyword's Site Audit crawls a site to surface redirects and broken links so you can review the technical results before and after the move. It supports the checklist; it does not replace the URL inventory, Search Console's own reports, response testing or a developer's launch checks. You can also run the free site audit for a crawl-led review.

For the wider technical launch review, use the technical SEO checklist alongside this migration-specific plan. Neither checklist can guarantee indexing or rankings.

Questions and answers

Website migration SEO checklist questions

Should I use 301 or 302 for a migration?

Use a 301 or 308 permanent redirect for a lasting domain, URL or HTTPS migration. A 302 or 307 is for a temporary change when the original URL will return. Google recommends server-side permanent redirects for site moves.

How long should redirects stay in place?

Google's site-move guide says generally at least one year and suggests considering indefinite redirects for users. The Change of Address documentation says at least 180 days, and longer if Google Search still sends traffic to the old URLs.

Will I lose rankings after changing domain?

Google says rankings may fluctuate temporarily while it recrawls and reindexes the site. It gives no fixed recovery guarantee. Permanent redirects do not cause a loss of PageRank, but processing takes place URL by URL.

Do I use Change of Address when switching to HTTPS?

No. Use direct permanent redirects, self-referencing canonicals, updated internal links and a new sitemap. Google's Change of Address tool is for moving from one domain or subdomain to another, not an HTTPS-only move.

Can I redirect every old page to the new home page?

Do not redirect unrelated old pages to one irrelevant destination. Map each URL to its closest relevant replacement. For removed content with no replacement, return 404 or 410 instead.

About this article

Written by the MrKeyword team, who build an SEO workspace on first-party Search Console and Bing data. Outside facts link to their original source below. We update this page when the product or the sources change.

Sources

  1. How to move a site with URL changes — Google Search Central, on URL mapping, permanent redirects, canonicals, sitemaps, monitoring and migration timing
  2. Change of Address tool — Google Search Console Help, on eligibility, ownership, domain-level moves, signals and redirect retention
Keep reading

More on technical SEO, plus the feature and free tool for the same job. All technical SEO guides →

Check the redirects after the move.

Use Site Audit to review redirect and broken-link findings, then confirm indexing in Search Console. Free plan for one website, no card; paid plans from $10 a month.