Salesforce Commerce Cloud SEO for stores in 2026
Plan Salesforce Commerce Cloud SEO across catalogue URLs, page rules, storefront rendering and search checks for your implementation.
- Published
- Last updated
Salesforce Commerce Cloud SEO starts by matching catalogue settings to the storefront that publishes your pages. Configure metadata and URL rules in the right system, then check the HTML and search signals customers actually receive.
A correct Business Manager preview can still produce a storefront page with missing tags. Separate merchandising changes from development work before assigning the backlog. For other storefronts, use the platform SEO guides.
Identify the commerce cloud implementation
Identify the Salesforce commerce product and rendering architecture before changing settings. The Business Manager instructions below apply to B2C Commerce. Salesforce’s B2B Commerce and D2C Commerce documentation describes different administration, including product SEO fields and Experience Builder page properties.
For B2C Commerce, record whether each route uses Storefront Reference Architecture (SFRA), Progressive Web App (PWA) Kit or a custom storefront. A hybrid site can use different renderers for different routes. Record the implementation version and the active storefront customisations too.
Assign responsibility by the output each system controls.
| Output | What the team must establish | Usual owner to involve |
|---|---|---|
| Product and category metadata | Where attributes and page rules are edited, and how they reach the HTML head | Merchandiser plus storefront developer |
| Public URLs and redirects | Whether Business Manager mappings, storefront routing or an edge layer handles each request | Storefront and hosting teams |
| Canonical and language links | Which template or component writes the final tags | Storefront developer |
| Sitemap | Who generates catalogue URLs and who serves the public file | Commerce administrator plus routing owner |
In SFRA, Salesforce’s metadata integration guidance connects generated page tags to the page metadata container and header template. Check that your customised storefront preserves that path.
For PWA Kit, inspect the page components that consume pageMetaTags and render the head. Salesforce’s PWA Kit metadata guidance distinguishes it from Storefront Next. Don’t apply Storefront Next’s component settings to an older PWA Kit implementation.
Configure product and category page rules
Use separate product-detail and product-listing scopes so category pages describe a range while product pages describe an individual item. Business Manager rules combine static text with values from objects such as Product, Category and Site.
With permission to manage the site’s SEO settings, work in a sandbox first.
- Open Merchant Tools, then Site, SEO & Discoverability and Page Meta Tag Rules. Select the product-detail or product-listing scope you intend to change.
- Select the title or description definition and the locale. Write the rule using attributes available in that scope.
- Assign the rule to the intended catalogue category. Preview a real product and category before widening the assignment.
- Test a missing attribute and a child category with its own rule. Confirm the intended fallback and override in each locale.
Salesforce’s configuration instructions show how to assign rules and preview their generated content. At a product record, open Page Meta Tag Rules and select the locale and Product Detail Page scope.
Root-category rules are inherited by child categories and assigned products. A child-category rule can replace the inherited rule. Salesforce’s inheritance guidance also places the current locale context before locale fallback.
A hypothetical outdoor retailer could generate these distinct outputs from its catalogue attributes.
| Page | Rule inputs | Example title | Example description |
|---|---|---|---|
| Hiking boots category | Category.displayName, category description and Site.displayName | Hiking boots | Example Outdoors | Browse hiking boots by material and available sizes at Example Outdoors. |
| Ridge boot product | Product.name, Product.pageDescription and Site.displayName | Ridge leather hiking boot | Example Outdoors | Explore the Ridge leather hiking boot, with product details and available sizes. |
The examples assume those attributes contain accurate, populated copy. Use conditional expressions for empty values so a missing description doesn’t leave a separator or an unfinished sentence.
An individual product’s description field affects output only if the chosen rule reads it or the storefront uses it as a fallback. Confirm the intended precedence in code. After previewing, check that the response contains one title and one description, with no duplicate legacy tags.
Review search-friendly URLs and locale paths
Choose a preferred URL for each indexable page and make its internal links and sitemap agree with that choice. A canonical identifies the preferred page among duplicate or very similar URLs. A redirect moves the request to another URL.
For Business Manager-managed paths, inspect URL Rules under SEO & Discoverability. Salesforce’s catalogue URL instructions include category and product rules, optional Page URL overrides and a preview by category, product and locale. Validate conflicts before applying changes.
For a headless storefront, first check whether those mappings control its public routes. A route created only in the storefront needs matching routing and redirect work there.
Consider a hypothetical product with the preferred Australian path /en-au/ridge-boot-P100.html.
- Open the product from both Hiking and Footwear categories. If each route shows the same product content, both must declare the chosen Australian canonical.
- Open the product with a campaign parameter. Keep the canonical free of tracking information and point catalogue links at the preferred path.
- Open an old product slug. If the URL is retired, configure a permanent redirect to its replacement through the layer that receives that request.
- Open
/fr-fr/chaussure-ridge-P100.html. Treat the translated product as a locale page and give it an appropriate same-language canonical.
These paths illustrate the mapping, not a required Salesforce URL format. Keep product variants separate in the decision when they have distinct content or offers.
Google’s canonical guidance explains how redirects and canonical tags signal a preference. Sitemap entries must support the same preference.
For language alternatives, Google requires fully qualified hreflang URLs with reciprocal references, including each page itself. Use en-AU for the Australian-English page in this example. Follow the language-version guidance and confirm where your implementation emits the annotations. A locale path alone doesn’t establish that connection.
Check crawlable storefront output
Compare the initial HTML response with the rendered page to find content that appears only after scripts run. Inspect the product name and description, then the price, currency and availability. Check category-to-product links and product structured data too.
In PWA Kit, Salesforce documents the __server_only debugging parameter. It stops hydration so you can inspect server-rendered output. Compare that view with the normal page and the initial response.
Google processes JavaScript, but missing rendered content cannot be indexed. Its JavaScript SEO guidance also warns that an initial noindex can prevent rendering. Don’t rely on client code removing it later.
For product pages, Google recommends putting Product structured data in the initial HTML. Its guidance for product snippets warns that JavaScript-generated markup can make shopping crawls less reliable for changing prices and availability.
Use the merchant listing requirements to check the properties your offer needs. Run the Rich Results Test against the URL and compare the detected offer with the visible product.
| Symptom | Diagnostic check | Corrective action |
|---|---|---|
| Product appears only after JavaScript runs | Compare response HTML with rendered product content | Fix server-side data loading or rendering |
| Preview has new metadata but public HTML has old tags | Compare the active locale and rule output with the served response | Trace the storefront integration and relevant cache |
| HTML has current stock but structured data has old availability | Compare both outputs with the catalogue response used by the page | Fix offer generation or its cache invalidation |
| Initial canonical changes after hydration | Inspect the head before and after client scripts | Make the server and client use the same canonical decision |
Send rendering and cache failures to the storefront team with the failing URL and captured output. Rewriting the product description won’t repair a missing server-rendered product or a stale offer.
Validate the release against search discovery
Validate a representative catalogue sample against written expected results before expanding the change. Include a category, an ordinary product, a product assigned to several categories and a translated product. Add a variant, a temporarily unavailable product and a retired URL if your catalogue has them.
For every sample, record the expected public URL and title, plus the description and canonical. Check the HTTP status and indexing directives. A retained product page must return its intended content with status 200. A retired path must follow its agreed redirect or missing-page policy.
Then validate discovery in order.
- Fetch the public sitemap index and its child files. Confirm that the intended canonical catalogue URLs appear and resolve without login or redirect chains.
- Check that robots.txt allows access to the pages you want crawled. Confirm that an intended indexable page has no blocking
noindexdirective. - Compare metadata and canonicals with the expected sample. Recheck product structured data against the visible offer.
- In Search Console, inspect the released URL and run Test Live URL. Review the tested HTML and resources, then compare the indexed record when Google recrawls it.
For headless sites, Salesforce’s sitemap procedure distinguishes routes configured in Business Manager from routes that need a custom sitemap. Check the file on the storefront’s public domain, even when another system generated it.
Google’s URL Inspection documentation distinguishes live accessibility from indexed data. The live test cannot predict Google’s selected canonical. Read that field in the indexed result and investigate any unexpected choice.
After the checks pass, an owner or full user of the Search Console property can request indexing for a small sample. Google’s recrawl guidance says a request guarantees neither immediate inclusion nor inclusion at all. Treat a successful release check as evidence of the output you fixed, then monitor crawling and search performance separately.
Use the ecommerce SEO audit to organise broader search problems. Keep this release’s next action specific: assign each failed sample to its metadata, routing or rendering owner and rerun the same check after the fix.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.