URL Rule Static and Dynamic Mapping Examples

Overview
This document captures less common but useful URL rules and highlights considerations and implications of their use.

Additional resources can be found at the SEO Resource Center:

https://xchange.demandware.com/community/merchants_and_marketers/seo-resource-center

Mapping Rule Purpose Be Aware

/source-url p,,,Search-
Show,,q,on-sitesearch-query
/source-url p,,,Cart-
AddProduct,,pid,garmin-
gpsmap-96c,src,source-code
/source-url
p,,,SourceCodeRedirect-
Start,,src,source-code
/source-url** p,,,Product-
Show,,pid,product-id-
here,{_querystring}
This static mapping rule takes the customer
directly to a search results page based on
the contents of “on-sitesearch-query” portion
of the mapping rule.
This static mapping rule takes the customer
directly to the cart and adds the identified
product to the cart along with the specified
source code.
This static mapping rule leverages the
redirect rule setup at the source code to take
the customer to the desired redirect location.
This rule allows for a customer friendly vanity
URL to be distributed while still arriving at the
desired destination with the source code
applied.
This static mapping rule is intended to pass
through the incoming querystring after the
redirect has occurred. This rule would be
used if legacy URLs contain querystring data
Each time a customer hits this URL it will count
as a search hit for the specified query in
analytics. This can be coupled with a search
driven redirect when attempting to redirect a
legacy or vanity URL to a page that is external
to Demandware. i.e. a jobs portal
(jobs.yourcompanyemployment.net).
Each time a customer hits this URL it will add
the item to the cart. If the source code is tied to
a promo really intended for single use it would
be better to remove the source code and use a
coupon code instead. Less automated but more
“secure”.
This is only necessary when giving out a vanity
URL with the expectation that the customer will
arrive at a desired destination along with having
the source code experience applied to the site
(slot configuration, sorting rule, promotion).
Demandware strips out querystrings from an
incoming unmatched URL.

1
Mapping Rule
/source-url p,,,Search-
Show,,cgid,category-id-
here,prefn1,refinement-
id,prefv1,refinement-value
Purpose
that needs to be maintained after the
redirect.
This static mapping rule is used to redirect to
a refined category page based on the
refinement identified and the refinement
value.
Be Aware
Multiple refinement values can be added in the
same format where each additional value would
be prefn# and prefv# incrementally (example:
prefn2, prefv2).

/source-url p,,,RedirectURL-
Hostname,,Location,full-
domain-url-here
/s/SiteName/* p,,,Home-
Show,,,
This static (or dynamic) mapping rule allows This will immediately take the customer directly
you to take an incoming URL request and off site.
redirect it to another domain. If setup as a
dynamic rule, a portion of the incoming URL
can be passed through dynamically to the
other domain. (example: /source-url/**
p,,,RedirectURL-
Hostname,,Location,http://www.my-
website.com/{0} where anything held in the **
location will be placed after www.my-
website.com/)
Clients that host multiple sites on the same This only a solution for dealing with traffic that
realm had problems that all sites are already “knows” the URL location. To prevent
accessible on all domains using our standard robots from crawling the structure define a
folder structure. By defining a redirect per disallow in the robots.txt.
Site requests can be redirected to the home
page.