ADVANCED AUTOMATED SEO

All websites managed by the SendSafe E-Business framework use dynamic database driven content. This type of website works differently than static HTML. All dynamic content sites should have dynamic / automatic SEO. SendSafe has dynamic / automatic SEO. The site detects a visiting search engine spider and display itself in a way that's very friendly to spiders and very ugly to people. This means that the website looks totally different to search engines than people:

Spider visits are logged in the eventlog. The eventlog record will be ecVisitorPageLoad type with the information field set to the "HTTP_USER_AGENT" value = the name of the spider. The info field will have a prefix of: "SPDR=". This log entry is in addition to a normal ecVisitorPageLoad event which will occur just prior to this event. The two page load log events can be correlated by IP address (CTracker does not work with spiders because spiders do not support cookies).

CLDR/CLDRF pages can be excluded from spider SEO indexing by including a postfix of .NL. in the sub component file name.

Sample Configuration	for global.inc.asa

' Spider Control
Application("SpiderDisplayOnThisPage") = "index.asp"	
Application("SpiderDisplayDynamicContentRender") = "CLDR.asp?PG=	
Application("SpiderProductDisplayPage") = "whatisoffered.asp"
Application("SpiderDynamicFileMatchToInclude") = "xxx.inc.htm"
Application("SpiderDisplayPageIncludeFile") = "spider.inc.htm"
Application("SpiderListOfContents") = true
Application("SpiderListOfPages") = true
Application("SpiderDynamicFileMinSizeToInclude") = 1000

 


Enhanced Advanced Search Engine Optimization System
This optional form of automated SEO provides the ability to fine tune each page of the site beyond that of standard automated seo.

Types of CSC Records are used configure enhanced SEO. Some types CSC records are used to display product specific SEO information on browser.inc.asp rendered pages. Other types of CSC records (type 14) are used to display SEO information on static content web pages. The type 14 CSC record is also used to build the static content page portion of the enhanced site map.

Notes:

  1. Use the pageconfig.inc.asp control variables to override default TAG values in a file by redefining the value before the metatags.inc.asp include.
  2. Default TAG values cannot be overriden on browser.asp and listing.asp
  3. The landing page will generate detailed indented site maps geared toward better listings including winning Google SiteLink entries.
  4. If a type 14 CSC record does not exist for a static page then it will not be included in the site map.
  5. The product tree display can be turned off by setting Application("SpiderProductDisplayPage") = ""

The Page Title is one of the most important SEO fields. Most search engines use the page title for its listing including Google's sitelink listings, so make sure any titles you pick are good one. You can see the titles as well as all the automated meta tags by loading a page in a browser and looking at the header fields in the raw HTML OR in the case of the title by just looking at the browser's titlebar.

The title is entered into Key3 for each CSC SEO Record. For SEO generated Page Titles, the rendered title will be some combination of:

In all cases what is entered into key3 will override any automatically generated page title. This is why it is important to leave Key3 empty on all CSC SEO records linked to product browsering pages.

On product browsing pages the title will be - Application("commonPageTitle")

On non-product browsing content pages the title will be key3 - Application("commonPageTitle")

Setup:

Standardized Search Engine Site Map Designation Files These maps should be setup and configured to point to the landpage of the site where the site maps can be found.

