Why does Google still show the old domain in site: queries after a 301 redirect?

What really happens when a site: query is performed on a redirected domain?

When you type site:olddomain.com into Google, the engine tries to show you what you're explicitly asking for—even if that domain redirects to a new one. This behavior can seem counterintuitive to those expecting to see the new domain immediately appear.

Google maintains a historical connection between the old and new domain, sometimes for several years. This association allows the engine to understand that you may be seeking information about the old site, not necessarily its current destination. This nuance often escapes SEO practitioners who tend to think of redirects as immediate and final transfers.

Does this mean my 301 migration has failed?

No. The display of the old domain in site: results does not indicate a migration issue. Cached pages do accurately show the destination URL—proof that Google understood and processed the redirect correctly.

This behavior is purely related to the interpretation of search intent. Google distinguishes between what you're looking for (the old domain) and where the content actually resides (the new one). This distinction is crucial: you might have a technically perfect migration while still seeing the old domain persist in site: queries.

How long does this historical connection last?

Mueller explicitly mentions several years, without specifying an exact limit. This duration likely depends on multiple factors: the age of the domain, its link history, and the frequency with which users or crawlers still attempt to access it.

In practice, cases have indeed been observed where the old domain remains visible 2 to 4 years after a migration. Google does not seem to have a deterministic algorithm to "clean" this association—it gradually fades as the new domain establishes itself as the canonical reference in the web ecosystem.

• Site queries: can display the old domain for years after a 301 redirect
• Cached pages always show the final destination URL, confirming that the migration is understood
• This persistence does not affect PageRank transfer or the indexing of the new domain
• Google maintains a historical connection to respond to explicit search intent
• No specific timeframe is communicated for the complete disappearance of this association

Is this statement consistent with field observations?

Absolutely. SEO practitioners have been reporting this phenomenon for years without always understanding it. Clients often panic because their old domain "still appears in Google"—when technically, everything is working perfectly.

What Mueller confirms here is that this behavior is intentional, not a bug. Google is not seeking to "clean" these historical traces quickly, which may seem strange for an engine obsessed with freshness and relevance. But it makes sense if you consider that some users are specifically looking for information on the old domain—to verify a migration, audit a history, or simply out of habit.

What nuances should be added to this claim?

Mueller remains deliberately vague on how long this connection can last. "Several years" is a broad range—and likely variable depending on the cases. [To be verified]: no numerical data is provided on the factors that accelerate or slow down this disappearance.

Another point: this statement says nothing about the potential impact in terms of duplicate content or dilution of authority. If Google maintains two distinct entities in its index (old and new domain), how does it handle canonicalization? Mueller does not specify, leaving a gray area regarding the internal mechanisms of signal consolidation.

In what cases could this rule pose a problem?

If your old domain has a toxic history (spam, penalty, questionable content), this persistence could create confusion for users and potentially for the algorithm. Can Google associate negative signals from the old domain with the new one? Nothing in this statement allows for a definitive conclusion.

Second case: complex migrations with multiple cascading redirects. If domain A → domain B → domain C, which version does Google favor in site: queries? [To be verified]: the statement only covers the simple case of a single redirect, not more sophisticated migration architectures.

What should be done practically after a 301 migration?

First, never rely solely on site: queries to validate a migration. They are not a reliable indicator of successful PageRank transfer or correct indexing. Instead, use the Search Console to track organic traffic, impressions, and clicks on the new domain.

Also, check that cached pages correctly point to the new domain, as Mueller specifies. If they still show the old one, that's where you have a real technical problem—uncrawled redirects, blocked robots.txt, or server timeout.

What mistakes should be avoided during a domain migration?

Don’t remove 301 redirects too early based solely on the disappearance of the old domain in site:. Since this connection can last for years, redirects should remain active for at least 12 to 18 months—ideally much longer if the domain has a significant link history.

Another common mistake: panicking when the old domain persists in results and multiplying technical interventions (changing redirects, contradictory canonicals, blocking in robots.txt). These actions can break a migration that was working correctly. Let's be honest: Google is slow but generally consistent—giving it time to consolidate is often the best strategy.

How to effectively monitor a migration to avoid nasty surprises?

Set up a tracking dashboard that aggregates critical KPIs: organic traffic by domain (old vs new), average positions on your strategic queries, crawl rate in Search Console, index coverage. These metrics will tell you if the migration is going well—much more reliably than site: queries.

Also monitor backlinks: how many still point to the old domain, how many have been updated to the new one? A large gap after 6 months may indicate that your partners haven't followed the migration, which dilutes your authority.

• Never use site: queries as the only success indicator of a migration
• Ensure that cached pages display the final destination URL
• Keep 301 redirects active for a minimum of 18 months, ideally 3 years for large sites
• Monitor organic traffic and positions in Search Console, not in generic SERPs
• Regularly audit backlinks to identify those still pointing to the old domain
• Don't intervene technically without a clear reason—stability takes precedence over impatience