|
||
Domain alias |
Specifies the domain name used for the alias. Enter it without the http:// protocol and www prefix. If you wish to use a different port than 80, specify it as well.
Example: If your website uses mycompany.com as its main domain and you also wish to use the my-company.co.uk domain and have it access the same website, you need to add the my-company.co.uk alias to the list of domain aliases. |
Visitor culture |
Sets the content culture that should be displayed by default to visitors who arrive on the website through a URL containing this domain alias.
The (Automatic) option means that the culture will be decided based on the preferences configured in the visitor's browser (in Internet Explorer, you can set the default language in Tools -> Internet Options -> Languages).
If the Site Manager -> Settings -> URLs and SEO -> Force domain culture setting is enabled, the culture specified here will always be selected and displayed when the site is accessed through the alias's domain name. All URLs of documents in the given culture will also be generated with the this domain name. |
Default alias path |
Used to select the default page (document) that should be displayed when the website is accessed through the alias. This overrides the Site Manager -> Settings -> Content -> Default alias path setting. |
Redirect URL |
Users will be redirected to the entered URL when they access the website through this domain alias. Both absolute and relative URLs are accepted. This field supports macro expressions.
If the only purpose of your aliases is to make the site available under multiple domain names, it is recommended to redirect them to the website's main domain. This is a common Search engine optimization practice that prevents duplicate web content (i.e. having several URLs leading to the same content).
Example:
Imagine that the main domain of your website is domain.com and you have domain.co.uk defined as a domain alias with the Redirect URL field set to:
{%protocol%}://domain.com{%relativepath%}
These macros can be used to dynamically redirect users to the correct page under a different domain.
{%relativepath%} - is resolved into the current relative URL path when the redirection takes place
{%protocol%} - is resolved into the current URL scheme name (protocol) when the redirection takes place
Now if a user accesses for example http://domain.co.uk/example.aspx, they will be redirected to http://domain.com/example.aspx.
|