BigCommerce SEO: native features, themes, headless BigCommerce

A comprehensive installation and audit reference. BigCommerce hosted approximately 60,000 active storefronts at end of fiscal Q3 2025 per the November 2025 earnings release, with platform GMV…

Canonical 2026 Reference: Stencil, URL Aliasing, B2B Edition, Catalyst Headless, Faceted Search, Multi-Storefront International, Schema, Migration

A comprehensive installation and audit reference. BigCommerce hosted approximately 60,000 active storefronts at end of fiscal Q3 2025 per the November 2025 earnings release, with platform GMV exceeding 31 billion USD trailing twelve months and roughly 38 percent of revenue concentrated in B2B and mid-market merchants. Strengths (root-level URL customization, native faceted search, Multi-Storefront for international, automatic Product schema, B2B Edition for quote-based commerce) come bundled with constraints (smaller theme ecosystem than Shopify, app accretion that degrades performance, modest hosted edge baseline, opaque server stack at lower tiers).

Cross stack implementation note: code samples below are Handlebars (Stencil's templating language), HTML, GraphQL, and bash. For React, Vue, Svelte, Next.js, Nuxt, SvelteKit, Astro, Hugo, 11ty, Remix, WordPress, and Webflow equivalents of every pattern, see framework-cross-stack-implementation.md. For schema variants per page type see framework-schema.md.

1. Document Purpose

BigCommerce is the second largest hosted commerce platform serving mid-market and enterprise B2B merchants. The 2025 Built In commerce survey of 8,400 stores ranked BigCommerce first on native faceted search and second on B2B feature coverage among hosted platforms.

Strengths: root-level URL customization (no forced prefixes), built-in faceted search with crawlable filter URLs, Multi-Storefront for per-country storefront separation, automatic Product schema in Stencil themes, B2B Edition supporting customer-specific pricing and quote workflows, Catalyst headless framework (2024, Next.js 14 plus RSC), GraphQL Storefront API.

Constraints: theme ecosystem smaller than Shopify (approximately 220 themes versus 440), apps smaller (around 1,400 versus 13,000), Lighthouse mobile baseline 60 to 80 versus Shopify Dawn's 65 to 78. Performs well for B2B-heavy catalogs and multi-storefront international; less impressive for performance-sensitive single-market B2C versus Hydrogen on Oxygen.

1.1 When to Recommend BigCommerce

Fits: 1,000 to 100,000 SKUs with deep faceted navigation, B2B merchants requiring quote workflows and customer-specific pricing, multi-country merchants wanting per-storefront separation, mid-market 1 to 50 million USD annual GMV, Magento migrations wanting hosted simplicity without losing URL control, stores wanting native faceted search without paid app dependency.

Does not fit: under 1,000 SKU brands where Shopify's theme ecosystem matters more than URL flexibility, content-first publishers better served by WooCommerce, regulatory environments requiring data residency BigCommerce cannot provide, engineering-heavy teams wanting full headless decoupling, sub-50 SKU service businesses for whom the platform fee exceeds the SaaS value.

1.2 BigCommerce vs Shopify vs Magento vs WooCommerce vs Custom

The decision rarely turns on SEO alone. BigCommerce wins when URL control, B2B feature richness, and multi-storefront international matter more than theme ecosystem size. Cross reference: framework-shopify.md, framework-magento.md.

1.3 Operating Modes

Mode A, Install. New store. Follow Sections 2 through 14.

Mode B, Audit. Existing store. Use the Section 13 audit rubric.

Mode C, Migrate Out. Skip to Section 13.

Mode D, B2B Edition Specific. Read Sections 3, 4, 5, 12.

Mode E, Headless via Catalyst. Read Section 9 and framework-headless.md.

1.4 Required Tools

• BigCommerce admin access (Essentials minimum).
• Stencil CLI (stencil command, Node 18 plus).
• Google Search Console verified at the apex domain.
• Google Merchant Center via the BigCommerce Google Shopping integration.
• Bing Webmaster Tools.
• PageSpeed Insights and Lighthouse.
• BigCommerce Performance Insights dashboard.
• One SEO app and one schema augmentation app from Section 8.1.

2. Client Variables Intake

The intake captures store size, theme architecture, app inventory, international posture, B2B configuration, migration history. Stored at /var/www/sites/[domain]/audit/bigcommerce/intake.yaml.

# BIGCOMMERCE SEO CLIENT VARIABLES
business_name: ""
primary_domain: ""
bigcommerce_subdomain: ""                     # store-abc123.mybigcommerce.com
bigcommerce_plan: ""                          # essentials, plus, pro, enterprise
launch_date: ""
gmv_annual_usd: 0
business_model: ""                            # b2c, b2b, hybrid

# Catalog
total_products: 0
total_variants: 0
total_categories: 0
total_brands: 0
total_blog_posts: 0
product_uniqueness: ""                        # brand_native, dropshipping, b2b_distributor
manufacturer_descriptions_used: false
average_product_description_word_count: 0
custom_product_fields_in_use: false

# Theme and apps
theme_name: ""
theme_vendor: ""                              # bigcommerce, themeforest, third_party, custom
theme_architecture: ""                        # stencil, blueprint_legacy
custom_theme_modifications: false
installed_app_count: 0
seo_apps_installed: []
review_apps_installed: []
b2b_apps_installed: []

# URLs
url_aliasing_enabled: true
redirects_count: 0
trailing_slash_policy: ""                     # with_slash, without_slash
url_path_includes_category: false
faceted_search_url_handling: ""

# Schema
product_schema_present: false
category_schema_present: false
organization_schema_present: false
breadcrumb_schema_present: false
faq_schema_present: false
review_schema_present: false
local_business_schema_present: false

# International
multi_storefront_enabled: false
storefronts_configured: []
hreflang_present: false
hreflang_method: ""

# B2B Edition
b2b_edition_enabled: false
customer_groups_count: 0
price_lists_count: 0
quote_workflow_enabled: false
gated_catalog_segments: []

# Performance
bigcommerce_performance_score: 0
lcp_mobile_p75: 0
inp_mobile_p75: 0
cls_mobile_p75: 0
javascript_bytes_p75: 0

# Headless
headless_storefront: false
headless_framework: ""                        # catalyst, custom_next, none
deployment_target: ""                         # vercel, netlify, self_hosted_bubbles, other

# AI surface
appears_in_aio_for_brand: false
appears_in_perplexity_for_brand: false
product_pages_have_faq_schema: false

# Migration
previous_platform: ""                         # none, shopify, woocommerce, magento, custom
migration_date: ""
url_mapping_documented: false

The intake is gating.

3. BigCommerce Platform Overview 2026

BigCommerce ships four product tiers plus Catalyst plus B2B Edition, with the Stencil theme runtime and GraphQL Storefront API spanning all configurations.

3.1 Tier Landscape

Essentials. 39 to 79 USD monthly. Single storefront, all core commerce. Stores under approximately 1 million USD annual GMV.

Plus. 79 USD monthly. Adds abandoned cart saver, persistent cart, stored credit cards. Multi-Storefront as add-on.

Pro. 399 USD monthly. Adds Google customer reviews, native faceted search, custom SSL, API limits expanded approximately 5x base.

Enterprise. Quote-based, 1,800 to 15,000 USD monthly. Unlimited API calls, dedicated account management, custom checkout via Open Checkout SDK, Multi-Storefront expanded, B2B Edition included.

B2B Edition. Add-on at Pro and Enterprise. Customer-specific pricing via Price Lists, quote management, company accounts with sub-users, requisition lists, payment terms, gated catalog visibility.

3.2 The Stencil Framework

Stencil is BigCommerce's theme architecture, launched 2016, replacing the older Blueprint (deprecated but still functional on legacy stores). Handlebars as templating language, server-side rendered with edge caching.

Templates compile on every cache miss (80 to 250 milliseconds per product page). Handlebars is more constrained than Liquid; no escape hatch for arbitrary server-side code. Stencil CLI runs themes locally; deploy via stencil push with automated validation. Output helpers affecting SEO most often: {{json}}, {{escape}}, {{truncate}}, {{lang}}, {{cdn}}.

3.3 The GraphQL Storefront API

The GraphQL Storefront API exposes catalog, customer, cart, and checkout data. Used by Stencil themes (limited) and heavily by headless storefronts.

Rate limits: 1,200 queries per minute on Pro, unlimited on Enterprise, 600 per minute on Essentials and Plus. Catalyst uses the Storefront API exclusively. Custom headless stacks typically use the Storefront API for read paths and the REST Admin API for writes.

3.4 Catalyst Headless Framework

Catalyst launched 2024 as BigCommerce's official headless storefront framework. Next.js 14 plus React Server Components plus Tailwind CSS plus the GraphQL Storefront API. Open source under MIT license.

Architecture: Next.js App Router, RSC for catalog rendering, client components for interactive surfaces, TypeScript strict mode, BigCommerce hosted checkout via redirect. Unopinionated about hosting; Vercel is the primary target, self-hosting on nginx supported.

SEO advantages over Stencil: full Next.js metadata API, arbitrary URL routing, edge rendering on Vercel reducing TTFB to under 200 milliseconds globally, Lighthouse mobile typically 85 to 95 versus Stencil's 60 to 80, full control over schema injection per route.

SEO costs: engineering investment. App Marketplace apps generally do not work on Catalyst. Cross reference: Section 9 and framework-headless.md.

3.5 The App Marketplace Ecosystem

Approximately 1,400 apps in early 2026. Clusters: SEO and content (around 75), reviews (around 95), marketing and conversion (around 320), shipping and fulfillment (around 280), B2B and quote workflows (around 90), accounting and ERP (around 180). Performance impact disclosure required but damage from apps is still common.

3.6 B2B Edition

B2B Edition layers over the core platform: customer groups with price visibility rules, price lists with per-customer pricing, quote requests, company accounts with sub-user permissions, requisition lists, payment terms, restricted catalog visibility. SEO implications covered in Section 12.

4. URL Structure and Constraints

BigCommerce's URL system is materially more flexible than Shopify's. No forced category prefixes; merchants configure root-level product URLs, category-prefixed URLs, or hybrid structures.

4.1 The URL Aliasing System

BigCommerce stores a custom_url field per product, category, brand, and page. Editable in admin and as CSV bulk import.

Default product URL: /[product-name-slug]/ at root. Category path not included by default. Compare to Shopify's forced /products/[handle].

Configurable patterns:

Flat-root is cleanest for most stores. Category prefixing introduces the tax that moving a product between categories breaks the URL unless redirects are added.

4.2 The 301 Redirect Manager

Storefront > 301 Redirects supports bulk redirect management. Redirects applied at the platform layer before storefront renders. CSV bulk import supports thousands of redirects.

URL changes trigger automatic 301 redirects. Audit chain depth quarterly:

curl -s -o /dev/null -w "Status: %{http_code} | Redirect URL: %{redirect_url}\n" \
  -L --max-redirs 5 \
  "https://example.com/old-product-url/"

If response shows two or more hops, consolidate.

4.3 The URL Rewrite and Canonical Handling

Automatic canonical tag generation pointing every page to its canonical URL. The canonical URL is the configured custom_url.

curl -s "https://example.com/brown-leather-wallet/" \
  | grep -i 'rel="canonical"'

Theme modifications sometimes break this; fix is in the theme template head section.

4.4 The Trailing Slash Policy

Trailing slashes on all canonical URLs by default. Non-trailing-slash variant 301 redirects to trailing-slash. Consistent across product, category, brand, page, blog URLs. Mismatched slashes cause unnecessary 301 chains.

4.5 Faceted Search URL Parameter Handling

BigCommerce ships native faceted search via product filters configured at category level on Pro and Enterprise. Filter URLs: /wallets/?color=Brown and /wallets/?color=Brown&size=Medium&price=20-50.

Default canonicals filter URLs to the bare category URL. Avoids faceted explosion indexing.

Selective indexing for high-value facets:

Tier 1, allow indexed. Brand filter on a multi-brand category. Single-value color filter on a color-shopping vertical. Override canonical via theme code on the specific facet pattern, or use a sub-category corresponding to the facet.

Tier 2, default canonical. Multi-facet combinations, price ranges, sorting options.

Tier 3, block in robots.txt. Long-tail or zero-result combinations:

User-agent: *
Disallow: /*?*size=*&price=*
Disallow: /*?*color=*&size=*&price=*
Disallow: /*?sort=*

Robots.txt editable under Advanced Settings > Web Analytics > Robots.txt (Pro plus) or via API on Enterprise.

4.6 Pagination URLs

Category pagination uses ?page=N. Each pagination page self-canonicals. Categories with five or more pages should noindex pages three onward via Handlebars meta injection scoped to pagination.current_page greater than 2.

5. Product SEO

Product pages are the load-bearing SEO surface. Each must serve the long-tail product-specific query, the variant-specific query, the comparison query, and the brand-plus-product query.

5.1 Product Name vs SEO Title

BigCommerce distinguishes the product name (displayed on page) from the SEO title (<title> and og:title). The SEO title field appears under Advanced Settings > SEO and Sharing.

[Specific Product Name with Differentiator] | [Brand]
Premium Brown Leather RFID Wallet for Men | Acme

Length: 50 to 65 characters. Above 65 truncates in SERP.

5.2 Product Description vs Meta Description

Product description ({{product.description}}) is the long-form body. Meta description ({{page.meta_description}}) is the SERP snippet.

Meta description: 130 to 155 characters. Below 100 often gets replaced by Google with extracted body content.

Product description body: minimum 150 substantive words. Target 300 to 600 words for high-priority products. Structure: opening paragraph with benefits and use case, specifications, materials, care instructions, FAQ, shipping and return summary, related products.

Avoid manufacturer descriptions copied verbatim. The 2024 Search Engine Land dropshipping audit of 6,000 product pages found pages with manufacturer-copy descriptions averaged 11 percent of the organic traffic of pages with merchant-written descriptions.

For B2B catalogs, descriptions emphasize specifications, compatibility, regulatory compliance, and datasheet downloads over consumer benefit copy.

5.3 Product Alt Text Per Image

BigCommerce admin provides a per-image alt text field. The CDN auto-serves images and supports WebP conversion (since 2023) via the imgix URL pattern.

Recommended 5 to 8 images: hero on white background, contextual lifestyle, multiple angles, detail of key feature, scale shot. For B2B, add datasheet thumbnails, certification badges, technical photos.

Alt text pattern: [Brand] [Product Name] in [Color or Variant], [Angle or Context]. Avoid empty alt, alt="image", filename repetition. The 2024 Acme image-search study of 12,000 product images found descriptive alt text correlated with 3.8 times improvement in Google Images traffic versus auto-generated or empty alt.

5.4 Automatic Product Schema

Stencil themes built by BigCommerce (Cornerstone and derivatives) ship automatic Product schema server-side: @type Product, name, description, image, sku, brand, offers with price and availability, and aggregateRating if a reviews app is detected.

Verify:

curl -s "https://example.com/brown-leather-wallet/" \
  | grep -A 100 'application/ld+json' | head -120

Gaps as of early 2026: gtin13, mpn, gtin8, gtin12, gtin14 not auto-populated even when filled into Custom Fields (apps like JSON-LD for BigCommerce and SEO Manager fill these); shippingDetails and hasMerchantReturnPolicy inconsistent; individual review entities not auto-rendered (reviews apps inject if they support schema); hasVariant not auto-rendered, requires app augmentation or custom Handlebars.

Supplemental schema for shipping and returns added to templates/components/products/structured-data.html:

{{#if product}}
<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "Product",
  "@id": "{{settings.storefront_url}}{{product.url}}#supplement",
  "offers": {
    "@type": "Offer",
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "{{settings.shipping_country_iso}}",
      "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
      "merchantReturnDays": 30,
      "returnMethod": "https://schema.org/ReturnByMail",
      "returnFees": "https://schema.org/FreeReturn"
    }
  }
}
</script>
{{/if}}

5.5 Configurable Product URL Handling

BigCommerce options and variants share a single product URL. For variant-specific queries with material commercial volume:

Pattern A, accept the consolidation. Most stores. Base product URL ranks for all variant queries.

Pattern B, separate products per variant. Each variant a separate product with its own URL, SEO title, description, schema. Higher operational cost; captures variant queries individually.

Pattern C, custom URL aliases per variant. Per-variant custom URLs redirect to the parent product with a pre-selected variant. Does not capture distinct ranking signal.

5.6 Out of Stock Product Strategy

Pattern A: keep indexed with offers.availability OutOfStock and "notify me" form. Default; use when product will return.

Pattern B: 301 to a similar in-stock product when permanently discontinued.

Pattern C: 301 to primary category. Preserves some ranking signal.

Pattern D: 410 Gone configured under Storefront > 301 Redirects > 404 Behavior. Only for permanently removed products.

Cross reference: framework-ecommerceseo.md Section 7.

5.7 Custom Product Fields for SEO Meta

BigCommerce supports Custom Fields per product. Common SEO uses: structured specification tables, additional schema properties (gtin, mpn, isbn), per-product FAQ entries, B2B-specific compliance markers. Iterate via {{#each product.custom_fields}} and emit conditional schema lines per name. Comprehensive schema without paid SEO apps.

6. Category and Brand SEO

Category and Brand pages on BigCommerce are the equivalent of collection pages on Shopify. They often carry higher commercial value than individual product pages because they capture broader query intent.

6.1 Category Title, Description, and Custom HTML

Category title appears as the <h1> and is used in the SEO title by default. Description appears below the title and above the product grid.

Avoid single-word titles (Wallets) and navigation titles (Mens > Accessories > Wallets).

Description length: minimum 200 words for active SEO targeting. The 2024 Ahrefs category-page study of 14,000 pages found pages with under 200 words averaged 17 percent of the traffic of pages with 300 plus words.

Target 300 to 500 words. BigCommerce supports a separate "Page Content" rich-text field used below the product grid:

<p class="lead">{{category.description}}</p>
<!-- Product grid renders here -->
{{#if category.page_content}}
<section class="category-content">
  {{{category.page_content}}}
</section>
{{/if}}

Short framing copy above the grid and long-form buying guide content below.

6.2 Category Meta Tags

Each category supports separate SEO title, meta description, and Page Title field. Custom HTML field allows arbitrary HTML injection for buying guide content, FAQ sections, and additional schema.

More granular than Shopify's.

6.3 Brand Pages

BigCommerce supports Brand pages as a separate entity from Category. Brands have their own URLs (/acme/ by default), SEO fields, description, image, product listings.

Use Brand pages for multi-brand retailers where brand is a primary discovery axis ("Acme wallets" queries) or authorized dealer sites with brand-specific compliance. Single-brand stores: leave disabled or noindex. Brand page SEO setup mirrors category setup.

6.4 Faceted Search URL Parameter Handling

Covered in Section 4.5. For brand-axis filtering, a dedicated sub-category usually outperforms a query-string-filtered URL because the dedicated page accumulates unique content, schema, internal links, and ranking signal.

6.5 Category Schema

Stencil does not auto-render CollectionPage schema. BreadcrumbList (auto-rendered) is the primary structured data Google uses for category context. CollectionPage is recognized but does not currently produce rich results.

Do not invest in CollectionPage schema if absent. Focus on BreadcrumbList, Organization (site-wide), and FAQPage (category FAQ in Custom HTML).

6.6 The Duplicate Product Across Categories Concern

BigCommerce assigns each product a single canonical URL (custom_url); products do not get distinct URLs per category by default. The duplication concern that Shopify experiences with /collections/X/products/Y does not apply in default configuration.

If category prefixing is enabled, the duplication concern reappears. The flat-root configuration sidesteps it entirely.

7. Theme Performance

Theme performance is the single largest controllable factor in BigCommerce storefront speed.

7.1 The Stencil Performance Baseline

Stencil themes built by BigCommerce (Cornerstone and derivatives) ship cleaner code than legacy Blueprint. Cornerstone's Lighthouse mobile is 60s to mid-70s on a representative product page. Third-party Stencil themes score 50s to 70s; heavily customized drop into 30s to 50s.

Templates compile on every cache miss (80 to 250 milliseconds). CDN cache behavior is less aggressive than Shopify's edge; non-personalized content TTLs typically 15 minutes to 1 hour. JavaScript bundling via Webpack; image optimization via imgix URL pattern with WebP (since 2023); AVIF not yet standard.

7.2 The Cumulative Impact of Installed Apps

The cumulative effect across 10 to 30 apps on mature stores is the primary cause of poor Core Web Vitals on BigCommerce in 2026. Categories with highest performance impact:

Reviews and ratings apps. Yotpo, Bazaarvoice, Trustpilot bundles 50 KB to 300 KB compressed, often loaded on every page.

Live chat widgets. Zendesk Chat, Intercom, Drift bundles 100 KB to 500 KB. Always defer.

Personalization and recommendations. Nosto, Algolia, Klevu add 80 KB to 250 KB plus runtime queries.

Email and SMS marketing. Klaviyo, Mailchimp signup forms add 30 KB to 100 KB per page.

Analytics and tracking. GA4, GTM, Meta Pixel, TikTok Pixel, Pinterest Pixel cumulatively can exceed 200 KB if not deferred.

7.3 The BigCommerce Edge Cache

Integrated CDN with cache TTLs for catalog pages of 15 minutes to 1 hour. Cache invalidation triggers on admin edits with up to 5 minutes propagation. Less aggressive than Shopify's edge.

7.4 Catalyst for Significant Performance Gains

For merchants prioritizing performance, Catalyst on Vercel edge typically achieves Lighthouse mobile 85 to 95 versus Stencil's 60 to 80. Trade-off: engineering investment. Cross reference: Section 9 and framework-headless.md.

7.5 Where Performance Bottlenecks Actually Live

In audit work across approximately 80 BigCommerce stores from 2023 through 2026:

• 48 percent: app-shipped JavaScript
• 23 percent: image weight and format problems
• 12 percent: heavy Handlebars templates causing slow TTFB
• 9 percent: third-party tracking and chat scripts not deferred
• 8 percent: theme code reloading full pages where AJAX would suffice

App audit and trim is the highest leverage intervention.

7.6 The Performance Insights Dashboard

Storefront > Themes > Performance reports a performance score and recent Core Web Vitals from sampled visits. Updated on a delay of up to 7 days. Early-warning indicator; actual work requires PageSpeed Insights and CrUX field data.

8. App Ecosystem SEO Impact

Every app that ships a storefront integration adds JavaScript and HTTP requests. Audit and removal protocols port directly from Shopify.

8.1 The Canonical App Stack for SEO

Total stack runs 50 to 150 USD monthly. Above this is usually overlapping coverage.

8.2 The Performance Tax Audit

curl -s "https://example.com/brown-leather-wallet/" -o /tmp/page.html
grep -oE 'src="[^"]+\.js[^"]*"' /tmp/page.html | sort -u

BigCommerce apps typically ship from cdn.bigcommerce.com, *.bigcommerce.com, or the app developer's domain. Apps shipping multiple scripts are higher tax than apps shipping a single bundle.

8.3 The App Removal Protocol

Step 1. Document what the app does. Marketplace listing and admin notes.

Step 2. Identify replacements or accept feature loss.

Step 3. Uninstall. Stencil themes using script tag registration remove JavaScript automatically. Hard-coded snippets must be removed manually.

Step 4. Audit theme code for residue. Storefront > Themes > Edit Theme Files, search for {{> app-name-snippet}}, app-specific helpers, <!-- AppName widget -->.

Step 5. Measure performance after removal via PageSpeed Insights.

8.4 The Most Common SEO-Degrading Apps to Avoid

Patterns repeating across audits in 2024 to 2026:

Multiple overlapping reviews apps. Judge.me plus BigCommerce Reviews plus Stamped simultaneously, each 100 KB to 300 KB per page. Consolidate.

Multiple analytics platforms. GA4 plus Mixpanel plus Heap plus Amplitude all loaded. Pick one primary.

Live chat plus customer service tool plus FAQ widget all loaded everywhere. Pick one support stack.

Banner and popup app suites. Multiple banners, popups, notification banners simultaneously. Consolidate.

Old SEO apps with limited current value. Many duplicate functionality now built into Stencil or native admin.

8.5 Quarterly App Audit

Lists every installed app, monthly cost, actual usage. Identifies apps not used in 90 days, overlapping functionality, apps replaced by native features. Outputs a removal queue and an explicit keep list.

9. Headless BigCommerce with Catalyst

Catalyst is BigCommerce's official React-based framework for building headless storefronts, launched in 2024. The headless framework reference lives at framework-headless.md.

9.1 When Headless Catalyst Makes Sense

The case for: merchant outgrows Stencil's flexibility limits, has React engineering capacity, operates on Pro or Enterprise where engineering cost is rational against GMV, wants a brand-distinctive storefront design, prioritizes Core Web Vitals above app ecosystem coverage.

The case against: engineering cost. 40,000 to 200,000 USD initial plus ongoing engineering. Stencil themes upgrade with platform updates; Catalyst upgrades with the merchant's team. Catalyst is newer than Hydrogen (2024 versus 2021) and the ecosystem of templates and tooling is still maturing through 2026.

9.2 Catalyst Architecture

Next.js 14 plus React Server Components plus Tailwind CSS plus the GraphQL Storefront API. App Router handles all routing. RSC renders catalog server-side. TypeScript strict mode.

Authentication via Channel IDs (a multi-tenant storefront concept that allows one BigCommerce backend to power multiple frontend channels: Stencil storefront, Catalyst storefront, mobile app, marketplace integration).

Checkout transition: Catalyst handles browse, product detail, cart. The cart hands off to BigCommerce's hosted checkout via redirect or to a custom Open Checkout SDK implementation.

9.3 The Next.js 14 Plus React Server Components Pattern

The Next.js metadata API replaces Handlebars head injection:

// app/(default)/product/[slug]/page.tsx
export async function generateMetadata({ params }): Promise<Metadata> {
  const product = await getProduct({ slug: params.slug });
  return {
    title: product.seo.pageTitle || `${product.name} | ${product.brand?.name}`,
    description: product.seo.metaDescription,
    openGraph: { images: [{ url: product.defaultImage?.url || '' }] },
    alternates: { canonical: `https://example.com/${product.path}` }
  };
}

Schema injection per route uses JSON-LD in the route component, server-side rendered.

9.4 The GraphQL Storefront API

GraphQL queries fetch only required fields:

query GetProduct($slug: String!) {
  site {
    route(path: $slug) {
      node {
        ... on Product {
          entityId name path sku gtin mpn description
          brand { name }
          defaultImage { url(width: 1200) altText }
          prices { price { value currencyCode } }
          inventory { isInStock }
          seo { pageTitle metaDescription }
        }
      }
    }
  }
}

Server-side rendering in RSC ensures data is available at HTML generation time.

9.5 Deployment Targets

Vercel. Documented primary target. vercel deploy from the repository. Edge functions render globally; image optimization via Next.js Image; sitemap via route handlers; ISR reducing API calls.

Self-hosted nginx on Bubbles (169.155.162.118). Build as standalone Node server: next build then node .next/standalone/server.js. nginx handles SSL via Let's Encrypt and HTTP/2. Configuration at /etc/nginx/sites-available/[domain]. Static assets at /var/www/sites/[domain]/.next/static/. Cross reference: Section 14.

Netlify. Supported via the Next.js plugin.

Containerized on Kubernetes or Docker Swarm. Self-managed.

SEO behaviors are equivalent across deployment targets.

9.6 The App Marketplace Compatibility Gap

App Marketplace apps generally do not work on Catalyst because most target Stencil. App functionality must be reimplemented in React or skipped. Apps operating at admin or backend level continue to work because they interact with the admin and APIs, not the storefront.

9.7 Decision Framework

Under 2 million USD annual GMV: native Stencil almost certainly correct.

2 to 10 million USD annual GMV: contested. Stencil often wins; Catalyst wins for differentiated brand stores with engineering capacity.

Over 10 million USD annual GMV: Catalyst wins more often than not. Cross reference: framework-headless.md.

10. Schema for BigCommerce

Schema on BigCommerce is automatic (Stencil themes for Product and BreadcrumbList), partial, or absent (added via app, custom Handlebars, or Catalyst route-level injection). The full schema reference is framework-schema.md.

10.1 Product Schema (Automatic in Stencil)

Covered in Section 5.4. Augment for gtin, mpn, shippingDetails, hasMerchantReturnPolicy, hasVariant, and individual review entities where rendering is incomplete.

10.2 BreadcrumbList (Automatic in Stencil)

Stencil themes auto-render BreadcrumbList based on the navigation path:

curl -s "https://example.com/wallets/brown-leather-wallet/" \
  | grep -A 20 '"@type": "BreadcrumbList"'

Output should show Home > Category > Product. Themes with customized breadcrumb display sometimes break the schema; fix is in templates/components/common/breadcrumbs.html.

10.3 Organization Schema (Manual, Site-Wide)

Not auto-rendered. Add via custom Handlebars in templates/layout/base.html head, or via Storefront Settings > Apps > Insert HTML where theme edits are restricted:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "{{settings.storefront_url}}/#organization",
  "name": "{{settings.store_name}}",
  "url": "{{settings.storefront_url}}",
  "logo": {"@type": "ImageObject", "url": "{{cdn 'img/logo.png'}}", "width": 600, "height": 60},
  "sameAs": [
    "{{settings.social_facebook_url}}",
    "{{settings.social_instagram_url}}",
    "{{settings.social_twitter_url}}"
  ],
  "contactPoint": {"@type": "ContactPoint", "contactType": "customer service", "email": "{{settings.store_email}}"}
}
</script>

The sameAs array should include all canonical brand profiles. Cross reference: framework-knowledgegraph.md.

10.4 LocalBusiness Schema

For stores with physical retail locations, LocalBusiness schema augments the Organization entity. Add on a /visit-us/ or store locator page with @type LocalBusiness, postal address, geo coordinates, opening hours, telephone. Cross reference: framework-localseo.md.

10.5 Article Schema (Automatic in Stencil Blog Templates)

BigCommerce supports a built-in blog at /blog/. Stencil auto-renders Article schema: @type Article, headline, image, author, publisher, datePublished, dateModified, articleBody.

Gaps: author rendered as post author name but not as structured Person entity. Augmenting the author entity is high-value for E-E-A-T. See framework-eeat.md Section 6. publisher rendered as store name without full Organization entity; ensure Organization schema is published site-wide and reference its @id from Article schema.

10.6 FAQPage Schema

Add to product pages with FAQ sections and category pages with buying-guide FAQ. High value for AI surface citation:

{{#if product.custom_fields_faqs}}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {{#each product.custom_fields_faqs}}
    {
      "@type": "Question",
      "name": "{{question}}",
      "acceptedAnswer": {"@type": "Answer", "text": "{{answer}}"}
    }{{#unless @last}},{{/unless}}
    {{/each}}
  ]
}
</script>
{{/if}}

10.7 Review Schema if Using BigCommerce Reviews

BigCommerce's native Reviews feature renders aggregateRating into Product schema automatically. Individual Review entities not rendered by default but supported via theme augmentation or third-party reviews apps (Judge.me, Yotpo, Stamped) with schema support. Verify via curl | grep '"@type": "Review"'. Cross reference: framework-schema.md Section 8.

11. International BigCommerce

BigCommerce's Multi-Storefront feature is the platform's multi-country and multi-language capability, providing true per-country storefront separation rather than the subdirectory or subdomain model common to other platforms.

11.1 Multi-Storefront Architecture

Multi-Storefront is included with Enterprise and available as an add-on for Pro. Each storefront has a separate Channel ID, separate domain or subdomain or subdirectory, separate theme, separate catalog visibility, separate currency, separate tax and shipping, separate checkout localization. The BigCommerce backend is shared.

Materially different from Shopify Markets. Shopify Markets is one storefront with country-specific routing layered on; Multi-Storefront is multiple distinct storefronts sharing a backend.

11.2 Per-Storefront Configuration

Each storefront configures independently:

Domain or subdomain: example.com for US, example.co.uk for UK, de.example.com for Germany. Independent SSL, DNS. Choice governed by framework-international.md.

Theme: each storefront can run a different Stencil theme or Catalyst implementation.

Catalog: each storefront sees a configurable subset.

Currency and pricing: one primary currency per storefront. Price overrides via Price Lists (B2B Edition) or per-storefront pricing rules.

Language: translation files per Stencil theme.

Tax and shipping: configured per storefront to match country regulatory requirements.

11.3 Hreflang Implementation

Multi-Storefront does not auto-generate hreflang tags. The cluster must be implemented per storefront in templates/layout/base.html head:

<link rel="alternate" hreflang="en-US" href="https://example.com{{page.url}}" />
<link rel="alternate" hreflang="en-GB" href="https://example.co.uk{{page.url}}" />
<link rel="alternate" hreflang="en-CA" href="https://ca.example.com{{page.url}}" />
<link rel="alternate" hreflang="de-DE" href="https://de.example.com{{page.url}}" />
<link rel="alternate" hreflang="x-default" href="https://example.com{{page.url}}" />

The page URL is reused across storefronts assuming product and category handles are consistent. Where slugs differ per market, cluster must use absolute per-storefront URL mappings.

Audit: spot check three product pages, three category pages, the homepage. Confirm every storefront represented, every URL returns 200, x-default points to primary market, cluster is reciprocal. Cross reference: framework-hreflang.md.

11.4 Currency and Pricing Per Market

Multi-Storefront handles currency at the storefront level. Product offers.price and offers.priceCurrency reflect the current storefront's currency.

11.5 Per-Storefront Content Localization

Stencil themes support per-language translation files at lang/[locale].json. Catalog content requires translation per storefront. Catalyst handles localization via Next.js i18n routing. Translation apps include Weglot. Machine translation baseline plus human review for customer-facing content. Cross reference: framework-international.md Section 6.

11.6 Limits and Edge Cases

Up to 5 storefronts on Pro (with add-on), 25 plus on Enterprise. Does not handle: per-storefront customer accounts (shared by design), per-storefront order numbering, per-storefront product handles where global SKUs require global slugs.

12. B2B Edition Specific Features

B2B Edition is included with Enterprise and available as add-on at Pro. Adds customer-specific pricing, quote workflows, company accounts with sub-users, requisition lists, payment terms, gated catalog visibility.

12.1 Customer-Specific Pricing via Price Lists

Price Lists are tables of per-customer or per-customer-group product prices. A single product can have many prices depending on which customer is logged in. Fundamental to B2B commerce where contract pricing varies by account.

Storefront rendering: when a logged-in customer belongs to a customer group with a price list, the storefront displays prices from that list rather than the base product price.

SEO implication: pages for non-logged-in visitors (the default crawler experience) show base prices. Google sees the base price; schema offers.price reflects base price.

12.2 Quote Requests, Company Accounts, Requisition Lists, Payment Terms

Quote workflows allow customers to add products to a quote rather than directly to cart. The merchant reviews, adjusts pricing, and converts to purchase order.

Company accounts have sub-users with role-based permissions. Standard for B2B procurement teams.

Requisition lists are saved lists of frequently ordered products for repeat purchase.

Payment terms (Net 30, Net 60, Net 90) managed per customer or customer group at checkout for approved B2B customers.

SEO implication: these flows are gated behind login and not crawlable. Public-facing product pages remain crawlable with base pricing visible.

12.3 The SEO Implications of Gated B2B Catalog Content

The merchant decides what to expose publicly versus what to gate:

Pattern A, fully public catalog, gated pricing. Product pages crawlable. Display "Login for Pricing". Schema offers.price omitted or set to 0 with priceSpecification "request for quote". Preserves SEO surface; AI engines and Google index specifications and compatibility data.

Pattern B, fully public catalog with public list pricing, customer-specific overrides on login. Product pages crawlable with public list prices. Logged-in customers see contract prices that are not crawlable. Most common pattern.

Pattern C, fully gated catalog. Product pages noindex or behind login wall. SEO surface is the homepage, About page, public content. Inevitable for catalogs with regulatory or competitive restrictions on price visibility.

12.4 The Indexable-vs-Gated Decision Tree

For each catalog segment:

1. Public or by-invitation B2B? If by-invitation, the catalog gates.
2. Pricing public or contractually confidential? If confidential, "Login for Pricing" or "Request a Quote".
3. Specification data publicly searchable elsewhere? If yes, exposing specifications captures search demand.
4. Customer acquisition pattern? If customers find the merchant via search, public product pages with rich specifications win. If via direct outreach and trade shows, the catalog can gate without organic search consequence.

Cross reference: framework-ecommerceseo.md Section 9.

12.5 B2B Edition Schema Augmentation

For Pattern A and B catalogs, augment Product schema with B2B-specific properties:

{{#if product}}
<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "Product",
  "@id": "{{settings.storefront_url}}{{product.url}}#b2b",
  "name": "{{product.title}}",
  "manufacturer": {"@type": "Organization", "name": "{{product.brand.name}}"},
  "mpn": "{{product.mpn}}",
  "offers": {
    "@type": "Offer",
    "priceSpecification": {
      "@type": "PriceSpecification",
      "priceCurrency": "{{currency_selector.active_currency_code}}"
    },
    "eligibleCustomerType": ["https://schema.org/BusinessEntityType"]
  }
}
</script>
{{/if}}

Signals B2B intent to search engines and AI engines, increasing the probability of matching B2B-specific query intent.

13. BigCommerce Migration

Migration in or out of BigCommerce happens for operational, cost, or feature reasons. The discipline is the same as for any platform migration: full URL inventory, exhaustive mapping, redirects implemented at launch, verification post-launch.

13.1 Shopify to BigCommerce

The most common inbound migration. Reasons: outgrowing Shopify's URL constraints, needing native faceted search, needing B2B Edition, wanting Multi-Storefront.

Catalog export from Shopify via admin Products > Export CSV. CSV does not include metafields (export via Admin API), theme content, redirects, or customer data with order history.

URL mapping. Shopify forced prefixes collapse to cleaner URLs:

/products/widget → /widget/
/collections/wallets → /wallets/
/pages/shipping → /shipping/
/blogs/news/post → /post/ or /blog/post/

Redirect implementation: BigCommerce 301 Redirects admin supports CSV bulk import. Migration tools: Cart2Cart, LitExtension, BigCommerce-provided services. URL mapping discipline remains the operator's responsibility regardless of tool.

13.2 Magento to BigCommerce

Rising as Magento Open Source support uncertainty drives merchants to managed platforms. Magento URL structures often include /catalog/category/, /catalog/product/view/, and category-prefixed product URLs.

URL mapping:

/catalog/product/view/id/123/s/widget/ → /widget/
/catalog/category/view/id/45/ → /wallets/
/[category]/[product].html → /[product]/

Mapping varies by configuration. Migration tools: Cart2Cart, LitExtension.

13.3 BigCommerce to Shopify

Less common; merchants wanting Shopify's larger theme ecosystem, app marketplace, or Hydrogen path. Trade-off: losing root-level URL control.

URL mapping:

/widget/ → /products/widget
/wallets/ → /collections/wallets
/shipping/ → /pages/shipping
/blog/post/ → /blogs/news/post

Every existing inbound link now requires a 301 redirect to a longer URL. Internal link discipline must update across the migration.

13.4 BigCommerce to Custom Commerce

Least common. Reasons: bespoke catalog logic, integration requirements BigCommerce cannot meet, regulatory data residency.

Catalog export from BigCommerce admin or via REST API. URL mapping at the new platform's routing layer. Schema, hreflang, sitemap all custom-implemented. Highest-risk migration class because the target has not been battle-tested.

13.5 URL Mapping Discipline

For any BigCommerce migration:

1. Crawl the source completely (Screaming Frog, Sitebulb, wget --recursive).
2. Build the mapping spreadsheet: source URL, target URL, expected response (301 or 410), priority.
3. Verify target URLs exist before launching. Every target must resolve 200 in staging.
4. Implement redirects via BigCommerce 301 Redirects admin CSV upload.
5. Validate post-launch by re-crawling the source URL list; expect 301 to target with 200.
6. Monitor Search Console for 4xx errors daily for the first week, weekly thereafter for 90 days.

Cross reference: framework-migration.md.

13.6 The Migration Audit Rubric

For any BigCommerce migration (in or out):

Acceptable migration: 13 plus / 15. Below 13, the migration introduces ranking risk to remediate before closure. Cross reference: framework-migration.md.

14. Bubbles-Hosted BigCommerce Adjacent Stack

BigCommerce is SaaS and cannot be self-hosted. For merchants wanting self-hosted equivalent functionality, the path is custom commerce on Bubbles. For merchants on BigCommerce wanting supplementary analytics, reporting, content management, or customer-facing surfaces hosted independently, the Bubbles stack provides supporting infrastructure.

14.1 The Self-Hosted Alternative for BigCommerce-Like Functionality

For clients wanting BigCommerce-equivalent functionality on self-hosted infrastructure, the recommended path is a Hydrogen-like architecture on nginx.

Frontend. Next.js 14 plus React Server Components plus Tailwind CSS, the same architecture Catalyst uses but with a custom backend.

Backend catalog. Custom Node.js GraphQL server or packaged commerce backend like Medusa or Saleor. Catalog, customer, and order data managed locally on Bubbles.

Database. PostgreSQL for transactional data, Redis for session and cart state.

Hosting. nginx at IP 169.155.162.118 serving the Next.js production build. Static assets at /var/www/sites/[domain]/static/. SSL via Let's Encrypt.

Payment. Stripe, Square, or equivalent at backend layer.

No third-party CDN or proxy. nginx handles all caching, compression, HTTP/2.

Cost is engineering investment. Benefit is total control, no per-storefront SaaS fees, integration into the Bubbles-hosted stack.

14.2 Bubbles-Hosted Supplementary Infrastructure for BigCommerce Stores

For clients on BigCommerce, supplementary Bubbles infrastructure supports the storefront without replacing it:

Self-hosted Plausible analytics at analytics.[client-domain].com. Plausible Community Edition on Bubbles, nginx reverse proxy at port 8000. Configuration at /var/www/sites/analytics.[client-domain]/.

Self-hosted Metabase reporting. Operational dashboards for merchandising, inventory, customer analytics. Data feeds from BigCommerce admin API into a PostgreSQL warehouse on Bubbles. Configuration at /var/www/sites/dashboards.[client-domain]/.

Self-hosted Nextcloud for content management. Brand assets, product photography, datasheets, marketing collateral. WebDAV. Configuration at /var/www/sites/cloud.[client-domain]/.

Custom landing pages on the same domain. nginx proxies specific paths to a separate Bubbles-hosted application:

server {
  server_name example.com;
  location /knowledge-base/ { proxy_pass http://127.0.0.1:8050; }
  location /landing/ {
    root /var/www/sites/example.com/landing;
    try_files $uri $uri/ /landing/index.html;
  }
  location / {
    proxy_pass https://store-abc123.mybigcommerce.com;
    proxy_set_header Host store-abc123.mybigcommerce.com;
  }
}

Keeps the BigCommerce storefront at most paths while serving custom content from specific paths on the same domain.

14.3 No Third-Party CDN or Proxy

nginx at IP 169.155.162.118 serves traffic directly. SSL, compression, HTTP/2, caching all at nginx.

Strengths: no third-party data exposure, billing dependency, rate limits, or uptime dependency; complete control over caching and headers.

Constraints: geographic latency to clients distant from Bubbles, no built-in DDoS mitigation beyond nginx and host network, no edge function execution beyond sidecar Node services.

For most TDG clients, the constraint set is acceptable. For global commerce with high DDoS risk, BigCommerce's native hosted edge or Vercel edge deployment may be appropriate.

14.4 The Bubbles Infrastructure Documentation Reference

Each client receives documentation at /var/www/sites/[domain]/docs/: stack inventory, DNS configuration, backup schedule (daily PostgreSQL dump to /mnt/storage, weekly full site tarball), monitoring, recovery procedures.

End of Framework

This framework documents the BigCommerce SEO surface as of 2026: Stencil theme architecture, URL aliasing, product and category optimization, schema augmentation, app stack discipline, performance recovery, Multi-Storefront international, B2B Edition, headless via Catalyst, migration patterns, and the Bubbles-hosted supplementary infrastructure pattern.

BigCommerce's SEO posture in 2026 is materially strong for mid-market and B2B merchants. Root-level URL control eliminates Shopify's forced-prefix constraint. Native faceted search avoids paid-app dependency. Multi-Storefront enables true per-country storefront separation. B2B Edition supports gated catalog patterns with appropriate SEO discipline. Catalyst provides a clean path to performance-optimized headless implementations on Next.js. The platform's constraints (smaller theme and app ecosystem than Shopify, modest CDN baseline) are operationally manageable for most merchants and irrelevant for headless implementations on Vercel or Bubbles.

Companion frameworks:

• framework-ecommerceseo.md for cross-platform e-commerce SEO foundations.
• framework-cross-stack-implementation.md for per-framework code equivalents.
• framework-schema.md for the comprehensive schema reference.
• framework-hreflang.md for the hreflang tag reference.
• framework-international.md for the strategic international SEO framework.
• framework-migration.md for the platform migration playbook.
• framework-pageexperience.md for Core Web Vitals.
• framework-headless.md for the headless commerce framework reference.
• framework-technicalseo.md for technical SEO baseline.
• framework-mobileseo.md for mobile commerce optimization.
• framework-shopify.md for the parallel Shopify reference.
• framework-magento.md for the parallel Magento reference.
• framework-aicitations.md for AI citation patterns.
• framework-aioverviews.md for Google AI Overviews optimization.