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.
Who this is for: Mid-market and enterprise brands, B2B sellers, and stores running BigCommerce Standard, Plus, Pro, or Enterprise with custom Stencil themes or headless storefronts.
These are the high-impact, low-effort BigCommerce fixes RankCart finds on most stores. Ship the easy ones first — they typically take an afternoon and recover 10-30% of lost organic traffic.
Why it matters: BigCommerce supports both legacy /categories/<slug> URLs and shorter /c/<id>-<slug> URLs. If both resolve, Google sees duplicate content. Same for products with /products/* and /p/*.
Fix: 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.
Why it 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.
Fix: 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.
Why it 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.
Fix: Audit the rendered HTML for <script type="application/ld+json"> on a sample PDP. If missing or partial, edit templates/components/products/product-view.html and add a complete schema block. Validate with Google's Rich Results Test.
Why it matters: BigCommerce's default <title> tag is just the product name. That ignores buying intent and brand recognition — both of which compound CTR.
Fix: Storefront → Web Pages → Page settings, or per-product under Storefront tab → Page title. Use {Product} — {Brand} | {Category}. For bulk edits, use the Products CSV export/import.
Why it matters: Some BigCommerce stores end up with /checkout, /account, /cart, and /login URLs indexed — usually after a theme update that broke the default robots.txt overrides.
Fix: Storefront → Robots.txt. Add Disallow rules for /checkout, /account, /cart, /login, /forgot-password, and any custom utility paths. Verify with Google's robots.txt tester.
Why it matters: BigCommerce Multi-Storefront lets you run multiple branded storefronts off one backend. Without unique copy and proper hreflang, identical content competes against itself.
Fix: For each storefront, write region-specific category and product copy where it matters. Use hreflang tags via theme.html to declare each storefront's locale. RankCart audits each storefront separately and flags content overlap.
Why it matters: BigCommerce's themes display visual breadcrumbs but don't always emit BreadcrumbList JSON-LD. Without it, you lose the breadcrumb-style search snippet that boosts CTR.
Fix: Add <script type="application/ld+json"> with @type BreadcrumbList in product-view.html. Each item: position, name, item URL. Validate with Google's Rich Results Test.
A complete sequence — run it top-to-bottom for a full BigCommerce SEO overhaul, or pick the steps that match the gaps in your audit.
Plug your storefront URL into RankCart. Note the baseline score and the top 10 critical issues. If you run multi-storefront, run an audit per storefront — each one accumulates issues independently.
Decide between /categories/* + /products/* or /c/* + /p/*. The legacy long form is usually preferable for SEO (more readable, more keyword density). Set 301 redirects from the secondary pattern using BigCommerce's Storefront → Web Pages → 301 redirects.
Storefront → Web Pages → URL settings. Decide which filter combinations should be indexable (color, brand) vs. ignored (sort, view, page). Add canonical tags pointing filtered URLs back to the parent category, or block parameters in robots.txt.
Open product-view.html in your Stencil theme. Confirm Product schema with @type, name, image, description, sku, brand, offers (price, priceCurrency, availability, url), and aggregateRating. Add BreadcrumbList. Deploy and validate with Google's Rich Results Test.
Export your product list via Storefront → Products → Export. Sort by revenue (or order count). Rewrite the top 50 product titles to {Product} — {Key Attribute} | {Brand} and meta descriptions to 145-155 chars with a clear value prop. Re-import.
Storefront → Robots.txt. Add Disallow rules for /checkout, /account, /cart, /login, /forgot-password, /search, and any other non-canonical utility paths. Save and validate via Google Search Console's robots tester.
If you run multiple storefronts, edit each storefront's theme.html and emit hreflang tags listing every alternate. Use ISO codes (en-US, en-GB, en-AU). Validate with Search Console's International Targeting report.
BigCommerce auto-generates /xmlsitemap.php for each storefront. In Google Search Console, add a property per storefront, verify ownership, and submit each sitemap individually. Monitor the Coverage report weekly for 30 days.
Real questions from real BigCommerce merchants. Answered without the fluff.
More than most platforms. BigCommerce ships with clean URLs, automatic XML sitemap, customizable robots.txt, server-side rendering, and Product schema in the Cornerstone theme. The gaps appear in custom Stencil themes, multi-storefront setups, and faceted-navigation configurations.
BigCommerce supports both. /products/<slug> is the legacy long form; /p/<id>-<slug> is the shorter modern form. If both resolve on your store, you have duplicate content. Pick one pattern, redirect the other. The long form usually performs better for SEO because of richer URL semantics.
The Cornerstone theme emits Product schema by default. For custom themes, add JSON-LD blocks to product-view.html, category.html, and base.html. Most BigCommerce stores need to add BreadcrumbList, FAQPage on product pages with FAQs, and Review schema on stores with native reviews.
If you sell physical products and your margins support paid traffic, yes. BigCommerce has a native Google Shopping integration that pushes product feeds to Merchant Center. Even if you don't run paid ads, having products in Merchant Center helps with the free shopping listings now powered by the Shopping graph.
Three usual reasons: (1) the description is empty or hidden by the theme, (2) faceted navigation is splitting authority across thousands of filtered URLs, (3) the page title is just the category name without modifiers. Fix all three. Category pages can rank for high-intent shoulder queries.
Yes — BigCommerce has first-class headless support via Storefront API and BigCommerce for WordPress. The SEO concern is the same as any headless setup: server-render every meta tag, canonical, and JSON-LD block. Don't rely on client-side hydration for SEO-critical elements.
BigCommerce gives you more native SEO controls — flexible URL structures, granular robots.txt, server-side rendering — without a theme rebuild. Shopify is more constrained but more polished by default. For brands above $1M GMV with technical resources, BigCommerce's flexibility wins. For lean teams shipping fast, Shopify wins.
RankCart audits your live BigCommerce store, finds every issue from this guide (plus a hundred we didn't list), and tells you which fix unlocks the most missed revenue first.