google = sitemap.xml (see: https://www.google.com/webmasters/tools/docs/en/protocol.html)
		This entry lists one item PER root to start crawling from
			<url>
			<loc>http://www.yoursite.com/</loc>
			<priority>0.5</priority>
			<changefreq>daily</changefreq>
			</url>

yahoo = urllist.txt
		This entry lists one line (URL) PER root to start crawling from
			http://www.yoursite.com/

Alternate Search Engines = ror.xml (see: http://www.rorweb.com)
		<item>
		     <link>http://www.yoursite.com/</link>
		     <title>My website - index</title>
		     <ror:updatePeriod>daily</ror:updatePeriod>
		     <ror:sortOrder>0</ror:sortOrder>
		     <ror:resourceOf>sitemap</ror:resourceOf>
		</item>

Configuration in pageconfig.inc.asp These controls configure a defaul value to be displayed for a META TAG. These values are changed by logic in the seoMetaTags() function in the metatags.inc.asp file.

enhancedSEOEnabled = true
defaultDescriptionTAG = "This is the page description."
defaultKeywordsTAG = "This is the keywords."
defaultCategoryTAG = "This is the category."
defaultRevisitTAG = "5 days"
defaultRobotsTAG = "all"
defaultRORTAG = "<link rel=""alternate"" type=""application/rss+xml"" title=""ROR"" href=""ror.xml""/>"
Application("commonPageTitle") = "My Web Site"

The Enhanced Automated SEO sitemap which appears on the search engine optimized landing page has three main components: spider-only text, the product tree, and the webpage tree. The SEO landing page is arrange as follows:

The content from the spider.inc.htm is displayed at the top
:
:
:
The product tree
:
:
:
The webpage tree
:
:
:
The page’s normal non-spider specific content
:
:
:

All the SEO record types are used for individual page SEO (static pages as well as all the automatically generated product pages). Type 14 is also used to generate the webpage tree. Your sort prefixes are all removed before brand, category, and subcategory are used in the generation of the product tree part of the sitemap.

The product tree is an indented tree-list which breaks down the products by brands, categories, and subcategories. This tree is automatically generated from the item in the database. All the subcategory entries are hyperlinked to a page which displays the items in that subcategory. The items page can then be drilled down by the spider to the showcase page. So this product tree has three layers of drilldown after the subcategory hyperlink (counting the subcategory hyperlink itself).

Record types 9, 10, 11, and 12 are used only to override the SEO which is automatically generated by the system. These records should only be used to tweak the automated SEO “if needed.” All the SEO for the browsing pages are created automatically.

For Record types 9, 10, 11, and 12, in almost all cases you should never use key3 to manually override the automatically generated page title; you should leave this field blank and let the automated SEO system create the title.

For the product tree the following is automatically generated from the DB:

  1. The page title is derived from the brand, category, subcategory, or item fullname fields in the items DB table. The derived title will be the product-field (described above) with the website’s name concatenated to the end; which in your case is SatetySign. The site name is configure in the system with the Application("commonPageTitle") setting. The field that is used for a given page depends on the level of drilldown i.e.
  2. The description metatag will contain the default description configured for the site OR the description in the Content field from a matching record type 9,10,11, or 12 (depending upon the level of drilldown on the browser.asp page).
  3. The keywords metatag will contain the default keywords configured for the site OR the keywords in the CSCAltSummary field from a matching record type 9,10,11, or 12 (depending upon the level of drilldown on the browser.asp page).
  4. The category metatag is always automatically generated by the automated SEO system using the category field from the items database table.

This is what the product tree in the sitemap looks like:

Brand A
            Category 1
                        Subcategory a ? link to page of items
                        Subcategory b ? link to page of items
                        Subcategory c ? link to page of items
            Category 2
                        Subcategory d ? link to page of items
                        Subcategory e ? link to page of items
                        Subcategory f ? link to page of items
            Category 3
                        Subcategory g ? link to page of items
                        Subcategory h ? link to page of items
                        Subcategory i ? link to page of items
Brand B
            Category 4
                        Subcategory j ? link to page of items
                        Subcategory k ? link to page of items
                        Subcategory l ? link to page of items
            Category 5
                        Subcategory m ? link to page of items
                        Subcategory n ? link to page of items
                        Subcategory o ? link to page of items
            Category 6
                        Subcategory p ? link to page of items
                        Subcategory q ? link to page of items
                        Subcategory r ? link to page of items
Brand C
            :
            :
            :
Brand D
            :
            :
            :

For the webpage tree the following is generated:
The webpage tree is an indented tree-list which breaks down the sites static pages into webpage-categories and webpage-subcategories. Do not include cart pages or pages like customer account pages in the site tree since these pages should never be spidered. The individual-page hyperlinks take the spider to the actual page. So this webpage tree has two layers of drilldown after the individual-page hyperlink (counting the individual-page hyperlink itself). The subcategories are optional as are the categories, though we do recommend always having categories.

This is what the webpage tree in the sitemap looks like:

Webpage category 1
            Webpage subcategory a
                        individual-page hyperlink 
                        individual-page hyperlink
                        individual-page hyperlink
            Webpage subcategory b
                        individual-page hyperlink
                        individual-page hyperlink
                        individual-page hyperlink
            Webpage subcategory c
                        individual-page hyperlink
                        individual-page hyperlink
                        individual-page hyperlink
Webpage category 2
            Webpage subcategory d
                        individual-page hyperlink
                        individual-page hyperlink
                        individual-page hyperlink
            Webpage subcategory e
                        individual-page hyperlink
                        individual-page hyperlink
                        individual-page hyperlink
            Webpage subcategory f
                        individual-page hyperlink
                        individual-page hyperlink
                        individual-page hyperlink
Webpage category 3
            :
            :
            :
Webpage category 4
            :
            :
            :

All automatically generated trees are updated by SendSafe once a day shortly after midnight.