SEO Image Names: A Practical Filename Rule for Ecommerce

An SEO image name should be short, descriptive, and faithful to what the image shows. Use lowercase words separated by hyphens, keep the real file extension, and include only the details that distinguish the asset. black-leather-crossbody-bag-front.webp is useful. best-cheap-designer-bag-buy-online-final-v7.webp is not.

The restraint matters because Google describes the filename as a source of very light clues, not a ranking lever to be packed with keywords. Alt text and relevant page context carry more meaning. A clean filename still earns its place: it costs little, gives a production team a readable asset, and may provide one accurate hint when the public URL preserves it.

Use the filename as a label, not an SEO pitch

A good filename identifies the visible subject before it tries to describe the page. Start with the product or subject, add one useful differentiator, then add the view or image job when it prevents ambiguity. Stop when a teammate could select the right file without opening it.

For ecommerce images, that usually produces a three-part pattern:

subject-differentiator-view.ext

Examples include linen-shirt-sage-front.webp, silver-hoop-earrings-pair.jpg, and ceramic-vase-blue-lifestyle.avif. A SKU can replace or precede the subject when it is the most stable identifier in your catalog, as long as the public words remain understandable: sku-1842-black-tote-interior.webp.

Google's image guidance says filenames should be short but descriptive, and explicitly calls a descriptive kitten filename better than a camera-style ID. It also says the filename offers only very light subject clues. That language is a useful ceiling on the tactic. Name the file well, then spend the serious effort on an indexable image, useful alt text, relevant nearby copy, and a page worth finding.

Decision rule: describe the asset, add only a useful distinction, then stop before the filename becomes a pitch.

The extension is part of the name. Google recommends that it match the actual file type. Renaming photo.png to photo.webp does not convert the image. Export or convert the file correctly, then keep the matching .jpg, .png, .webp, .svg, or .avif extension.

Name the image from what a buyer can verify

The safest naming test is visual: could the words be confirmed from the pixels? Product type, material, color, angle, detail, and context are often fair game. Claims such as “best,” “luxury,” “sale,” “high converting,” or “eco friendly” usually are not visible properties and should stay out unless the image literally and legitimately represents that fact.

Use visible, differentiating facts. Keep claims and production-only state out of the public name.

This rule prevents filename and image from drifting apart. If a front-view filename is reused for a back view, the label has stopped being evidence. If every image on a product page gets the same base phrase plus a number, the names no longer explain why the files differ.

Do not write alt text by copying the filename into a sentence. Filenames identify files; alt text replaces the image's meaning in its page context. The W3C decision tree treats informative, functional, redundant, and decorative images differently. A decorative image may need empty alt text even when its operational filename remains descriptive. A linked icon may need alt text that describes the action rather than its appearance.

Keep production identity separate from the public description

Studios need identifiers that SEO advice rarely covers: SKU, color code, shot ID, crop, channel, version, and approval state. Forcing every production field into a public filename creates long, brittle strings. Removing all identifiers makes retouching and delivery harder. The practical answer is to separate the stable production key from the short public description.

A working master might be BAG-1842_BLK_03_select-r2.tif. The approved web derivative can become black-leather-crossbody-bag-interior.webp. Store the relationship in the digital asset manager, product information system, or delivery manifest. Do not ask the public filename to replace the production record.

The same separation helps variants. Color or material belongs in the public name when the image genuinely changes and the distinction matters. A sequence number is acceptable when it represents a real ordered set, but a view name is usually more useful than -01, -02, and -03. Keep locale, channel, and campaign codes in structured metadata unless they change the public asset or prevent a collision.

For outsourced derivatives, put the public naming rule in the lifestyle product photography services handoff: production IDs preserve traceability; the approved web export gets the short visible description.

For capture planning, the product photography shot list explains how to carry a shot ID through tethering, selects, retouching, and delivery. The SEO image name begins at the approved derivative boundary, not at the camera card.

Check the public URL your CMS actually serves

