Is your site migration stuck in 'pending' status in Search Console? Find out why! ?

What does the 'pending' status actually mean?

Google keeps track of every site address change reported through Search Console. This internal tracking remains active long after the migration has been technically digested by the algorithms. The 'pending' status does not reflect a blockage or slowdown in the migration process.

This is a simple archival mention: Google maintains an archive of the move in its databases without displaying any status of completion. No interface will ever switch this flag to 'completed' or 'done'. It is a peculiarity of the tool, not a performance indicator.

How does Google actually handle a migration?

The engine manages site migrations by gradually re-evaluating the URLs: it crawls the old domain, follows the 301 redirects, indexes the new URLs, and then gradually transfers ranking signals. This process spans several weeks, sometimes several months for large sites.

Declaring a change of address in Search Console speeds up the acknowledgment but does not fundamentally change the process. Google will continue to crawl the old domain for months to check whether the redirects persist. The status displayed in GSC has absolutely no direct link to the actual progress state of this migration on the index side.

What signals indicate a successful migration?

The real indicators are elsewhere: the source of organic traffic, the gradual disappearance of the old URLs from the SERPs, the transfer of ranking positions to the new pages. If Google still heavily displays your old URLs in the search results several months after the migration, it indicates that your redirects are failing or that the crawl budget is insufficient.

Traffic coming from the old domain is a clear alarm signal: this means either some redirects are failing (404 errors, loops, chains of redirects), or Google has not yet fully reindexed your new site. In this case, you need to audit the technical quality of the 301s, check sitemaps, and possibly force a recrawl of the critical URLs.

• The 'pending' status in GSC is a interface artifact, not a technical diagnosis
• A successful migration is measured by the actual transfer of traffic to the new domain
• Clean 301 redirects (1:1, without chains, without loops) are the only guarantee of a smooth migration
• Google may take 3 to 6 months to fully finalize a migration on a medium or large site
• Declaring in Search Console speeds up detection, but does not replace the technical rigor of redirects

Is this statement consistent with field observations?

Absolutely. For years, SEOs have noticed that this 'pending' status persists indefinitely, with no correlation to the actual success of the migration. Google has always been vague about the exact lifecycle of this indicator. This official confirmation puts an end to years of unnecessary concern among practitioners who compulsively monitored this status.

In the field, well-executed migrations (clean 301 redirects, updated sitemap, 1:1 structure) show an almost complete traffic transfer within 4 to 8 weeks, well before the GSC status changes — since it never does. This gap between perception and technical reality generates a lot of unnecessary anxiety among clients and juniors.

What nuances should be added to this statement?

Mueller mentions checking the source of traffic, but remains vague on critical thresholds. [To verify]: at what percentage of residual traffic on the old domain should we start worrying? 5%? 20%? Google provides no figures, whereas this is precisely what SEOs need to diagnose an anomaly.

Another vague point: the distinction between normal residual traffic (Google continues to crawl the old domain as a precaution) and pathological traffic (broken redirects). Without clear metrics, we remain in interpretation. A tool like index coverage reports or server logs becomes essential to make a decision.

In what cases does this rule not apply?

If you have declared multiple successive migrations (failed test, rollback, then new attempt), the 'pending' status can become quite misleading. Google keeps track of all address changes, and the interface may display an old or ambiguous status. In this case, completely ignore GSC and rely solely on traffic metrics and indexing reports.

Partial migrations (subdirectory to subdomain, redesign of only one section) should not use the address change tool, which is designed for complete domain migrations. In these cases, the 'pending' status makes absolutely no sense — and Google does not clarify this enough.

What should you monitor during a site migration?

Forget the 'pending' status in Search Console. Focus on three key metrics: the distribution of organic traffic between the old and new domain (via Google Analytics or your analytics tool), the evolution of the number of indexed URLs on each domain (GSC coverage reports), and the average position of your strategic queries (Google Search Console or position tracking tool).

Set up automatic alerts if traffic on the old domain exceeds a threshold that you deem abnormal (e.g., 10% of total traffic after 8 weeks). Also, watch for 404 or 5xx errors in GSC reports: they often indicate broken or missing redirects.

What critical mistakes to avoid during a migration?

The most common: redirect chains (old URL → intermediary URL → new URL). Google follows these chains, but at the cost of time and signals. Aim for direct 1:1 redirects. Another classic mistake: redirecting all old URLs to the homepage of the new site, instead of mapping each page to its equivalent.

Never declare a change of address in GSC before your redirects are in place and tested. Google will immediately start to recrawl the old domain — if the 301s are not ready, you create confusion in the index. Test at least 20-30 representative URLs with a tool like Screaming Frog or OnCrawl before launching the official declaration.

How to verify that the migration is proceeding correctly?

Export organic traffic data by hostname weekly from your analytics tool. You should see a clear downward trend for the old domain and a symmetrically rising trend for the new one. If both curves stagnate or if the old domain remains dominant after 6-8 weeks, immediately audit your redirects and canonicals.

Analyze your server logs: Googlebot should gradually reduce its activity on the old domain and intensify its crawl of the new one. If Googlebot continues to crawl the old site massively several months after the migration, it means something is blocking the transfer of signals — often improperly configured canonicals or residual internal links pointing to the old domain.

• Map each old URL to its new equivalent before launching the migration
• Implement clean 301 redirects without chains, tested URL by URL
• Declare the change of address in Search Console only after technical validation
• Weekly monitor the distribution of organic traffic between the two domains
• Audit index coverage reports and 404/5xx errors in GSC
• Analyze server logs to check Googlebot's behavior