Demandware SEO: Salesforce Commerce Cloud SEO for SFRA and Composable Storefronts

Updated October 2026 · Written and maintained by the Progression Agency strategy team

Salesforce Commerce Cloud SEO is technical work inside a platform most marketers never see: URL rules in Business Manager, SEO attributes on products and categories, redirect mappings, locale alternates, search refinement URLs and, on composable storefronts, what a crawler receives before JavaScript runs. Demandware SEO is the same job under the platform’s old name, which many teams still use. This page walks through each area, the migration risks and what to ask a Demandware SEO expert. We run ecommerce and technical SEO for large stores, and on Commerce Cloud we write the fix list and work with your developers or systems integrator, who change the code.

What is Salesforce Commerce Cloud SEO?

Salesforce Commerce Cloud SEO is the work of making a Commerce Cloud storefront easy for search engines to crawl, understand and rank. It covers the settings that build URLs and meta tags, the redirects that carry old addresses forward, the locale setup of multi-site stores and, on newer builds, how pages are rendered.

What did Salesforce Commerce Cloud used to be called?

The platform was called Demandware. Salesforce announced in June 2016 that it would acquire Demandware, and its release said the deal would create the new Commerce Cloud. Salesforce’s current training and developer material calls the product B2C Commerce, and teams use all three names, which is why Demandware SEO and Commerce Cloud SEO describe the same storefronts.

Is Salesforce Commerce Cloud a CMS?

Not in the way WordPress is. It is a commerce platform with a catalog, a storefront and content tools: content assets that live in folders and libraries, and Page Designer for building pages from components. Some teams pair it with a separate content system for long articles. Where that content lives changes where its SEO is controlled.

Stores and teams this page is for

This page is for brands and retailers running B2C Commerce, whether on SFRA or on a PWA Kit storefront, and for the in-house ecommerce, SEO and development teams around them. We work with businesses only. If you are choosing a platform rather than optimizing one, our ecommerce marketing agency page is the better start.

Is Salesforce Commerce Cloud good for SEO?

It can be, and the outcome depends on configuration and on the storefront code. The platform gives you the controls that large stores need; whether they are used well decides if Commerce Cloud SEO helps or hurts.

What the platform handles well

Salesforce’s training describes search-friendly URL patterns that you control, page meta tags that can be managed in Business Manager, sitemap creation for external search engines and locale handling across sites. The controls are real. A store that uses them deliberately starts well ahead of one that leaves the defaults in place.

Where Commerce Cloud stores lose search traffic

The losses are consistent: refinement URLs that multiply thin pages, redirect gaps after launches, third-party scripts that slow templates and, on headless builds, pages that depend on client-side rendering. Duplicate URLs for variation products and locales that fail to point back at each other round out the list.

How it compares with Shopify and BigCommerce for search

Platforms with a more fixed structure, such as Shopify and BigCommerce, tend to leave fewer choices to get wrong. Commerce Cloud leaves more to configure and to code, which suits large catalogs with several sites and a team that can change code. A smaller store may not need that freedom; see Shopify SEO and BigCommerce SEO for those.

Commerce Cloud SEO settings in Business Manager

Commerce Cloud SEO starts in Business Manager, where administrators set how URLs and meta tags are produced and which pages go in sitemaps. Menu names change between Salesforce releases, so we do not print paths; your administrator can find the current ones in the Salesforce documentation for your release.

Salesforce Commerce Cloud URL rules and SEO URLs

A URL rule is a pattern that tells the platform how to build an address, for example from the category path and the display name joined by hyphens. Salesforce’s training also covers character replacement, such as turning an ampersand into a hyphen, lowercase conversion and whitespace handling, a 1,800 character URL limit and a preview that surfaces conflicts. Settle the patterns before launch, because every change later is a redirect you must maintain.

Page meta tag rules

Meta tag rules produce titles and descriptions from product and category data, so thousands of pages get a sensible tag at once. The platform lets these rules be inherited down the category tree or from content folders. Write rules that place the product or category name first, then override by hand on the categories that earn the most revenue.

SEO attributes on products, categories and content assets

Products, categories and content assets each carry fields for a page title, page description, page keywords and a page URL, in the platform’s own script reference. Filling them matters most where a generic rule gives a weak result: top categories, hero products and buying guides. The page URL field can replace a pattern-based address, which makes it a tool to use sparingly.

Robots and the Salesforce Commerce Cloud sitemap

Salesforce’s training says Business Manager can create sitemaps for external search engines, and that sites should be registered and the sitemaps submitted to Google. Categories also carry sitemap inclusion, frequency and priority fields. Check that each site’s sitemap lists only indexable, canonical URLs, and that robots rules block crawl traps without hiding pages you want ranked.

