BigCommerce SEO

TL;DR — BigCommerce is a hosted store platform (like Shopify) that does a lot of SEO for you automatically: it builds your sitemap, sets up redirects when you change a URL, lets you edit your robots.txt, and adds product schema. The parts you still have to handle yourself are filter pages (faceted navigation), multi-language/multi-country setups, and review stars in search.

What “BigCommerce SEO” means

BigCommerce is a SaaS ecommerce platform — you pay a monthly fee and they host your store, handle servers, security, and updates. You don’t install it on your own hosting the way you would WordPress. In that sense it’s a direct competitor to Shopify.

“BigCommerce SEO” is just the regular SEO work — getting your products and category pages found, crawled, indexed, and ranked — applied to a store that happens to run on BigCommerce. The reason it’s worth its own guide is that BigCommerce makes some choices for you, and you need to know which boxes it already ticks and which it leaves empty.

What BigCommerce does for you automatically

• Sitemap. BigCommerce builds and keeps an XML sitemap up to date as you add or change products. You just submit it to Google.
• Redirects. If you rename a product or change its URL, BigCommerce automatically creates a 301 redirect from the old URL to the new one, so links and rankings don’t break.
• Clean URLs. Unlike Shopify, BigCommerce doesn’t force /products/ or /collections/ into your URLs. You can have a tidy /blue-widget/ if you want.
• Robots.txt. You can edit your robots.txt right in the BigCommerce admin. (Shopify doesn’t let you do this natively.)
• Product schema. The default theme (Cornerstone) adds the behind-the-scenes “structured data” that can give you rich results in Google.
• HTTPS and a CDN. Every plan includes SSL and a global content delivery network (Akamai) so your images load quickly worldwide.

What you still have to do yourself

• Fill in your SEO fields. Page titles and meta descriptions for your home page, products, and categories. BigCommerce gives you the boxes; you write the copy.
• Filter (faceted) pages. When shoppers filter by color, size, or price, each combination can create a new URL. Left alone, this floods Google with near-duplicate pages. BigCommerce does not clean this up for you.
• Review stars. The default schema covers product details but not star ratings — you need a reviews app (like Yotpo or Stamped) or custom code for those.
• Multiple countries/languages. If you run separate storefronts per country, the tags that tell Google which version to show (hreflang) are not added automatically.

The thing most people get wrong

People assume that because BigCommerce has “good SEO,” they don’t need to do anything. The automatic parts are real and genuinely helpful — but the two things that most often hold an ecommerce store back, filter pages and slow loading, are exactly the parts BigCommerce leaves to you. Don’t confuse a strong starting point with a finished job.

Want the practitioner version — URL structure options, the faceted-nav canonical strategy, the Stencil-vs-Catalyst decision, and the hreflang Akamai gotcha? Switch to the Advanced tab.

TL;DR — BigCommerce ships the highest native SEO floor of any hosted SaaS platform: editable robots.txt, fully custom URL structures (no forced prefixes), auto-generated and self-updating XML sitemaps, automatic 301s on URL change, and JSON-LD Product + BreadcrumbList in Cornerstone. The work it leaves you is what actually scales: faceted-navigation canonical/noindex strategy, multi-storefront hreflang (watch the Akamai geo-redirect), review schema, and Core Web Vitals. Stencil (server-rendered Handlebars) vs Catalyst (Next.js headless) sets your performance ceiling — and migrating between them is where redirect maps get lost.

The frame: what’s automatic vs what’s yours

Most BigCommerce SEO content is either a generic checklist (“write your meta descriptions!”) or a pitch for a BigCommerce agency. Neither tells you the thing that actually matters: BigCommerce gets an unusual amount right at launch, and the remaining gaps are specific and predictable. Sort everything into two buckets and the platform stops being mysterious.

Right by default: XML sitemap, canonical tags per page type, editable robots.txt, automatic 301s on URL change, full URL-structure control, Akamai CDN + Image Manager, Cornerstone JSON-LD (Product, BreadcrumbList, Organization), SSL.

Yours to do: faceted-navigation canonical + noindex strategy, multi-storefront hreflang, review/AggregateRating schema, pagination robots.txt audit, blog/content strategy, and Core Web Vitals on Stencil (app JS bloat + unoptimized source images).

