Salesforce Commerce Cloud SEO: URLs, Facets and Templates

Salesforce Commerce Cloud SEO is mostly configuration, not content. Rankings depend on the URL rules and canonical flags set per site and locale in Business Manager, the SEO fields on each product…

Quick answer. Salesforce Commerce Cloud SEO is mostly configuration, not content. Rankings depend on the URL rules and canonical flags set per site and locale in Business Manager, the SEO fields on each product and category, how refinement parameters are handled, and whether your SFRA or Composable Storefront template renders meta tags and structured data server-side. None of it ships tuned; every default needs a decision.

What matters most
  • On Salesforce Commerce Cloud, URLs are configuration: one URL rule marked canonical per locale decides what every product and category path looks like.
  • The canonical tag is rendered by the template and can contradict the URL rule, so the two have to be audited together.
  • Refinement parameters need an index-or-exclude decision written into the search template, because there is no settings screen for it.
  • SFRA and Composable Storefront emit head tags in different places, and only server-rendered tags are dependable.
  • There is no app store, so metadata, structured data and redirect handling are code-and-deployment work.
What does Salesforce Commerce Cloud control, and what stays manual?

Salesforce Commerce Cloud, still called B2C Commerce in most documentation, splits SEO work across two layers. The first is Business Manager: URL Rules, Aliases, and the per-locale SEO fields on every product, category and content asset. The second is the storefront code that turns those settings into HTML. Most stalled SEO projects on this platform come from confusing the two. A merchandiser can fill in a page title, but only a template decides whether it reaches the page.

The platform is configurable rather than open. There is no app store to install an SEO plugin from. Improvements arrive as cartridge code, Commerce API integrations, or rules at the CDN edge in front of the storefront. That gives you precise control and a slow change cycle. Assume template work needs a developer, a code version and a deployment window.

Two storefront architectures are in use. SFRA renders ISML templates on the application server. Composable Storefront, formerly PWA Kit, runs a React application on Managed Runtime. Both read the same catalogue and the same URL configuration, but they fail in different ways. Establish which one you run before you plan anything.

Where to go next
How do URL rules and canonical tags behave on Salesforce Commerce Cloud?

URL Rules, under Merchant Tools > SEO, define the path each controller produces for each site and locale. A rule is a pattern built from catalogue identifiers and names. One rule per locale can be marked canonical, and that choice decides which URL the storefront generates for a product or category.

Because URLs are configuration, they are also fragile. Change a URL rule and every product URL on the site changes at once. Plan the redirect set before you touch the rule, not after. Aliases give you 301s, but they are managed one entry at a time. A replatform-sized redirect map usually needs a scripted import or a redirect layer sitting in front of the CDN.

Controllers without a matching rule fall back to parameter-based URLs. Any new page type you add, such as a buying guide or a brand landing page, needs its own rule before it looks like a real page to a crawler.

The canonical tag is a separate decision from the URL rule. It is rendered by the template from the page’s metadata, and it can disagree with the rule that generated the page. When the two conflict, search engines follow the tag, so a stale canonical can quietly point every product at a URL that redirects. Audit the tag, not only the rule.

Multi-site setups need care. Each site and locale carries its own rules, and a default site redirect catches people who land on the wrong one. Do not canonicalise every locale to a single language version; pair them with hreflang instead. One canonical per locale, cross-referenced between them.

How should you handle faceted navigation and refinement URLs?

Refinements in Salesforce Commerce Cloud are parameters appended to the search controller, not path segments. Every combination a shopper can click is a URL a crawler can reach. Colour, size, price band, sort order and page number multiply quickly, and none of them are excluded by default.

Decide a policy in three buckets and write it down:

The hard part is implementation. In SFRA, the search results template renders one head for every refinement state unless the template branches on which refinements are present. So the index-or-exclude rule has to live in code, keyed on the refinement set, not in a settings screen. A blanket noindex across all refinements throws away the landing pages worth having; a blanket index fills the crawl with dead combinations.

A canonical tag back to the base category only works when the filtered page genuinely shows the same products. When the set differs, treat it as a distinct page or exclude it. Use canonical tags to consolidate duplicates, not to hide pages nobody wants to write.

Refinement definitions are configured per site, so this is a merchandising decision as much as a technical one. Fewer, cleaner facets make both the filter panel and the crawl easier to manage.

  • Index: the base category, plus a short list of refinements that match real demand, each with a dedicated landing page, copy and internal links.
  • Exclude: two or more refinements combined, sort order, view mode and page number. These add crawl paths and rarely earn a visit.
  • Block: tracking, session and preview parameters. These never carry content.
Meta tags and structured data sit in two different layers

In SFRA, product and category pages read page title, description and keywords from the localizable SEO fields in Business Manager, then render them through the shared head template, common/htmlHead.isml. Product pages use product/productDetails.isml; category and search pages use search/searchResults.isml. When a field is empty, the template falls back to a default, usually the item name plus the site name. That is how a catalogue ends up with hundreds of near-identical titles.

Composable Storefront works differently. The React app renders on Managed Runtime, so head tags must be in the server response. Anything a component adds after hydration is unreliable for crawlers, which is a well-documented limitation of JavaScript rendering. View source, not the rendered DOM, when you check a page.

