2. WCS SEO
Creation of simple static URLS for store pages that shoppers and search bots can
understand
Title and Meta Description of pages
Creating 301 URL redirection when a web page is moved
Sitemap
3. Simplifying URL’s
Shortening Context Root
http://hostname/webapp/wcs/stores/servlet/Product2_10001_10001_10029_-
1_10007_10001_10001_ProductDisplayErrorView
TO
http://hostname/shop/Product2_10001_10001_10029_-
1_10007_10001_10001_ProductDisplayErrorView
Seo friendly urls
http://hostname/webapp/wcs/stores/servlet/Product2_10001_10001_10029_-
1_10007_10001_10001_ProductDisplayErrorView
TO
http://hostname/shop/side-tables/two-drawer-side-table
4. Shortening Context Root
How to configure?
Modify httpd.conf
Modify wc-server.xml
<VirtualHost *:80>
RewriteEngine on RewriteRule ^/shop/(.*) /webapp/wcs/stores/servlet/$1 [PT,L]
//Do the same for :443 as well
<SEOConfiguration defaultUrl="" dynamicUrl="true" enable="true">
<context-root-rewrite value="/shop" />
</SEOConfiguration>
6. SEO URL’s
How to configure?
1> select * from seourl where seourl_id=13242
2> go
SEOURL_ID TOKENNAME TOKENVALUE PRIORITY CHANGE_FREQUENCY MOBILE_PRIORITY MOBILE_CHG_FREQ OPTCOUNTER
--------- ------------- ---------- -------- ---------------- --------------- --------------- ----------
13242 CategoryToken 10020 0.0 N 0.0 N 0
1> select * from seourlkeyword where seourl_id=13242 and LANGUAGE_ID=-1
2> go
SEOURLKEYWORD_ID SEOURL_ID LANGUAGE_ID STOREENT_ID URLKEYWORD MOBILEURLKEYWORD STATUS OPTCOUNTER
---------------- --------- ----------- ----------- ------------------- ---------------- ------ ----------
51960 13242 -1 10001 shoes-10020--1 NULL 0 1
53001 13242 -1 10001 apparel-girls-shoes NULL 1 0
1> select * from seoredirect where SEOURLKWD_ID_NEW=53001
2> go
SEOREDIRECT_ID SEOURLKWD_ID_NEW SEOURLKWD_ID_ORIG OPTCOUNTER
-------------- ---------------- ----------------- ----------
10501 53001 51960 0
7. JSP
wcf:url - JSTL Taglib for constructing SEO urls
It builds a full path URL, rather than a relative path.
It builds SEO compliant URLs if the feature is used in WebSphere Commerce.
It adds a prefix to the URL with the appropriate protocol, HTTP or HTTPS, depending on the Struts
configuration files.
11. Page Title & Meta Description
How to configure?
SEOPAGEDEFDESC
http://www-
01.ibm.com/support/knowledgecenter/SSZLC2_7.0.0/com.ibm.commerce.database.doc/database/seo
pagedefdesc.htm?lang=en
SEOPAGEDEF_ID LANGUAGE_ID TITLE META_DESC META_KEYWORD
IMAGE_ALT_DESC LASTUPDATE CREATEDTIME FIELD1 FIELD2 FIELD3 OPTCOUNTER
------------- ----------- ---------------------------- ------------------------------------------------------- ------------------------------------
------ ------------------------------------- ----------------------- ----------------------- ------ ------ ------ ----------
10058 -1 Welcome to <seo: StoreName/> Shop <seo: StoreName/> online. <seo: StoreDescription/> <seo: StoreName/> <seo:
StoreDescription/> Image for <seo: StoreName/> home page 2014-03-01 09:05:26.248 2014-03-01 09:05:26.248 NULL NULL NULL 1
Query execution time => 2 ms
select * from SEOPAGEDEFDESC where SEOPAGEDEF_ID=10058 and LANGUAGE_ID=-1;
12. Image alt texts
Image alt text – Text which appears when you hover images
13. Image alt texts
How to configure?
CATENTDESC - http://www-
01.ibm.com/support/knowledgecenter/SSZLC2_7.0.0/com.ibm.commerce.database.doc/database/catent
desc.htm?lang=en
14. Sitemap
File with a list of web url’s in your site
Bot’s use this file to crawl site more intelligently
When do we need sitemap
Your site is really large
Your site has a large archive of content pages that are isolated or well not linked to each other
Your site is new and has few external links to it
Your site uses rich media content, is shown in Google News, or uses other sitemaps-compatible annotations
15. Sitemap xml’s
sitemap_10001 (Index file)
sitemap_10001_1.xml (Original Site map
contents
sitemap_10001.xml.gz – Zipped file which has the
above sitemap xml
https://support.google.com/webmasters/answer/7
5712?hl=en
16. Generating Sitemap
Admin Console Scheduler
Run job SitemapGenerate
Minimal params required are
1. storeId
2. catalogId
3. storeType
storeId – The Store Identifier
storeType – B2C or B2B
maxUrlNumber - The maximum number of URLs a sitemap is allowed to have.
Default 50,000
catalogId – Sales catalog id used. If not specified, master catalog id is used
validation – Whether validation against schema is required
compareFiles – Compare files against last run
uploadXMLToEAR – his flag indicates whether to upload the uncompressed
generated sitemap XML files to the EAR directory (set to false by default). Both
the compressed and uncompressed versions are uploaded.
updateEAR - This flag allows the caller to disable the EAR update (set to true by
default). All files remain in the temporary directory (FEP 8+)
http://www-
01.ibm.com/support/knowledgecenter/SSZLC2_7.0.0/com.ibm.commerce.seositema
p.doc/tasks/tsdgsmsched.htm
17. SiteMap Output
Sitemap files will be generated at WAS_Profiles/temp directory
updateEAR – Set this to true, otherwise an ear update will also happen