If you run a BigCommerce store and feel like Google doesn't rank you the way it should, you're probably right. BigCommerce ships with strong SEO defaults but a handful of platform quirks — duplicate category URLs, faceted navigation traps, and schema gaps in custom themes — that erode rankings if left alone. RankCart audits the live store, not the admin settings, and flags every issue specific to your BigCommerce setup.
This guide walks through every issue we see in the typical BigCommerce audit — what it is, why it costs you traffic, and exactly how to fix it. Most of these are afternoon-sized tasks; a few need a developer. None of them require an SEO agency.
The fast version: BigCommerce SEO fixes — the URL traps and schema gaps that cost you traffic.
What's actually wrong with most BigCommerce stores
Every ecommerce platform has its own SEO blind spots. BigCommerce is no exception. The patterns below show up on the majority of stores we audit — and the platform itself doesn't surface them in any admin dashboard, so they sit there leaking traffic until someone audits the live site.
1. Duplicate category URLs from /categories/* and /c/*
Why this matters: BigCommerce supports both legacy /categories/
How to fix it: Decide on one canonical URL pattern in Storefront → Web Pages → URL settings. Set canonical tags consistently, and 301-redirect the secondary pattern. RankCart flags every duplicate path pair.
2. Faceted navigation creating thin / duplicate pages
Why this matters: Filters like /c/shoes?attr_color=red&attr_size=10 generate thousands of crawlable URL combinations, all near-duplicate. Crawl budget collapses on a large catalog.
How to fix it: Use the Faceted Search settings to exclude facets from indexable URLs, or block filter parameters in robots.txt. For facets that should rank (e.g. /shoes/red), build them as standalone category pages with unique copy.
3. Stencil theme not emitting full Product schema
Why this matters: BigCommerce's Cornerstone theme emits Product schema with offers and reviews. Custom Stencil themes often strip this during development, especially after a designer-led refresh.
How to fix it: Audit the rendered HTML for