ChecklistLab

Website Launch

Domain Migration Checklist

A domain migration is not just a DNS change. It can break organic traffic, email delivery, analytics, canonical tags, SSL, and every hard-coded link that points at the old domain. Use this checklist to control the move before, during, and after cutover.

Use when: You are changing a primary domain, moving from a temporary domain, or consolidating brands under a new domain.

Best for: Founders, agencies, developers, and SEO teams who need a migration plan that covers more than redirects.

Start with: A full URL inventory and redirect map. Do not touch DNS until old-to-new URL ownership is clear.

Then review: SEO Site Launch Checklist before requesting indexing on the new domain.

Copy workflow

Confirm migration scope

Define exactly what is moving so the migration does not expand quietly mid-launch.

  • Document the old domain, new domain, staging domain, and any subdomains involved.
  • List every system that references the domain: CMS, analytics, ads, email, CRM, forms, payment tools, CDN, and social profiles.
  • Decide whether the URL structure will stay the same or change at the same time as the domain.
  • Freeze non-essential content changes until the migration has stabilized.
  • Assign a single launch owner who can approve cutover and rollback decisions.

DNS, SSL, and hosting

DNS and certificate mistakes can make a clean migration look like a site outage.

  • Lower DNS TTL before launch so changes propagate faster during cutover.
  • Confirm the new domain points to the correct hosting environment before public launch.
  • Install and test SSL on the new domain, including www and non-www variants.
  • Choose the canonical host version and redirect all variants to it.
  • Keep the old hosting environment active long enough to serve redirects reliably.

Redirect map

Redirects protect users and search equity. They should be mapped before anything goes live.

  • Export a full list of indexable old URLs from the CMS, sitemap, analytics, and crawl tools.
  • Map every valuable old URL to the closest matching new URL, not just the homepage.
  • Use 301 redirects for permanent moves and avoid redirect chains.
  • Test high-value redirects manually before DNS cutover.
  • Keep a copy of the redirect map with owner, status, and test result columns.

Search signals

Search engines need consistent signals that the new domain is the canonical destination.

  • Update canonical tags to point to the new domain on every indexable page.
  • Update XML sitemap URLs to the new domain and submit in Search Console.
  • Verify the new domain property in Search Console before launch day.
  • Update internal links so they point directly to new URLs, not through redirects.
  • Check robots.txt and meta robots tags to make sure the new domain is not blocked.

Email and third-party systems

Domain changes can break more than the website. Email, ads, forms, and integrations often need separate updates.

  • Confirm SPF, DKIM, and DMARC records if email will send from the new domain.
  • Update form notification recipients and reply-to domains where needed.
  • Update Google Ads, Meta, LinkedIn, and other ad destination URLs.
  • Update social profile links, directory listings, and important partner links.
  • Update analytics filters, referral exclusions, and conversion destinations.

Cutover monitoring

A migration is not complete when the new domain loads. Monitor the first week closely.

  • Crawl the new domain after launch and flag 404s, redirect chains, blocked pages, and canonical mismatches.
  • Check Search Console coverage, indexing, sitemap processing, and manual action status.
  • Compare analytics traffic, conversions, and form submissions against the pre-migration baseline.
  • Watch server logs or hosting analytics for spikes in 404s from old URLs.
  • Keep rollback instructions documented, even if you do not expect to use them.
DOMAIN MIGRATION CHECKLIST

SCOPE
[ ] Document old and new domains
[ ] List subdomains and systems affected
[ ] Freeze non-essential content changes
[ ] Assign launch owner

DNS AND SSL
[ ] Lower DNS TTL
[ ] Point new domain to correct hosting
[ ] Install SSL for www and non-www
[ ] Choose canonical host

REDIRECTS
[ ] Export old URL inventory
[ ] Map each old URL to closest new URL
[ ] Avoid redirect chains
[ ] Test priority redirects

SEARCH SIGNALS
[ ] Update canonical tags
[ ] Update XML sitemap
[ ] Verify new Search Console property
[ ] Update internal links

POST-LAUNCH
[ ] Crawl new domain
[ ] Monitor Search Console
[ ] Compare traffic and conversions
[ ] Track 404s and rollback needs

Next step

Use this next

After the domain migration plan is ready, run the SEO launch checks that protect crawlability and indexing.

SEO & Content

Checklist

SEO Site Launch Checklist

Confirm indexability, sitemap, canonical, metadata, and crawl readiness before launch.

Pair it with the Post-Launch Monitoring Checklist for the first week after cutover.

Domain Migration Checklist FAQ

How long should old-domain redirects stay active?

Keep them active indefinitely for important URLs. At minimum, maintain redirects long enough for users, partners, and search engines to update references. Removing old redirects too early creates avoidable 404s and traffic loss.

Should you change domain and URL structure at the same time?

Avoid it unless there is a strong reason. Changing both at once makes diagnosis harder because traffic drops can come from domain signals, redirects, information architecture, or content changes. If possible, keep URL paths stable during the domain migration.

What is the biggest domain migration mistake?

The biggest mistake is treating migration as a launch-day DNS task instead of a search, tracking, email, and redirect project. The redirect map and canonical signals should be ready before cutover.