Product image naming conventions that survive a catalog migration

The default camera filename — IMG_4821.jpg — is a missed ranking signal repeated across your entire catalog. The filename is one of the oldest and most reliable things Google Images reads, and a good convention also saves you during the migration that eventually breaks everyone’s image URLs.

Encode meaning, not sequence

A filename should tell a human and a crawler what the image is without opening it. A convention that holds up looks like:

brand-product-name-color-view.jpg → acme-merino-crew-charcoal-front.jpg

Every token is deliberate: brand and product for relevance, colour because variants are what people search, and view (front/back/detail) so the same product’s images don’t collide.

Why it survives migrations

When you replatform, image URLs are regenerated from filenames or SKUs. If your names encode SKU and variant, the mapping is mechanical and lossless. If they’re sequence numbers, you’re reconciling thousands of orphaned files by hand — the classic post-migration Image-search traffic cliff.

Pair it with the metadata

The filename is the label; the embedded IPTC title and keywords are the substance. Keep them consistent — the same product, colour and view described the same way in the name and the metadata — and you give every consumer of the image the same clear signal.

Takeaway: adopt brand-product-color-view now, generate it from your product data, and you’ll rank better today and migrate painlessly later.