BigCommerce has a reputation as the SEO-friendly platform — the one migration agencies recommend when Shopify's limitations start to hurt. That reputation is mostly earned at the page and site-architecture level. Image SEO is a different story: BigCommerce leaves more of it in your hands than most sellers realize.
This matters most for the sellers actually choosing this platform. Mid-market stores migrating off Shopify, B2B catalogs with thousands of SKUs, and merchants upgrading from WooCommerce all land here with an expectation. They assume the platform handles image optimization the way it handles checkout and hosting. Some of it is automatic. A meaningful chunk is not, and the gap between the two isn't obvious from the admin panel alone.
This guide separates what BigCommerce genuinely automates from what you still have to do yourself. That covers filenames, alt text, structured data, and the API-level work that matters once your catalog crosses a thousand products.
Key Takeaways
- Unlike Shopify, BigCommerce keeps your uploaded filename in the live image URL permanently — get it right before upload, since there's no rename option after.
- Alt text lives in a field literally labeled "Description (Image alt text)" in the product image manager, not in the product's main description box.
- BigCommerce does not aggressively compress uploads. A 15MB original stays 15MB unless you compress it yourself first.
- For catalogs over 1,000 SKUs, the Catalog API's image endpoints are the only realistic way to fix alt text and ordering at scale.
Why BigCommerce Image SEO Matters More Than Sellers Assume
BigCommerce ranks well out of the box for the things that don't depend on your input. Clean URL structures, fast default hosting, and solid on-page technical SEO all come standard. Sellers extend that trust to images and assume the same automation applies.
It mostly doesn't. Shopify auto-compresses images more aggressively and strips your filename entirely, replacing it with its own asset ID. BigCommerce does neither. It keeps your filename exactly as uploaded and serves your image at closer to its original file size. That's a double-edged trade: a real SEO opportunity if you name files well, and a real performance cost if you don't compress before uploading.
The platform's own documentation and Stencil theme code confirm this pattern across the board. Responsive image generation exists, but nothing forces you to use it correctly. Nothing writes your alt text for you either.
BigCommerce vs. Shopify vs. WooCommerce: Who Auto-Optimizes What
Before you invest effort into any single fix, know which platform behaviors are automatic and which require your own theme code or manual input.
| Behavior | BigCommerce | Shopify | WooCommerce |
|---|---|---|---|
| Filename in live URL | Preserved exactly as uploaded | Replaced with internal asset ID | Preserved exactly as uploaded |
| Automatic compression | Minimal — near-original file size served | Aggressive, automatic on upload | None — depends entirely on hosting/plugins |
| Responsive srcset | Via Stencil's getImageSrcset helper, theme-dependent | Automatic across all themes | Plugin or theme-dependent |
| WebP delivery | Format-negotiated by the CDN, browser-dependent | Automatic | Plugin-dependent |
| Alt text field | "Description (Image alt text)" in Image Manager | Dedicated Alt Text field per image | Native WordPress Media Library alt text field |
| Image sitemap | Automatic at /xmlsitemap.php | Automatic | Plugin-dependent (Yoast, RankMath) |
The pattern across this table: BigCommerce sits closer to WooCommerce's "bring your own configuration" model for compression and responsive images. For the sitemap, though, it's closer to Shopify's "it's automatic" model. Know which column you're actually in before you assume a fix is unnecessary.
For Shopify's specific alt text mechanics, see How to Add Alt Text to Shopify Images. For WooCommerce, see How to Add Alt Text to WooCommerce Images.
Alt Text on BigCommerce: The "Description" Field Confusion
Alt text on BigCommerce lives in more places than most sellers check, and the field name itself causes real mistakes.
Where Alt Text Actually Lives
- Product images: Inside a product's Images tab in the admin, each image has a field labeled Description (Image alt text). That literal label is BigCommerce's own attempt to head off the confusion — it still doesn't work for everyone.
- Category images: Set inside the category's edit page, in a similarly labeled description field tied to that category's banner image.
- Homepage carousel: Each carousel slide has its own alt text field inside the Carousel widget settings, separate from the slide's caption text.
- Blog images: Set per-post, separate from both product and category images entirely.
The Confusion in Practice
The field is genuinely called "Description," with "(Image alt text)" in smaller text beside it. Sellers used to a separate "product description" field elsewhere in the same admin often skip this one, assuming it's redundant. It isn't. This field, and only this field, populates the rendered alt attribute your storefront serves to Google.
Leave it blank, and your product image has no alt text at all — regardless of how thorough your actual product description page copy is.
Bulk Fixing Alt Text
For a catalog with a few hundred products, BigCommerce supports bulk product edits through CSV export and re-import, which includes the image description field. For catalogs beyond that, the Catalog API (covered later in this guide) is the realistic path.
Filename SEO: BigCommerce Keeps What You Upload
This is the single biggest structural difference from Shopify, and it cuts both ways.
The URL Keeps Your Filename
Upload IMG_2025_032.jpg, and that exact string lives in your product's image URL indefinitely. Upload mens-navy-running-shoes.jpg, and that keyword-rich filename becomes part of the URL Google crawls and indexes. BigCommerce does not rename or replace it the way Shopify does.
There's No Rename Button
Once an image is attached to a product, you cannot edit its filename in place. Fixing a bad one means deleting the image and re-uploading a correctly named replacement — the same constraint you'd hit on Squarespace or WooCommerce.
The Pre-Upload Workflow
- Rename the file on your computer before uploading it anywhere in BigCommerce's admin.
- Use the formula:
[product-type]-[color-or-material]-[key-feature].jpg, hyphens only, all lowercase. - Keep it to 3–6 meaningful words —
mens-navy-running-shoes.jpg, not a ten-word keyword stuffing attempt. - Only then upload it through the product's Images tab.
Bulk Renaming via CSV
For a catalog with existing bad filenames, BigCommerce's product CSV export includes image URLs. You can't rename in place through the CSV directly. Exporting first does give you a full inventory of which products need new images. Use that inventory to prioritize your highest-traffic products, rather than attempting a full-catalog rename in one pass.
Squarespace shares this same filename-preservation quirk. Squarespace Image SEO: The Complete Guide covers the identical pre-upload discipline in more depth, and the naming formula applies just as directly here.
The BigCommerce Image CDN: cdn11, WebP, and imbypass
BigCommerce serves product images through its own CDN, visible in image URLs on the cdn11.bigcommerce.com domain.
Format Negotiation
The CDN dynamically serves WebP to browsers that support it, whenever doing so produces a smaller file. The URL itself often still shows the original extension, like .jpg. This happens automatically — you don't configure it.
The imbypass Parameter
Some product image URLs include an imbypass=on query parameter. This selectively disables the CDN's on-the-fly optimization for that specific image. It's most commonly used for high-resolution zoom images, where you want the full, unoptimized file served rather than a resized version.
When to Layer a Custom CDN
BigCommerce's own CDN handles standard resizing and format negotiation well for most stores. Consider adding a service like imgix or ImageEngine on top only for transformations BigCommerce's own URL parameters don't support. That means things like smart cropping around a product's focal point, or art-directed image variants per breakpoint. For most stores under a few thousand SKUs, this is unnecessary complexity. For a broader comparison of when a dedicated image CDN earns its cost, see Image CDN for E-commerce: A Complete Comparison.
Responsive Images in Stencil: getImage vs. getImageSrcset
Stencil themes handle responsive images through Handlebars helpers in the theme's template files, not through a setting you toggle in the admin.
The Two Helpers
{{getImage}} outputs a single image URL at one specified size — useful for a fixed-size thumbnail, but not responsive on its own. {{getImageSrcset}} is the newer helper, built specifically to generate a full srcset string. It lets the browser choose the right size for the visitor's screen and pixel density.
Configuration Options
{{getImageSrcset}} accepts a use_default_sizes=true flag, which lets BigCommerce pick a standard set of sizes automatically. Alternatively, a theme developer can specify explicit width values for full control over exactly which sizes get generated.
How to Audit Your Theme
Right-click a product image on your live storefront and inspect the rendered <img> tag. If you see a srcset attribute listing multiple image URLs at different widths, your theme is using getImageSrcset correctly. If you see only one image URL with no srcset, your theme is still using the single-size getImage helper. That's likely an older custom Stencil build, and it's serving one fixed size to every device regardless of screen.
Cornerstone, BigCommerce's official base theme, has used srcset-based responsive images since its 4.0 release. Older custom themes built before that update may not have been upgraded. For the underlying mechanics of how srcset and sizes actually work, see Responsive Images and srcset: The SEO Guide.
Multiple Product Images: Order, Thumbnails, and the Primary Image
Product image order isn't cosmetic — it determines what shoppers see first and what data feeds get.
Gallery Order
Images display in your product gallery in the order set inside the product's Images tab, controlled by a sort_order value. Drag-and-drop reordering in the admin updates this value directly.
The Primary Image
The first image in that sort order becomes the product's primary image. It's the one that populates your Google Merchant Center feed, social share previews, and category page thumbnails. Getting this sequencing right matters more than most sellers realize, since a poorly chosen primary image affects every downstream surface at once.
Sequencing for SEO
Lead with the clearest, most representative product shot — not a lifestyle image or a packaging photo. Follow it with detail shots, alternate angles, and size or scale references in that order. Each image still needs its own alt text; sequencing them well doesn't reduce that requirement.
Structured Data: What Cornerstone Ships and What's Missing
If you're on Cornerstone or a Cornerstone-derived theme, basic Product schema markup is already present in your page's JSON-LD. This replaces the older microdata approach BigCommerce used previously.
What's There
Product name, price, and availability are typically included by default in Cornerstone's JSON-LD output.
What Varies
Enhanced properties like aggregateRating and brand are often missing or incomplete, depending on your theme version and whether you've customized the product template. ImageObject completeness — specifically, whether your schema includes the image at multiple aspect ratios rather than a single reference — varies the same way.
How to Audit and Extend
Use Google's Rich Results Test on a live product page to see exactly which schema properties are present. If ImageObject or aggregateRating are missing and matter for your catalog, you have two paths. Customize your Stencil theme's product template directly, if you have developer access. Or use a schema-focused app from the BigCommerce marketplace if you don't. Product Image Schema and Structured Data covers the specific JSON-LD structure worth adding for multi-aspect-ratio image objects.
The BigCommerce Image Sitemap
BigCommerce automatically generates an XML sitemap at yoursite.com/xmlsitemap.php, updating it whenever you add, remove, or change products.
What's Included
Product pages in this sitemap include their associated images inline. This happens without any configuration on your part.
Verifying Category and Blog Coverage
Visit your sitemap URL directly and search for a category or blog post you've recently published. If products are consistently included but a specific category or blog image is missing, check the page's visibility setting in the admin. Hidden or unpublished pages don't appear in the sitemap, regardless of what images they contain.
Submitting to Search Console
Add /xmlsitemap.php as a sitemap URL inside Google Search Console's Sitemaps report. A known Search Console quirk sometimes shows a "Couldn't fetch" status on BigCommerce sitemaps that are actually working correctly. Check the Coverage report for actual indexed pages before assuming the sitemap itself is broken.
For a deeper look at what makes an image sitemap functionally useful versus just present, see The Complete Guide to Image Sitemaps for SEO.
Lazy Loading: Native vs. Legacy JS, and the LCP Trap
Stencil themes lazy-load images below the fold by default, and how they do it has shifted over time.
The Legacy Approach
Older Cornerstone versions relied on a JavaScript library (lazysizes) to handle lazy loading, rather than the browser's native mechanism. This created a specific, documented problem. A product page's main image sometimes wasn't requested until the JavaScript itself finished loading and executing, adding real delay before the image even started downloading.
The Native Approach
Newer Cornerstone versions have moved toward the native loading="lazy" HTML attribute, which browsers handle without any JavaScript dependency. This removes the JS-execution delay entirely for images using it.
Identifying and Preloading Your LCP Image
Run your product or category page through PageSpeed Insights to see which image it flags as your Largest Contentful Paint candidate. If that image is being lazy-loaded, whether through the old JS method or native loading="lazy", remove the lazy-load attribute from it in your theme's template. Then add a <link rel="preload"> hint for it in your page's head.
Category and Brand Page Images
Category and brand pages carry their own images: header banners, category thumbnails. They get less optimization attention than product images, despite being just as indexable.
How They Get Indexed
Category and brand pages are included in the same automatic sitemap as products, and their images are crawled the same way. There's no separate technical barrier to indexing them.
Alt Text for Header Banners
Category header banners have their own description field, set on the category's edit page, functioning identically to the product image alt text field. It's commonly left blank, since sellers focus their alt text effort almost entirely on individual product images and forget the category page wrapping them.
Blog Image SEO on BigCommerce
BigCommerce's built-in blog is a separate content type from products and categories, with its own image handling.
Alt Text UI
Each image inserted into a blog post through the content editor has its own alt text option. You set it through the editor's image insertion dialog, not a separate description field.
Featured Image Handling
A blog post's featured image is set separately from any inline images within the post body. It's the one used for the post's thumbnail on your blog index page and its social share preview. Both need their own alt text — setting one does not populate the other.
The B2B and Wholesale Angle
BigCommerce's customer-group pricing features, common on B2B and wholesale stores, create image and feed considerations product-only stores don't face.
Gated Product Images
Some B2B stores hide entire products behind a login wall for exclusive or negotiated-price items. A fully gated product is invisible to Google's crawler, images included — there's no partial indexing of a page requiring authentication.
Merchant Center and Rich Pins Accuracy
For stores using customer-group pricing, Google's crawler only sees the public, logged-out price and product visibility. Submit your Merchant Center feed using public retail pricing, not wholesale customer-group pricing. Keep the product page itself publicly visible, even if the negotiated price requires login to see. Google only indexes what an anonymous visitor sees.
Customer-Group-Specific Images
Some catalogs show different product images to different customer groups — a common setup for private-label or co-branded catalogs. Only the image visible to a logged-out visitor gets indexed and appears in Google Images. Plan your default, public-facing image accordingly.
API and Bulk Operations for Large Catalogs
Past roughly a thousand SKUs, manual alt text and filename fixes stop being realistic. BigCommerce's Catalog API is built for exactly this scale.
Updating Alt Text Programmatically
The v3 Catalog API's product images endpoint lets you update the description field — the same field that renders as alt text. A script can update it across your entire catalog, rather than opening each product individually.
Reordering Images
The same endpoint's sort_order field controls gallery order and which image is treated as primary. Lowering one image's sort order automatically reorders the images around it, which matters if you're scripting a bulk resequencing pass.
Retrieving CDN URLs
The API returns each image's live CDN URL directly. That's useful for auditing which products still have generic camera filenames baked into their live URLs, without manually opening every product page.
For sellers without in-house development, fixing filenames and alt text before the initial upload avoids this API work for a first pass. Scripted updates still matter later, for correcting an existing catalog at scale.
Theme Choice Matters
Not every Stencil theme handles images equally, and this is worth checking before you buy one.
Cornerstone (Official Base Theme)
Cornerstone gets BigCommerce's own ongoing performance work first. Native lazy loading, srcset-based responsive images, and JSON-LD schema all landed here before spreading to other themes.
Paid Marketplace Themes
Paid themes vary widely. Some are Cornerstone forks that inherited its image handling. Others are older, independently built themes that predate getImageSrcset and still rely on the single-size getImage helper.
Custom Stencil Builds
A fully custom theme's image handling is only as good as whoever built it made it. Before committing to a custom build or a paid theme purchase, ask the developer or vendor directly. Does the theme use getImageSrcset? Native loading="lazy"? Is Product schema present in the templates? These are answerable, concrete questions, not vague performance claims.
Common BigCommerce Image SEO Mistakes
Uploading images far larger than needed. BigCommerce doesn't downscale aggressively on upload. A 6000px-wide camera original stays close to that size unless you resize it yourself first.
Missing alt text on carousel and hero images. These sit in a separate settings panel from product images, and sellers who diligently fill in product alt text often skip the homepage carousel entirely.
Forgetting category and brand page images. Alt text effort concentrates on individual products; the category banners wrapping them are frequently left blank.
Hardcoded image URLs inside product descriptions. Pasting an image directly into a product's rich-text description, rather than using the dedicated Images tab, bypasses the alt text field entirely and often breaks if that image is ever moved or deleted.
How to Verify Your Image SEO Is Actually Working
View source for the real rendered output. Right-click any live product image and choose Inspect to see the actual alt attribute and the filename baked into the src URL — not what you assume you set in the admin.
Run PageSpeed Insights on product and category pages. It identifies your LCP image directly and flags whether lazy loading is delaying it.
Check Search Console's Coverage report, filtered by image URLs. This shows which of your image URLs Google has actually crawled and indexed, separate from whether they simply exist in your sitemap.
Frequently Asked Questions
Does BigCommerce compress images automatically? No. BigCommerce stores and serves whatever resolution you upload, and generates resized versions for different display contexts, but it does not aggressively compress the original file. A 15MB product photo stays a 15MB product photo unless you compress it yourself before upload.
Is BigCommerce better than Shopify for image SEO? Neither platform wins outright. BigCommerce keeps your original filename in the image URL, which Shopify does not, giving you a real SEO advantage there. Shopify auto-compresses images more aggressively by default. Both require you to write your own alt text — neither automates that step.
Where do I add alt text to a BigCommerce product image? In the product's Images tab inside the admin, click an image and look for the field labeled Description (Image alt text). That literal field, not the product's main description box, is what BigCommerce renders as the image's alt attribute on your storefront.
Can I rename a BigCommerce product image after uploading it? Not in place. BigCommerce's image URL is built from the filename you uploaded with, and there's no rename button for an existing image. Fixing a bad filename means deleting the image and re-uploading a correctly named version.
Do I need a custom CDN if I'm already on BigCommerce? Usually not for delivery speed — BigCommerce's own CDN handles format negotiation and resizing well for most stores. Consider a layered CDN like imgix or ImageEngine only if you need advanced transformations BigCommerce's URL parameters don't support, such as smart cropping or art-directed variants.
Does BigCommerce show Rich Pins or Merchant Center listings correctly for B2B pricing? Only if you configure your feed to submit public retail pricing, not customer-group wholesale pricing. Google's crawler sees whatever price is visible to a logged-out visitor. Gate the negotiated price behind login, but keep the product and its images publicly visible so Google can index them.
Conclusion
BigCommerce gets you further than most platforms before you touch a single setting: clean architecture, an automatic sitemap, and Product schema baked into Cornerstone. What it won't do is name your files, write your alt text, or notice that your homepage carousel has no descriptions at all. Those stay entirely your responsibility, whether you're running a five-product storefront or a ten-thousand-SKU B2B catalog.
Start with filenames, since BigCommerce makes that decision permanent the moment you upload. Then work through alt text — product images first, category and carousel images second, since those get skipped most often. For catalogs large enough that manual fixes aren't realistic, the Catalog API and bulk CSV tools exist precisely for this.
For stores managing image SEO across a large catalog without custom API scripting, ImgSEO generates SEO-ready filenames and alt text for entire upload batches. It does this before they ever reach your BigCommerce admin. For the full foundational picture of image SEO beyond any single platform, see the Image SEO Guide.