Redirects and URL mappings during launches

Every release that changes a URL needs a redirect, and Commerce Cloud stores gather them quickly. The platform gives you mapping tools; the discipline of using them belongs to your team and your integrator.

Static and dynamic mappings

Static mappings suit single pages and content with unknown legacy addresses. Dynamic mappings use a pattern to send a whole set of legacy URLs, such as a category, to new ones, with wildcards allowed at the start or the end of a path but not both. Salesforce cites a quota of 25,000 URL redirects per site, so keep a clean redirect map outside the platform as well, and review the Salesforce Commerce Cloud redirects list after each release.

Checking redirect chains after each release

A chain sends a visitor through two or three hops before the final page. Google’s guidance for moving URLs asks for each old address to point straight at its final destination. After each release, crawl the old URL list and flag any that return anything other than a single permanent redirect to a live page.

Discontinued products and replacement pages

A product that is gone for good needs a decision: the closest replacement, the parent category or an honest removal. Our ecommerce SEO services page sets out how to choose. On Commerce Cloud the extra step is to confirm the mapping exists in the platform and in your outside redirect map, so the two do not drift apart.

Salesforce Commerce Cloud hreflang and multi-site storefronts

Multi-site stores need every locale to point at its siblings, and Salesforce Commerce Cloud hreflang is something to build on purpose and then test. Google ignores alternates that do not point back at each other.

Locale URLs and site aliases

A site has a set of allowed locales and currencies, and the locale of a request can come from the hostname alias, the URL path or a URL parameter, according to Salesforce’s training. A request that matches no rule falls back to the default locale. Map out which hostnames and paths serve which locale before you plan alternates.

Alternates in tags or the sitemap

Google’s localized versions guidance accepts alternates in HTML tags, HTTP headers or the sitemap, and says to choose one method. Each page must list itself and every alternate, links must be reciprocal and URLs fully qualified. Add an x-default for pages with no matching locale. Our hreflang guide and international SEO page go further.

Country and currency selectors crawlers should not follow

A selector that appends a currency or country parameter to every link creates a copy of the whole catalog. Keep the choice in a session or cookie where you can, or make sure the parameter URLs point their canonical at the clean address. Selector links that crawlers can follow can be a source of duplicate pages on multi-site stores.

Search refinements, faceted URLs and canonicals

Search refinements let shoppers filter a category by color, size or price, and each combination can become a crawlable URL. Most of them should not be indexed.

Which refinement pages deserve indexing

Index a combination only when shoppers search for it and enough products fill the page. Google’s faceted navigation guidance says there is often no good reason to let filtered pages be crawled, and asks for a 404 where a combination has no results. In Commerce Cloud, refinement text can be added to the end of an SEO URL, and Salesforce’s training sets limits of thirty configurable URL refinements and five per category, with a robots rule as one way to stop crawling of a refinement path.

Canonicals for product variations

A master product collects variants that differ by color or size, and the master itself is not orderable. If each variant has its own address and near-identical content, they compete. Pick one page per product family, point the others at it with a canonical and keep internal links aimed at the winner. Google treats a canonical as a strong signal, not a command.

Paged category grids and infinite scroll

Google’s pagination guidance asks for a unique URL per page, a canonical for each page rather than the first, and ordinary links with an href. It no longer uses rel next and prev. A load-more button that fetches products without changing the URL can hide everything past the first screen from a crawler, so give each batch an address.

Is Salesforce Commerce Cloud headless, and what changes with PWA Kit?

Commerce Cloud supports template-based SFRA storefronts and headless builds, and a Salesforce Commerce Cloud headless storefront can be built with PWA Kit, Salesforce’s React-based toolkit. It changes where pages are built and what a crawler receives.

SFRA storefronts: server-rendered templates

SFRA, the Storefront Reference Architecture, is the template-based storefront; Salesforce’s script reference describes ISML templates being rendered by the platform into the response. For SFRA SEO, that points to content arriving in the first response, which is the safe starting point, though you should confirm it on your own templates. The risks sit in template logic, meta output, canonicals and added scripts, all of which your developers can change.

PWA Kit SEO: what a crawler receives

Salesforce describes PWA Kit as a storefront technology for headless commerce using Salesforce Commerce APIs and React, bundles go to Managed Runtime, and the React SDK’s release notes describe a server-side rendering (SSR) path. PWA Kit SEO still has to be tested, not assumed. Google’s JavaScript SEO guidance says server-side or pre-rendering remains a good idea, and that links must be anchor elements with an href.

Rendering checks on staging

Test on staging before every release. Crawl it behind its login, compare the raw HTML with the rendered HTML for each template and run Search Console’s URL Inspection on the live pages after launch. Check that titles, canonicals, links and product data are in the response you receive. Any mismatch becomes a ticket for your developers or systems integrator.

