Product page SEO for Salesforce Commerce Cloud
Quick answer. Product page SEO for Salesforce Commerce Cloud means three things: making sure each PDP returns server-rendered HTML with a unique title, description and canonical; keeping the catalogue’s SEO fields (pageTitle, pageDescription, image alt text) populated per locale; and controlling which facet, pagination and internal-search URLs are indexable through Business Manager URL rules and robots.txt. Structured data and internal links come next.
What matters most
- Titles and descriptions on Salesforce Commerce Cloud come from catalogue fields, so empty pageTitle values produce duplicate titles at scale — fix the export before you touch the template.
- Only a deliberate subset of refinement, sorting and internal-search URLs should be indexable; the rest need canonical or noindex treatment at template level.
- SFRA does not ship Product JSON-LD, and adding it only makes you eligible for rich results — it is not a ranking lever on its own.
- Revenue by organic landing page is the number that proves PDP work, and it requires joining GA4 landing-page data to transactions because Commerce Cloud will not do it for you.
- Reports on what shoppers type into internal search are the best available input for deciding which facets deserve an indexable URL.
Where does the work actually happen?
Salesforce Commerce Cloud is two storefront stacks in one product. B2C Commerce runs SFRA or legacy SiteGenesis on ISML templates and controllers; the product page is `product/productDetails.isml` in `app_storefront_base`, reached through the `Product-Show` controller. PWA Kit, now sold as Composable Storefront, is a React application that reads catalogue data from the Shopper Products API and renders on Managed Runtime. The principles are identical. The files you edit are not.
The work splits into three jobs. Data first: every field that appears on the page or in the head comes from the catalogue, so empty SEO fields produce near-duplicate titles across hundreds of products. Crawl control second: a Commerce Cloud catalogue generates refinement, pagination, sorting and internal-search URLs that nobody designed on purpose. Rendering third: price, availability and the canonical tag have to be in the HTML the crawler receives, not added after hydration.
Most teams open the template first. Open the catalogue export instead. Correcting 4,000 products with an empty `pageTitle` in a spreadsheet is faster, safer and more reversible than rewriting a template, and it survives the next replatform.
Where to go next
Which catalogue fields decide what a product page ranks for?
In Business Manager, the fields that reach the product page sit under Products: `name`, `pageTitle`, `pageDescription`, `pageKeywords`, `shortDescription`, `longDescription`, plus image alt text, brand and the variation attributes. Each is localised per locale, which matters on multi-site setups where one product ID serves several languages from the same catalogue.
Two failures repeat. Variants inherit or duplicate the parent copy, so a size run of one shoe produces a dozen pages that say the same thing. And `pageTitle` is treated as free text, so titles drift between seasons and between merchandisers. Write the rule once — brand, product name, defining attribute, site name — then apply it with an import job rather than by hand.
- `pageTitle` — the title tag. Falls back to product name plus site name when empty.
- `pageDescription` — the meta description. Not a ranking input, still shapes the snippet.
- `pageKeywords` — ignored by Google. Do not spend a merchandiser’s week here.
- `name` and variation attributes — the words that match how people actually search.
- `longDescription` — the only field with room for specification, compatibility and use-case detail.
- Image alt text — set per image, not per product; usually the field nobody owns.
- Price and availability — feed structured data and merchant listings, and must match the visible page.
Which Salesforce Commerce Cloud URLs should be indexable?
A catalogue produces more URLs than a merchandiser expects. Refinement URLs carry `prefn1` and `prefv1` parameters, sorting adds `srule`, pagination adds `start` and `sz`, and internal search adds `q`. Left alone, a mid-sized catalogue offers search engines a large number of combinations, most of them thin or identical.
URL rules live under Merchant Tools > SEO > URL Rules and map a controller endpoint such as `Product-Show` to a readable pattern like `/{CategoryName}/{ProductName}-{ProductID}.html`. Settle that pattern before launch. Changing it later means mapping redirects for every product, and Commerce Cloud will not write them for you.
| URL type | Where it is controlled | Typical risk | Default action |
|---|---|---|---|
| Product detail page | `Product-Show` URL rule pattern | PID changes break live URLs | Lock the pattern, 301 the old one |
| Refinement and facet | `prefn`/`prefv` parameters, refine URL settings | Combinatorial explosion of thin pages | Index only facets with real demand |
| Pagination and sorting | `start`, `sz`, `srule` parameters | Duplicate listing pages and crawl waste | Self-canonical page one, block sort variants |
| Internal search results | `Search-Show` with `q` | Unbounded thin URLs | robots.txt disallow plus noindex |
| Product variants | Variation URLs from the parent product | Near-identical PDPs competing | Canonical to parent unless genuinely distinct |
How do you handle structured data and rendering on product pages?
SFRA does not ship Product JSON-LD out of the box. You add it, usually in the head of `productDetails.isml` or through a Page Designer component, reading `name`, `sku`, `image` and `brand` from the product model and price and availability from the product’s price and availability objects. Keep to properties you can populate truthfully. Google’s product structured data guidance sets out what merchant listings require; it describes eligibility, not a ranking bonus.
On PWA Kit, server-side rendering on Managed Runtime means the first response can carry the full head, the price and the availability. Confirm that with a raw HTTP request rather than a browser. A route that only paints price after hydration gives Google a different page from the one shoppers see.
Structured data that contradicts the page is worse than none: a JSON-LD price that disagrees with the visible price, `InStock` on a backordered item, or `aggregateRating` on a product with no reviews. Those are the errors that cost you merchant listings.
What can you measure, and where does the measurement stop?
Search Console gives page-level impressions and clicks, and query data that is thin for product URLs. Do not expect clean per-SKU keyword reporting. Use page-level trends and the Page Indexing report to confirm PDPs are indexed and canonicals resolve the way you intended.
GA4 needs a data layer. SFRA storefronts typically wire analytics through a tag manager or the bundled analytics cartridges; PWA Kit needs events added to the React routes. Once organic landing pages and ecommerce transactions sit in one property, you can report revenue by starting URL, which is the number a head of digital actually asks for.
Commerce Cloud’s own search reports in Business Manager show what shoppers type into internal search. That is the cheapest demand research available to you, and it is the right input for choosing which facets earn an indexable URL. It is aggregate data. It does not separate organic sessions from paid ones.
Two things stay out of reach. Per-variant rank tracking is unreliable, and no native report joins organic sessions to catalogue attributes such as brand, price band or stock status. Any dashboard that appears to do it is joining data somewhere, usually in a warehouse, and you should know where that join happens.
What should you do in the first two weeks?
Work in this order. The early items are cheap and expose how much of the problem is data rather than code. The platform-specific context sits in our [Salesforce Commerce Cloud SEO work](/platforms/salesforce-commerce/), and the wider process is covered under [ecommerce SEO services](/services/ecommerce-seo/).
- Export the catalogue and count products with an empty `pageTitle` or `pageDescription`, per locale.
- Crawl the live site and list every URL pattern that returns a product or listing.
- Decide which facets have search demand; canonicalise or noindex the rest.
- Check that `robots.txt` blocks internal search results and sort parameters.
- Add Product JSON-LD to the PDP template and validate one simple product, one variant and one out-of-stock item.
- Confirm the canonical tag on variants and on page two of any listing.
- Build a GA4 report of revenue by organic landing page before you change anything else.
- Review crawl stats and index coverage again thirty days after the fixes ship.
Frequently asked questions
Do I need a separate SEO app for Salesforce Commerce Cloud product pages?
No. Titles, descriptions, canonicals, URL rules, robots directives and structured data are all either catalogue data or template changes on the platform. Third-party apps can inject schema or metadata, but they rarely fill empty catalogue fields, and they add another render dependency to the page. Fix the data and the templates first, then consider tools for reporting rather than for output.
Should facet URLs be indexed on Salesforce Commerce Cloud?
Only the ones shoppers actually search for. Colour, material and a small number of category-level attributes usually justify an indexable refinement URL. Sorting, pagination past page one and long attribute combinations should be canonicalised or blocked. On SFRA this is a mix of URL rule design and canonical or noindex tags in the head template. Review the facet set once a season.
Does SFRA add Product structured data automatically?
No. SFRA renders meta title, description and keywords, but Product JSON-LD is not included by default. You add it to the product detail template or through a Page Designer component, pulling price, availability, SKU and images from the product model. Validate after the change with Google’s Rich Results Test, and check a simple product, a variant and an out-of-stock product before shipping.
How do I change a product page title in Business Manager?
Open the product under Products, edit the `pageTitle` field for the relevant locale and save. The change appears once the page cache clears. For more than a handful of products, use the Products import and export tools so the edit is repeatable and reviewable. Field-level overrides beat bulk edits on hero products, where the title earns traffic on its own.
Can a PWA Kit storefront rank as well as an SFRA one?
Yes, if the HTML a crawler receives includes the title, canonical, price and availability. PWA Kit renders on Managed Runtime, so server-side rendering gives you that by default, but verify it with a raw HTTP request rather than a browser. The common failure is client-only rendering on routes that matter, not the framework itself.
Sources
- Product structured data requirements for merchant listings and product snippets
- Product schema type and its properties
- How Google renders JavaScript and what it needs in the initial HTML
Start with a crawl and catalogue audit
The audit reviews your Salesforce Commerce Cloud templates, catalogue fields, URL rules and indexable URL set, then returns a prioritised list with owners. You get the findings in a document you can act on directly.



