Domain change
Signals not transferred; Change of Address needed
Changing your domainFree SEO tool · Interactive template
Every task that keeps rankings through a site migration, from planning to the months after launch. Pick what you are changing, tick tasks off as you go, and download the list for your team.
Choose every type that applies. The checklist keeps the tasks for those types; choose none to see everything.
0 / 54 tasks done
The CSV opens in Google Sheets or Excel, with phase, task, details, guide link and status.
The checklist
Tasks follow the order you will need them. Each links to the guide that explains it, or to the Google documentation it is based on.
Weeks before launch · 9
Domain, protocol, URL paths, templates, CMS, hosting: each change brings its own risks, and most migrations combine several. Tick every type that applies above.
Google suggests timing the move for a period of lower traffic. Avoid your peak season and leave the team time to fix problems in the days after launch.
Small and medium sites can move all URLs at once. Google says larger sites can move one section at a time, starting with a section that changes less often.
A hosting or CDN move is only low-risk if every URL, status code and directive stays identical. Any URL change turns it into a full migration.
Lower DNS TTLs ahead of the switch, keep the old host serving while DNS propagates, and agree when you would roll back.
Every URL you keep is one less redirect to get right. Check the new CMS can reproduce the old paths before accepting its defaults.
If the domain was used before, look for manual actions or security issues in its Search Console data before you move onto it.
Where both sites cover the same topic, pick one destination and fold the best content into it rather than keeping near-duplicates.
Google recommends verifying both the old and new sites, including www / non-www and HTTP / HTTPS variants, and making sure verification keeps working after the move.
Before launch · 9
It's your record of every URL with its status, title, canonical and indexability, and the baseline you compare against after launch.
Crawlens: audit the crawl and keep it in the project; Compare needs two audited crawls.
Clicks, impressions and visits per URL tell you which pages the redirect map must get exactly right, and give you a before/after comparison.
Crawlens: connect Search Console and Google Analytics 4 to see them next to each crawled URL.
A crawl misses orphan pages. Add URLs from sitemaps, Search Console, analytics, server logs and backlink tools, plus images, videos and PDFs.
Google suggests keeping this list so you can ask the most important sites to update their links after the move.
One row per old URL. Never send everything to the homepage: Google says that can confuse users and might be treated as a soft 404.
Pattern rules are fine for the long tail, but the pages that earn clicks and links deserve a manual check of their destination.
If nothing on the new site matches, a clean 404 or 410 is better than a redirect to an unrelated page.
Keep language and country intact in every pair, and keep translated content, prices and availability where they matter.
Sample representative pages of each template so you can prove the new host serves the same thing.
Before launch, on staging · 14
Authentication keeps previews out of search and stops staging rules from being copied to production by accident.
Same scope and same rendering mode, so the two crawls compare like for like.
Crawlens doesn't log in to sites: allow its IP address, and turn off Respect robots.txt if staging blocks crawlers.
Check meta robots and X-Robots-Tag on every template, and that canonicals never point at a staging hostname.
Google recommends that each new URL has a rel=canonical pointing at itself, not at the old URL.
Every internal link to an old URL adds a redirect hop for users and crawlers. Fix them in templates, menus and content.
Only if the site has language or country versions. Every page in a set must link to all the others on their new URLs.
Compare each template with the benchmark: status, indexability, title, description, H1, canonical, word count, links, structured data and images.
If the new front end renders in the browser, compare raw and rendered HTML for content, links and directives.
Staging has no real-user data yet, so run Lighthouse tests on key templates and compare them with the old site's.
Run every row, including unusual slugs, uppercase, trailing slashes, parameters and non-HTML files, before the rules go live.
Cover www and non-www, and check that images, scripts, fonts and forms all load over HTTPS.
Compare the benchmark sample: redirects, robots.txt, X-Robots-Tag, caching headers, and that crawlers are not blocked by bot protection.
Google says it temporarily crawls a moved site more heavily. Rate limits or a small server can turn that into 5xx errors.
Write the new site's robots.txt deliberately rather than copying staging's, and check it still allows CSS and JavaScript.
Launch day · 8
Google recommends server-side permanent redirects. Don’t use 302s for a permanent move; JavaScript redirects are a last resort.
Point existing redirects straight at the new final URLs so old chains do not grow. Google advises keeping chains short.
The most common launch-day mistake. Check the live robots.txt and the meta robots of a page from every template.
Every reference to an old URL tells Google something different from your redirects.
List only new, indexable URLs. Google expects the old sitemap’s indexed count to fall towards zero as the new one rises.
Google's tool is for moves from one domain or subdomain to another. It is not needed for HTTP to HTTPS or www changes, and a move into a path on an existing host may not qualify.
Homepage, top landing pages and one page per template: status 200, right content, right canonical, indexable.
Crawlens: paste the URLs in URL list mode for a quick check.
Verification files and meta tags often disappear with a new host or CMS. Losing verification means losing your monitoring.
First weeks after launch · 9
Every old URL should answer with a single 301 or 308 to its mapped destination, and that destination should return 200 and be indexable.
Crawlens: paste the old URLs in URL list mode. The audit flags redirect chains, loops, temporary redirects and 4xx pages.
A redirect to the wrong page passes a status check but loses the ranking. Compare final URLs with the approved map.
Pages that earned clicks or visits before the move are where mistakes cost most.
Crawlens flags pages with search traffic that return errors or are not indexable, and landing pages with visits that return errors.
Look for new issues, URLs that disappeared, status code changes, pages that became non-indexable and changed titles.
Crawlens: Compare shows new and fixed issues plus URL changes between two crawls.
Migrations often break days later, when a cache clears or someone edits a redirect rule. Crawl daily or weekly and get alerted when things get worse.
Crawlens: Schedule & alerts runs while the app is open (it can stay in the system tray); email alerts need SMTP settings.
Check both properties. Old URLs should drop out of the index as new ones come in; look for spikes in 404s and server errors.
Search Console's Crawl Stats report shows host status, response codes and response times as Google crawls the new setup.
Redirects pass the signals, but direct links are faster and do not depend on the old host. Update your own social profiles too.
Google says rankings can fluctuate for a few weeks or more on a medium-sized site. A drop concentrated in one group points to a specific problem.
Months after launch · 5
Google recommends keeping them as long as possible, generally at least a year, so signals transfer to the new URLs.
Letting it lapse breaks every link that still points to it, and someone else can buy it.
Redirect rules get lost in later releases. Keep the old-URL list and re-crawl it whenever routing changes.
Wait until logs show no more requests to the old servers and post-launch checks pass.
They are the only record of what the site looked like before, and you will need them for the next migration or a traffic investigation.
Guides by migration type
The checklist covers the shared process. These guides go deeper on what goes wrong in each type.
Signals not transferred; Change of Address needed
Changing your domainMissing redirects and mixed content
HTTP to HTTPS migrationMissing or wrong redirects
Redirect mappingLost titles, content, links or structured data
CMS migration SEOServer errors and blocked crawlers
Hosting migration checklistOverlapping pages mapped to irrelevant destinations
Merging two websitesIncomplete URL mapping or old-host signals
Subdomain to subfolderLost regional signals and broken hreflang pairs
ccTLD SEO migrationWant the reasoning behind the checklist? Read the site migration SEO guide, and if traffic has already dropped, the traffic drop after migration guide.
Good to know
Source for Google’s recommendations: site moves with URL changes (Google Search Central).
A benchmark of the old site, a page-to-page redirect map, a test of the new site before launch, permanent redirects and updated internal links, canonicals, hreflang and sitemaps at launch, then a crawl of every old URL and ongoing monitoring after launch.
Google recommends keeping redirects for as long as possible, generally at least one year, so it can transfer signals to the new URLs. Links on other sites keep relying on them for much longer.
Google suggests timing the move for a period of lower traffic. Large sites can move one section at a time; small and medium sites can move every URL at once.
Google says rankings can fluctuate temporarily, and for a medium-sized site it can take a few weeks or more for the new URLs to replace the old ones. Larger sites take longer. A deep or lasting drop usually points to a technical mistake.
Only when moving from one domain or subdomain to another. Google says it is not needed for HTTP to HTTPS moves or switching between www and non-www; redirects, internal links and sitemaps do that work.
Crawl the old site as a benchmark, test staging, crawl the old URL list after launch and compare crawls side by side. Crawlens flags redirect chains, loops, temporary redirects and pages with traffic that now fail.
Download free for Windows