SEO for Demandware

Demandware (now Salesforce Commerce Cloud) is an enterprise ecommerce platform that, out of the box, generates a mess of URLs. A single product can appear at /product/blue?size=m, /product/blue?size=m&view=grid, /product/blue?size=m&colour=red, and so on. Search engines see each variant as a separate page, which dilutes your ranking signals and wastes crawl budget. The job is to tell Google which URL is the canonical one, block the non-essential paths, and manage your site architecture so that the important pages get the attention they deserve. I always start with canonical tags on every parameterised URL pointing to the clean product or category page. Then I block /demandware.store/ and /demandware.static/ in robots.txt. But I also spend time on URL rules in Commerce Cloud to create descriptive paths instead of default numbers. If you skip this, you are handing over control to the platform's defaults, which will hurt your [SEO services](/seo-services/) effort. Many [digital marketing agencies](/digital-marketing-agency/) overlook the URL rules setting, but it is free traffic you are leaving behind.

This matters most when you are launching a new Demandware store or migrating from another platform. Getting the technical foundation right from day one avoids months of cleanup. I worked on a store with 2,000 products that generated over 50,000 URLs through faceted navigation. Google crawled only 15% of our important pages in the first month. After implementing canonical tags and noindex directives for filter pages, crawl coverage improved to 90% within two weeks. It also matters when you see a sudden drop in organic traffic; duplicate content is often the culprit because Google stops trusting a site that serves near-identical pages. For large catalogues (1,000+ products), the parameter explosion can lead to millions of indexable URLs, overwhelming your crawl budget. If you run an [enterprise SEO agency](/enterprise-seo-agency/) style setup, you need to actively monitor Google Search Console for spikes in crawled URLs that are not your core pages. This is especially true for B2B catalogues where [B2B SEO](/b2b-seo/) requires clean architecture. Finally, if you are doing seasonal campaigns with many new product variants, ensure you have a strategy to either canonicalise or noindex those temporary pages.

I used to think that blocking paths in robots.txt would stop duplicate URLs from being indexed. It does not. Google still knows about those URLs from internal links and sitemaps, and may index them without crawling. You need canonical tags or noindex meta tags to prevent indexing entirely. I also once left the default metadata on 500 products. Every product page had the same title "Product | Store Name". Google ignored them all. That cost me months of organic traffic. Another mistake was ignoring faceted navigation. I had colour and size filters creating hundreds of thousands of URLs, and I thought noindex on all of them was enough. But the faceted pages themselves had high value for long-tail queries (e.g., "blue running shoes size 10"). I learned to use canonical tags to point to the parent category and keep the filter URL indexable only if it has unique content. Finally, I underestimated URL rules. I used to rely on default Commerce Cloud paths like /on/demandware.store/Sites-Site/default/Product-Show?pid=123. Once I set up static mapping to convert those to /product/nike-air-max, the click-through rate improved by 12% in Google Search Console. This lesson applies even more if you work on [SaaS SEO](/saas-seo/) where product variants can multiply.