Salesforce Commerce Cloud SEO

Salesforce Commerce Cloud (SFCC) is the SaaS commerce platform Salesforce acquired from Demandware in 2016. The platform is still often referred to as Demandware in technical contexts, and many SFCC implementations carry legacy Demandware patterns — older SiteGenesis cartridges, classic Business Manager controls, and OCAPI integrations. SFCC SEO has to span both the modern stack (SFRA storefront reference architecture, SCAPI) and the legacy stack (SiteGenesis, OCAPI). We audit and ship on both.

Yes. While our deepest tenure is on Shopify Plus (certified Plus Partner), BigCommerce (Elite Partner since 2012), and Adobe Commerce (14 years), we ship SFCC SEO engagements as part of our enterprise platform competency. Our SFCC work covers SiteGenesis and SFRA storefronts, Business Manager URL and SEO controls, OCAPI / SCAPI headless implementations, and Core Web Vitals on both classic and modern stacks. Trusted by 400+ brands with a 4.9/5 rating across 941+ verified reviews.

SFRA (Storefront Reference Architecture) is SFCC's modern storefront framework — server-side rendered, ISML templating, controller-based routing, designed for clean separation of concerns. SiteGenesis is the legacy reference architecture — older cartridges with deeper coupling between presentation and business logic. SEO differences: SFRA storefronts typically achieve cleaner Core Web Vitals out of the box (smaller bundles, better caching defaults), more maintainable schema injection, and simpler URL routing. SiteGenesis stores rank fine but need more aggressive performance work and often have legacy URL patterns that compound 301 chain depth.

Business Manager is SFCC's admin UI. SEO-relevant controls: (1) URL configuration — SEO-friendly URLs (slug-style) vs. legacy parameter URLs; (2) per-site canonical settings — choose which storefront context owns canonical for shared catalog products; (3) robots.txt configuration per site; (4) sitemap generation cadence and inclusion rules; (5) hreflang configuration for multi-locale storefronts. We audit Business Manager settings as part of every SFCC SEO engagement — many issues are configuration, not code.

ISML (Internet Store Markup Language) is SFCC's templating system — server-rendered, with custom tags for catalog data and content slot rendering. ISML templates handle meta tag emission, canonical, hreflang, and JSON-LD output. Constraints: (1) custom code typically lives in cartridge controllers and ISML templates, so SEO changes ship through cartridge deployment; (2) content slots (managed in Business Manager) can inject HTML that breaks structured-data validity if not authored carefully; (3) URL rewriting is controlled via Business Manager URL rules and pipeline routing — changes require careful regression testing because legacy URL patterns can be load-bearing for indexed pages. We design SEO changes to respect cartridge deployment cadence.

SFCC's faceted search (refinements) generates parameter URLs by default. SEO patterns: (1) canonical tag on filter URLs points back at the unfiltered category to prevent duplicate-content cannibalization; (2) selectively whitelist high-intent filter combinations as indexable landing pages with their own meta, content, and breadcrumb schema; (3) Business Manager URL rules can map specific filter values to friendly slugs (e.g. /shoes/men instead of /shoes?refine_1=men) — a one-time architecture decision that pays off in SERP click-through; (4) robots.txt patterns or meta-robots noindex,follow for non-promoted filter combinations.

OCAPI (Open Commerce API, REST) and SCAPI (Salesforce Commerce API, modern REST + GraphQL) expose catalog, customer, and order data to headless front-ends. SEO ownership moves to the front-end repo — typically Next.js, Nuxt, or React Native Web. We follow the same playbook as our broader headless commerce SEO program: SSR-first render strategy, sitemap orchestration at the front-end origin (querying OCAPI/SCAPI for catalog data), schema injection at the layout, llms.txt deployment, and crawler-equivalent HTML verification. SFCC API rate limits matter — we cache responses at the edge and rate-shape sitemap generation.

SFRA storefronts typically need bundle size work (vendor JS, ISML-rendered content slots, third-party tag injection from Business Manager content assets) and image optimization (SFCC's Dynamic Imaging Service is good but underused — most stores serve un-resized images). SiteGenesis stores need deeper performance work: legacy RequireJS/jQuery patterns, larger CSS bundles, slower TTFB from heavier cartridge controllers. INP work focuses on minicart, search-as-you-type, and refinement update handlers — the usual offenders. We instrument LCP, INP, CLS per template and produce a per-route improvement plan.

Yes, via SFCC B2B Commerce (formerly Salesforce B2B Commerce on Lightning, then migrated to the SFCC platform). SEO patterns: indexable / gated boundary between public catalog and authenticated buyer portal; customer-group-aware schema that emits public prices only; quote-only PDP patterns with Offer schema reflecting "quote required" semantics; multi-site B2B configurations with canonical pinning across regional or sub-brand storefronts. The underlying SEO discipline is the same as BigCommerce B2B SEO or Plus B2B Edition; the implementation maps onto SFCC's site, customer-group, and pricing-book primitives.

Phase 1: audit covering Business Manager SEO settings, URL rule cleanliness, sitemap freshness, canonical and hreflang topology, ISML schema coverage, refinement (faceted) indexation, OCAPI/SCAPI caching for any headless surfaces, and Core Web Vitals per template (SFRA or SiteGenesis). Phase 2: corrective — Business Manager configuration tuning, URL rule consolidation, schema rebuild via ISML templates, faceted-nav rules, CWV work targeted at the template-level. Phase 3: keyword-to-category mapping, content briefs aligned with SFCC's content slot system, AI-engine optimization (llms.txt, entity-rich PDPs), and citation tracking across ChatGPT Shopping, Perplexity Shop, Google AI Overviews, Gemini, Microsoft Copilot.