Develop > Presentation layer > Search engine optimization (SEO) > WebSphere Commerce integration with sitemaps > Customize sitemaps integration


Sitemaps integration template

The Sitemap.jsp file is used to generate all of the URLs that to be indexed by a search engine, such as Google. It will generate It is located under each stores root for which you have generated a sitemap for example, WC_EAR /Stores.war.

The Sitemap.jsp file takes a storeId, and optionally a list of catalog IDs as its parameter, and generates URLs that access all the categories and catalog entries of the store, in all of the languages supported by the store. The sitemap.jsp files provided are samples based on the URLs in the ConsumerDirect and AdvancedB2BDirect starter stores only. You can add or update any URLs in these files as long they conform with the Sitemap Protocol v0.9.

If you have customized your store, and have to create the own Sitemap.jsp file, adhere to the following conventions outlined in the Sitemap Protocol v0.9:

The following example displays a sample XML file generated by Sitemap.jsp:

<?xml version="1.0" encoding="UTF-8"?>  
<urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">   
<url>    
<loc>http://www.example.com/</loc>    
<lastmod>2005-01-01</lastmod>   
</url>  
 
</urlset> 

Where:

<loc>

URL of the page. All the URLs that the merchants want to be indexed by Google search engine. The following views are to be included in the sitemap for WebSphere Commerce:

<lastmod>

The date the JSP page was modified last. For the CategoryDisplay page, the field LASTUPDATE of the table CATGROUP can be used as the last modification date. For the ProductDisplay page, the field LASTUPDATE of the table CATENTRY can be used as the last modification date.


Related concepts

WebSphere Commerce integration with sitemaps


Related tasks

Customize sitemaps integration


+

Search Tips   |   Advanced Search