URL structure

URL options live at Store Setup → Store Settings → URL Structure. You get Short (slug only), Long (adds /products/, /categories/, /pages/), SEO Optimized (removes prefixes), SEO Optimized (Category) (injects the first parent category into the product URL), and Custom (placeholder-based, using %productname%, %category%, %categoryname%, %sku%).

The genuinely interesting one for duplicate content is SEO Optimized (Category): BigCommerce picks the first category a product is placed in and won’t generate duplicate URLs for a product listed under multiple categories. That’s a real duplicate-content win — but confirm the behavior on your own store before relying on it.

Here’s the honest part, though: this is the BigCommerce-vs-Shopify talking point everyone leads with, and it’s the least important difference. Shopify forces /products/ and /collections/; BigCommerce doesn’t. Google has said repeatedly that URL structure is a minor ranking signal. eComOne put it well in their comparison: “the nuts and bolts of on-page SEO in both platforms are easy to manage, though BigCommerce has perhaps a slight edge because unlike Shopify, it doesn’t insert any prefixes before your URLs. However, Google has said repeatedly that URL structure is a minor signal.” Pick SEO Optimized, move on, and spend your energy on faceted nav and speed.

XML sitemap and robots.txt

BigCommerce auto-generates a sitemap and keeps it current as your catalog changes. The path depends on your stack: legacy Stencil serves /xmlsitemap.php; Catalyst serves /sitemap.xml. On Catalyst, BigCommerce “automatically redirects any requests for the legacy Stencil sitemap /xmlsitemap.php to /sitemap.xml,” and Catalyst “fetches the sitemap index from BigCommerce by making a request to the canonical URL of the channel.” The sitemap covers products, categories, brands, and content pages; hidden menu pages are excluded by default, and BigCommerce is explicit that “third-party systems generating content” need their own separate sitemaps.

robots.txt is editable directly in the admin under Settings → Website → Search Engine Robots — a real advantage over Shopify, which gives you no native control. BigCommerce combines your custom rules with its system defaults.

The gotcha worth a five-minute audit: practitioners repeatedly report BigCommerce’s default robots.txt blocking paginated category pages (?page=2 and beyond). On a large catalog that quietly keeps page 2+ of your categories out of the index. Don’t assume the defaults are safe — crawl your own store and look at what’s disallowed.

Meta tags and on-page fields

SEO fields live per object: home page (Store Settings → SEO), products (Products → Edit → Other Details → SEO), categories (Product Categories → Edit → SEO), and blog posts. You get Page Title, Meta Description, Meta Keywords, and a Custom URL field.

Two clarifications that save confusion:

• Meta Keywords is dead for ranking. BigCommerce’s own glossary says it plainly: “Meta keywords tag is defunct, as it was originally intended for search engines to determine what the content of a page was about, but it was severely abused by spammers and search engines now almost entirely ignore it.” Don’t waste time on it.
• “Search Keywords” ≠ Meta Keywords. BigCommerce has a separate Search Keywords field that feeds its internal site search, not Google. People conflate the two constantly. Search Keywords is worth filling in — for on-site search, not rankings.

301 redirects

This is one of BigCommerce’s quiet strengths. 301 redirects are created automatically whenever you change the name or URL of a product, category, or page (you can opt out per item by unchecking “Create redirects for old product URLs”). There are two kinds:

• Dynamic — BigCommerce updates the destination automatically if the target URL later changes. Use these for internal moves.
• Manual — you enter a fixed destination string; if that target later changes, the redirect breaks until you fix it by hand.

The manager lives at Marketing → 301 Redirects and supports bulk CSV import, which is what you’ll use for a migration redirect map. Prefer dynamic redirects for anything internal so you’re not maintaining a brittle list.

Structured data / schema

Cornerstone (Stencil’s default theme) emits JSON-LD for Product (name, image, description, SKU, nested brand, Offers with price/currency/availability), BreadcrumbList, and basic Organization — no developer work required. JSON-LD is what Google recommends over microdata, so the default is the right format.

