You can reduce avoidable traffic loss during a website migration, but you cannot guarantee that rankings or visits will stay unchanged while Google recrawls and reindexes the site. Start by identifying whether public URLs will change: a domain, protocol, or path move needs URL mapping and redirects, while a hosting or CDN change with the same URLs mainly requires a carefully monitored infrastructure and DNS transition.
Choose the right migration workflow
The work depends on what changes for visitors and crawlers. A redesign or CMS replacement may also change URLs, content, or internal links, so list each planned change rather than treating every migration as the same kind of move.
As an Amazon Associate I earn from qualifying purchases.
| Move type | Main work | Change of Address? |
|---|---|---|
| Domain or subdomain change | Map old URLs to relevant new URLs, redirect them, update canonicals and sitemaps, then monitor both sites. | Yes, for eligible verified properties, after the move and redirects are in place. |
| HTTP to HTTPS | Redirect affected URLs to HTTPS and update URL signals, including canonicals and the sitemap. | No. |
| Path changes on the same domain | Redirect changed paths to their new destinations and update internal links and the sitemap. | No. |
| www to non-www, or the reverse | Choose the preferred host and use consistent canonical signals and redirects. | No. |
| Hosting or CDN change with unchanged visible URLs | Prepare and test the new infrastructure, change DNS, monitor both hosts, and retire the old service only after the new one is confirmed to work. | No. |
Google distinguishes URL-changing moves from hosting changes that leave URLs unchanged. Its separate guides cover moves with URL changes and moves without URL changes. The Change of Address tool is for eligible domain or subdomain changes—not HTTPS-only moves, path changes, www/non-www changes, or hosting-only transitions.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteBuild a baseline and inventory before changing anything
Record what is changing: domain, protocol, URL paths, CMS, host, CDN, content, design, or some combination. Save the current URL inventory and a baseline of organic traffic and indexing so you can compare the new site with its previous state. For a URL change, identify important URLs using existing sitemaps, Search Console, analytics, server logs, and known inbound links.
#1 Best Overall
- Note the pages that bring organic visits, conversions, or valuable inbound links.
- Capture current indexing and query performance in Search Console, alongside relevant analytics data.
- Keep a record of the old URL inventory and the planned destination for each URL.
When project constraints allow, avoid combining a URL restructuring with a redesign or major content overhaul. Google notes that multiple simultaneous changes can mean it must relearn and reassess individual pages, making it harder to isolate migration problems.
Prepare and test the destination before launch
Build the new site in a test environment and check representative pages and critical templates before changing DNS or enabling redirects. Confirm that important content and assets are present, pages return the intended status codes, forms work, and internal links lead to the right destinations.
- Check images, downloads, forms, and other important page functions.
- Review canonical tags, robots directives, and any migration-only
noindexrules or robots blocks. - Check that the new server has enough capacity for visitors and increased crawling.
- Confirm that important pages are accessible to crawlers and that their intended canonical URLs are correct.
For URL-changing moves, make a URL map from old pages to the closest relevant new pages. A consolidated page can be a suitable destination if it genuinely covers the old page’s subject. Do not send many unrelated URLs to the homepage as a catch-all: Google warns that this can confuse users and may cause those URLs to be treated as soft 404s.
Free tools Windows power users keep installed
One-click scans. No signup required.
Implement direct, permanent redirects
When URLs change, use permanent server-side redirects—such as HTTP 301 or 308—where technically feasible. Ask your server administrator or hosting provider which implementation fits your stack, such as server configuration or CMS rules. Google’s guidance on redirects and Google Search says that “301 and other permanent redirects don’t cause a loss in PageRank.” That statement concerns PageRank signals; it is not a guarantee that rankings or traffic will never fluctuate.
Rank #3
- For each old URL, redirect directly to its final, most relevant destination.
- Check that each destination exists, returns the intended response, is crawlable, and has the correct canonical.
- Test redirects in bulk as well as by checking representative high-value URLs.
- Fix redirect loops, broken destinations, and avoidable chains before launch.
Googlebot may follow up to ten redirect hops, but Google recommends directing users and crawlers straight to the final URL. If a chain cannot be avoided, keep it short: Google advises ideally no more than three hops and fewer than five, since chains add latency and some clients may not handle long chains reliably.
Choose a lower-traffic period when practical and make sure the destination can handle the additional load. Google recommends moving small and medium-sized sites at once; larger sites may move section by section so teams can detect and address problems incrementally. This is a planning decision, not a promise of faster indexing.
Launch, update signals, and notify Google when eligible
For a URL-changing migration, activate the redirects, update the destination pages’ canonical tags to their new URLs, and remove temporary blocks that would prevent crawling. Submit a sitemap containing the new URLs. Update internal links and other links you control—such as paid campaigns and important business profiles—so they point directly to the destination rather than relying on redirects.
For an eligible domain or subdomain move, verify both properties in Search Console and submit Change of Address for the old site after the redirects are live. Do not submit it for the other move types listed in the table. For a hosting-only change with unchanged URLs, follow the infrastructure workflow: prepare and test the new host, change DNS, monitor service on both hosts, and keep the old host available until the new one is confirmed to be functioning.
Best Value
Monitor both properties and diagnose unexpected drops
Keep watching the old and new sites in Search Console, analytics, and server or access logs. Review sitemap processing, indexed URL trends, search queries, crawl errors, missing pages, and server errors. After an infrastructure change, Googlebot’s crawl rate can dip briefly and then rise over the next few days. After a URL move, crawling of the new site may increase, so monitor server capacity as well as indexing.
If traffic or indexing falls unexpectedly, investigate the specific failure rather than assuming every fluctuation is a redirect problem:
- Old URLs: Confirm they return the intended redirect and land on the matching page, not a 404 or unrelated homepage.
- Redirect paths: Remove avoidable chains, loops, and incorrect destinations.
- New URLs: Check that important pages are crawlable and are not blocked by migration-only
noindexdirectives or robots rules. - Canonical and sitemap signals: Verify they identify the new URLs consistently.
- Infrastructure: Look for server errors, downtime, or capacity problems affecting visitors or crawlers.
- Links and measurement: Check internal links, analytics, Search Console properties, paid campaigns, and important external profiles for stale destinations or configuration errors.
Keep redirects in place and set realistic expectations
Do not use a fixed recovery date as a migration target. Google says most pages on a medium-sized site may take a few weeks or more to move, while larger sites can take longer. Processing depends in part on the number of URLs and server speed, and there is no guaranteed crawl schedule or recovery date. Ranking changes can occur while Google recrawls and reindexes pages.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsGoogle says a move is not complete from its perspective until Googlebot has visited every URL on both the old and new sites at least once. Keep redirects for as long as possible; Google’s migration documentation generally recommends at least one year. Its Change of Address help page separately says to retain redirects for at least 180 days and longer while Google Search still sends traffic. The conservative approach is to keep redirects for at least a year and longer when feasible. Retain control of the old domain as well, to reduce the risk of it being acquired by someone else.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