Structured data is not a built-in module on either architecture. You template the JSON-LD yourself: Product and Offer with price, currency and availability, plus whatever supporting types your catalogue can honestly fill. Because you own the markup, you also own the mistakes, so validate it against schema.org and in Search Console after every template release.

The table below is the comparison worth keeping. The failure modes differ far more than the settings do.

JobSFRA (ISML)Composable Storefront (React)What to verify
Head tagsRendered on the application server via common/htmlHead.ismlRendered during server-side React rendering on Managed RuntimeTags present in page source
URL controlURL Rules in Business Manager, per site and localeThe same rules, or routes defined inside the appOne canonical rule per locale
Structured dataJSON-LD written into ISML templatesJSON-LD written into the rendered componentValid output in Search Console
Refinement pagesParameters handled in searchResults.ismlParameters handled on the search routeIndex or exclude decision per refinement
Migration traps that cost the most traffic

SiteGenesis to SFRA to Composable Storefront is a common path, and each step touches URLs and head tags. The front end changes, but the catalogue and the URL configuration stay behind. If the new storefront builds URLs differently, every old product URL returns a 404 on launch day.

Test by crawling the old and new URL sets and comparing them side by side, before launch. After launch, keep the redirect layer in place for as long as analytics still shows arrivals on old paths. Do not remove it because the redirect report looks quiet.

  • URL rules re-implemented from scratch, so paths change with no redirects behind them.
  • Product and category URL identifiers regenerated by a catalogue import, silently changing every path.
  • Staging, sandbox and demo sites left crawlable and competing with production.
  • Canonical tags still pointing at the previous domain or at a staging hostname.
  • Sitemaps generated from a different rule set than the storefront uses.
  • Cached HTML at the CDN holding old canonicals long after a rule change.
How do you measure Salesforce Commerce Cloud SEO honestly?

Business Manager reporting is built around orders and catalogue performance. It will not tell you which organic landing pages earn revenue. For that you need Search Console plus your analytics, joined on landing URL, with a consistent URL format on both sides. Clean, stable URL rules are what make that join possible.

The limits are real. On a headless build, analytics can fire client-side only, so you see the visit but lose the landing page. Multi-site and preview setups can split reporting across hostnames. Neither is an SEO problem until it hides the data you need for a decision.

Three checks are worth running monthly: how many URLs are indexed against how many the storefront can generate, how many indexed URLs carry a refinement parameter, and how many products have empty SEO fields. The last one is answerable from a catalogue export, without a developer.

What should you fix first?

Work in this order. Each step makes the next one cheaper.

None of it is exotic. It is configuration and template work, done in a fixed sequence, on a platform where both layers have to agree before a page can rank.

  • Crawl the live storefront and compare it with the catalogue: orphaned products, redirect chains, URLs reachable only through filters.
  • Audit the URL Rules, confirm one canonical rule per locale, then check the canonical tag on a sample of product and category pages against it.
  • Fill SEO fields at category level first, then the highest-revenue products. One category template covers many more URLs per edit.
  • Set the refinement policy and implement it in the search template rather than reaching for robots.txt.
  • Repair or add Product structured data, and revalidate it after every release.
  • Put a redirect process in place before the next replatform or catalogue import, not after it.
Frequently asked questions

Does Salesforce Commerce Cloud have an app store for SEO tools?

No. Unlike Shopify or BigCommerce, B2C Commerce has no marketplace where you install an SEO app. Changes arrive as cartridge code, Commerce API integrations or rules at the CDN edge. That means metadata, structured data and refinement handling all need a developer and a deployment. The upside is that nothing else is competing for control of the page head.

Can a merchandiser edit meta titles and descriptions in Business Manager?

Yes. Products, categories and content assets each carry page title, page description and keyword fields per locale. The catch is that the storefront template has to output them, and empty fields fall back to defaults. Editing the fields is a merchandising task. Making sure they appear correctly, with a sensible fallback, is template work.

Should I block faceted URLs with robots.txt?

Rarely as a first move. Blocking stops crawling, not indexing, and it also hides pages you may want to keep. Decide per refinement instead: index the ones with real demand and a dedicated landing page, exclude combinations and sort parameters with meta robots, and reserve robots.txt for parameters that never carry content.

Is Salesforce Commerce Cloud bad for SEO out of the box?

It is neither good nor bad; it is unconfigured. The platform can produce clean, stable URLs and fully server-rendered HTML. It will do neither until someone sets the URL rules, fills the SEO fields and writes the head templates. Most Salesforce Commerce Cloud SEO problems are decisions nobody made, not limitations in the product.

Does moving to Composable Storefront hurt rankings?

A move does not have to, but the risk is higher than a template refresh. URLs, head tags, structured data and analytics all get rebuilt in a React app, and anything rendered only after hydration is a risk. Keep the URL structure identical, render tags on the server, and compare old and new URL sets with a crawl before launch.

Sources
Audit the storefront before you brief a rebuild

We crawl Salesforce Commerce Cloud storefronts, compare live URLs against the catalogue and the URL rules, and hand back a prioritised fix list for the template and merchandising teams.

Request the SEO audit