A catalogue-scale workflow for naming files, writing useful alt text, keeping image URLs stable and connecting visual assets to the right product pages.
Product image SEO is not a game of adding the same keyword to every filename and alt attribute. Search engines and assistive technology need accurate context. Buyers need fast, clear pages. Your operations team needs a naming system that survives catalogue growth. The best workflow solves all three and starts with the truthful masters described in GPTWala’s AI product photography guide for Indian businesses.
Google says filenames can provide very light clues about an image, while alt text is a more important source of image metadata and supports accessibility. It also uses the surrounding page content and computer vision to understand the subject. Read the current Google Search Central image SEO guidance alongside this implementation system.
What the filename, alt text, caption and page copy each do
| Field | Primary job | Example | Common misuse |
|---|---|---|---|
| Filename | Stable, descriptive asset identity | amber-glass-jar-750ml-front.webp |
best-cheap-jar-buy-online-1.webp |
| Alt text | Contextual text alternative for the image | “Front view of the 750 ml amber glass jar with black screw lid” | Repeated keyword list |
| Caption | Visible clarification when readers benefit | “Lid and sealing ring shown separately” | Duplicating nearby paragraph without value |
| Page copy | Full product facts, benefits, conditions and choice guidance | Capacity, material, dimensions and compatibility | Expecting alt text to carry the whole listing |
| Image URL | Crawlable, reusable location of the file | /images/amber-glass-jar-750ml-front.webp |
Changing URL on every feed or resize run |
Write short, descriptive product image file names
Google recommends short but descriptive filenames and advises against generic names such as image1.jpg. A scalable product filename should help a human recognise the asset and remain stable after upload.
A practical pattern
[product-or-sku]-[variant]-[view-or-purpose].[extension]
linen-kurta-blue-front.webplinen-kurta-blue-fabric-detail.webppump-px40-inlet-connection.jpgspice-gift-box-6-pack-contents.jpg
Use lowercase words separated by hyphens. Include only attributes that distinguish the asset. Keep the correct file extension for the actual format. Do not append adjectives such as “best”, “premium” or “cheap” unless they are part of the official product name.
SKU-first versus product-name-first
SKU-first naming is efficient for large B2B catalogues and production teams. Product-name-first naming is easier for editors and can be more descriptive. A combined form works when it stays readable, for example px40-transfer-pump-side.jpg. Choose one convention and document it.
Write alt text for the image in its page context
Alt text should communicate the relevant content or function of the image to a person who cannot see it. That means the same file can reasonably have different alt text in different contexts. A clean product image on a product page may need the item, variant and view. The same image inside an article about closures may need to emphasise the visible closure.
A practical product-page formula
[View or action] of [exact product] [important visible variant/detail]
- “Front view of the blue linen kurta with concealed button placket”
- “Close-up of the PX40 pump inlet connection and thread”
- “Six-piece spice gift box with all included jars arranged beside the outer carton”
Write what is visible, not what you hope to rank for
If “food-safe”, “waterproof” or “handmade” is not visible in the image, it usually does not belong in the alt text. Put verified claims in the relevant product copy and structured data. Avoid repeating the business name in every alt attribute. Include GPTWala or another brand only when the brand is genuinely needed to identify the visible product or graphic.
File-name and alt-text templates
| Image type | Filename template | Alt-text template |
|---|---|---|
| Clean hero | [product]-[variant]-front |
Front view of [product] in [visible variant] |
| Back or side | [product]-[variant]-back |
Back view of [product] showing [visible detail] |
| Material detail | [product]-[material]-detail |
Close-up of [product] showing [texture/material feature] |
| Scale or fit | [product]-[variant]-in-use |
[Product] [worn/held/placed] to show [relevant scale or fit] |
| Pack contents | [product]-pack-contents |
[Product or set] with [visible included items] |
| Diagram | [product]-dimensions-diagram |
Dimension diagram of [product] showing [visible measurements] |
Weak versus useful examples
| Weak | Why it is weak | Useful replacement |
|---|---|---|
IMG_9231.jpg |
No asset meaning | amber-glass-jar-750ml-front.jpg |
| “product image” | Does not identify the content | “Front view of 750 ml amber glass jar with black lid” |
| “jar jar buy jar online cheap jar” | Keyword stuffing and poor accessibility | Describe the exact visible item and view once |
| “red dress” for a blue variant | Factual mismatch | Use variant data and visual QA before publish |
| Full product description in alt | Overloads the text alternative | Keep specifications and benefits in page copy |
Scale the system across an ecommerce catalogue
- Define approved source fields. Product name, SKU, colour, size, view, material and included parts must come from the catalogue record.
- Create a controlled view vocabulary. Use “front”, “back”, “side”, “detail”, “in-use”, “contents” and category-specific terms consistently.
- Rename before upload. Avoid changing URLs later unless the image itself changes or there is a migration plan.
- Generate a first draft at scale. A spreadsheet, PIM or script can combine approved fields.
- Review visually. Automation cannot confirm that the image actually shows the intended variant or detail.
- Publish with page context. Place images near relevant text and use captions only where readers need them.
- Audit after rendering. Check responsive size, layout stability, lazy loading, links and accessibility.
This workflow should connect to the broader product-page SEO system and the product-page copy template, not operate as a separate keyword exercise.
Technical image SEO checks
Google Search Central recommends standard HTML image elements with a crawlable src, responsive image practices with a fallback source, supported formats, high visual quality and attention to page speed. It also explains that Google does not index CSS background images as product images in the same way as standard img elements.
| Check | Pass condition | Why it matters |
|---|---|---|
| HTML | Meaningful images use standard img markup with src |
Supports discovery and accessibility |
| Responsive delivery | srcset/picture has a fallback src |
Serves appropriate files across devices |
| Dimensions | Width and height or aspect ratio are reserved | Reduces layout shifts |
| Compression | File is small enough for fast delivery without visible damage | Balances speed and quality |
| URL | Stable, crawlable and not blocked unintentionally | Lets search systems fetch and reuse the asset |
| Context | Image is near relevant product text | Clarifies subject and page relationship |
| Metadata | Preferred image is represented consistently in page/social/schema setup where used | Supports page previews and eligible search features |
For shopping feeds, the main and additional image URLs must also follow the destination’s product-image requirements. See GPTWala’s cross-channel product image rules.
Variants, repeated images and duplicate assets
Each visible variant should use the correct image and alt text. Do not show a red SKU with a blue filename/alt string because the template was copied. If a genuinely identical component image is reused across pages, keep one stable image URL where practical and write alt text for each page context.
Avoid uploading several identical copies with small filename changes solely to target keywords. That increases media-library clutter and creates no new product evidence.
Decorative images and linked images
An image used only for decoration generally needs an empty alt attribute so assistive technology can skip it. Do not omit the attribute entirely. If an image is a link, its alt text should communicate the destination or action where surrounding link text does not already do so.
Complex charts and diagrams may need concise alt text plus a nearby detailed explanation. Do not force an entire table into one alt attribute.
Product image SEO QA checklist
- Filename is short, descriptive, stable and matches the actual file format.
- Image shows the exact product, variant and view described.
- Alt text is useful in context and not stuffed with keywords.
- Verified product facts live in page copy or product data, not invented in alt text.
- Meaningful images use crawlable HTML image markup.
- Responsive files include a fallback source and do not overflow the reading column.
- Dimensions are reserved and file size is optimised without visible quality loss.
- Image URLs are not accidentally blocked and remain stable.
- Decorative images use empty alt text.
- The final rendered page is checked on desktop and narrow/mobile view.
Frequently asked questions
What should I name product images for SEO?
Use a short, descriptive filename that identifies the product or SKU, visible variant and image purpose, such as amber-glass-jar-750ml-front.webp.
Are image filenames important for SEO?
They can provide light clues and improve asset management, but they are only one signal. Accurate alt text, relevant page context, crawlable markup, quality and performance are more important parts of the system.
How do I write alt text for ecommerce product images?
Describe the visible product, relevant variant and view or action in the context of the page. Keep specifications and non-visible claims in the product copy.
Should every product image include the keyword in alt text?
No. Repeating a target phrase in every alt attribute harms usefulness and can become keyword stuffing. Describe each image naturally and accurately.
Should decorative images have alt text?
Use an empty alt attribute for purely decorative images so assistive technology can skip them. Meaningful images need a useful text alternative.
Can I automate product image alt text?
You can generate a first draft from approved product fields and a controlled view vocabulary, but a person should verify that the image, variant and detail actually match before publishing.