Use with Caution Options: - The page Name Plug-in
JavaScript plug-in strips “http://www,” from URL page names. This plug-in shortens the page names and makes them a little more manageable for users. They may be suitable for Web sits with well-defined URL structure. The following limitations may exist when using the pageName plug-in:

  • Even though the domain has been stripped from the page names, using URLs for page naming can still lead to long page names.
  • Will treat different URL variables of the same Web page as separate pages.
  • Will aggregate dynamic pages under the same page name because it ignores the query string.
Document.title - Uses the title of each page instead of URL.
  • s.pageName can be set to each Web page’s TITLE tag;
  • example: s.pageName=document.title;
The following limitations may exist when using document.title:
  • Page titles aren’t always unique to one page.
  • Page title can be long and contain unnecessary information such as the company’s name.
  • SEO initiatives can pack page title with unnecessary keywords and cause the page title to change on a regular basis for optimization purposes.
  • Translation tools such as Bebel Fish can translate TITLE tag and create other instances of the Web page under different translate names.
Site Catalyst defaults to page URL. If the page Name variable is left blank, the URL will be entered into s.pageName (excluding any query strings). The following limitations may exist when leaving the pageName variable blank:
  • URL page names can be very long and unwieldy for users.
  • Valuable real state at the beginning of each page name is unnecessarily wasted on “ ...”
  • Different URL variations of particular Web page will be treated as a separate pages instead of aggregated together (e.g., and are both the home page but will be listed as separate pages).
  • Dynamic pages are aggregated under the same page name because query strings are normally excluded.
Disadvantages of Using URLs.
By default, Omniture displays the page URL in the Site Catalyst reports. URLs are used for Web operation, not Web analytics. The disadvantage to using URLs in Web analytics reports in the users who are not familiar with the URL names may get confused when they view the reports. Therefore, Omniture makes it possible to apply “friendly names” to replace the URLs in the Site Catalyst reports.

There are there aspects of effective page naming, as illustrated.
Context Context focuses on the URL structure stem, which helps to identify where a page resides. Include directory structure or content hierarchy in the page name to help users orient the page within the site and simplify report filtering.
Clarity Clarity is an overarching concern for the entire page name. Ensure that it is clear and easy identifiable for infrequent users.
Conciseness Conciseness primary focuses on making the URL structure steam as short as possible. The specific page name part should also be as concise as possible, but most of the emphasis will be on the steam. Keep the page name as short as possible to maximize limited character space.
Friendly Page Name Example
1. E-commerce: women:outerwear:ski jackets:main
  • Context: Page name includes merchandising category and subcategory.
  • Clarity: Page name identifies the page as the main entry page for this product group and doesn’t include unnecessary code (.aspx, .jps, .cfm, .php and etc).
  • Conciseness: Instead of using category’s full name, “women’s apparel,” it has been abbreviated to just “women”. You can only abbreviate directories and subdirectories so far before they compromise the clarity rule.
2. Content site: business:technology:article:best ipod gear
  • Context: Page name includes relevant content hierarchies.
  • Clarity: Page name provides shortened article name, not an ambiguous article ID.
  • Conciseness: It doesn’t include unnecessary words or terms (e.g., “news”).