Should you really implement 301 redirects for your images when changing domains?

Why do images have their own quality signals?

Images are not just decorative files. Google assigns quality signals to them based on their performance history: click-through rates in Google Images, user engagement, age, authority of the source domain.

A well-optimized image generates autonomous traffic. It accumulates signals that strengthen its position in search results. A domain change without redirection breaks this continuity. The URL changes, and Google doesn't automatically make the connection — you lose that history.

What happens without a 301 redirect on images?

Without a redirect, Google discovers new image URLs on your new domain. It treats them as new content, without history. The old URLs become 404s, and the accumulated signals disappear.

Traffic from Google Images collapses. Your images lose their ranking. The re-indexing time and reconstruction of signals can take several months. This is exactly what a 301 redirect prevents.

Do 301 redirects for images work like they do for pages?

Yes. A 301 redirect transfers quality signals from the old URL to the new one, whether it's for an HTML page or a JPG image. Google follows the redirect, indexes the new URL, and consolidates the historical signals there.

The logic is the same as for text pages. The transfer is not instantaneous — Googlebot needs to recrawl the old URLs, detect the redirects, and then re-index the new ones. But the process is smooth if technically well executed.

• Images have their own SEO signals (popularity, engagement, history) that Google uses to rank them.
• A domain change without a 301 redirect leads to a loss of these signals and a temporary collapse in Google Images traffic.
• 301 redirects work for images just like for pages: they transfer signals to new URLs.
• The technical setup must cover all image URLs, including those hosted in subfolders or CDNs.
• The signal transfer takes time — several weeks to months depending on crawl frequency and image volume.

Is this recommendation consistent with real-world observations?

Absolutely. Poorly managed domain migrations regularly show collapses in Google Images traffic that persist long after recovering classic organic traffic. SEO teams that neglected image redirects during migration pay the price.

What's interesting is that Google is finally explicit about what many of us observed empirically. Images are not a detail — for some sites (e-commerce, news, recipes, DIY), Google Images accounts for 15 to 30% of total organic traffic. Losing these signals means losing revenue.

What uncertainties remain in this statement?

Mueller does not specify the time it takes to transfer signals or the percentage of retention. It's known that a 301 redirect transfers the majority of PageRank, but what about signals specific to images (CTR, visual engagement, etc.)? [To be verified] on real cases with before/after measurements.

Another gray area: images hosted on external CDNs. If your images are served from a third-party CDN (Cloudinary, Imgix, etc.) and you change your main domain, the redirect from the main domain does not cover the CDN URLs. This case needs to be managed separately — Mueller does not mention it.

In what cases does this rule not fully apply?

If your images generate very little Google Images traffic (technical B2B site, SaaS without strong visual content), the impact of not having a redirect will be marginal. It may not be worth the effort if implementation is complex.

Also, if you are radically changing your editorial strategy and the old images are no longer relevant on the new domain, it could be counterproductive to redirect to misaligned content. It’s better to let the old URLs expire and start anew — but this is a rare scenario.

How to set up 301 redirects for images during a migration?

First step: inventory all indexed image URLs on the old domain. Use Google Search Console (Performance report, filter by type = Image), a crawler like Screaming Frog, or an XML sitemap export for images. Don’t limit yourself to images on main pages — think about thumbnails, images in blog posts, product galleries.

Second step: map each old image URL to its new URL on the new domain. If the folder structure changes, a correspondence table or regex mapping script is essential. Ensure that the new URLs are accessible and serve the correct image file.

What technical errors must be absolutely avoided?

Do not redirect all images to the homepage of the new domain. This is a classic migration error — Google detects soft-404s and ignores these redirects. Each image must point to its exact equivalent or to a relevant replacement image.

Be cautious of redirect chains (old URL → intermediate redirect → new URL). Googlebot follows chains, but with a signal loss and wasted crawl time. Aim for direct redirects in a single jump. Test your redirects with curl or an HTTP validator to confirm a clean 301 status.

How to check that redirects are working and transferring signals?

Monitor Google Search Console on both properties (old and new domain). The Google Images traffic from the old domain should gradually migrate to the new one. Use the Performance report filtered by Images to compare impressions and clicks week after week.

Regularly crawl the new domain to check that the new image URLs are properly indexed. Use the URL Inspection tool in GSC to force the re-indexing of strategic images. If after 6-8 weeks the transfer stagnates, it’s a warning signal — check the redirect configuration and the crawl budget allocated.

• Inventory all indexed image URLs on the old domain (GSC, crawler, sitemap)
• Map each old URL to its equivalent new URL (no generic redirection to home)
• Configure 301 redirects at the server level (Apache, Nginx) or via .htaccess
• Test redirects with curl or an HTTP validator (301 status, no chains)
• Submit the new XML image sitemap in Google Search Console
• Monitor Google Images traffic transfer for 2-3 months (GSC Performance report)