How to Update Product Images on Live Listings Without Hurting Rankings (2026 Guide)

Shooting a better product photo is the easy part. Getting it to actually replace the old one — everywhere, without tanking your ranking or leaving half your customers staring at a cached image from last year — is where most sellers come unstuck.

Swapping an image on a live listing is a completely different job from uploading one to a new listing. A new listing has no cache, no index history and no performance baseline to protect. An established listing has all three. Get the swap wrong and you can suppress a listing, lose accumulated Google Images ranking, or spend six weeks wondering why Google Shopping still shows the old photo.

This guide covers what actually happens behind the scenes on Shopify, Google, Amazon and the South-East Asian marketplaces when you replace an image — and the order of operations that keeps you safe.

The two clocks you are fighting

Every image swap runs on two independent timers, and confusing them is the single most common source of panic:

• Platform processing time — how long the marketplace takes to accept, validate and publish your new file.
• Cache time — how long the old file keeps being served from a CDN, a browser, or a partner's copy of your feed, even after the platform has accepted the new one.

You control the first by uploading correctly. You control the second mostly by changing the URL. When a seller says "I uploaded it three days ago and it still shows the old picture," it is almost always clock two, not clock one.

Shopify: the April 2026 CDN change that caught everyone out

This is the most important recent change for anyone running their own store, and a lot of sellers still have not registered it.

As of 7 April 2026, when you replace or delete a file in the Shopify admin, Shopify no longer proactively purges that file's URL on cdn.shopify.com. The previously cached version keeps being served until the URL's TTL expires. Shopify made the change to reduce purge volume and improve consistency across its edge providers — but the practical effect for merchants is that "replace file, same name" is no longer a reliable way to update an image.

What Shopify recommends instead:

• In themes, render images through the Liquid URL helpers — image_url, file_url, asset_url — so the current versioned URL (the ?v= parameter) is always emitted. That version string changes on every re-upload and is what busts the cache.
• For products, upload through Shopify's native media uploader rather than hardcoding <img> tags pointing at a cdn.shopify.com path.
• For apps and integrations, fetch file URLs at request time from the Admin GraphQL or Storefront API instead of storing and reusing a cached URL.

If you have hardcoded CDN URLs anywhere — a custom section, an email template, a landing page, a supplier feed — those are now the places where stale images will linger longest. Audit them before your next big image refresh.

Google Shopping: change the URL, or wait six weeks

Google Merchant Center is unusually explicit here, and the numbers are stark.

If you submit a new, unique image URL in your product data, Google typically crawls it within three days — often within 24 to 72 hours. If you change the image content but keep the same URL, it can take up to six weeks for Google to detect the change and re-crawl.

Google's own guidance is to change the image filename and URL whenever you change the image. Products also re-review within roughly 24 to 48 hours of a feed re-fetch, so a corrected image on a disapproved product does not need to wait long — provided the URL is new.

Two related things worth diarising while you are in there:

• The 500x500 minimum. Google's 2026 product data specification raises the minimum resolution to 500x500 pixels for every product image, including additional images, across all categories and marketing methods. Warnings began appearing in Merchant Center on 14 April 2026, with enforcement from 31 January 2027. Google has said it will optimise some smaller images automatically — using a high-resolution near-duplicate or AI upscaling — but relying on that means letting Google decide what your product looks like. Upload proper resolution instead.
• The 30-day clock. Products move into a "needs update" state 30 days after their last update, so a feed that goes quiet will decay regardless of image quality.

The trade-off nobody mentions: Merchant Center versus Google Images

Here is the genuine tension. Merchant Center wants a new URL for a fast re-crawl. Google Images works the other way — an image URL that has been live and indexed for two years has accumulated ranking that a brand-new URL starts without.

The resolution is not complicated, but it is deliberate:

• For images that drive organic Google Images traffic (hero shots on well-established product pages), change the URL and 301-redirect the old path to the new one so the equity carries across.
• For images that exist mainly to feed Shopping and ads, just mint the new URL and move on. There is nothing to preserve.
• Never do the thing that fails both: quietly overwriting the file at the same URL. Google Images has no signal to re-crawl, and Merchant Center may take six weeks to notice.