Core Web Vitals on Commerce Cloud storefronts

Core Web Vitals measure loading, responsiveness and stability. Commerce Cloud pages tend to lose points on the same things as any large store: tags, images and heavy templates.

Third-party tags and cartridges

Audit what loads on product and category templates: analytics, reviews, personalization, chat and the extras that integrations add. Each one is a request and a script. Remove what no one uses, load the rest later where possible and put the decision for each in writing, since marketing and development can each assume the other added it.

Images and the product grid

The product grid is full of images, and the largest one above the fold usually sets the loading score. Serve images at the size the grid displays, reserve their space so the layout does not jump and avoid loading hidden images first.

Field data versus lab scores

The web.dev Core Web Vitals guide sets good thresholds at 2.5 seconds for loading, 200 milliseconds for interaction and 0.1 for layout shift, measured for most visits by real users. Lab tools such as Lighthouse help find causes but cannot measure interaction. Judge releases on field data. See website speed optimization.

Structured data for products, reviews and breadcrumbs

Structured data tells search engines what a page sells and for how much. On Commerce Cloud it is output by templates or components, so errors tend to repeat across thousands of pages.

Product markup for rich results and Shopping

Google separates product snippets from merchant listings, and a page where shoppers can buy needs the merchant fields: a name, an image and an offer with a price above zero and a currency. Extra fields such as brand, SKU and rating add eligibility. Google’s merchant listing documentation also warns that a past price validity date can stop a listing from showing.

Review markup must match visible reviews

Google’s policies say not to mark up content that visitors cannot see, and to include all the reviews that are visible. Ratings must come from real users, and a review feed from another site cannot be recycled. If a template emits a rating that the page does not show, remove it.

Breadcrumbs and Organization markup

A breadcrumb list needs at least two items, each with a name and position, and the last may omit its address. Breadcrumbs should follow a typical shopper path. Shipping and return policies work best at the Organization level. Our schema copy validator compares what the markup claims with the visible copy.

Category and product content inside Commerce Cloud

Large catalogs hold data fields more than prose, so category and product content needs deliberate work on any platform, Commerce Cloud included. The fixes are editorial and template decisions, not new platform features.

Category copy that helps shoppers

Write category text that helps someone choose: what separates the types, who each suits and the questions that come up before buying. Decide per template where it sits so it does not push products down the page, and keep the headings and copy unique to the category. Boilerplate repeated across hundreds of categories earns nothing.

Product descriptions fed from a PIM

Many Commerce Cloud stores receive product data from a product information system. Fix the description where it starts, in that feed: write a distinct paragraph per product, avoid manufacturer text copied by every retailer and map attributes so specs appear as real text on the page and not as images.

Content assets and Page Designer pages for buying guides

Content assets and Page Designer pages let merchandisers publish buying guides inside the store without code. Give each guide its own address, link it from the categories it helps and add it to the sitemap. Check that Page Designer output renders as plain HTML links and text that a crawler can read.

Salesforce Commerce Cloud migration without losing rankings

A Salesforce Commerce Cloud migration protects rankings when every old URL has a mapped destination, the new pages carry the old content and the launch is checked in stages. Salesforce Commerce Cloud replatforming raises the same issues in either direction.

How do you move off Salesforce Commerce Cloud without losing rankings?

Build a URL inventory, map each old address to its closest new page, keep the content equivalent, crawl staging and test the redirects before launch. Google’s site move guidance asks for permanent redirects without chains, redirects kept for at least a year and an updated sitemap. A move to Shopify follows the same steps; see website migration. We make no ranking guarantee.

Moving onto Commerce Cloud from another platform

Arriving on Commerce Cloud means rebuilding URL patterns in the platform’s rules, loading redirects into its mappings and keeping the old content intact. Salesforce’s training notes that where old and new URLs are identical, no redirect is needed. Preview the generated addresses against the old list before any traffic moves.

SFRA to PWA Kit is also a migration

A move from SFRA to PWA Kit changes how pages are built even when the platform stays the same. URLs, rendering, metadata and scripts can all change, so treat it as a replatform: inventory, redirect checks, a staged crawl and post-launch monitoring. See ecommerce website redesign for the design side.

Search Console, analytics and logs for Commerce Cloud

Measurement on a multi-site store is mostly a matter of structure: one property per hostname, tagging that matches, and logs where you can get them.

Verifying each site and locale

Google’s property types include a Domain property, which covers every subdomain and protocol and needs DNS verification, and URL-prefix properties for a specific address. For a multi-site store, set up a Domain property per domain and prefix properties for locale paths you need to isolate.

Crawl stats and server logs

