Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A Google site migration can take more than four months, but Google does not say that every migration will—or set four months as a completion target. For a URL-changing move, Google’s general guidance is that most pages on a small or medium-sized site may move in Search within a few weeks; larger sites take longer. The time depends in part on how many URLs Google must process and how quickly its systems can crawl them.
What Google means by a site migration
Google’s migration timeline applies to moves that change URLs. Examples include switching from HTTP to HTTPS, changing a domain, merging hostnames, or changing URL paths. Google processes these moves URL by URL, so the transition is not necessarily complete when the new site launches or when its homepage appears in Search.
Google says a move is complete only after Googlebot has visited every URL on both the old and new sites at least once. Its guide does not give a fixed crawl schedule, an exact maximum duration, or a four-month deadline. Its “few weeks” guidance for most pages on small and medium-sized sites is a general expectation, not a guarantee for every URL.
A hosting change that keeps the visible URLs the same is a different scenario. Google says crawl rate can dip temporarily just after a hosting move, then rise over the following days if Googlebot can access the new infrastructure without serious problems. That short-term crawl pattern should not be confused with the URL-by-URL processing involved in a URL-changing move. See Google’s site-move guidance for URL changes and its separate guidance on changing hosting without changing URLs.
#1 Best Overall
Why a migration can take months
Google has to process URLs individually
A migration involves more than discovering the new homepage. Google needs to recrawl old URLs, follow their redirects, discover the corresponding new URLs, and process those pages. There are no fixed crawl frequencies that guarantee when a particular URL will be revisited.
Large sites have more URLs to move
Google identifies URL count as a factor: larger sites take longer because more pages need to be discovered and processed. Submitting a sitemap containing the new URLs can help Google find them, but it does not create a fixed completion date.
Server speed and capacity affect crawling
Google also says processing time depends on server speed. During a move, Google may crawl the new site more heavily than usual: it can request the new pages directly while also requesting old URLs and following their redirects. A server that cannot handle that demand reliably can impede crawling.
Recommended Free Tools
Visibility changes do not follow one universal schedule
Google warns that Search visibility can fluctuate temporarily while it recrawls and reindexes a site. Its separate guidance on debugging Search traffic drops says a medium-sized website may take a few weeks for Google to notice a change, while larger sites can take longer; some effects of site changes can take several months. Those are general explanations of Google’s systems and site changes—not a promise that a migration will finish within a particular period.
How to prepare for a URL-changing move
- Build and test the new site before launch. Map each old URL to its relevant new destination. Avoid sending unrelated old pages to the homepage, which does not preserve a meaningful page-to-page move.
- Use direct permanent redirects where possible. Google advises keeping redirects in place as long as possible, generally at least one year, so it can recrawl old URLs and transfer signals to the new ones.
- Update references on the new site. Change canonical annotations and internal links to point to the new URLs. Create and submit a sitemap listing the new URLs.
- Verify both sites in Search Console. Keep access to the old and new properties so you can monitor indexing, crawl errors, and traffic during the transition.
- Choose a rollout that fits the site’s scale and risk. Google generally recommends moving small and medium-sized sites all at once. For a large or risky migration, moving an initial section first can make it easier to monitor results and correct problems before proceeding with the rest.
Google’s migration troubleshooting guidance covers common issues to check during the move.
What to check if traffic or indexing is slow
Do not assume every post-move traffic change is a migration failure, but do not treat a continuing decline as something that will automatically resolve with time. Check the technical setup and whether Google can crawl the intended pages.
- Look for blocked pages: remove any unintended
noindexdirectives or robots.txt rules that prevent crawling. - Check redirects: confirm old URLs redirect to the correct, working new destinations—not to unrelated, missing, or broken pages.
- Review crawl errors and server capacity: investigate errors in Search Console and verify the new server can handle requests to both new pages and redirected old URLs.
- Inspect the sitemap: make sure the submitted sitemap lists the new URLs rather than lingering old addresses.
- Compare old and new properties: monitor indexing, crawl errors, and traffic in Search Console to help identify where the transition is getting stuck.
If a traffic decline is not recovering, use Google’s traffic-drop guidance and its migration troubleshooting steps to investigate rather than relying on a general waiting period.
Free tools Windows power users keep installed
One-click scans. No signup required.
What timeline should site owners plan for?
For a small or medium-sized URL-changing move, plan around Google’s general expectation that most pages may move in Search within a few weeks, while allowing for individual URLs to take longer. For a large site, a move can take longer; Google does not publish a universal maximum. A transition lasting more than four months is therefore possible, but the duration alone does not establish whether the migration is healthy. The URL count, crawl access, server performance, and accuracy of redirects all matter.
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.
