Website Migration SEO Checklist: Google’s Site Move Rules for 2026

Key takeaways
- Use permanent server-side redirects (301 or 308) from every old URL to its closest new equivalent, directly to the final address.
- Keep redirects for as long as possible, and generally at least a year.
- The Search Console Change of Address tool is only for domain or subdomain moves, not for HTTP to HTTPS, www changes or path changes. Google updated its guidance on 17 June 2026 to cover every verified subdomain variant.
- Expect a few weeks (or more) for small and medium sites to settle, and temporary ranking swings are normal.
- Most migration disasters come from the same few mistakes: a leftover
noindex, a staging robots.txt, redirects to the home page and missing sitemaps.

What counts as a site move?
Google treats it as a site move whenever URLs change: a new domain, a move from HTTP to HTTPS, a new CMS with different paths, a subdomain consolidation or a structural redesign that renames pages. A pure visual redesign that keeps every URL the same is not a move, though it still needs care. Use this table to pick the right tools.
| What is changing | Redirects | Change of Address tool |
|---|---|---|
| New domain | Yes, from every old URL to its new equivalent | Yes, for every verified variant of the old domain |
| Subdomain to another subdomain | Yes | Yes |
| HTTP to HTTPS | Yes | No |
| www to non-www (same domain) | Yes | No |
| URL paths change (same domain) | Yes | No |
| Redesign with identical URLs | Not needed | No |
Phase 1: Before you build
- Benchmark the current site. Export top pages, impressions, clicks and conversions from Search Console and your analytics. You will need these to judge the move later.
- Collect every old URL. Use your sitemaps, analytics, server logs and CMS, and remember images, videos, scripts and stylesheets that other sites or pages link to. For a simple domain-wide move with a wildcard redirect you can skip this.
- Decide what happens to each URL. Keep, merge, or retire. Retired content should return a real 404 or 410, not a redirect to the home page.
- Verify both sites in Search Console, including all variants (www, non-www, HTTP and HTTPS).
- Check the new site’s server capacity. Google may crawl more after a move.
Phase 2: Build the redirect map
This is the heart of the migration. A simple spreadsheet is enough:
old_url,new_url,status
https://old.example.com/services/web-design.html,https://example.com/services/web-design/,301
https://old.example.com/blog/post-1,https://example.com/blog/post-1/,301
https://old.example.com/old-offer,,410
Google’s rules for redirects:
- Use server-side permanent redirects, such as 301 or 308. A 302 is temporary and is not the right choice for a move.
- No chains. Redirect straight to the final destination. Googlebot can follow up to 10 hops, but Google recommends keeping chains to about 3 at most and always under 5.
- Do not send everything to the home page. Redirect each page to the most relevant new page.
- Keep them for as long as possible, generally at least one year.
Phase 3: Prepare the new site
- Copy over content, images and downloads, and keep the same CMS where possible to limit changes.
- Update canonical tags, hreflang and internal links to the new URLs. Use absolute URLs in canonicals and give each page a self-referencing canonical.
- Prepare the new robots.txt and plan when any staging
noindexorDisallowrules come off. - Build a new XML sitemap that lists only the new, canonical URLs.
- Configure HTTPS and certificates if the move includes HTTPS.
- Test everything on staging, with the staging site hidden from search engines (use password protection, not only robots.txt).
Phase 4: Launch day
- Choose a low-traffic time, and have a developer on hand.
- Remove staging blocks:
noindextags,X-Robots-Tagheaders and anyDisallow: /in robots.txt. - Switch on the redirects and test a sample of every URL type. This one-liner shows the final destination and the number of hops:
curl -sIL -o /dev/null -w "%{http_code} %{url_effective} hops:%{num_redirects}\n" https://old.example.com/services/web-design.html
- Submit the new sitemap in Search Console and remove the old one.
- For a domain or subdomain move, use Change of Address for the old site. Google’s guidance says to submit it for every verified variant of the old domain, including subdomains and www or non-www versions, even unused ones. It is not for HTTP to HTTPS, www to non-www on the same domain, or path changes.
- Test key pages with URL Inspection and check the live pages work, forms submit and analytics fires.
Phase 5: Monitor for the next weeks
Googlebot has to visit every old and new URL at least once, and there is no fixed schedule. Google says small and medium sites may need a few weeks or more for most pages to move, while larger sites take longer. Temporary ranking fluctuations are normal.
| Where to look | What good looks like |
|---|---|
| Search Console Sitemaps report | Indexed pages falling on the old sitemap and rising on the new one |
| Page indexing report | No unexpected spike in errors, soft 404s or “blocked” pages |
| Performance report | New URLs start getting impressions and clicks |
| Server logs | Googlebot hits mostly new URLs and redirects, with few 404s |
| Analytics | Old-site traffic falls as new-site traffic rises, with conversions holding |
Canonical tags during a migration
Google’s canonicalization guide says redirects are the strongest signal, rel="canonical" is a strong signal and sitemaps are a weak one. They work best together. Avoid these mistakes during a move:
- pointing a canonical at a URL that redirects or returns an error
- leaving canonicals pointing to the old domain
- using relative URLs in canonical tags
- listing HTTP URLs in sitemaps after an HTTPS move
- using
noindexto steer which duplicate Google chooses
Google also added clarifications on 10 July 2026 about how long canonical re-evaluation can take, so do not judge the result after a few days.
The mistakes that cause most migration problems
- A leftover
noindexor staging robots.txt on the live site. - Redirects to pages that do not exist on the new site.
- Chains and loops created by stacking old and new rules.
- Everything redirected to the home page, which Google may treat as a soft 404.
- Old sitemap left in place or the new one never submitted.
- Not enough server capacity for the extra crawling.
- Dropping pages that earn traffic because nobody checked the benchmark.
A printable checklist
- Benchmark traffic, rankings and conversions.
- List every old URL and map each to a new one (or a 410).
- Verify all Search Console variants of both sites.
- Staging site is private and fully tested.
- Canonicals, hreflang, internal links and sitemap all point to the new URLs.
- Staging
noindexand robots rules removed on launch. - 301 or 308 redirects live, tested, with no chains.
- Change of Address submitted (domain and subdomain moves only).
- New sitemap submitted, old one removed.
- Monitoring plan for at least four to six weeks.
- Redirects kept for a year or longer.
For a redesign that keeps your URLs, start with our website redesign SEO checklist, and read our guide to URL structure before you decide to change paths. Planning a migration and want a second pair of eyes? Our CMS and website team handles moves end to end, and you can talk to us before you start.
Frequently asked questions
How long does it take Google to process a site move?
Google says small and medium sites may take a few weeks or more for most pages to move, and larger sites take longer. Temporary ranking fluctuations during that period are normal.
Should I use 301 or 302 redirects for a migration?
Use permanent server-side redirects such as 301 or 308. A 302 is temporary and is not the right choice for a move.
How long should I keep my redirects?
For as long as possible, and generally at least one year, according to Google’s site move guidance.
When should I use the Change of Address tool?
Only when you change domains or move between subdomains. Do not use it for HTTP to HTTPS, www to non-www on the same domain, or path changes. For domain moves, submit it for every verified variant of the old domain.
Can I redirect all my old pages to the new home page?
Avoid it. Google’s guidance is not to redirect many pages to an irrelevant page such as the new home page. Map each old page to its closest equivalent.
What is the most common migration mistake?
Leaving staging rules in place: a noindex tag or a Disallow rule in robots.txt on the live site. Check both before and after launch.