Search Console’s crawl reports show how Googlebot treats the store. Server logs show more, but what log access exists depends on your setup and hosting arrangement, so ask your team early. Even a sample of logs reveals crawl waste on filter and parameter URLs.

Organic revenue by category

We tie search results to money: revenue from organic visits, split by category and product, with rank, index status and crawl health kept as supporting checks. Our ecommerce SEO services page uses the same model on other platforms. It tells a merchandiser which category to fix first.

Hiring a Demandware SEO expert or consultant

A Demandware SEO expert knows where this platform keeps its SEO controls and how they fail, and can say so with URLs from your store. A Demandware SEO consultant should also tell you who will change the code, because most fixes need a developer.

What a Demandware SEO expert should show you

Platform-specific findings with URLs: which refinement pages are indexed, which redirects chain, which locales lack alternates and what a crawler gets from your templates. A tool export with thousands of generic warnings is not an audit. The findings should be ranked by revenue at stake, with a ticket-ready note for each.

Questions for a consultant before the contract

Ask who changes code and who tests it, how releases are checked for SEO regressions, how redirects are kept and who owns the reports. Ask for a written scope, ask what happens when the integrator disagrees and ask what the consultant will not do. Specific answers separate a Demandware SEO consultant from a generalist.

SEO agency, systems integrator or in-house team: who does what

The roles overlap less than they seem. This table shows a typical split for a Commerce Cloud store.

How AI assistants answer “is Salesforce Commerce Cloud good for SEO?”

AI assistants answer platform questions by blending documentation, agency guides and forum threads, and they summarize rather than judge. A store or consultant gets named when its own pages state specifics. The same Salesforce Commerce Cloud SEO facts that rank also get quoted.

What assistants draw on for platform questions

Salesforce’s own documentation and training, long-form agency guides, developer forums and comparison articles. Assistants favor pages that answer the question in the first lines and agree with other sources. Vague claims such as always good or always bad are less likely to be quoted than a page that names conditions.

Product facts AI shopping answers pick up

For product questions, assistants look for complete specs, clear availability, accurate prices and structured data, and they need to be allowed to fetch the page. See technical AEO and the AI crawler access checker to confirm crawlers can reach your products.

Salesforce Commerce Cloud SEO alongside the rest of your Salesforce stack

Commerce Cloud rarely stands alone. Orders, customers and campaigns often move between it and other Salesforce products, and a Salesforce SEO plan should say which team owns which data.

Marketing Cloud and Commerce Cloud data

Marketing Cloud holds customer and campaign data. SEO does not run on that data directly, but landing pages for campaigns need addresses, canonicals and tracking that match the store. Our Salesforce Marketing Cloud agency page covers the campaign side.

Core platform development

Our Salesforce development covers Apex, Flow, integrations and Experience Cloud on the core platform; see Salesforce development company, CRM consultant and API development. We do not claim Commerce Cloud code work, which is why this page assigns code changes to your developers or systems integrator.

What Salesforce Commerce Cloud SEO costs

What Salesforce Commerce Cloud SEO costs depends on the size of the store and whether you want a monthly program or a one-off project. Our published prices apply, and any development is quoted after a written scope. We guarantee no rankings or revenue.

Retainers sized for enterprise stores

Large catalogs, several sites and locale sets take more hours than a small store, so the large and enterprise rows fit most Commerce Cloud stores. We do not work below about $1,500 a month. Our SEO services page describes each tier.

One-off audits and migration support

A one-off audit gives your team a ranked list to act on, and migration support builds the redirect map before a replatform. Our SEO pricing page lists the project prices. A first look at your store is a free SEO audit.

Developer time and Salesforce licenses are separate

Developer or integrator time is quoted after a written scope by whoever does the work, and Salesforce license fees are set by Salesforce. Plan for both beside the SEO fee, and ask your integrator for a ticket estimate before the audit begins.

Related services for Commerce Cloud stores

These pages cover the work around Salesforce Commerce Cloud SEO.

• Ecommerce SEO services
• Enterprise SEO agency
• Technical SEO
• SEO audit
• Salesforce development company
• Salesforce Marketing Cloud agency
• CRM consultant
• API development
• Shopify SEO
• BigCommerce SEO
• WooCommerce SEO
• Magento SEO
• Shopify marketing agency
• BigCommerce versus Shopify
• Shopify versus WooCommerce
• Website migration
• Ecommerce website redesign
• Website speed optimization
• International SEO
• Hreflang guide
• Multilingual website design
• Headless CMS versus traditional CMS
• Headless CMS options
• JavaScript development
• Ecommerce marketing agency
• Ecommerce development
• Technical AEO
• AI crawler access checker
• Schema copy validator
• SEO services
• SEO pricing

Frequently asked questions