What’s missing is the high-value stuff: review/AggregateRating schema is not included by default. As SeoProfy puts it, “BigCommerce includes basic product schema, but doesn’t add review markup by default.” You get review stars in search via a reviews app (Yotpo, Stamped) or custom JSON-LD through Script Manager. FAQ and VideoObject schema are similarly DIY.

One Stencil quirk: the schema is only as complete as the data on the page. If a product has no brand displayed, the brand property won’t appear in the schema. Fill the fields if you want the markup.

On Catalyst, structured data is “composable JSON-LD through reusable TypeScript functions” — more maintainable than Stencil’s Handlebars templates if you have the engineering capacity.

Faceted navigation — the #1 problem

This is where BigCommerce stores actually lose. Filter and sort combinations generate unique, crawlable URLs with no automatic canonicalization back to the parent category. NetProfitMarketing describes the failure mode bluntly: every filter “can generate a new URL, resulting in an exponential spike in… crawlable pages,” diluting authority and burning crawl budget. And BigCommerce gives you no native fix — OuterBox notes “there still is no easy way to do this without editing theme files directly.”

So you classify parameters and act per type. My working rule set:

Implementation is theme-level canonical overrides in Stencil templates, or Script Manager JavaScript injection. Two principles to keep straight:

• robots.txt blocks crawling, not indexing. A URL blocked in robots.txt can still be indexed if something links to it — and Google can’t see your canonical or noindex because it never read the page. Pair parameter rules with on-page canonical + noindex for real control.
• Don’t noindex your paginated pages. Google’s ecommerce guidance is to “give each page a unique URL” and “assign each page its own canonical URL rather than using the first page as canonical.” noindex belongs on “filter variations or alternative sort orders,” not on page 2 of a category. BigCommerce still emits rel="next"/rel="prev", which Google stopped using in 2019 — harmless, just not a signal.

(The platform-agnostic deep dive lives in the faceted navigation cluster; the canonical mechanics are in canonicalization.)

CDN, images, and Core Web Vitals

Every store ships with Akamai’s global CDN free, plus Akamai Image Manager for on-the-fly WebP conversion and responsive resizing. Two caveats:

• WebP delivery depends on theme version — newer Stencil themes enable it; older Blueprint and some early Stencil versions don’t. Verify yours.
• The source image still matters. A 5 MB source PNG served as WebP is still a big file. Upload optimized sources; the CDN is not a substitute for image discipline. Images are typically 60–70% of a page’s total weight.

The default Akamai config is often loose — agencies report that tuning cache rules, enabling Brotli, and optimizing edge caching can cut TTFB by 30–50% (an agency estimate, but directionally right). The bigger Stencil performance killers are third-party app JavaScript bloat (every app injecting JS degrades INP and LCP — audit your installed apps) and unoptimized source images. Stencil also serves the original image file without automatic resizing in some configurations, which hurts LCP directly.

Stencil vs Catalyst — the trade-off that sets your ceiling

Stencil is the current server-rendered framework (Handlebars, rendered on BigCommerce’s infrastructure). 1Digital Agency describes it as “server-rendered by default. Every page is HTML on first byte” — which is great for crawlability. Cornerstone is the actively maintained default theme and is competitive on Core Web Vitals for moderate catalogs.

Catalyst is BigCommerce’s “open-source, composable, and fully-customizable headless commerce framework” — Next.js + React on the GraphQL Storefront API. BigCommerce markets a “Google Lighthouse score of 100” out of the box and the ability to “experiment and scale without affecting Core Web Vitals.” Treat the Lighthouse-100 as a baseline/demo number, not a production guarantee: real-world performance still depends on your bundle size, app JS, and image discipline.

Agency LCP benchmarks (estimates, not BigCommerce-official): Stencil ~1.8–2.5s, Catalyst ~0.8–1.5s.

A practical decision matrix:

• Stay on Stencil/Cornerstone if: mid-size catalog, limited Node/React expertise, Core Web Vitals already passing.
• Move to Catalyst if: you have Next.js capability, CWV is failing on Stencil despite optimization, you need complex frontend UI, or you’re running multi-brand at scale.
• Never migrate without: a complete redirect map, a Googlebot-accessible preview environment (set X-Robots-Tag: noindex or a robots.txt block on Vercel branch previews so they don’t get indexed), and a pre/post CWV benchmark.

