A Google site migration can take more than four months, but Google does not set four months as a standard timeline or maximum. For a URL-changing move, Google says most pages on a small or medium-sized site may move in Search within a few weeks; larger sites take longer. The process depends chiefly on the number of URLs and server speed, and Google considers the move complete only after Googlebot has visited every URL on both the old and new sites at least once.
How long does a site move take?
Google’s guidance is a general expectation, not a promise for every URL: most pages on a small or medium-sized site may move in Search within a few weeks, while larger sites can take longer. Google gives no fixed crawl schedule or exact maximum, so a transition lasting more than four months is possible, but it is not Google’s prescribed timeline. See Google’s Site Moves and Migrations guidance.
As an Amazon Associate I earn from qualifying purchases.
Google processes URLs individually. It says a move is complete only when Googlebot has visited every URL on the old and new sites at least once. That definition is about crawling the URLs, not a guarantee that rankings or traffic will immediately return to previous levels.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
First identify what kind of move you made
Google distinguishes moves that change URLs from hosting changes that keep the same visible URLs. Their timelines and troubleshooting differ, so do not apply the URL-migration guidance automatically to an infrastructure-only change.
#1 Best Overall
| Move type | What changes | Google’s relevant guidance |
|---|---|---|
| URL-changing move | For example, HTTP to HTTPS, a domain change, merging hostnames, or changing URL paths. | Google processes the old and new URLs; small and medium sites may see most pages move in a few weeks, with larger sites taking longer. Source. |
| Hosting-only move | The hosting infrastructure changes but visible URLs stay the same. | Crawl rate may dip temporarily after launch and then rise over the following days if Googlebot can access the new infrastructure without serious problems. Source. |
What can stretch the transition?
- URL count and site scale: Google crawls URLs individually, so larger sites require more processing.
- Server speed and capacity: Google identifies server speed as a factor. After a move, Google may crawl the new site more heavily because it must request redirected old URLs as well as crawl new-site URLs. A server that cannot handle the load can complicate the transition.
- How easily Google can discover the new URLs: A submitted sitemap can help Google find them, but it does not create a fixed crawl timetable.
- Migration structure: A correct old-to-new URL map and direct redirects help Google understand the move. Large sites may be moved in sections for easier monitoring and correction; Google generally recommends that small and medium sites move all at once.
Prepare and monitor a URL-changing migration
- Map and test destinations before launch. Match each old URL to its relevant new destination. Avoid redirecting unrelated pages to the homepage. Test the new site before moving traffic.
- Set up permanent redirects. Use server-side permanent redirects where possible. Google advises keeping them for as long as possible, generally at least one year, so signals can transfer as URLs are recrawled. See Google’s migration troubleshooting guidance.
- Update the new site’s references. Change canonical annotations and internal links to point to the new URLs. Update the sitemap so it lists the new URLs, then submit it.
- Verify and watch both properties. Verify the old and new sites in Search Console. After launch, monitor indexing, crawl errors, and traffic for both.
- Choose a rollout that fits the site. For a large or risky move, consider migrating an initial section first so you can detect and correct problems before moving the rest. For small and medium sites, Google’s general guidance is to move all at once.
What to check if traffic or indexing is slow
A temporary visibility fluctuation can occur while Google recrawls and reindexes URLs. It does not, by itself, prove the migration failed. If a decline is not recovering, investigate technical causes rather than assuming the only solution is to wait. Google’s Debug Google Search Traffic Drops page advises using the migration troubleshooting guidance when a post-move decline persists.
- Check the new site for leftover
noindexdirectives or robots.txt rules that block crawling. - Confirm redirects lead to the intended, working destination—not a wrong or nonexistent URL.
- Review Search Console for crawl errors and indexing problems on both old and new properties.
- Check that the server has enough capacity and that Googlebot can access the new infrastructure.
- Make sure the submitted sitemap lists the new URLs rather than the old ones.
Google’s traffic-drop guidance also says a medium-sized site may take a few weeks for Google to notice a change, larger sites may take longer, and some effects of site changes can take several months. Those statements describe Google’s systems and the possible effects of changes generally; they are not a specific migration deadline or a promise that every move will settle within four months.
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.
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 errors
