Why does an old URL still show up in Google after a redirect?

What actually happens when Google follows a redirect?

When a Googlebot encounters a 301 or 302 redirect, it follows that redirect and indexes the destination page. This page becomes the canonical version in the eyes of the engine. Ranking signals (backlinks, authority, etc.) gradually transfer to this new URL.

However, the old URL does not immediately disappear from the index. It remains technically known to Google, even if it is no longer considered the main version. This is a crucial point that many practitioners overlook during post-migration audits.

Why does the old URL still appear in search results?

Mueller's statement clarifies a specific case: explicit requests like site:oldurl.com. These operators force Google to display what it knows about that domain or specific URL, even if it redirects elsewhere.

This does not mean that the old URL is actually ranking for organic queries. Google simply keeps a record in its index to manage direct requests, technical checks, or cases where the URL is still referenced elsewhere on the web.

This persistence may last for weeks or months, depending on the site’s crawl frequency and the quality of signals sent to Google. A site with a low crawl budget will see its old URLs persist longer.

What is the difference between being in the index and active indexing?

It is important to distinguish between two often-confused concepts. Presence in the index means that Google knows the URL and can retrieve it in specific cases (like site:). Active indexing, on the other hand, means that the URL is considered valid, crawled regularly, and likely to rank for organic queries.

An old redirected URL technically remains present, but is no longer actively indexed. Google keeps it in memory to manage transitions, potential errors, or incoming backlinks still pointing to it. This is normal engine behavior, not a bug.

• The destination page receives the ranking signals and transferred authority
• The old URL may temporarily appear in site: queries without impacting SEO
• Consolidation of signals takes time, especially on low crawl budget sites
• External backlinks to the old URL still pass their juice through the redirect
• The speed of transition depends on crawl frequency, sitemap quality, and coherence of internal signals

Is this statement consistent with real-world observations?

Yes, completely. We regularly observe this residual persistence of old URLs after migration or redesign. What Mueller confirms here is that this behavior is not a malfunction — it’s a system characteristic.

The problem is that many clients panic when they still see their old URLs in a site: query. They believe the migration has failed. In reality, you need to look at actual organic performance: if the new URLs are ranking and generating traffic, everything is fine. Residual presence in site: has no impact.

What nuances should be added to this statement?

Mueller talks about redirects, but does not specify the type of redirect. A permanent 301 should accelerate consolidation. A temporary 302, on the other hand, can delay authority transfer and prolong the floating period. [To be checked]: Does Google treat all redirects the same way in terms of transition speed?

Another point: the statement does not mention redirect chains. If oldurl.com redirects to intermediateurl.com which redirects to finalurl.com, Google may take even longer to consolidate, or lose some juice along the way. In complex migrations, we sometimes observe erratic behavior for several weeks.

Finally, Mueller says nothing about poorly configured internal redirects. If your internal links still point to the old URLs (which redirect), you dilute the signals. Google will see two versions coexisting for longer. An audit of internal links post-migration is essential to speed up the transition.

In what cases does this rule not apply?

If the old URL returns a 404 error instead of redirecting, it will gradually disappear from the index. Google will crawl it a few times to confirm the error, and then remove it. But be careful: if external backlinks still point to it, you will permanently lose that juice.

Another case: soft 404s. If your old URL returns a 200 code with empty content or an error message, Google may keep it in the index much longer, thinking it is still active. This is a classic trap during poorly managed redesigns.

What should you concretely do after a migration or redesign?

First action: check the HTTP return codes of all your redirects. Use a crawler like Screaming Frog or Oncrawl to identify 301s, 302s, redirect chains, and potential errors. Each redirect should point directly to the final version, without intermediaries.

Second action: update all internal links to point directly to the new URLs. Don't rely solely on redirects. Google will see more coherent signals if your internal linking is clean from the start. This speeds up consolidation.

Third action: submit a new XML sitemap containing only the new URLs. Remove the old sitemap or mark it as obsolete in Search Console. Google needs to clearly understand which version you want to index.

What mistakes should be avoided when managing redirects?

A classic mistake: redirecting all old URLs to the homepage. This is considered a soft 404 by Google if the content is not relevant. Each old URL should redirect to its closest thematic equivalent on the new architecture.

Another pitfall: removing redirects too early. Some clients remove 301s after a few weeks, thinking the migration is over. But external backlinks may still point to the old URLs for years. Keep redirects for at least 12 months, ideally indefinitely.

Finally, don't panic if old URLs still appear in site: several weeks after migration. As long as your new URLs are ranking and generating traffic, it’s a sign that Google has consolidated properly. Residual index presence is just a technical artifact with no real SEO impact.

How to verify that the transition went smoothly?

In Search Console, compare the change in the number of indexed pages before and after migration. You should see the new URLs gradually rising, and the old ones dropping. Use the coverage report to identify URLs with errors or exclusions.

Also monitor organic performance: impressions, clicks, average positions. A temporary drop of 10-20% is normal during a migration. If it exceeds 30% or persists beyond 4-6 weeks, there’s likely a structural issue to investigate.

Finally, crawl your site regularly to detect new redirect chains or 404 errors that may arise. Migrations often generate unexpected bugs that only become apparent after a few weeks of real usage.

• Audit all HTTP codes to confirm that each redirect is a direct 301
• Update internal linking to point only to the new URLs
• Submit an updated XML sitemap containing exclusively the final URLs
• Monitor Search Console for indexing or coverage errors
• Keep redirects for at least 12 months, ideally indefinitely
• Do not panic if old URLs still appear in site: several weeks later