The two classic migration failures, per 1Digital: “losing ranking authority through missing redirect maps or shipping JavaScript-heavy builds that worsen Core Web Vitals performance.” Both are avoidable; both are common.

International SEO and hreflang

BigCommerce does not generate hreflang automatically for multi-storefront setups. With one control panel driving multiple storefronts (each its own domain, language, currency) off a shared catalog, you get us.example.com/blue-widget/ and uk.example.com/blue-widget/ as near-duplicates needing bidirectional hreflang. You implement it via Script Manager JS, custom Stencil templates, or XML sitemap annotations.

Two things most “hreflang on BigCommerce” articles miss:

• Partial deployment is worse than none. As DigitalRoxy notes, “partial deployment is worse than no deployment because Google requires bidirectional confirmation across all storefronts before recognizing hreflang signals.” An unpaired set is discarded — you get the work with none of the benefit.
• The Akamai geo-redirect trap. Akamai redirects visitors by IP geo-location. Googlebot crawls from US IPs, so it gets redirected away from your international storefronts and can’t crawl them. The fix: “whitelist Googlebot’s published IP ranges” in Akamai Property Manager to bypass the geo-redirect. This single issue silently de-indexes entire international storefronts.

Standard hygiene still applies: use ISO codes (en-GB, not en-UK), keep HTTP/HTTPS and trailing slashes consistent, use region codes where needed (en-US, not bare en), and always include x-default. Validate with Aleyda Solis’s hreflang checker, GSC’s International Targeting report, and URL Inspection.

Blog and content SEO

BigCommerce has a native blog (Storefront Content → Blog) with posts, categories, tags, and meta fields. It’s adequate for a small catalog. It’s not a serious content platform: limited layout/CRO tooling versus WordPress, and historically some quirks worth verifying on your store (older reports of subdomain defaults and full-post listing pages; confirm current behavior rather than trusting old write-ups).

Two escape hatches when content is a real channel for you:

• WordPress + BigCommerce. BigCommerce’s WordPress plugin runs WordPress as the content frontend with BigCommerce as the commerce backend — you get Yoast/RankMath, custom post types, and real taxonomies while BigCommerce handles catalog and checkout.
• Headless CMS on Catalyst. Contentful, Prismic, or Contentstack give full content flexibility at the cost of implementation complexity.

Google Shopping / Merchant Center

BigCommerce has a native free “Ads and Listings on Google” app that syncs your catalog (product data, prices, availability, images) to Google Merchant Center for Shopping Ads and free listings, with automated updates. For finer feed control, the App Marketplace has third-party feed tools (FeedOps, DataFeedWatch, ExportFeed). For JS-driven “load more”/infinite scroll on category pages — which Googlebot won’t trigger — the Merchant Center feed and your sitemap are how products stay discoverable.

BigCommerce vs Shopify — the honest version

Both platforms rank just fine. BigCommerce’s genuine wins are editable robots.txt, no forced URL prefixes, and stronger built-in schema. Shopify’s genuine wins are a far larger SEO app ecosystem (640+ vs ~25) and slightly faster average out-of-box speed. The URL-prefix difference everyone argues about is a minor signal. Choose on the things that scale.

AI summary

A condensed take on the Advanced version:

