Salesforce Commerce Cloud (Demandware) & SEO Salesforce Commerce Cloud (Demandware) & SEO

Salesforce Commerce Cloud (Demandware) & SEO

by ,
on 4 May 2015

0
0

Thanks to our client experience, we have been able to build some strong SEO skills when it comes to Salesforce Commerce Cloud (Demandware). As always, our work is geared towards commerce. Discover the advantages and disadvantages of this platform which is widely used here in France and abroad today.

GOING OVER THE BASICS

1. MANAGING META(S)

The section “Engine Optimization Support” enables meta(s) administration in two ways.

Specifically, individually:
› By default, it is possible to personalize the “basic” fields : Title/ meta description/ meta keyword
› The “custom” fields can even be added to them

Via an imported file:
› Export/import SEO tags from the catalogue via an XML file
› The import file can also be personalized by adding the field “custom SEO”

demandware3

The little extra(s)
> Manage language fields directly from the back office on the same interface. A select language” menu allows you to choose the default language and, if you are on a multilingual site, the language of the target country

> Administration of all specific meta(s) for content pages via the tab “library folder

2. URL ET RE-DIRECTIONS

The URL Rules can be administered from the back office and many settings are available.

URL Rules
> Lower caser (managing lower/upper cases)
> Blank replacement (space management)
Example: replace “space” with a dash
> Character replacement (managing exotic characters)
Example: replace “&” with a dash

Catalog URLs
> It’s easy to create constants or virtual files after the domain name
Example: [ [ constant, cat ],/,[category-parent,[attribute, displayName, noname],- ]]

demandware4

Content URLs
> Write the rule for a file or a content page
> Manage the URL nomenclature
Example:  [ attribute, name, noname ]

Pipeline URLs
> Lets you make alias in a simple way with re-write rules
Example: renommer /checkout/ <> /on/demandware.com

demandware5

Managing re-direction
Managing re-direction is completely independent and can be done in the back office in three different ways.

> Static Mapping: set up re-direct rules via an avoidable text zone with the possibility to create rules in the administration module
Exemple: http://www.ndd.com/fr/ ,,,Home-Show,fr_FR

Dynamic Mapping: enables you to define dynamic URL mapping rules for the entire site

URL Redirects: lets you define re-direction rules for the entire site
simple” re-direction with a source URL and a target URL
– Definition of the type of redirection: 301, 302, 307
– Possibility to take into consideration the URL source settings in the re-direction

The little extra(s)
Simplified management of domain names
> A text field enabling you to easily manage the domain alias
> For each domain, it is possible to write a re-direction rule in order to route towards a different host.

3. INDEXING

Robots.txt
> Customizable via a file you can edit
> Lets you manage development (prod/pre-prod/staging)

demandware6

Sitemap.xml
Page by page set up of sitemap.xml via the back office. However, the native sitemap is not optimal and needs to be modified. There are still a number of functionalities proposed by the administration interface

Included: choice of the sitemap to include in prod/staging/pre-prod

> Frequency: frequency that the bots come

> Priority: degree of importance (from 0 to 1, 1 being the most important level) of the category /content page/product page

> Schedule: management of the date and time of generation & updates to the sitemap file
– From xx/xx/xxxx
– Every xx/(min, hours, days…)

> URL Maximum: possibility to set up the maximum number of URLs to include in each sitemap type

The little extra(s)
Intelligent management of color attributes via the creation of buckets”
> Lets you group by color/size in one theme
> Avoid having 20 different color filters with color nuances that are rarely searched for (ocean blue, navy blue, sky blue, royal blue…) as well as corresponding URLs

WITH LARGE CONSTRAINTS

1. HOME PAGE ADMINISTRATION

The Home Page SEO elements are completely disassociated and isolated from the content and product catalog pages
They can be found with difficulty under the tab Library Folders”  >>  roots

demandware7

2. MANAGING FACETS

> Managing facet settings is very rigid.
If the site is shared by multiple sites using the same platform for example, facet management is shared. With this configuration, modification of the facet structure of one site will have an impact on the other sites using the platform.
> By default, facet & sorting URLs are “noindex, nofollow” and carry the category canonics.
Example: URL with the settings “Pmin and Pmax” or “Prefn and Prefv1”
> In the same way, product pages carry the canonical meta verses the default product (without the SKUs). It can also send the product URL to the list page with the position settings on the page (?start=)

3. CONFIGURATION OF NATIVE URLs

Default format of the Home Page: /on/demandware/

2 Google requests:
“ site:monsite.ext inurl:on/demandware.store ”
“ site:monsite.ext inurl:/default/Home-Show ”

> Brooks Running Home Page
http://brooksrunning.com/on/demandware.store/Sites-BrooksRunningCA-Site/default/Home-Show

> Geox Home Page
http://www.geox.com/on/demandware.store/Sites-geox-Site/fr/Home-Show 
Duplication of: http://www.geox.com/

Colombia Sportwear Home Page
http://www.columbiasportswear.co.uk/on/demandware.store/Sites-Columbia_EU-Site/default/Home-Show

Strabucks Home Page
http://store.starbucks.com/on/demandware.store/Sites-Starbucks-Site/default/Home-Show 
No redirect towards the version “canonicalised”

Playmobil Home Page
http://www.playmobil.de/on/demandware.store/Sites-FR-Site
Duplication ofhttp://www.playmobil.fr/Page-daccueil

Default Format of content pages: /on/demandware/
The same think

Adidas pages
http://www.adidas.co.uk/on/demandware.store/Sites-adidas-GB-Site/en_GB/Cart-Show

4. ACCESSING PRODUCT VISUALS

In some cases (not client side media servers) product visuals are hosted by Salesforce Commerce Cloud (Demandware) on an edgesuite domain. This configuration can cause problems with engine access for media and penalize visibility.

demandware9


 

TO SUMMARIZE: DEMANDWARE & SEO

One solution:
> with a number of native SEO functionalities and respecting engines’ best practices
> enabling the development of a number of SEO customizations
> limited in the advanced management of facets and products
> Needing Demandware team intervention for certain evolutions because of their “SAAS” approach


More information?
referencement@altima-agency.com

tags:

, , ,

to read next...

Leave a Reply

Your email address will not be published. Required fields are marked *

0
0

Salesforce Commerce Cloud (Demandware) & SEO