BigCommerce SEO

How SEO works on BigCommerce — what the platform gets right automatically (editable robots.txt, custom URLs, auto sitemaps, automatic 301s, built-in schema), what you still have to do by hand (faceted nav, hreflang, review schema), and how the Stencil-vs-Catalyst choice shapes your Core Web Vitals ceiling.

First published: Jun 25, 2026 · Last updated: Jul 25, 2026 · Advanced
demand #4 in Ecommerce Platforms#13 in Platform SEO#91 in Technical SEO#121 on the site

BigCommerce gives you the strongest built-in technical SEO foundation of any hosted SaaS ecommerce platform: editable robots.txt, fully custom URL structures (no forced prefixes), auto-generated XML sitemaps, automatic 301 redirects on URL change, and JSON-LD product schema in the Cornerstone theme. What it leaves to you is the work that actually moves the needle at scale — faceted-navigation canonicals, multi-storefront hreflang (with an Akamai geo-redirect gotcha), review schema, and Core Web Vitals on Stencil. The Stencil-vs-Catalyst (headless Next.js) decision sets your performance ceiling.

TL;DR — BigCommerce ships the highest native SEO floor of any hosted SaaS platform: editable robots.txt, fully custom URL structuresURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly. (no forced prefixes), auto-generated and self-updating XML sitemapsAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags., automatic 301s on URL change, and JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. Product + BreadcrumbListBreadcrumbs are a secondary navigation trail (Home > Category > Page) that shows where a page sits in a site's hierarchy. They create internal links that pass PageRank, and when marked up with BreadcrumbList structured data they can drive the path Google shows in desktop search results. in Cornerstone. The work it leaves you is what actually scales: faceted-navigation canonical/noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. strategy, multi-storefront hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. (watch the Akamai geoGenerative Engine Optimization (GEO) is the practice of optimizing content and brand presence so AI-powered search engines and assistants — Google AI Overviews, ChatGPT, Perplexity — cite, recommend, or mention you when generating answers. Google's position is that it's still SEO.-redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't.), review schemaReview schema (schema.org/Review) is structured data for a single critic's or user's evaluation of one specific thing — one author, one itemReviewed, one reviewRating — distinct from AggregateRating, which summarizes many reviews into an average., and Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data.. Stencil (server-rendered Handlebars) vs Catalyst (Next.js headless) sets your performance ceiling — and migrating between them is where redirect maps get lost.

Evidence for this claim BigCommerce documents platform-managed sitemap, URL, redirect, and storefront SEO capabilities; these are platform features rather than search-engine guarantees. Scope: BigCommerce platform behavior only. Confidence: high · Verified: BigCommerce Support: SEO features Evidence for this claim BigCommerce storefronts remain subject to Google's crawlable-link, canonicalization, and product structured-data requirements. Scope: Google requirements independent of ecommerce platform. Confidence: high · Verified: Google Search Central: Ecommerce documentation

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

Most BigCommerce SEOBigCommerce 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. 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 sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags., canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. per page type, editable robots.txt, automatic 301s on URL change, full URL-structure control, Akamai CDN + Image Manager, Cornerstone JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. (Product, BreadcrumbList, Organization), SSL.

Yours to do: faceted-navigation canonical + noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. strategy, multi-storefront hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., review/AggregateRating schemaAggregateRating schema (schema.org/AggregateRating) is structured data that represents the average of many ratings or reviews of an item, usually nested inside a parent type (or standalone with itemReviewed) to power star-rating rich snippets in search results., paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does. robots.txt audit, blog/content strategy, and Core Web VitalsWeb Vitals is Google's initiative (launched May 2020) for unified page-experience quality signals. Core Web Vitals — LCP, INP, and CLS — are the subset used in ranking; the rest (TTFB, FCP, TBT, Speed Index) are diagnostic, not ranking factors. on Stencil (app JS bloat + unoptimized source images).

URL structure

URL options live at Store Setup → Store Settings → URL StructureURL structure is how the parts of a web address — scheme, domain, path, query string, and fragment — are organized and formatted. It mostly affects crawling, usability, and how engines understand a page, not rankings directly.. 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 contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. 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 sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. 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 indexA sitemap index is a sitemap of sitemaps — a single file that lists your other sitemap files instead of listing URLs directly. It's how large sites stay under the 50,000-URL / 50MB-per-sitemap limit while submitting just one file. 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 DescriptionThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through., 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 tagThe meta keywords tag — <meta name=\"keywords\" content=\"...\"> — is a mid-1990s HTML head element meant to let a page declare its own topic keywords to search engines. Google has publicly ignored it for ranking since 2009, and no major search engine uses it as a ranking signal today. It's dead as SEO, and a populated one only leaks your target keywords to anyone who views your source. 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 redirectsA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. 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 schemaVideoObject schema (schema.org/VideoObject) marks up video content for Google's video rich results — thumbnail, duration, and key moments — surfacing on main search, the Video tab, Google Images, and Google Discover. It also covers the related Clip (key moments) and BroadcastEvent (LIVE badge) types on the same guide. 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 dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. 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 canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. 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 budgetThe number of URLs an engine will crawl in a timeframe.. 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:

