How long does it really take for Google to reindex after a site relaunch?

Why does Google keep old URLs cached after a relaunch?

When you change your domain or redesign your URL structure, Google does not instantly switch to the new addresses. The engine temporarily maintains old URLs in its index, even if they properly redirect to the new ones.

This behavior can be explained by how Googlebot crawls and processes redirects. The bot must first discover the redirect, validate the new target URL, and then update its index. This process is not synchronous — each URL follows its own recrawl schedule based on its historic update frequency and its importance in the link graph.

What does this mean for SEO during the transition?

During this phase, you will observe a coexistence of old and new URLs in the SERPs. Users may click on an old URL, be redirected, and land on the new page without any issues from an experience perspective.

However, on the metrics side, it complicates tracking. Rankings may fluctuate because Google is testing both versions, comparing signals (CTR, dwell time, backlinks), and gradually consolidating toward the new URL. Organic traffic may temporarily decline, not because you've lost rankings, but because Google is still distributing impressions between the old and new.

How long does this transition period really last?

Mueller does not provide a specific figure — and this is intentional. The duration depends on your usual crawl frequency, the volume of affected pages, and the quality of your redirect plan.

For sites that are crawled daily with a good crawl budget, the switch may take a few weeks. For less frequently visited sites or those with thousands of pages, it can stretch over several months. Google guarantees no SLA — you can only optimize the conditions to speed up the process.

• Old URLs remain temporarily visible in results even with well-configured 301s
• The transition duration varies based on site size, crawl budget, and crawl history
• No guaranteed SLA from Google — you can only facilitate the recrawl, not force it
• Metrics are skewed during migration: rankings and traffic fluctuate without reflecting a true loss of ranking
• Signal consolidation (backlinks, engagement) happens gradually between the old and new URLs

Does this statement align with what we observe on the ground?

Absolutely. Every SEO who has managed a site migration recognizes this pattern: the floating period post-relaunch where the old and new coexist in the index. Mueller is simply officially confirming a behavior that practitioners have been noticing for years.

What is lacking here is the granularity of timing. Saying "some time" gives no actionable benchmark. On a small site of 500 well-crawled pages, you may see the majority of URLs switch in 2-3 weeks. On a large e-commerce site with 100k products and limited crawl budget, it may drag on for 6 months. [To verify]: Google does not publish any data on the statistical distribution of these delays according to site profiles.

What are the risks if this transition is not managed well?

The first risk is client panic. If you have not indicated that a temporary drop in traffic is normal, you will have to handle anxious calls a week after the relaunch. Anticipating and communicating this timeline is part of the job.

Technically, the real danger is breaking redirects too soon. Some decide to delete old URLs or cut off the old domain before Google has finished consolidating. The result: you lose untransferred signals, and Google may interpret this as content disappearing rather than being migrated. Patience — as long as old URLs are redirecting, you are not losing anything.

In what cases does this rule not apply completely?

Mueller talks about "reindexing", but it is important to distinguish between crawling, indexing, and ranking. A URL can be crawled quickly (a few days if you push via Search Console) but take longer to fully recover its ranking because backlinks to the old address have not yet been recrawled and consolidated.

Another case: sites with very low authority or insufficient crawl budget. If Google was only visiting your old site once a month, do not expect the migration to miraculously speed things up. The speed of transition directly depends on your ability to attract Googlebot — and a simple statement will not change that.

What should you do before and during a relaunch?

Before you even switch, map all your URLs: old to new, 1:1 when possible. Prepare a comprehensive file of 301 redirects — zero approximation. Forgetting a strategic page can cost you months of lost traffic.

During the migration, force the recrawl via Search Console. Submit new URLs through the inspection tool, update your XML sitemap with the new addresses, and ping Google to accelerate discovery. The faster Googlebot finds the new pages, the quicker it consolidates.

How to effectively monitor the transition and avoid critical errors?

Set up a weekly tracking on a sample of representative URLs: top 50 pages by traffic, main categories, conversion pages. Track the evolution of status (old URL visible vs new URL indexed) in the SERPs via a rank tracking tool that shows the actual displayed URL.

Monitor the server logs to ensure Googlebot is crawling the new URLs properly and following the redirects. If you see it looping on the old ones without ever recrawling the new, you have a discoverability problem — add internal links, fresh backlinks, or submit manually.

What mistakes should you absolutely avoid to prevent prolonging the floating period?

Never create redirect chains. If old-URL-A redirects to URL-B which redirects to URL-C, Google will take a long time to consolidate — or even abandon. One redirect, one hop, that's it.

Another classic mistake: changing canonical tags too quickly on old URLs before Google has finished the transfer. Allow old URLs to redirect properly in 301 without any weird self-referential canonical. And above all, do not block old URLs in robots.txt — Googlebot must be able to crawl them to discover the redirects.

• Thoroughly map all URLs before migration (old → new, 1:1)
• Set up direct 301 redirects, without chains or loops
• Submit new URLs via Search Console and updated XML sitemap
• Weekly monitor a sample of strategic URLs (index status, positions, traffic)
• Analyze server logs to ensure Googlebot is properly following redirects
• Never block old URLs in robots.txt during the transition