During a website migration, crawl frequency does not necessarily keep increasing, and changes do not follow a fixed timeline. For Googlebot, a change in hosting infrastructure often brings a brief drop in crawl frequency after migration begins, followed by a gradual recovery over the next few days. It may even rise above its pre-migration level. This pattern is not guaranteed for every type of migration; recovery also depends on whether Googlebot can access the new environment without problems or slowdowns. The explanation below focuses on Google’s guidance, so the same behavior cannot be assumed for other search engines.
Why might crawl frequency drop and then rise after a hosting change?
Google explains that many signals affect crawl frequency, and these signals change when hosting changes. A brief drop after moving to a new server is therefore not, on its own, evidence that the migration has failed.
Recovery has an important condition: Googlebot must be able to access the new infrastructure without serious problems or slowdowns. Under those conditions, it will crawl as quickly as needed. “Recovery over the next few days” describes a common pattern, not a deadline that every website must meet. Likewise, a potentially higher crawl frequency does not mean an increase is certain.
A recovery within days does not mean the URL migration is complete
If the migration involves URL changes, distinguish between changes in crawl frequency and progress in processing the old and new URLs. Google must recrawl and index the pages, processing the migration URL by URL. Google needs to visit every URL on both the old and new sites at least once.
Google’s documentation gives a timeframe of several weeks for migrating most pages on small to medium-sized websites. On medium-sized websites, new URLs may also take several weeks or longer to gradually replace old ones; larger websites generally take longer still. These timeframes describe URL migration progress, not how long a drop in crawl frequency will last. Processing speed depends primarily on the number of URLs and server speed. Rankings and search visibility may fluctuate temporarily during this period, but ranking changes do not directly indicate increases or decreases in crawling.
Monitor both traffic shifts and accessibility
To assess whether a migration is going smoothly, do not rely solely on crawl volume at a single point in time. Also check the following:
- When changing hosting providers, review the logs on both the old and new servers. As the DNS settings take effect and traffic shifts, traffic to the old server should decline while traffic to the new server increases accordingly.
- Check for serious access problems or slowdowns on the new infrastructure. Do not simply treat a drop in crawl volume accompanied by these problems as a normal fluctuation.
- If URLs are changing, use tools such as Search Console to track user and crawler activity on both the old and new sites, and monitor indexing progress.
For example, a drop in crawl volume followed by a recovery after changing hosts matches the common pattern described in the documentation. But any access problems occurring at the same time should not be dismissed on the grounds that “fluctuations are normal during migration.” Focus on whether changes are accompanied by problems, rather than expecting the same number of crawls every day.
Crawl frequency during website migrations: perspectives from across the web
How does migrating during a low-traffic period help with crawling?
If your website has seasonal or regular weekly traffic lows, consider migrating during one of those quieter periods. This may reduce the number of users affected by migration problems and leave more server resources available for Googlebot to crawl. However, this is a scheduling recommendation, not a guarantee that crawl frequency will increase.
Can submitting a sitemap help Google complete the migration faster?
Submitting a sitemap can speed up Google's discovery of URLs, but it does not guarantee that the entire migration will be completed within a particular timeframe. If URLs are changing, you can also use the Sitemaps report in Search Console to monitor how many submitted URLs have been indexed. Discovering a URL and indexing it are still separate stages.
When can you shut down the old hosting infrastructure after changing hosting providers?
Google recommends checking the old provider's server logs and waiting until traffic to that provider drops to zero before shutting down the old hosting infrastructure. This recommendation applies to changes in hosting providers; do not assume that all traffic has shifted simply because the new host has started receiving traffic.
References
- 網站遷移與移轉作業 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How does migrating during a low-traffic period help with crawling?; Can submitting a sitemap help Google complete the migration faster?
- 變更網站代管與搜尋引擎最佳化 (SEO) | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: When can you shut down the old hosting infrastructure after changing hosting providers?



