More in this section
Forums / Suggestions / Extend canonical support by adding the rel=alternate for multi-lingual

Extend canonical support by adding the rel=alternate for multi-lingual

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, 1 answered
  1. Jochem Bökkers
    Jochem Bökkers avatar
    787 posts
    13 Aug 2007
    16 Sep 2013
    Link to this post
    Currently the canonical support solves us the problem of Google penalizing us for the 6+4*n double urls. While that's already helpful, I wonder if its support can be enhanced to give proper context on synced pages.

    In order to enhance multi-lingual support we'd need two changes:
    1) Allow us an option to set the primary language canonical tag to either include or exclude the /en/
    2) Automatically insert the rel="alternate" and html lang="" tag alongside the canonical tag.

    Imagine a website with 2 languages (English and Dutch) and 'welkom' being the Dutch synced alternative of 'home'. Currently Google sees the following:

    While it understands now there's a multi-tude of urls, pointing to 2 primary urls it has no understanding why. Ideally Google would see and get the following:

    <link href="http://domainname/en/home" rel="canonical">
    <link rel=”alternate” hreflang="nl" href="http://domainname/nl/home" />
    <html lang="en">
    http://domainname/en/home ;    [lang:EN | canonical:/EN/home | alternative:/NL/welkom]
    <link href="http://domainname/nl/home" rel="canonical">
    <link rel=”alternate” hreflang="en" href="http://domainname/en/home" />
    <html lang="nl">
    http://domainname/nl/welkom ;    [lang:NL | canonical:/NL/home | alternative:/EN/home]

    Now Google understands our multi-lingual strategy and understands why these urls point to two pages and it understands the relationship between those two pages and thus offer us better localized SERP.

    All that needed to be done is insert a rel=alternate tag with a language variant and url that can be resolved since we know what the alternative pages are in the system.
  2. Ivaylo Angelov
    Ivaylo Angelov avatar
    68 posts
    10 Feb 2017
    18 Sep 2013
    Link to this post
    Hello Jochem,

    Thank you for contacting us!

    What seems to be a workaround for your question for the time being is the following:
    In the HTML included in the <head> tag (except title, keywords, description) section of the Page properties you can manually add the link tag with all attributes you want. Also, make sure to disable the Canonical URL option from the drop-down above.
    As far as auto-generation of these is concerned, this might become part of future product roadmaps.

    I hope this information helps.

    Ivaylo Angelov
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Jochem Bökkers
    Jochem Bökkers avatar
    787 posts
    13 Aug 2007
    18 Sep 2013 in reply to Ivaylo Angelov
    Link to this post
    Hey Ivaylo,

    On behalf of all serp lovers, thanks!

    You're right, I can add the alternate tag manually to all the pages, just felt tideous :) 

    I figured since you guys already insert the canonical it would be just a few lines of codes to retrieve all language variants of a page and spit out rel=alternate links for those.

    Anyone who cares about canonical, cares about alternate as well and if there weren't any language variants it wouldn't clutter the mark-up either so its a win for everybody.

3 posts, 1 answered