Page typeCanonicalRobots directive
Main categorySelfindex
High-demand filter (real search value)Selfindex
Navigation-only filterMain categorynoindex,follow
Sort-order onlyMain categorynoindex,follow
Pagination (page 2+)Self (its own URL)index
Product in multiple categoriesFirst-category URLindex
TIP Classify BigCommerce filter URLs before writing blanket rules

The duplication finding shows that two filter parameters normalize to the same value. That is evidence for consolidation, not permission to noindex every filtered category.

Paste a sample of real storefront URLs into my Faceted Navigation Auditor to separate useful landing pages from duplicate filters, sorting, tracking, and pagination. Faceted Navigation Auditor Free

  1. Export representative category, filter, sort, tracking, and pagination URLs from the store.
  2. Classify parameters by intent and duplication before assigning canonical or indexability rules.
  3. Verify the resulting tags in rendered templates and confirm important category paths remain crawlable.
Classify each parameter family before choosing index, noindex, canonical, or crawl controls.

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

  • robots.txt blocks crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., not indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.. 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 navigationEcommerce SEO is the practice of optimizing an online store so its product and category pages rank in organic search and attract purchase-intent visitors. It uses the same Google algorithm as any other site, but compounds the usual SEO work with commerce-specific challenges like faceted navigation, product variants, and platform-imposed URLs. cluster; the canonical mechanics are in canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it..)

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 TTFBTime to First Byte — the time from the start of a request to when the first byte of the response arrives. It's a diagnostic metric (not a Core Web Vital) and a major input to FCP and LCP; ≤0.8 s is good. 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 INPInteraction to Next Paint — the input-to-paint latency at the 75th percentile of a page's interactions. ≤200 ms is good. and LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. — 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 crawlabilityCrawlability is how well search engine crawlers can discover, access, and fetch a site's pages. A crawlability issue is any technical condition — blocked access, broken links, server failures, or bloated URL inventory — that stops pages from reaching the index.. 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 LighthouseLighthouse is Google's free, open-source tool that audits a page under simulated lab conditions and scores it 0–100 across Performance, Accessibility, Best Practices, and SEO. It's lab data — useful for debugging, not a ranking signal. 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 GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer.-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-redirectA geo-redirect automatically sends a visitor to a location- or language-specific URL based on IP or browser signals — a UX/serving mechanism that's separate from, and can actively undermine, hreflang. trap. Akamai redirects visitors by IP geoGenerative Engine Optimization — visibility inside AI answer engines.-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/HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.' 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.

TIP Test each storefront as a complete hreflang cluster

A missing return tag invalidates that relationship even when the source page looks correct. Multi-storefront reviews need the whole reciprocal cluster, not a spot check of one page.

Run representative locale URLs through my returntag - hreflang checker to map reciprocal pairs and expose the storefront that fails to link back. returntag - hreflang checker Free

  1. Start with one equivalent product or category URL from every active storefront.
  2. Check reciprocal return tags, self-references, language-region codes, and x-default together.
  3. Retest through the public Akamai path so geo redirects and edge behavior are part of the evidence.
One missing return can break an otherwise plausible storefront cluster.

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 CMSA content management system that separates the content repository from the presentation layer, delivering content via API to any front-end framework rather than rendering HTML server-side itself. It doesn't specify the rendering mode, hosting, cache, preview security, or publishing workflow — those are separate decisions. 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 CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. 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 scrollInfinite scroll is a loading pattern where content appears automatically as a user scrolls, instead of via numbered pages. Because Googlebot doesn't scroll or click, indexable infinite scroll needs real per-chunk URLs (paginated loading) that update via the History API — otherwise deep content may never be crawled, or worse, get merged into the wrong page. 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

BigCommerceShopify
URL prefixesNone forced; custom controlForces /products/, /collections/
Robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere.Editable in adminNot natively editable
Built-in schemaYes (Cornerstone)App required
SEO app ecosystem~25 apps640+ apps
Out-of-box speed1.8–2.5s LCP (Stencil) / 0.8–1.5s (Catalyst)~1.3s avg
301 automationAuto on URL changePrompts, less seamless
Headless optionCatalyst (Next.js)Hydrogen

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.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.