First-party audit, 6 September 2026: this exact local-to-CDN filename pair was matched by the rendered alt text, “Unbranded black handbag positioned between square and portrait acrylic crop frames.” All 12 sampled images across three pages had descriptive local names, opaque public names, and descriptive alt text. Names wrap in the graphic; no ranking effect was measured.

Renaming the source file does not guarantee that its words survive on the web. A content management system, image optimizer, or CDN may replace the basename with a hash, add transformation parameters, or create several responsive URLs. Inspect the rendered page and the browser's actual image request before treating a tidy library filename as a public search signal.

On 6 September 2026, we checked 12 rendered article images across three Look Atlas pages. All 12 local source files had descriptive basenames, all 12 live Framer CDN basenames were opaque hashes, and all 12 rendered images carried descriptive alt text. This is a first-party operational sample, not a ranking study. It proves one narrow point: a disciplined source-library name and a descriptive public URL are not the same thing.

The result changes the workflow. Keep descriptive source names because they improve handoff and may survive on platforms that preserve them. Then audit the delivered URL separately. If the platform replaces the name, do not stuff the alt text to compensate. Confirm that the image is discoverable in standard HTML, the alt text fits its role, the surrounding content is relevant, and the page can be indexed.

Google says it can discover images in the src attribute of standard img elements, including inside picture, but it does not index CSS background images in the same way. It also recommends reusing the same image URL when the same image appears on multiple pages so Google can cache and reuse it. The Shopify product picture size guide shows the related delivery check: inspect the image the theme actually serves, not merely the export sitting on disk.

Rename before upload, then protect live URLs

The cleanest time to name an image is before its first upload. At that point the filename can change without breaking a public address, invalidating a cache, or separating a CMS record from an existing search result. Put the naming rule between final selection and web export, where the team already knows the subject, variant, and view.

Renaming an image that is already live is a URL change when the platform exposes the basename. Treat it as a migration, not housekeeping. Update every reference, preserve the old address with an appropriate permanent redirect when the platform supports one, verify the new image returns successfully, and confirm that responsive variants, structured data, feeds, and sitemaps still point to the intended asset. If none of that is available, the small benefit of a cleaner filename may not justify disturbing a working image URL.

Conceptual illustration: the clean naming moment sits between approved selects and the first public upload.

For a large existing library, prioritize future uploads and high-value exceptions. Rename a live asset when the old URL is broken, misleading, unsafe, or part of a planned migration. Do not churn thousands of stable URLs simply because their basenames are generic. Google explicitly frames filename information as light, while discovery, page relevance, alt text, quality, and speed remain a larger system.

Make the rule automatic without making it generic

A scalable naming function needs controlled inputs, not a language model improvising keywords. Start with a canonical product name or approved category, add the variant value that actually changes, add a controlled view label, normalize to lowercase, remove unsafe punctuation, collapse whitespace into hyphens, and preserve the true extension.

Use a collision rule that exposes meaning. If two files would both become black-leather-tote-front.webp, add the stable SKU or a meaningful crop label rather than final-final-2. Keep a small controlled vocabulary for views such as front, back, side, detail, interior, on-model, and lifestyle. Reject empty subjects, unsupported claims, duplicate outputs, and names that exceed the team's practical limit.

Localization deserves an explicit decision. Google's image guidance recommends translating filenames when images are localized. Do that when the localized page receives a genuinely localized asset and your URL system safely supports it. Do not create duplicate image files for every language by default. One shared product image may be better served from one stable URL with context-appropriate alt text on each page.

After a product source and its derivative rules are approved, Look Atlas can create on-model, studio, lifestyle, and campaign-style imagery from product photos. Keep generated derivatives inside the same naming contract. Name what the frame visibly contains, preserve provenance in the asset record, and never let a filename imply that generated context is documentary evidence.

The final release check is short: descriptive source name, truthful extension, unique production mapping, appropriate alt text, relevant page context, discoverable rendered image, and a stable public URL. A filename passes when it makes the asset easier to understand without pretending to do the rest of image SEO by itself.