Moving a website to a new domain is a technical and marketing project, not just a DNS change. Pages may move to new URLs, redirects need to be mapped, search tools need to be updated and tracking must continue working. A carefully planned migration reduces avoidable disruption, although no checklist can guarantee that rankings and traffic will remain identical during processing.
The safest approach is to inventory the current site, preserve important content and URLs where possible, map every changed URL to a relevant destination, test the new site before launch and monitor the transition after publishing.
TL;DR
- Crawl the old site and record important pages, traffic, links and conversions before making changes.
- Map old URLs to corresponding new URLs and use relevant permanent redirects for permanent moves.
- Update canonicals, internal links, sitemap, analytics and verification settings.
- Check for staging blocks, redirect errors and missing pages after launch.
- Monitor the move over time and investigate specific problems instead of reacting to every daily fluctuation.
Before the domain move
1. Record your baseline
Crawl the old site and export URLs, titles, status codes, canonical tags and internal links. Use Search Console to identify pages earning impressions and clicks, and analytics to identify landing pages that contribute to leads or sales. Record known valuable backlinks where possible. This inventory gives you a basis for deciding what should be preserved.
2. Decide what is changing
Are you changing only the domain, or also the URL structure, design, content and platform? Changing several major elements at once makes the move harder to diagnose. If the old structure works, preserve paths where practical. If you are changing paths, treat those changes as part of the migration plan and map the affected URLs.
3. Prepare an old-to-new URL map
For every important old URL, record its intended new destination. Redirect each old page to the closest relevant new page. Avoid sending the whole old site to the new homepage: visitors expect the content they clicked, and unrelated redirects may be treated as soft 404s.
4. Check the new site before launch
Make sure important pages return successful responses, the content renders correctly, and canonicals point to the new domain. Review robots.txt and meta robots directives so staging restrictions do not accidentally block the production site. Test forms, phone links and any conversion tracking.
Preparing a redesign or domain move?
The Super Shoppe builds custom business websites and supports SEO planning. Explore our website service to discuss the build, and view SEO & GEO services if you need help preserving discoverability while the website changes.
During development and launch
Implement the redirects
Use server-side permanent redirects where possible for permanent moves. Test the mapping instead of assuming the redirect configuration works. Check protocol changes, hostname variants and page-level paths. A redirect should reach the final destination with no loops or unnecessary intermediate hops.
Update canonical tags and internal links
The new site's canonical tags should refer to the new preferred URLs. Internal navigation, breadcrumbs, contextual links and sitemap entries should not keep pointing to the old domain. Update links in email templates, social profiles, directory listings and paid campaigns that you control.
Publish the new sitemap
Generate a sitemap containing the new canonical URLs intended for indexing. Submit it in Search Console for the new property. The sitemap helps Google discover the new URLs, but it does not replace redirects or guarantee indexing.
Keep measurement working
Verify analytics tags, key events and consent behaviour on the new domain. If form submissions, calls or checkout steps are business-critical, test them end to end. Record the migration date and annotate major releases so post-launch performance can be interpreted in context.
The post-launch checklist
- Confirm that the new homepage and main service pages load securely and return the expected status codes.
- Test the old-to-new redirect map, including important deep URLs—not only the old homepage.
- Confirm that the production site is not blocked by staging robots rules or accidental
noindexdirectives. - Inspect representative URLs with Search Console and review the sitemap report for errors.
- Crawl the new site and find internal links still pointing at old URLs or redirect chains.
- Submit test enquiries and verify analytics records the correct actions without duplicate events.
- Monitor indexing, clicks, impressions, errors and enquiries over time.
Expect some fluctuation as search engines recrawl URLs and process the move. A temporary change in visibility is not enough, by itself, to determine that the migration has failed. Investigate patterns: are key pages missing, redirects wrong, canonicals inconsistent or the new site inaccessible?
Migration mistakes to avoid
Launching before the URL map is ready. This makes it easy to lose old service pages or redirect them to the wrong destination.
Leaving staging restrictions on production. The site may work for people but be excluded from crawling or indexing due to inherited configuration.
Redirecting every old URL to the homepage. This discards page context and can confuse users.
Forgetting forms and analytics. Organic traffic may appear stable while the main enquiry path silently fails.
Removing the old domain too soon. Keep control of the old domain and redirects for as long as needed to maintain the migration and support people following old links. Do not let domain renewal lapse accidentally.
How The Super Shoppe can help
The Super Shoppe builds custom websites with clear structure and customer journeys. Explore our website service for redesign and migration planning, or view SEO & GEO services for technical checks, indexability and ongoing visibility measurement.