Sitemaps

Sitemaps are XML files that provide search engines, such as Google, Yahoo, and MSN, with information about a web site so crawler can index it more efficiently. Sitemaps contain a list of all the URLs available for indexing and can provide the search engine with additional information, such as when a page was last updated, frequency of updates, and the relevance of a page. Search engines use this information to construct links to your site and control the ranking of links within its search results.

The main advantages of using sitemaps are as follows:

Google

Google is an example of a search engine and SiteGenesis is an example of a site. Because Google has almost half the market share of all search engines, a concentrated effort to optimize the traffic driven from Google makes good business sense. However, because most search engines use the sitemap.org protocol to define their sitemaps, the sitemaps that you generate for Google can also be registered and used with other search engines, such as Yahoo or MSN.

See Sitemap Topology.

Configuring Sitemaps in Salesforce B2C Commerce

B2C Commerce generates a sitemap that's compatible with the Sitemap Protocol 0.9 from Sitemaps.Org. This is the standard sitemap definition for Google.

To use sitemaps on B2C Commerce:
  1. Configure sitemap attributes in the respective data, either through a feed or manually in Business Manager.
  2. Generate sitemaps in Business Manager. See Generating Sitemaps.
  3. Create an account with the search engine of choice and verify site ownership. See Notifying Search Engines About Your Sitemap.

Home Page Link in Sitemap

The B2C Commerce storefront-generated map contains a link to the homepage of your store in this format:

http://<alias>/on/demandware/Sites-<Sitename>-Site/default/Home-Show.

However, if you configure a domain alias for your site which resolves to your home page, using a rule similar to:

"www.mysite.com" : [
{"pipeline":"Home-Show"} 
],

Then the generated sitemap contains a link similar to:

http://www.mysite.com/
Note: Configure sitemap settings individually for each instance type. You can't replicate sitemap site preferences between Staging and Production or Development. You must create the settings and job to generate the sitemap on each instance

Multiple Sites

If you have multiple sites, you might need multiple sitemaps. If your sites share the same master catalog, even if they have different locales, they do not need separate sitemaps.

However, if your sites don't share the same master catalog, they need different sitemaps. These sitemaps must be registered and generated separately.