BigCommerce SEO: What It Gets Right and Where It Slips

Aug 10, 2026 · Platform SEO

Last spring I helped a 4,000-SKU apparel retailer move off Shopify, and the deciding factor wasn't apps or pricing — it was URLs. Shopify locks every product into /products/ and every category into /collections/, and this client had category pages ranking on legacy URLs they couldn't replicate. BigCommerce let them keep the exact structure. Three months post-migration, organic revenue was up 18%, mostly because nothing broke.

That story captures what BigCommerce SEO is like in practice: the platform gets the fundamentals right in ways its competitors don't, and then leaves a couple of sharp edges you need to know about before they cut you.

Where BigCommerce SEO is genuinely strong

Out of the box, BigCommerce handles more technical SEO correctly than any other major SaaS cart I work with. The two standouts:

• Fully customizable URLs. Under Settings › URL Structure you can define patterns for products, categories, and pages — no forced prefixes. You can use /category/product-name/ or flat /product-name/, whichever matches your existing structure. If you're comparing against Shopify's rigid paths, this alone is worth reading the Shopify SEO guide side by side.
• Automatic canonical tags. Every product and category page gets a self-referencing canonical tag without configuration, which soaks up most of the duplicate-URL risk from sorting parameters and tracking codes.

Here's how the automatic-versus-manual split shakes out:

One historical note: BigCommerce used to push AMP support in its Stencil themes. That's deprecated now, and if you're on an older theme still referencing AMP templates, remove them — they're dead weight.

The faceted search problem nobody warns you about

Product Filtering (available on Pro plans and up) is BigCommerce's faceted navigation. It's great for shoppers and dangerous for crawl budget. Every filter combination — brand, size, color, price band — generates a parameterized URL, and a category with six filter types can spawn thousands of crawlable variations.

The canonicals point back at the clean category URL, so you usually won't see duplicate content penalties. What you will see is Google spending its crawl budget on ?brand=nike&size=10&color=red pages instead of your new products. On stores above a few thousand SKUs, I've watched indexing of new products lag by weeks because of this.

The fix is direct because BigCommerce lets you edit robots.txt: go to Settings › Website › Search Engine Robots and disallow the filter parameters, for example Disallow: /*?brand= and similar patterns for each facet. Keep one or two high-value facets crawlable only if you've deliberately built landing pages around them.

Settings to change in your first week

1. URL Structure. Settings › URL Structure — decide on flat product URLs versus category paths before launch. Changing later means a redirect project.
2. 301 redirects. Settings › Redirects lets you bulk-import via CSV. If you're migrating, map every old URL here on day one, not after traffic drops.
3. WWW consolidation. In the domain settings, pick www or non-www and let the platform 301 the other — then never touch it again.
4. Title templates. BigCommerce auto-fills page titles from product names, which produces flat, keyword-thin titles at scale. Override the important ones manually in each product's SEO section (bottom of the product edit page).

Speed on Stencil themes

BigCommerce serves everything through Akamai's CDN, so raw delivery is fast. The problems come from theme weight. Stencil themes vary enormously — Cornerstone (the free default) is reasonably lean, but many marketplace themes ship with three carousel libraries and unoptimized hero videos.

Practical guidance: audit your theme's third-party scripts in Storefront › Script Manager and remove anything you don't actively use — abandoned chat widgets and old pixel tags are the usual suspects. Compress product images before upload; the platform serves WebP but won't rescue a 4 MB source file. If your Core Web Vitals are failing, the culprit is almost always the theme plus scripts, not BigCommerce's infrastructure.

The rough edges: blog, out-of-stock pages, pagination

Three smaller weaknesses come up in nearly every BigCommerce engagement, so plan for them:

• The built-in blog is thin. No categories, no tags worth the name, awkward image handling, and limited layout control. If content marketing is central to your strategy, most serious BigCommerce merchants run WordPress on a subdirectory or subdomain for the blog and keep BigCommerce for the catalog. It's an extra system to maintain, but fighting the native blog is a slower kind of pain.
• Out-of-stock and discontinued products need a policy. BigCommerce will happily keep serving a dead product page forever, or you can delete it and serve a 404. Neither default is right: a product that's gone for good should 301 (via Settings › Redirects) to its closest replacement or parent category, preserving whatever links and rankings the page earned. Make this part of your merchandising workflow, not an annual cleanup.
• Category pagination is crawlable by default. Page 2 and beyond of large categories get indexed with self-referencing canonicals. That's actually correct behavior since Google retired rel="prev/next", but it means your paginated pages need real titles — check that your theme appends page numbers rather than serving fifty identical titles per category.

Structured data without an app

Cornerstone and most modern Stencil themes emit Product schema (price, availability, review ratings) automatically. Verify it with Google's Rich Results Test rather than assuming — some marketplace themes emit malformed JSON-LD. For anything beyond products — Organization, FAQ, BreadcrumbList — inject JSON-LD through Script Manager or directly in the theme's templates/layout/base.html if you're comfortable editing Stencil.

So, should you build on it?

BigCommerce is my default recommendation for catalogs between roughly 500 and 50,000 SKUs where URL control and B2B features matter. Skip it if you're a five-product brand (Shopify's app ecosystem will serve you better) or if you need deep customization of checkout logic (look at Magento, and bring a developer).

Whatever you launch on, verify the outcome instead of trusting the defaults: run a full crawl with WebsiteChecker.Tech after go-live and again after any theme change. The faceted-URL bloat and redirect gaps described above show up in a crawl report long before they show up in your revenue.