Product image SEO is not the same as blog image SEO. The stakes are higher, the buyer journey runs straight through Google Images, and the rules that work for an atmospheric blog photo can actively hurt a product listing. If you sell through WooCommerce, your product images are doing sales work, not decoration work — and they should be optimised accordingly.
This is the e-commerce-specific companion to our complete image SEO guide, and a sister piece to the complete guide to WooCommerce product galleries.
Why product image SEO is its own thing
Shoppers search visually. They type “black ankle boots side zip” and scan the image results before they read a single product description. Baymard’s research found that exploring product images is the first action most shoppers take on a product page. That means your product image is often the first thing a potential customer sees of you — sometimes before they have even visited your site, in the Google Images grid. Optimising it is optimising your storefront window.
Naming products vs naming blog photos
For products, the filename should describe the product the way a shopper would, not the way your inventory system does. navy-linen-suit-front.jpg beats both SKU-44821.jpg and best-suit-cheap-2026.jpg. Use the product name and the angle, keep it consistent across the catalogue, and resist the urge to cram in pricing or promotional words — those read as spam and date instantly.
Alt text for products: the descriptive formula
Product alt text should read like a sales associate describing the item to someone who cannot see it: material, colour, key feature, style. “Black leather ankle boots with a side zip and block heel” tells a shopper and a search engine exactly what they are looking at. “Leather boots best price free shipping” tells them you are stuffing keywords. The descriptive version wins on both accessibility and ranking.
Do this now. Open your three best-selling products and check the alt text on their main images. Rewrite any that are blank, filename dumps, or keyword-stuffed into a plain description of material, colour, and key feature. These are the products where image-search visibility converts to revenue fastest.
Product schema and image URLs
Product schema with image URLs is what makes your products eligible for product rich results and the image carousels above organic listings. This is one of the four cases where image structured data genuinely earns its place (see structured data for images). The image URL inside the product schema must be absolute and must resolve — a broken URL silently disqualifies the rich result.
Tip. WooCommerce and your SEO plugin both try to output product schema. Run a product page through Google’s Rich Results Test to confirm you have exactly one valid Product block, not two competing ones — duplicate schema is a common source of “invalid” warnings.
Image dimensions: the 10x speed difference
An 800-by-800-pixel WebP at around 150KB loads roughly ten times faster than a 2000-by-2000-pixel JPEG at 2MB, and on a product page the customer cannot tell the difference at display size. Since product images are usually the Largest Contentful Paint element on a product page, and most product pages fail Core Web Vitals because of their images, this single change moves both speed and conversion. Set sensible product and thumbnail sizes (commonly 800-square for the main image, 600-square for grid thumbnails) and serve modern formats.
Do this now. Check the file size of your main product image (right-click, open in new tab, look at the size). If it is over about 300KB, it is too heavy. Resize to 800px square, serve as WebP, and watch your product-page LCP drop.
Variants, swatches, and zoom — what Google sees
When a shopper selects a variant, the gallery should switch to that variant’s images — and the alt text and schema should match. Search engines index the images they can see in the markup, so variant images that only appear via JavaScript after a click may not be crawled. This is a place where the default WooCommerce gallery and many themes fall short, and where a gallery built for the job carries each variant’s images, names, and metadata properly. We cover the variant gallery mechanics in variable products and variant galleries done right.
A worked example: one product, done right
Make it concrete with a single product — a navy linen suit — optimised end to end. The filenames describe the product and angle: navy-linen-suit-front.jpg, navy-linen-suit-back.jpg, navy-linen-suit-lapel-detail.jpg. The main image is 800px square, served as WebP at around 150KB, eager-loaded with high priority (it is the LCP element). Its alt text reads “Navy linen three-piece suit, front view, slim fit” — material, colour, cut, view. The product carries a single valid Product schema block whose image URL is absolute and resolves. Each colour variant switches the gallery to that variant’s images, and those images exist in the markup so a crawler sees them. All the product’s images sit in a category-segmented image sitemap. None of this is exotic — it is the same handful of decisions applied deliberately to one product. The discipline is doing it for every product, which is exactly why it has to be a system rather than a per-product chore.
Contrast that with the default: a 20240817_141233.jpg filename, a 3MB straight-from-the-camera JPEG that is the slowest element on the page, blank alt text, no variant image switching, and no sitemap entry. The same product, invisible to image search and slow to load — and the only difference between the two is decisions, not budget.
The image sitemap for catalogues
For a large catalogue, segment the image sitemap by category so it stays manageable and crawlable. Every product image in the sitemap is a product image Google can find for the visual searches your buyers are running. For an image-heavy shop, this is among the highest-leverage SEO actions available — a single setting that exposes hundreds or thousands of product images to image search at once. The catch at catalogue scale is that doing the per-product work (naming, alt text, schema, variant images) by hand across thousands of SKUs is impractical, which is the recurring theme: product image SEO done well is a system applied consistently, not heroics applied occasionally. Where your gallery or product setup can carry these decisions automatically — consistent naming, per-variant images in the markup, valid schema, sitemap inclusion — that is the difference between a catalogue that is fully optimised and one where only the few products someone manually touched are.
Key takeaways
- Shoppers search visually — product images are your storefront window in Google Images.
- Name and describe products the way a shopper would; never stuff pricing or promo words.
- Product schema earns rich results — confirm exactly one valid block with no broken image URLs.
- 800px WebP beats a 2MB JPEG by ~10x on speed, and product images are usually the LCP.
What size should WooCommerce product images be?
A common setup is 800px square for the main product image and 600px square for grid thumbnails, served as WebP. An 800px WebP loads about ten times faster than a 2000px JPEG with no visible quality loss at display size.
Do WooCommerce products need image schema?
Yes — product schema with image URLs makes products eligible for product rich results and image carousels. Confirm you output exactly one valid Product block (WooCommerce and your SEO plugin can both try) and that the image URL is absolute and resolves.
Why aren’t my variant images showing in Google?
If variant images only appear via JavaScript after a selection, search engines may not crawl them. Use a gallery that carries each variant’s images in the markup with matching alt text, so every variant is visible to crawlers.