More in this section
Forums / Developing with Sitefinity / Localization and search engines

Localization and search engines

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
3 posts, 0 answered
  1. IT
    IT avatar
    52 posts
    30 Sep 2008
    10 Nov 2008
    Link to this post
    If I use localization how will google index my pages? 
    Will a search end up having both lanugage versions?
    Will all my links show up as  

    I'd like to avoid having the /en/ in the URL's (and would prefer to avoid the querystring version as well).  If it were up to me, the persistence would be kept in a [cookie/session/pagevar] or have a separate subdomain alltogether.

    Any thoughts you'd like to share on your experience with localization?  Thanks!
  2. John
    John avatar
    32 posts
    08 Oct 2008
    11 Nov 2008
    Link to this post
    Hey Mike,

    Sitefinity stores localization information using a path prefix ( or as a query string ( At this time, there's no of the box option to store language information inside of a cookie.

    Sitefinity stores all of the pages inside of the database. It will store one version for English and then another version of the page in Spanish for example. As a result, Google will index your pages in three ways:

    1. Google will index the actual words on your site
    2. Google will index the meta key values, such as page title and description when you make a page
    3. Google will index the URL of your site

  3. Georgi
    Georgi avatar
    3583 posts
    28 Oct 2016
    17 Nov 2008
    Link to this post
    John, thank you for your answer!

    starting from Sitefinity 3.5, you may use DomainName and DomainExtension options for your multilingual web site. DomainName option will separate the localization by domain, for example it might be:
    While the other option will enable different domain extensions for different languages.

    Other than that, there is still no way to hide the query string or the path separator. We will consider an option for storing the language in a cookie or a session.

    Sincerely yours,
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Register for webinar
3 posts, 0 answered