Amazon: propagation, suppression and the ranking signal

On Amazon, images typically take up to 24 hours to appear on a detail page, though 24 to 48 hours is common and sellers regularly report 72 hours or longer during busy periods. Before raising a case, hard-refresh the page (Ctrl+F5) — browser cache means you will often be the last person still seeing the old image.

Two risks specific to Amazon:

Suppression. If a required image is missing or fails validation, the listing can be suppressed from search entirely. That makes the gap between "old image removed" and "new image accepted" genuinely dangerous. Always add the new image and confirm it is live before deleting the old one, rather than clearing the slot first.

The main image is a ranking input, indirectly. It drives click-through rate and conversion rate, both of which feed Amazon's ranking. Image improvements that move CTR and CVR generally show measurable change within two to four weeks; a full listing optimisation takes roughly six to eight weeks to settle. Judging a new hero image after four days is measuring noise.

If you are Brand Registered with a Professional account, Manage Your Experiments lets you A/B test the main image properly. Two caveats: low-volume SKUs will not qualify because they cannot reach statistical significance, and tests typically run four to ten weeks. Change one variable per experiment, and do not touch price, offer or inventory mid-test — you will destroy the comparison.

Shopee, Lazada and the regional platforms

The South-East Asian marketplaces re-evaluate listings after edits, and heavy editing has a cost. The working consensus among sellers is to refresh listings roughly monthly, and to avoid major changes more than once per week — repeated large edits can temporarily depress ranking while the platform re-assesses the listing.

The practical implication: batch your changes. Swapping the cover image on Monday, the second image on Wednesday and the size chart on Friday is three re-evaluations. Doing all three in one edit is one.

Update timings at a glance

A safe swap workflow

1. Prepare every size first. Export the full set — marketplace square crops, Shopify hero, feed image at 500x500 or better — before touching a single live listing. Doing the resizing after you have started swapping is how half-finished catalogues happen. A batch tool like PixelPrep handles the per-marketplace dimensions in one pass so the whole set lands together.
2. Record a baseline. Note current sessions, CTR and conversion rate per SKU. Without this, you cannot tell whether the new image helped.
3. Change one thing. Swap the hero image, or the gallery, not both. Do not stack an image change on top of a price or title change.
4. Add before you remove. Upload the new file, confirm it is live, then delete the old one. Never leave a required slot empty.
5. Use a new filename and URL for anything Google crawls — and 301 the old path if the image had organic traffic worth keeping.
6. Force a feed re-fetch in Merchant Center rather than waiting for the scheduled pull.
7. Verify in a private window on desktop and mobile. Your own browser cache is not evidence of anything.
8. Wait two to four weeks before reading results, longer for low-traffic SKUs.

When not to change your images

Some swaps cost more than they return. Hold off if you are mid-campaign on Shopee or Lazada, mid-experiment on Amazon, inside your peak trading fortnight, or if the only change is cosmetic and the current image is already converting well. "It looks a bit dated to me" is not a business case — check the conversion data first.

Pre-swap checklist

• All output sizes exported and named before any live edit
• Baseline CTR and conversion rate recorded per SKU
• New filename and URL for anything Google crawls
• 301 redirects planned for images with organic Google Images traffic
• Feed image at 500x500 minimum, ideally far larger
• New image added and verified before the old one is deleted
• Shopify theme rendering via image_url / file_url, no hardcoded CDN paths
• Merchant Center feed re-fetch triggered manually
• Checked in a private window, desktop and mobile
• Marketplace edits batched into one pass, not spread across the week
• Review date set two to four weeks out

The rule underneath all of this: an image swap on a live listing is a change to a working system, not a file upload. Treat it like a deployment — prepare everything, change one variable, verify, then measure — and you keep the upside of a better photo without the ranking damage that catches out sellers who just drag and drop.