Why does Google still show old URLs for image landing pages despite redirects?

What exactly is an image landing page?

An image landing page is an intermediate URL that displays before the user accesses the high-resolution image. Some sites use this type of page to generate ad impressions or control access to visual resources.

The problem arises when you decide to redirect these landing pages directly to the final image files. Google may take time to understand that the old structure should no longer appear in its results.

Why doesn't Google update these URLs immediately?

Google's crawling engine operates in successive waves of crawling and reprocessing. When a redirect is set up, Googlebot must first detect it, then reassess the relevance of the destination URL.

The images and their associated pages are not a priority in Google's crawl budget. Therefore, Google may continue to serve the old URL in temporary results, the one it already knows and has indexed, even if the redirect technically works.

What is the impact on image search results?

Users clicking on an image in Google Images may be redirected to the old URL of the landing page. The browser then follows the redirect, but Google continues to display the old path in its snippets.

This creates a dissonance between the displayed URL and the actual destination URL. For an e-commerce site with thousands of product visuals, this situation can create confusion and degrade engagement metrics.

• Image redirects are not processed in real-time by Google—the delay can be several weeks
• The old URL can remain visible in the SERPs even if the redirect works perfectly on the server side
• This phenomenon mainly affects Google Images, not necessarily standard web search
• No direct negative impact on ranking is mentioned, but user experience may degrade
• Google refers to this display as “temporary” without specifying an exact duration

Is this statement consistent with real-world observations?

Yes, and it's even a classic case of latency in index updates. On sites with a complex image architecture, delays of 4 to 8 weeks are regularly observed before Google consolidates the redirected URLs.

The crucial point? Google says nothing about the real impact on organic traffic. We know that the redirect works, but does the CTR in Google Images drop when the displayed URL does not match the final destination? [To be verified]—Google provides no data on this.

What nuances should be added to this statement?

Mueller talks about “temporary results”, but temporary here can mean several months. On a site with rapid product turnover, this is problematic. A promotional image with a URL that changes every 6 weeks will never have time to stabilize.

Another point: the statement does not distinguish between 301 (permanent) redirects and 302 (temporary) redirects. However, the speed of consolidation differs significantly. A 301 should theoretically be processed faster, but Google does not specify this here.

Finally, it is unknown whether this delay varies depending on the PageRank of the hosting page or the search volume for the particular image. Will a popular image on an authoritative site be consolidated faster? Probably, but Mueller remains vague.

In what cases does this rule not apply?

If your images are hosted on a CDN with stable URLs and you have never used intermediate pages, this issue does not concern you. Google directly indexes the image file without going through an additional layer.

Similarly, if you use native lazy-loading or JavaScript galleries that load images via AJAX, Google does not see a traditional HTTP redirect. The behavior described by Mueller applies to traditional server redirects (301/302/307), not to client-side URL changes.

What specific actions can be taken to limit this problem?

First, avoid image landing pages if possible. Serve the image file directly with a clean and stable URL. If you absolutely must go through an intermediate page, ensure it provides real value (context, enriched metadata, ImageObject schema).

If you’ve already set up redirects, force a recrawl via Google Search Console. Use the URL inspection tool to request re-indexing of the hosting pages containing the images. This can speed up the update, though there are no guarantees.

Next, monitor your URLs in Google Images with a dedicated image position monitoring tool. If the old URL persists beyond 8 weeks, Google is encountering a blockage. Check your server logs to confirm that Googlebot is indeed following the redirect.

What mistakes should be absolutely avoided?

Never create multiple redirect chains between the landing page, a transition URL, and then the final image. Google can lose track and continue indexing the oldest URL. A redirect should be direct: A → C, never A → B → C.

Also, avoid changing the final image URL too frequently. If you redirect to /image-v2.jpg then to /image-v3.jpg a few weeks later, Google may get stuck on the first URL it indexed.

Finally, do not abruptly delete old landing pages by sending 404 or 410 responses if Google is still indexing them massively. Keep the redirects active while the index consolidates, even if it means maintaining them for several months.

How can I check if my site is affected?

Use a query site:yourdomain.com inurl:landing or any identifiable pattern from your old URLs. If landing pages still appear in Google Search while redirecting for weeks, you are experiencing the case described by Mueller.

Next, compare the organic traffic from Google Images before and after implementing the redirects. A sharp drop without recovery after 4-6 weeks may indicate that Google continues to display old URLs, degrading CTR.

Check your coverage reports in Search Console. Old URLs may appear as “Excluded - Redirected” but remain visible in results. If that's the case, initiate a manual crawl and wait for the next major index update.

• Serve images with stable and definitive URLs from the start
• Set up direct 301 redirects (no multiple chains)
• Force a recrawl via Search Console after each structural change
• Monitor the appearance of old URLs in image SERPs for at least 8 weeks
• Keep redirects active for several months even if the destination URL works
• Verify that Googlebot properly follows redirects in server logs