• BigCommerce is a hosted SaaS ecommerce platform (like Shopify) with the highest native SEO floor of the hosted platforms.
• Automatic: XML sitemap (self-updating; /xmlsitemap.php on Stencil, /sitemap.xml on Catalyst), canonical tags per page type, editable robots.txt (Shopify can’t), automatic 301s on URL change (dynamic vs manual; bulk CSV import), fully custom URL structure (no forced prefixes), Akamai CDN + Image Manager, Cornerstone JSON-LD (Product + BreadcrumbList), SSL.
• URL structure is a minor ranking signal — the BigCommerce-vs-Shopify prefix debate is overrated; pick “SEO Optimized” and move on.
• You must do by hand: faceted-navigation canonical/noindex (the #1 duplicate-content + crawl-budget problem; no native fix), review/AggregateRating schema (needs an app or custom JSON-LD), multi-storefront hreflang, a pagination robots.txt audit (defaults may block ?page=2+), and Core Web Vitals.
• Don’t noindex paginated pages — give each its own canonical URL; noindex belongs on filter/sort variations.
• hreflang: entirely manual; partial deployment is worse than none; whitelist Googlebot’s IPs in Akamai or geo-redirect de-indexes your international storefronts.
• Stencil (server-rendered) vs Catalyst (Next.js headless) sets your performance ceiling. Catalyst markets Lighthouse 100 (a baseline, not a guarantee). Never migrate without a redirect map, noindexed preview env, and a CWV benchmark.
• Blog is basic — use the WordPress plugin or a headless CMS for serious content.

Official documentation

Primary-source docs from BigCommerce and Google.

BigCommerce

• Intro to SEO — BigCommerce’s own SEO overview.
• SEO Fields — where the title/description/URL fields live per object, and the Search Keywords distinction.
• Sitemaps — auto-generation and submission.
• Understanding the Robots.txt File — editing robots.txt in the admin.
• 301 Redirects — automatic redirects, dynamic vs manual, bulk import.
• Stencil Themes — the current theme framework.
• Cornerstone (GitHub) — the default reference theme source and release notes.
• Catalyst overview — the headless Next.js framework and its performance claims.
• Catalyst sitemap docs — how Catalyst serves and redirects the sitemap.
• Redirects API — programmatic redirect management.

Google

• Ecommerce pagination & incremental loading — unique URLs per page, noindex on filters not pagination.
• URL structure guidance — “create a simple URL structure” (and why it’s a minor signal).
• Product structured data — required/recommended Product fields.
• Structured data intro — JSON-LD recommended over microdata.

Quotes from the source

On-the-record statements from BigCommerce and Google, plus a few from the practitioners whose BigCommerce-specific findings shaped this guide. Each search-engine link deep-links to the quoted passage where the page supports it.

BigCommerce — Catalyst (official)

• “open-source, composable, and fully-customizable headless commerce framework” Jump to quote
• “Google Lighthouse score of 100” — a baseline/demo claim; verify against your own production build. Jump to quote
• “Experiment and scale without affecting Core Web Vitals.” Jump to quote

BigCommerce — Catalyst sitemap (docs)

• “automatically redirects any requests for the legacy Stencil sitemap /xmlsitemap.php to /sitemap.xml” Jump to quote
• “fetches the sitemap index from BigCommerce by making a request to the canonical URL of the channel” Jump to quote

BigCommerce — meta keywords (glossary)

• “Meta keywords tag is defunct, as it was originally intended for search engines to determine what the content of a page was about, but it was severely abused by spammers and search engines now almost entirely ignore it.” Jump to quote

Google — pagination & URL structure

• “Give each page a unique URL.” — Google ecommerce pagination guidance. Jump to quote
• “Apply noindex meta tags to filter variations or alternative sort orders” (not to paginated pages themselves). Jump to quote

Practitioners — BigCommerce-specific findings (relayed; confirm at source)

• “BigCommerce includes basic product schema, but doesn’t add review markup by default.” — SeoProfy. Source
• “There still is no easy way to do this without editing theme files directly.” — OuterBox, on faceted-nav canonicals. Source
• “Partial deployment is worse than no deployment because Google requires bidirectional confirmation across all storefronts before recognizing hreflang signals.” — DigitalRoxy. Source
• “Server-rendered by default. Every page is HTML on first byte.” — 1Digital Agency, on Stencil. Source
• “Google has said repeatedly that URL structure is a minor signal.” — eComOne. Source

BigCommerce SEO checklist

Prioritized by impact — top items move the needle most.

High impact

• Faceted navigation handled — filter/sort URLs get canonical + noindex per the parameter rules; combinations without search demand don’t get indexed.
• Pagination not noindexed — page 2+ keeps its own canonical and stays indexable; verify the default robots.txt isn’t blocking ?page=2+.
• Core Web Vitals passing — audit installed apps for JS bloat; upload optimized source images; confirm WebP delivery is on for your theme version.
• Migration redirect map (if moving themes/to Catalyst) — complete, with dynamic redirects for internal moves; previews noindexed.

Standard setup

• URL structure set to SEO Optimized (or a deliberate Custom pattern).
• XML sitemap submitted in Google Search Console and Bing Webmaster Tools.
• Page titles + meta descriptions written for home, top products, top categories.
• Canonical tags confirmed correct per page type (auto, but verify).
• Review schema added via app (Yotpo/Stamped) or custom JSON-LD.
• Google Merchant Center connected via the native Ads & Listings app.

International (multi-storefront only)

• hreflang implemented bidirectionally across all storefronts (no partial sets).
• x-default present; ISO codes correct (en-GB, not en-UK).
• Googlebot IP ranges whitelisted in Akamai so geo-redirect doesn’t block crawling of international storefronts.

The mental models

1. Two buckets: automatic vs yours. Everything BigCommerce SEO either ships free (sitemap, canonicals, robots.txt, auto-301s, custom URLs, Cornerstone schema, CDN, SSL) or is left to you (faceted nav, hreflang, review schema, pagination audit, CWV, content). Knowing which bucket a task is in tells you whether to configure it or build it.

2. The faceted-nav parameter triage. Sort every filter/sort parameter into one of three classes:

• Index (self-canonical) — filters with standalone search demand (“red running shoes”).
• Canonicalize + noindex,follow — navigation-only filters and sort orders.
• Block (only alongside canonical/noindex) — junk combinations with no demand. Remember robots.txt stops crawling, not indexing — never block a URL whose canonical/noindex you need Google to read.

3. Stencil vs Catalyst = your performance ceiling. Stencil is a strong, low-effort default with a real LCP ceiling. Catalyst raises the ceiling but adds infrastructure (Node app, Vercel, bundle discipline). Choose based on whether CWV is actually failing on Stencil after optimization — not on the Lighthouse-100 marketing number.

4. hreflang is all-or-nothing. Bidirectional confirmation across every storefront, or Google discards the set. Partial deployment costs effort and returns nothing. And on BigCommerce specifically, hreflang is useless if Akamai geo-redirects Googlebot away from the pages — whitelist first.

BigCommerce SEO cheat sheet

Where things live in the admin

URL structure options

Sitemap paths

• Stencil: /xmlsitemap.php
• Catalyst: /sitemap.xml (and /xmlsitemap.php auto-redirects here)

Faceted-nav rules

Don’ts

• Don’t noindex paginated category pages.
• Don’t rely on robots.txt to deindex (it blocks crawling only).
• Don’t deploy partial hreflang.
• Don’t trust the default robots.txt around ?page= — audit it.
• Don’t treat Catalyst’s Lighthouse 100 as a production guarantee.

Tools for BigCommerce SEO

• Google Search Console — sitemap submission, URL Inspection, International Targeting (hreflang), Crawl Stats. Your ground truth for what Google actually does.
• Bing Webmaster Tools — second sitemap submission, crawl control, site scan.
• Screaming Frog / Ahrefs Site Audit — crawl your store to catch the faceted-nav URL explosion, a default robots.txt blocking pagination, redirect chains, and thin/duplicate category pages. This is how you find the BigCommerce-specific gaps.
• Reviews apps — Yotpo or Stamped to add AggregateRating/review schema the default theme omits.
• Feed tools — the native Ads & Listings on Google app, or FeedOps / DataFeedWatch / ExportFeed for finer Merchant Center feed control.
• Aleyda Solis hreflang checker — validate multi-storefront hreflang before trusting it.
• PageSpeed Insights / Lighthouse — benchmark Stencil vs Catalyst CWV pre/post any migration; re-check after every batch of app installs.
• BigCommerce Script Manager — where you inject the JSON-LD and canonical overrides BigCommerce doesn’t provide natively.

Mistakes people actually make on BigCommerce

These are the recurring, avoidable mistakes on this platform specifically — not generic SEO advice.

Assuming faceted navigation is “handled” because BigCommerce is good at SEO

BigCommerce’s genuine strengths (auto sitemap, auto 301s, editable robots.txt) lead people to assume the platform also manages filter/sort URLs. It doesn’t. Why it’s wrong: left alone, every filter combination gets its own crawlable URL with no automatic canonical back to the parent category — an exponential spike in near-duplicate pages that dilutes authority and burns crawl budget. What to do instead: classify every filter and sort parameter per the triage table in the Advanced tab (index / canonicalize + noindex / block) and implement it via Stencil theme overrides or Script Manager. Nobody does this for you.

Filling in “Meta Keywords” and expecting it to help rankings

The SEO fields panel still has a Meta Keywords box, and people fill it in because it’s there. Why it’s wrong: BigCommerce’s own glossary calls the tag defunct — search engines almost entirely ignore it, and time spent on it is time not spent on title tags or meta descriptions, which do matter. What to do instead: ignore Meta Keywords entirely. If you want to help your own site’s internal search, use the separate Search Keywords field instead — it’s a different field with a different purpose, and confusing the two wastes effort on both fronts.

Noindexing paginated category pages

Faced with a “too many indexed pages” problem, it’s tempting to slap noindex on page 2, page 3, etc. of a category. Why it’s wrong: Google’s own ecommerce guidance is to give each paginated page its own unique URL and its own canonical — noindex is meant for filter/sort variations, not pagination. Noindexing pagination just removes real product inventory from search. What to do instead: keep each paginated page self-canonical and indexable; save noindex for the navigation-only filter and sort-order URLs that are actually duplicates.

Migrating to Catalyst without a complete redirect map

Moving from Stencil to Catalyst (or between themes) is treated as a frontend project, with SEO bolted on at the end if at all. Why it’s wrong: per 1Digital’s own account of the classic migration failures, the two most common causes of lost ranking authority are missing redirect maps and JavaScript-heavy builds that worsen Core Web Vitals — both are avoidable, both keep happening. What to do instead: build the redirect map (old URL → new URL) before the migration starts, keep the preview environment noindexed with X-Robots-Tag or a robots.txt block, and benchmark Core Web Vitals before and after the switch.

Deploying hreflang on some storefronts but not others

A team rolls out hreflang on the two or three storefronts they’re actively working on and plans to “finish the rest later.” Why it’s wrong: hreflang needs bidirectional confirmation across every storefront in the set before Google recognizes any of it — a partial set is discarded entirely, so the team did the work and got none of the benefit. What to do instead: implement hreflang across all storefronts at once, or don’t implement it yet. There’s no partial-credit version.

Should you move from Stencil to Catalyst?

The Stencil-vs-Catalyst choice is the one genuine “which path do I take?” branch on this platform — it sets your Core Web Vitals ceiling and comes with real infrastructure cost if you get it wrong. This tree walks the same decision matrix from the Advanced tab.

Prompts for BigCommerce SEO tasks

Copy-paste starting points for the recurring analysis tasks in this guide. Paste your own store’s data in; check the output against the rules in the Advanced tab before acting on it.

Classify a list of faceted-navigation URLs

Paste in a list of URLs pulled from a crawl (Screaming Frog, Ahrefs Site Audit, or your server logs). Expect back a table sorting each URL into the triage buckets from this guide, with a canonical target and robots directive for each.

Here is a list of URLs from my BigCommerce category and filter pages:

[paste URLs, one per line]

For each URL, classify it as one of:
1. Main category or high-demand filter (has standalone search value) — self-canonical, index
2. Navigation-only filter or sort-order variation — canonicalize to the parent category, noindex,follow
3. Pagination (page 2+) — self-canonical, index

State the reasoning for each classification and the canonical URL you'd assign.
Flag any URL you're not confident about instead of guessing.

Draft hreflang tags for a multi-storefront setup

Paste in your list of storefront domains and their language/region. Expect back the bidirectional hreflang block (including x-default) for one representative page, which you then implement via Script Manager, custom Stencil templates, or sitemap annotations — and replicate across every storefront in the set, since a partial rollout is discarded entirely.

I run these BigCommerce storefronts off one shared catalog:

- us.example.com — English, United States
- uk.example.com — English, United Kingdom
- ca.example.com — French, Canada

Generate the bidirectional hreflang tag set (with x-default) for the product page
at /blue-widget/ across all three storefronts, using correct ISO region codes
(not bare language codes). Show me the exact tags for each version of the page.

Audit a Stencil-to-Catalyst redirect map for gaps

Paste in two URL lists — your current Stencil URLs and your planned Catalyst URLs (or a CSV export of both). Expect back a matched-pairs list plus a flagged list of any old URL with no corresponding new-URL mapping, which is the single most common cause of lost ranking authority in these migrations.

Here is my current URL list (Stencil) and my planned URL list (Catalyst):

Current:
[paste URLs]

Planned:
[paste URLs]

Match each current URL to its most likely planned-URL equivalent. List any current
URL that has no clear match so I can add it to the redirect map manually before
migrating. Don't guess a match you're not confident about — flag it instead.

Resources worth your time

On-site, related

• Faceted navigation — the platform-agnostic deep dive on the #1 BigCommerce SEO problem; this article is the BigCommerce-specific implementation.
• Canonicalization — the canonical mechanics behind the faceted-nav rules above.
• Crawling — crawl budget and why the faceted-nav URL explosion matters.

BigCommerce official

• Catalyst — the headless framework.
• Intro to SEO and SEO Fields.

Practitioner guides (useful, but verify platform-current behavior)

• Orbit Media — BigCommerce SEO settings — screenshot walkthrough of the admin SEO settings.
• NetProfitMarketing — BigCommerce SEO guide and their faceted-nav parameter rules.
• 1Digital Agency — Stencil vs Catalyst SEO — the performance trade-off analysis.
• DigitalRoxy — multi-storefront hreflang — the Akamai geo-redirect fix.
• OuterBox — BigCommerce SEO issues and SeoProfy.
• eComOne — Shopify vs BigCommerce SEO.

From around the industry

• NetProfitMarketing — Stencil to Cornerstone upgrades: SEO and performance gotchas — theme-migration pitfalls specific to BigCommerce that overlap with the Stencil/Catalyst migration risks.
• NetProfitMarketing — BigCommerce faceted-navigation parameter rules and canonicals — BigCommerce-specific parameter classification and canonical implementation for filter URLs.
• BigCommerce — Faceted search overview — BigCommerce’s own primer on how faceted search works, useful context before implementing canonical/noindex rules.
• PageSpeedMatters — Ultimate BigCommerce speed guide — Akamai CDN tuning, Brotli, edge-cache optimization, and the TTFB/LCP impact on BigCommerce stores.
• SearchFit.ai — BigCommerce SEO features review — independent audit of BigCommerce’s built-in SEO features and their limits, including Stencil image-serving behavior.

Test yourself: BigCommerce SEO

Five questions on what BigCommerce does automatically versus what you have to do yourself. Pick an answer for each, then check.

BigCommerce SEO

BigCommerce SEO is the technical, on-page, and content work you do on a store built on BigCommerce — a hosted SaaS ecommerce platform that ships with more native SEO controls than most of its rivals (editable robots.txt, custom URL structures, auto sitemaps, and automatic 301s), while still leaving faceted navigation, multi-storefront hreflang, and review schema for you to handle.

Related: Faceted Navigation, Canonicalization, Core Web Vitals

BigCommerce SEO

BigCommerce is a SaaS ecommerce platform — like Shopify, it’s hosted for you, not self-managed on your own server. Where it differs is the height of the SEO floor it gives you out of the box. BigCommerce auto-generates XML sitemaps, writes canonical tags for every page type, lets you edit robots.txt directly in the admin (Shopify doesn’t), creates 301 redirects automatically when a product, category, or page URL changes, and — unlike Shopify’s forced /products/ and /collections/ prefixes — lets you configure your product URL format, including removing prefixes entirely.

The theme layer matters. Stencil (with Cornerstone as the default reference theme) is BigCommerce’s current server-rendered framework; it emits JSON-LD Product and BreadcrumbList schema without developer work. Catalyst is the newer Next.js + GraphQL headless framework, a different deployment pattern with a higher performance ceiling and a different set of SEO trade-offs. (The old Blueprint themes are deprecated.)

What BigCommerce does not do for you: canonicalize or noindex faceted-navigation filter URLs, generate hreflang for multi-storefront international setups, or add review/AggregateRating schema. Those are the hands-on parts of BigCommerce SEO — the same crawl-budget, duplicate-content, and Core Web Vitals problems every ecommerce platform has, just with a particular set of BigCommerce-specific levers for fixing them.

Related: Faceted Navigation, Canonicalization, Core Web Vitals

Changelog