URLs that are optimized for search engines also make it easier for website visitors to navigate to and throughout your website. Friendly URLs preclude the need for visitors to have to write down or memorize hard to remember addresses. Furthermore, an optimized URL better represents the contents of a page and its location on the website which means that visitors can more quickly find the page(s) they are looking for. Because optimized URLs benefit both search engines and visitors, they are referred to as "friendly" URLs.
When XperienCentral's SEO component is installed, theoretically all URLs for your website are friendly. The friendly URL for pages is constructed using the page's location in the navigation tree together with the URL title, navigation title, or page title (depending on how SEO is configured). For example, if a page has the title "XperienCentral", then the URL of the page will be .../xperiencentral.htm
(or .html). With SEO disabled, the URL of a page is not created using the pages's friendly URL title, instead an internal ID as assigned to pages within XperienCentral is used, for example .../id=77581/langid=42
. For search engines and users, the unfriendly URL provides no useful meaning regarding the contents of the page and/or its location in the website's navigation hierarchy.
The friendly URL of an item in XperienCentral includes the relative path to the item based on the structure of the navigation tree, the title of the item and an extension, in much the same way that a path for a file is delineated in a file system. The precise URL that an item will be assigned is derived using a set of rules that evaluate the item's title(s) as well as its location in the website's navigation hierarchy. In XperienCentral, you can assign the following three titles to pages/content items:
Title | Description |
---|---|
URL Title | The title to use in the friendly URL for the item. |
Navigation Title | The title that will be used for the page in your website's navigation tree. Navigation titles only apply to pages. |
Page/Content item title | The title of the item itself that appears when the page or content item displays in the browser. |
When determining which of the three titles to use in the friendly URL, the following title sequence is stepped through by XperienCentral:
The table below shows what the URL for items in a tree structure would be for some sample pages. The values in the following examples assume the following:
Title | Navigation Title | URL Title | Friendly URL |
---|---|---|---|
Welcome to GX | Welcome | /welcome.htm | |
News | welcome/news.htm | ||
Articles | welcome/news/article.htm | ||
News Archive | welcome/news/news-archive.htm | ||
Products overview | Products | welcome/products.htm | |
XperienCentral | welcome/products/gx-xperiencentral.htm |
For Content Repository items, the situation is a bit different. Because Content Repository items do not have navigation titles, only the URL title or the title of the item itself is used in the friendly URL. If a content item has a URL title, it is used in the friendly URL, otherwise the title of the content item itself is used. The exact friendly URL that a content item will have when it is viewed depends on the page on which it is displayed.
For example, if a content item has the title "GX releases XperienCentral 10", the friendly URL of the content item is 'GX-releases-XperienCentral-10.htm'. There is no hierarchical structure prefixed internally to the friendly URL of the content item because it is stored in the Content Repository. When the content item is displayed on a page, the hierarchical structure of the 'display on' page is prefixed to the content item's friendly URL with the result being the friendly URL for the page and the content item. Based on the example friendly URLs shown in the table above, the friendly URLs for the following sample content items would be:
Content Item Title | Display on Page | Friendly URL |
---|---|---|
XperienCentral 10 | Products | welcome/products/gx-xperiencentral-10.htm |
Engagement | Articles | welcome/news/articles/engagement.htm |
Version 10 | XperienCentral | welcome/products/gx-xperiencentral/version-10.htm |
If the Google News id has been enabled in XperienCentral, the friendly URL of content items is generated in a slightly different manner. A unique id (number) is prefixed to the part of the friendly URL just before the title of the article, for example,.../02041/GX-releases-XperienCentral-version-10,htm
. This is done in order to satisfy a requirement of the Google News article aggregation service.
XperienCentral does not distinguish between uppercase and lowercase letters when resolving URLs. That is, the URLs http://www.gxsoftware.com/Welcome.htm
and http://www.gxsoftware.com/welcome.htm
resolve to the same address. While friendly URLs in XperienCentral can be a mixture of uppercase and lowercase letters as displayed in the address bar of a browser, all versions of an address using a mixture of cases are the same.
In addition to the friendly URL, a content item can also be navigated to from a second friendly URL that omits the friendly URL separator. For example, if the friendly URL separator is a dash (-) and the friendly URL for a page is gx-products.htm
then the above page is also available at the friendly URL gxproducts.htm
In XperienCentral it is not required that all web pages have a unique title. Because the friendly URL is determined based on the title of a page plus its location in the navigation structure, two or more pages can have the same title and not have friendly URL conflicts. For example:
Parent Page Title(s) | Page Title | Friendly URL |
---|---|---|
GX/Support | Contact | gx/support/contact.htm |
GX/Sales | Contact | gx/sales/contact.htm |
GX Public | Contact | gx-public/contact.htm |
In the example above, the "Contact" pages all have the page title "Contact" but because of their relative locations in the site structure, the friendly URLs for the pages remain unique. Given the fact that the friendly URL is determined by a page's title (URL, navigation, page), the following situation in which three pages in the same tree have the same page title also does not lead to friendly URL conflicts:
Parent Page Title(s) | URL Title | Navigation Title | Page Title | Friendly URL |
---|---|---|---|---|
GX/Sales | Contacting | Contact | gx/sales/contacting.htm | |
GX/Sales | Contact us | Contact | gx/sales/contact-us.htm | |
GX/Sales | Contact | gx/sales/contact.htm |
In XperienCentral, content items must have a unique friendly URL title compared to the following:
This is because content items can be displayed on any page and therefore XperienCentral has no way of determining at the time that a content item is created where it will be displayed and therefore what its full friendly URL will be. XperienCentral only compares the friendly URL of newly created content items to last part of all existing friendly URLs '.htm'. For example, creating a content item that resolves to the friendly URL 'Contact.htm' would lead to a friendly URL conflict with all the pages in the following table:
Parent Page Titles | URL Title | Navigation Title | Page Title | Friendly URL |
---|---|---|---|---|
GX/Public | Contact | Contacting us | gx/public/contact.htm | |
GX/Sales | Contact | Contact GX | gx/sales/contact.htm | |
GX/Support | Contact | gx/support/contact.htm |
In XperienCentral, when two pages/items attempt to resolve to the same friendly URL, the conflict is resolved automatically. The mechanism for resolving friendly URLs is fully described in How Friendly URLs are Constructed.
In XperienCentral, it is possible for two or more pages/items to resolve to the same friendly URL as a result of your website's structure. This can occur, for example, when through a combination of URL titles, navigation titles, and/or item titles, the calculated friendly URL for two or more pages/items turns out to be identical. Naturally, only one item can claim a specific unique friendly URL if this occurs. All other items that try to claim a friendly URL that is already claimed (in use) will be automatically assigned a different friendly URL in order to resolve the conflict.
XperienCentral determines which item claims a friendly URL in a straightforward manner: The item that was created first claims the friendly URL it wants — All other items that try to claim that friendly URL are assigned a different, unique URL based on the name of the original. For items that attempt to use a claimed URL, a dash (-) plus a number is appended to the end of the original friendly URL and that is used in the address for the item. The number increments by one for each successive item that wants to claim the original friendly URL in the order they are created. The following simple example assumes that the pages are assigned no URL or navigation title but share the same page title in the same tree structure:
Order Created | Page Title | Friendly URL |
---|---|---|
1 | Contact | contact.htm |
2 | Contact | contact-1.htm |
3 | Contact | contact-2.htm |
4 | Contact | contact-3.htm |
As you can see above, if you create a page named "Contact" and then later another with the same name in the same tree structure, the second page will be assigned the friendly URL "Contact-1.htm", the third "Contact-2.htm", and so forth.
The example above shows how page titles that attempt to claim the same URL are resolved. It is also possible to have URL conflicts that are the result of more complicated circumstances, such as URL titles and/or navigation titles that conflict with a page or object title or navigation titles that conflict with each other, content item titles that conflict with a page's friendly URL, and so forth. The following table shows what the URL result would be for conflicts at a variety of title and navigation title levels.
Order Created | URL Title | Navigation Title | Page Title | Friendly URL |
---|---|---|---|---|
1 | Contact | Contact | contact.htm | |
2 | Contact | contact-1.htm | ||
3 | Contact us | Contact | contact-us.htm | |
4 | Contact | contact-2.htm | ||
5 | Contact | Contacting GX | contact-3.htm |
When you create a new page or content item, XperienCentral assigns a friendly URL to it based on the rules explained in the previous sections. For each new page/content item you create, a check is made to see whether the requested friendly URL is available. If the friendly URL that the page/content item wants is available, it is granted. If, however, the friendly URL is already in use, a message will appear above the page/content item indicating that the desired friendly URL is already in use and that a new friendly URL has been assigned to the current page/item. For example, the friendly URL title 'Contact' is already claimed by another page or content item. When the page below entitled "Contact" is created, an indicator that the friendly URL is already claimed displays above the page
In the example above, the message that displays is: "URL is set to 'Contact-1.htm'. Contact already uses URL 'Contact.htm'" In this case, because the friendly URL 'Contact.htm' is already claimed, the current page is automatically assigned the URL 'Contact-1' to ensure that all friendly URLs remain unique. The above action is performed on all XperienCentral pages and content items that attempt to use a friendly URL that is already claimed. To link to the page/content item that is claiming the friendly URL that the current page/content item wants, click the name of the item that is claiming the friendly URL that you want to use in the indicator ('Contact' in the example above).
When the friendly URL you want to use for an item is already claimed, you have the following options:
The XperienCentral SEO component maintains a comprehensive overview of all your website's URLs. From a central location you can generate various reports for the friendly URLs currently in use on your website. This makes it possible to easily manage your website's friendly URLs and also to ensure that pages and content items have the friendly URL that you want them to have. The SEO component can generate the following friendly URL overviews:
The SEO component allows you to generate a comprehensive list of all friendly URLs on your website. The overview is exported in the form of a file containing comma separated values (CSV) that you can open in another application, such as Microsoft Excel, in order to view and search through the list. Follow these steps:
[Download overview]
.[Open]
or [Save][Open]
, the exported file will open in the application associated with .csv files. If you click [Save]
, you can specify the name of the file (export.csv by default) and the location where you want to save it.In the overview, the column headings have the following meanings:
Heading | Description |
---|---|
id | An internal identifier for the friendly URL within XperienCentral. IDs are assigned in the order that friendly URLs are created, beginning with 1 and incrementing by 1 for each new friendly URL. |
URL title | The title of the friendly URL as derived from the URL title, navigation title, or page/content item title. |
Normalized URL title | The friendly URL title after it has been normalized. Normalizing URL titles is necessary in order to ensure that they are valid for browsers. The normalizing of friendly URL titles is described in detail in the section URL Title Standardization. Note: The normalized URL title as it appears in the exported list does not preserve case usage and does not contain the separator symbol that is substituted for spaces in the friendly URL |
Querystring | An internal string that XperienCentral uses to retrieve pages, content items, and external database objects. The query string syntax for each item type within XperienCentral has a unique form, for example:
|
Current URL Title | Specifies the identifier (from column 1) that is the current friendly URL for this item. If an item contains an entry in this column, it means that it is no longer an active URL: When this friendly URL is navigated to, the visitor will be redirected to the friendly URL referenced by the id in 'Current URL title' instead.See Maintaining Items with More Than One Friendly URL for more information. |
WebsiteID | An internal identifier that refers to the web initiative that the page belongs to. Content Repository items are assigned the value "-1" because they can appear in any web initiative in the configuration and therefore do not belong to a specific one. |
As a result of many factors, it is possible that a page or item can have a claim on more than one friendly URL. This can occur if the URL, navigation or page title of a page or content item is changed or renamed or if a page is moved from one location to another in the navigation structure. Whenever a page or content item is saved, a friendly URL for it is calculated — if any changes occur to the friendly URL of a page or content item, it receives a new friendly URL based on the current circumstances and also keeps the previous URL(s) it once had which now act as redirects. This is explained in more detail in Maintaining the URL History of Pages and Content Items.
To generate a list of all items that are claiming more than one friendly URL, follow these steps:
[Apply]
. The friendly URLs will be released and can now be used by other items on your website. This task can also be performed on individual content items and pages. For more information, see Deleting URLs from a Page or Content Item's URL History.When a content item or page is created that attempts to use a claimed friendly URL, it is assigned a unique URL based on the title of the URL it wants as described in Friendly URL Claiming. To see the items on your website attempting to claim a friendly URL that is already in use, follow these steps:
If the original friendly URL becomes once again available, an indicator appears in the list of items that want the same friendly URL in the form of green text that appears next to the title of the friendly URL that had multiple claims. The message indicates that the friendly URL is once again available as shown in the following example ("URL is available again").
In theory, all items in XperienCentral have friendly URLs. If, however, items don't have a friendly URL, you can easily add friendly URLs to them. To see the items that have no friendly URL, follow these steps:
[Calculate]
. Items with no friendly URL will be assigned one.