A domain migration SEO checklist should protect three things: rankings, traffic and leads. Before you move, audit every important URL, map old pages to new ones, test 301 redirects, keep content signals intact, update tracking and monitor errors after launch. Skip those steps and Google may treat your shiny new domain like a stranger.
Why moving to a new domain can go wrong
A domain change is not just a branding job. To Google, it is a site move. You are asking search engines to understand that everything they knew about oldsite.co.uk now belongs to newsite.co.uk. If you make that clear, the move can settle down properly. If you make it messy, rankings can drop, enquiries can dry up and everyone starts blaming the new website.
The biggest problems usually come from simple mistakes. Old URLs get sent to the homepage. Redirects are missing. Important pages are rewritten for no good reason. The staging site gets left on noindex. Analytics stops tracking halfway through. Lovely stuff.
Google has its own site move guidance, and the core message is boring but important: use permanent redirects, keep things consistent and monitor the move properly. If you want the painful version of what happens when redirects are botched, read this guide on how redirects work and why getting them wrong kills your rankings.
Crawl and audit the current site before touching anything
Before you move domains, you need a full record of what currently exists. Not what you think exists. What actually exists. That means crawling the site, exporting URLs from Google Search Console, checking analytics data and finding pages with backlinks.
Use a crawler such as Screaming Frog, Sitebulb or a similar tool to collect every indexable URL. Then compare that against Search Console performance data, GA4 landing page data and any backlink data you have. You are looking for pages that bring traffic, earn links, rank for useful keywords or support conversions.
This is where many businesses mess it up. They only migrate the pages visible in the menu and forget old blog posts, landing pages, PDF files, location pages and product URLs. Those forgotten pages might be carrying the authority that helps the whole site rank.
If you are already seeing crawl errors, duplicate pages or indexing problems before the move, fix them first. A proper technical SEO review can save you from carrying old rubbish into the new domain and wondering why things still smell funny afterwards.
Build a proper URL inventory
Your URL inventory is the control sheet for the whole migration. It should list every old URL, what it does, whether it has value and where it will go on the new domain. This is not glamorous work, but neither is fixing a traffic crash at 11pm because someone redirected 300 pages to the homepage.
A useful URL inventory should include enough information to make decisions, not just a big list of links. Keep it clean and practical. If a page gets organic traffic, has backlinks or supports sales, it needs careful handling.
| Field | Why it matters |
|---|---|
| Old URL | The exact address search engines and users already know |
| New URL | The destination on the new domain |
| Status code | Whether the page is live, redirected, missing or removed |
| Organic traffic | Helps identify pages you cannot afford to lose |
| Backlinks | Shows which URLs pass authority into the site |
| Main keyword or topic | Helps match old pages to the most relevant new page |
| Action | Keep, redirect, merge, rewrite or remove |
Do not let a web designer, developer or enthusiastic nephew guess this stuff. Guessing is how good rankings end up in the bin.
Decide what should move, merge or die
A domain migration is a chance to clean up the site, but do not get carried away. You should not move every ancient page just because it exists, and you should not delete useful pages because they look old.
Start by putting pages into sensible groups. Pages with traffic, backlinks, conversions or strong rankings should usually be kept or redirected to a very close replacement. Similar pages can sometimes be merged if they compete with each other. Thin, useless pages with no traffic and no links can be removed, but only if you are sure they are not doing quiet background work.
If a page no longer exists on the new site, redirect it to the most relevant alternative. A discontinued service page should go to the nearest service page, not the homepage. An old blog post about a specific topic should go to a closely related article if one exists.
If there is genuinely no useful replacement, a 410 or 404 may be fine. That is better than lying to Google with a pointless redirect. Search engines are clever enough to notice when every old URL magically becomes the homepage. They are not impressed.
Map redirects page by page
Redirect mapping is the bit that protects most of your SEO value. Every important URL on the old domain should have a clear destination on the new domain. In most cases, that means a 301 redirect from the old page to the matching new page.
Do not use temporary 302 redirects for a permanent domain move. Do not create redirect chains where old page goes to middle page and then finally to new page. Do not redirect everything to the homepage because it was quicker. Quick is often expensive.
Your redirect map should be tested before launch. Check that old HTTP and HTTPS versions behave correctly. Check www and non-www versions. Check trailing slash differences if your site uses them. The goal is boring consistency.
A good redirect map looks like this:
| Old URL | Correct new URL | Redirect type |
|---|---|---|
https://oldsite.co.uk/services/ |
https://newsite.co.uk/services/ |
301 |
https://oldsite.co.uk/roof-repairs-crewe/ |
https://newsite.co.uk/roof-repairs-crewe/ |
301 |
https://oldsite.co.uk/blog/old-guide/ |
https://newsite.co.uk/blog/updated-guide/ |
301 |
If this spreadsheet makes you want to throw your laptop into a canal, fair enough. But it still needs doing.
Test the new domain before launch
The new domain needs to be checked before anyone pushes the button. A staging site hidden from Google is fine. A live site accidentally blocked from Google is not fine. That one happens more often than it should, and yes, it is as annoying as it sounds.
Check the basics first. The new site should load over HTTPS. Important pages should return 200 status codes. Canonical tags should point to the new domain, not the old domain or staging domain. Internal links should use the new URLs. XML sitemaps should only contain final live URLs.
Pay close attention to robots.txt and meta robots tags. Developers often block staging sites with Disallow: / or noindex, which is sensible during development. The problem is when that setting goes live on launch day. Then Google politely stays away, and your phone stops ringing.
Also test mobile rendering. Google uses mobile-first indexing, so if key content, links or navigation are missing on mobile, you have a real problem. The desktop version looking pretty does not rescue a broken mobile experience.
Keep your on-page SEO signals intact
A domain migration is not the ideal time to rewrite the entire website, change every title tag, delete half the content and restructure the navigation because someone found a new WordPress theme. Too many changes at once make it much harder to work out what caused any ranking movement.
Keep the important on-page signals as stable as possible. That means page titles, headings, core body content, internal links, image alt text, schema markup and page purpose should stay broadly consistent unless you have a clear reason to change them.
This does not mean copying rubbish forever. If a page is weak, improve it. But do not turn a high-performing service page into a vague brand essay because it sounds nicer in a meeting. Google ranked the old page for reasons. Preserve the useful bits.
Internal links matter too. If your old site linked heavily to key service pages from blogs, menus or location pages, rebuild those paths on the new domain. Internal links help search engines understand priority and context. They also help actual humans find the thing they came for, which is still fairly important.
Prepare Search Console, analytics and sitemaps
Before launch, make sure tracking and reporting are ready. You need to know what happens after the move, not guess based on vibes. Vibes are useless when leads drop and everyone wants answers.
Verify both the old and new domains in Google Search Console. If you use domain properties, even better, because they cover protocol and subdomain variations. Set up or confirm GA4, conversion tracking, call tracking and any form tracking you rely on.
Once the new domain is live and redirects are working, submit the new XML sitemap in Search Console. For a proper domain change, use Google Search Console’s Change of Address tool. It helps Google understand that the old domain has moved to the new one.
You should also keep the old domain verified. Do not cancel it, let it expire or remove hosting immediately. The old domain needs to keep serving redirects for a long time. I would usually keep them in place for at least a year, and often much longer if the site has strong backlinks or old URLs still get traffic.
Launch without creating a bin fire
Launch day should be calm because the hard work has already been done. If everyone is discovering problems for the first time on launch morning, that is not a launch plan. That is a group project with consequences.
Use a clear launch checklist and make one person responsible for final sign-off. Not five people. Not whoever is available. One person who understands the SEO risks and can say, “No, we are not launching with noindex still switched on.”
Run these checks as soon as the new domain goes live:
- Confirm the new domain loads correctly on HTTP, HTTPS, www and non-www versions.
- Test a sample of old URLs and make sure they 301 to the correct new URLs.
- Crawl the new domain and check for broken internal links.
- Confirm canonical tags point to the final new URLs.
- Check
robots.txtand meta robots tags for accidental blocking. - Submit the new XML sitemap in Search Console.
- Test forms, phone tracking, checkout flows and enquiry buttons.
- Check analytics and conversions are recording properly.
Do not celebrate until those checks are done. Then you can have the biscuit.
Monitor the first 30 days properly
Some ranking movement after a domain migration is normal. Panic is not useful, but neither is ignoring obvious problems. You need to watch the right data closely for the first few weeks.
Start with Search Console. Look for crawl errors, indexing drops, soft 404s, redirect problems and pages that are no longer being discovered. Check the Performance report, but remember it may take time for data to settle. Compare landing pages, not just total clicks.
Crawl the site again after launch. Then crawl it weekly for the first month if the site is important to your business. You are looking for broken links, redirect chains, canonical mistakes, duplicate pages and URLs returning the wrong status code.
| When | What to check |
|---|---|
| Launch day | Redirects, indexability, forms, analytics and sitemap submission |
| First week | Crawl errors, 404s, redirect chains and important rankings |
| Weeks two to four | Organic traffic trends, indexed pages and Search Console warnings |
| After 30 days | Remaining errors, traffic recovery and pages needing extra work |
If traffic drops and stays down, do not just wait. Find the cause. Hope is not an SEO strategy, despite what some agencies seem to sell.
Local business extras you cannot ignore
If you run a local business, your domain migration is not limited to the website. Google Business Profile, local citations, directory listings and tracking links may all reference the old domain. If those are not updated, your local SEO signals become messier than they need to be.
Update your website link in Google Business Profile as soon as the new domain is live and tested. Check key directories such as Yell, Bing Places, Apple Business Connect, Facebook, trade directories and industry bodies. Your name, address, phone number and website should be consistent.
If you use UTM tracking on your Google Business Profile link, rebuild it properly for the new domain. Do not just paste in whatever URL is closest. Local businesses often rely heavily on map pack traffic, calls and direction requests, so this stuff matters.
For businesses in Cheshire and across the UK that depend on local leads, Google Business Profile optimisation should be part of the migration plan, not an afterthought scribbled on a Post-it note.
Do not change everything at the same time
A domain migration already gives Google plenty to process. If you also change the CMS, redesign every template, rewrite every page, remove half the services, change the URL structure and switch hosting on the same day, you have made diagnosis much harder.
Sometimes multiple changes are unavoidable. A rebrand may require a new domain and a new site. An old CMS may be too knackered to keep. Fine. But document what changed and test each part properly.
Where possible, keep the migration clean. Move the domain first, keep the structure stable and let search engines process the change. Then make larger content or design changes once the move has settled. This staged approach is less exciting, which is usually a good sign.
The worst migrations happen when the SEO bit is treated as a final polish. Someone builds the site, launches it, then asks why traffic disappeared. SEO needs to be in the planning stage, not invited in afterwards like a plumber asked to fix a flood with a tea towel.
A plain-English domain migration SEO checklist
If you only take one thing from this, take the checklist. Save it before anyone starts moving domains, redesigning pages or fiddling with DNS settings after three coffees.
- Crawl the old domain and export every indexable URL.
- Pull organic landing page data from GA4 and Google Search Console.
- Identify pages with backlinks, rankings, leads or sales value.
- Decide which pages to keep, merge, remove or redirect.
- Create a page-by-page 301 redirect map.
- Build the new domain with clean internal links and correct canonicals.
- Check
robots.txt, meta robots tags and staging settings before launch. - Test redirects before and immediately after launch.
- Verify old and new domains in Google Search Console.
- Submit the new XML sitemap after launch.
- Use the Change of Address tool for a full domain move.
- Monitor crawl errors, traffic, rankings and conversions for at least 30 days.
That is the sensible version. Not magic. Not secret. Just the boring stuff done properly, which is where most SEO wins are hiding.
When you should get help
If the website brings in leads, sales or bookings, do not treat a domain migration as a casual admin job. A small mistake can cost more than getting help in the first place. That is especially true for established businesses with years of content, links and local visibility behind them.
You should get help if you have lots of URLs, strong existing rankings, multiple locations, e-commerce pages, international versions, old redirects, messy tracking or a history of previous site moves. You should also get help if nobody involved can clearly explain what a canonical tag, redirect chain or 404 response means. No shame in that. Better to ask than accidentally bury the site.
For WordPress sites, migration problems often hide in plugins, themes, permalink settings and cached redirects. If that sounds familiar, proper WordPress SEO support can stop the technical bits turning into a slow-motion headache.
A new domain can be the right move. Just do it with a plan, not crossed fingers.
Frequently Asked Questions
Will migrating to a new domain hurt my SEO? It can cause temporary ranking movement, but it should not wreck your SEO if the move is planned properly. The main risks are missing redirects, changed content, blocked crawling, broken internal links and poor tracking. A clean migration tells Google where everything has moved and protects as much existing value as possible.
How long does Google take to process a domain migration? There is no fixed timescale. Small sites may settle within a few weeks, while larger or more complex sites can take several months. Google needs to crawl the old URLs, follow redirects, process the new URLs and update its index. Keeping redirects live and monitoring Search Console helps the process.
Should I keep the old domain after moving to a new one? Yes. Keep the old domain active and serving 301 redirects for at least a year, and often longer. If the old domain has backlinks, old customers using bookmarks or branded searches still happening, those redirects continue to matter. Letting the old domain expire is asking for trouble.
Can I redesign my website during a domain migration? You can, but it increases the risk. If rankings drop, it becomes harder to know whether the domain change, design changes, content changes or technical changes caused the problem. If possible, keep URLs, content and structure stable during the move, then make bigger improvements after things settle.
Do I need to use the Change of Address tool in Google Search Console? Yes, if you are moving the whole site from one domain to another. The Change of Address tool helps Google understand that the old domain has moved to the new domain. It does not replace 301 redirects, sitemaps or proper testing. It is an extra signal, not a magic button.
What is the biggest domain migration SEO mistake? The biggest mistake is redirecting old URLs to irrelevant pages, especially the homepage. It wastes relevance, confuses users and weakens the signal Google needs to understand the move. Every valuable old URL should redirect to the closest matching new URL wherever possible.
