BigCommerce Catalyst SEO

Catalyst is BigCommerce's open-source Next.js + React headless storefront, paired with the Makeswift visual editor for non-developer content authoring. Stencil is the classic templated stack — Cornerstone theme on Handlebars served by BigCommerce's edge. The differences that matter for SEO: Catalyst gives you full Next.js control (App Router, RSC, edge runtime, ISR, custom sitemap and metadata APIs), while Stencil ships with BigCommerce's templating and sitemap conventions out of the box. Catalyst trades convenience for control — and SEO ownership shifts to the front-end repo.

Yes — 1Digital® Agency is a BigCommerce Elite Partner and BigDev Certified, with BigCommerce work continuously since 2012. We've audited and shipped SEO on both Stencil + Cornerstone and Catalyst + Makeswift stacks, with 400+ brands trusted and a 4.9/5 rating across 941+ verified reviews. Catalyst SEO engagements pair naturally with React engineering capacity from the same team.

Catalyst on Next.js App Router uses RSC by default. SEO consequences: (1) RSC-rendered HTML ships to crawlers without client-side JS execution requirements, which is good for Google and excellent for AI-engine crawlers that don't execute JS; (2) client component boundaries (use client directives) must be drawn carefully — interactive widgets (variant pickers, mini-cart, search-as-you-type) need 'use client', but PDP body content, breadcrumbs, schema, and metadata stay in RSC; (3) loaders and Server Actions handle data fetching, so JSON-LD can be emitted at the server with live catalog data. Drawing the RSC / client boundary at the component level is the highest-leverage Catalyst SEO decision.

BigCommerce's GraphQL Storefront API exposes catalog data (products, categories, variants) that Catalyst queries at build time, request time, or on a revalidation schedule. For sitemap orchestration: (1) build a sitemap-index.xml at the front-end origin with sub-sitemaps for products, categories, content, and editorial routes; (2) sub-sitemaps query the Storefront API on a revalidation cadence (every 60 minutes is typical) or on webhook from BigCommerce; (3) rate-shape sitemap generation to stay within Storefront API plan limits — generating 50k-product sitemaps per request can exhaust your daily budget. We architect the orchestration and instrument cache headers.

JSON-LD must be server-emitted on every indexable route. In Next.js App Router (Catalyst's framework), that's either (a) the generateMetadata() function for metadata-shaped schema, or (b) a server component that renders with content loaded from Storefront API. We architect schema at two levels: layout-level (Organization, WebSite — once per app) and route-level (Product, Offer, Review, BreadcrumbList, FAQPage, Article — per page). All schema is server-rendered; no client-side dynamic schema, which crawlers may not execute.

Makeswift is the visual editor BigCommerce ships alongside Catalyst — non-developers compose pages with React components in a WYSIWYG canvas. SEO consequences: (1) editorial routes (landing pages, content marketing surfaces) authored in Makeswift need the same metadata, schema, and canonical discipline as code-authored routes — we wire Makeswift's metadata fields into Next.js generateMetadata; (2) sitemap generation must include Makeswift-authored URLs alongside catalog URLs; (3) component-level schema (FAQPage, Article) is injected by the Makeswift component set, not authored per page. We extend the Makeswift component library with SEO-aware variants.

Stencil pros: zero-config sitemap, BigCommerce-managed canonical conventions, faster initial setup, no front-end ops burden. Catalyst pros: full Next.js control, edge runtime for lower TTFB and better INP, RSC for AI-crawler-friendly server-rendered HTML, custom routing for programmatic SEO, Makeswift for editorial without dev tickets. For brands where SEO depth is a competitive moat — programmatic landing pages, deep editorial, headless-multi-channel — Catalyst wins. For brands that just need a fast catalog with good defaults, Stencil is often enough. We help merchants pick the right stack for their SEO ambitions, not the most fashionable one.

Default to SSR for PDPs and categories that need fresh catalog data per request. Use ISR for editorial routes (blog, landing pages) and high-traffic PDPs where 60-300 second revalidation is tolerable. Use SSG for evergreen marketing pages and programmatic SEO templates with low update frequency. Never use pure CSR for indexable routes — Google's render budget multiplies indexation latency, and AI-engine crawlers (GPTBot, ClaudeBot, PerplexityBot) typically don't execute JS. We define a per-route render strategy and document it in the repo.

Yes. Catalyst can authenticate against BigCommerce B2B Edition's customer-group and price-list system via Storefront API auth. SEO implications: customer-group-aware rendering must respect the indexable / gated boundary — anonymous visitors (Googlebot) see the public catalog only; authenticated visitors see group-specific pricing and gated SKUs; JSON-LD Offer.price always reflects the public catalog price, never per-group discounts. See BigCommerce B2B SEO for the full B2B Edition SEO program — Catalyst is one of two stacks we ship on (the other is Stencil).

Phase 1: render-strategy audit per route (SSR / ISR / SSG), RSC vs client component boundary review, schema coverage map, sitemap orchestration audit, Storefront API rate-limit health, Makeswift integration audit, Core Web Vitals per template. Phase 2: foundation — sitemap-index rebuild, schema graph at layout + route, canonical and hreflang topology, INP-targeted hydration boundary refactor, llms.txt deployment, edge runtime audit. Phase 3: growth — keyword-to-route mapping, programmatic SEO templates, Makeswift-driven editorial production, AI-engine citation tracking. Code lands directly in the Catalyst repo.