Domain Migration SEO: Map URLs Before You Move

A domain migration can preserve much of a site's search value, but it cannot make the transition invisible. Google's current guidance still warns that rankings may fluctuate while its systems recrawl and reindex changed URLs; for a small or medium-sized site, most pages can take several weeks to move, while larger sites may take longer.

The durable advice is to map each old URL to a deliberate outcome, launch direct permanent redirects and keep the old domain operational. Two details deserve particular attention now: Google recommends retaining redirects for at least a year, and its Change of Address tool is for domain or subdomain moves—not a simple HTTP-to-HTTPS conversion.

Why a homepage redirect is not a migration plan

The unit of a domain migration is the individual URL, not the brand or homepage. Product pages, articles, category pages, images and downloadable files may all hold links, receive search visits or appear independently in an index. Sending every old address to the new homepage discards that context and can leave visitors far from the information they expected.

Google's current site-move guidance recommends mapping old URLs to corresponding destinations, updating internal links and annotations, submitting a new sitemap, and avoiding irrelevant bulk redirects that may be treated as soft 404s. It also says permanent redirects do not inherently lose PageRank, although visibility can still fluctuate while the move is processed.

Build the mapping before changing DNS or enabling redirects. Each old address should have one of three recorded outcomes:

An equivalent new page, receiving a direct permanent redirect.
A genuinely consolidated replacement that satisfies the old page's purpose.
No replacement, in which case the retired address should return an appropriate 404 or 410 response instead of being forced to an unrelated page.

Use analytics, Search Console data, server logs, the content management system and existing sitemaps to find URLs. Include pages with external links even when their recent traffic is low: the migration must account for discoverability and referrals, not only last month's visits.

Keep the move technically narrow

A domain change already asks search engines to reassess every affected address. Combining it with a new CMS, rewritten content, a redesigned information architecture and different URL paths makes failures harder to isolate. Unless those changes are inseparable from the business decision, preserve the content and structure first, then redesign after indexing and traffic have stabilized.

Prepare the destination behind restricted access or another controlled test arrangement. Confirm that templates, forms, images, scripts and downloads work; that production robots rules permit crawling; and that temporary noindex directives have been removed before launch. Every new indexable page should reference its own final URL in its canonical annotation, while hreflang annotations, structured data, internal navigation and sitemap entries should use the new domain.

Capacity is also part of SEO risk management. During a move, requests for old URLs are redirected to the new infrastructure while Google also crawls the new addresses, creating additional work for the destination server. Load testing and monitoring response times therefore belong in the launch checklist, particularly for large catalogues.

Use direct permanent redirects

For a lasting domain change, configure server-side 301 or 308 responses from each old URL to its final counterpart. Google's redirect documentation classifies both codes as permanent and says its indexing pipeline uses a permanent redirect as a signal that the destination should be canonical; temporary 302, 303 and 307 responses do not send the same canonicalization signal.

Avoid chains such as old domain to an intermediate URL and then to the final address. Point the original URL straight to the destination, including when earlier migrations have already left redirects in place. This reduces latency for users and removes extra failure points for crawlers.

Test more than a sample of home and category pages. An automated check should verify the complete mapping, response status, final destination, absence of loops, and whether the destination returns a successful response. Separately crawl the new site to find internal links that still pass through the old domain or through redirects.

Use Change of Address only for the move it supports

After redirects are live, owners moving from one domain or subdomain to another can submit Change of Address from the old Search Console property. Both the source and destination must be verified under the same Google account, and separate old variants or subdomains may require their own handling.

The official Change of Address instructions explicitly exclude HTTP-to-HTTPS changes, moves between www and non-www on the same domain, partial path changes and hosting changes that leave public URLs unchanged. The tool operates for 180 days, but that window should not be mistaken for a deadline to remove redirects: Google separately recommends keeping migration redirects for at least a year, and retaining useful redirects longer can still help people following old links.

Submit a sitemap containing the new canonical URLs and preserve ownership verification for both properties. A sitemap helps discovery, but it does not replace redirects, correct canonicals or working destination pages. Likewise, Change of Address supplements the technical move; it does not repair a bad URL map.

Launch in an order that exposes mistakes early

Freeze the approved inventory of old URLs and their destinations or retirement status.
Crawl and test the new site while access remains controlled.
Remove temporary indexing blocks and confirm canonical, hreflang and internal-link targets.
Enable direct permanent redirects and run automated checks across the mapping.
Verify the old and new Search Console properties, submit Change of Address when eligible, and submit the new sitemap.
Update high-value external links, advertising destinations, profiles and owned campaign links.
Monitor search, crawl and server evidence on both domains before making further structural changes.

For a small or medium-sized site, moving all URLs together usually gives users a more consistent experience and helps search systems recognize the change. A large site may justify a section-by-section rollout so the team can detect capacity, redirect or indexing failures before they affect the entire catalogue.

Measure transfer, not just total traffic

A successful migration produces a directional pattern: crawls, indexed pages, impressions and clicks decline for old URLs while corresponding activity appears on the new domain. Total organic traffic alone can hide a failed section, especially when a strong homepage or seasonal demand offsets losses elsewhere.

Compare old and new URL groups by template, language, market and business importance. Watch for unexpected 404 responses, redirect loops, soft 404 classifications, server errors, blocked resources and pages for which Google selects an old or unrelated canonical. Server logs are especially useful because they show whether crawlers continue requesting old addresses and whether those requests receive the intended response.

Do not declare completion on a fixed calendar date. The stronger operational test is that important old URLs consistently resolve to valid counterparts, the new pages are indexed and earning impressions, crawler activity on the old site has materially receded, and no major section shows an unexplained gap. Keep the old domain registered and its redirects functioning after that point: the redirect layer remains the bridge for bookmarks, external links and delayed recrawls.

Moving Domains Can Shake Rankings—Map Every URL, Not Just the Homepage