Multilingual and Canonicalization
-
Hey there Mozzers,
If I have a site that is translated in 5 languages with main language as English ( most pages are only template translated top menu and footer ) is this correct?
Right now the main page which is example.com/en is mentioned 3 times in the href code 1st as a canonical later as alternate and 3rd as x default which seems a bit weird.
| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | -
Hi!
My first (warm) suggestion is to allocate budget for content localization. Having just the template translated is not enough for having visibility in markets like Spanish, Chinese or Russian, and this is not just because you won't rank at all for queries in those languages (hence you won't be discovered by users in those markets), but also because English is not so known, so it is possible that people will bounce out very fast, and that is going to be a very bad user signal, one of those that Google more and more is going to take into consideration in its algorithm.
Said, that, you are doing right using the hreflang, because it is suggested by Google itself also for cases like yours, when only the template is localized:
- You keep the main content in a single language and translate only the template, such as the navigation and footer. Pages that feature user-generated content like a forums typically do this.
What I don't agree is about the use of the rel="canonical".
The combined use of hreflang and rel="canonical" is quite tricky in international SEO, so let me try to explain my negative to cross canonical use with hreflang.
The rel="canonical" is used to suggest Google that a page is identical to another one. Google, then, will not consider the canonicalized URL and show in the SERPs the canonical one only.
But with the hreflang you are giving Google a signal that is contradicting the rel="canonical" one.
In fact, you are telling Google two opposite things:
- Do not consider this URL because it is canonicalized to this other one;
- Consider this URL because I want you to show it in this specific market (i.e.: es-ES).
What Google must do?
My suggestion, then, is to quite the cross canonical and leave the hreflang annotation only.
Google, infact, finally is able to understand that - albeit the content may be substantially identical to the one present in another page - that specific URL targeting that specific international market has tiny differences that means a big changes in meaning (i.e.: currency) for that targeted market, hence Google won't consider it into a Panda schema.
I hope I was clear enough
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Managing multi-regional and multilingual sites
Hello, It's been a year since we launched our website and at first, we did it with a domain name called misitio.co. We have just bought the domain name mysite.com and my doubts are what should I do with the domains I have in other countries, for example .mx .br, should I redirect them to mysite.com or manage them independently? Thank you very much
International SEO | | Isabelcabreromunoz1 -
Multilingual webshop SEO
Hi, I have a question concerning multilingual SEO for webshops. This is the case: the root domain is example.be, which has several subdomains. One of these subdomains is shop.example.be which is used for two webshops (Dutch and French), being shop.example.be/nl and shop.example.be/fr .
International SEO | | Mat_C
The other root domain is example.lu (for Luxemburg) which is only used for the subdomain for the Luxemburg webshop in French, being shop.example.lu/fr.
The content on the .lu/fr webshop is a small part of the content on the .be/fr webshop, and the product descriptions are the same and are both of course in French. The webshops will be redesigned and restructured, and the question is what to do with the .lu/fr webshop. There are two possibilities: Integrate this webshop for Luxemburg in the existing .be webshop, since most of the products are the same and the .lu webshop doesn't get a lot of visitors because of Luxemburg being a small country. The only thing to do then would be setting up a 301 from the .lu webshop to the .be/fr version to transfer link value.
People in Luxemburg already sometimes get pages from the .be/fr webshop in the SERP anyway because these already have a bigger authority than the .lu/fr pages. Keep the .lu/fr webshop and use hreflang tags so the correct pages with similar content are shown in the correct country. I know that when using different TLD's this normally isn't an issue anyway, so implementing hreflang tags even isn't really necessary. Please feel free to share your thoughts about what would be the best approach. Thanks!1 -
What strategy is better for a multilingual site for the SEO point of view?
Hi everyone, in a case for a site with two languages like spanish and english, how would do you deal with it? I can see 4 cases, which is better?? 1. With differents domains: mydomain.es (for spanish version) and mydomain.com (for english version). 2. With subfolder mydomain.com/es/ and mydomain.com/en/ 3. With Subdomain: es.mydomain.com and en.mydomain.com 4 With URL translation (any url is translated in ther languages but not use of subdomain or subfolder): mydominain.com/hola and mydomiain.com/hello Thanks very much for your answers (i love this forum). 🙂
International SEO | | webtematica0 -
Multilingual Sitemap with some non-matching URLs
The website has two languages, English (.com/en-int/) and French (.com/fr-fr/). Some pages only exist in French, and some only in English, but there are many that are a 1-to-1 match. So, my questions is, in the multilingual sitemap, should I only include the URLs that are alternates, and then create a 2nd sitemap for all non-matching URLs? Or should I have 3 sitemaps: 1) Multilingual sitemap for all matching URLs (https://support.google.com/webmasters/answer/26208650 , 2) English sitemap for only URLs not included in multilingual sitemap, 3) French sitemap for only URLs not included in multilingual sitemap. And then create a sitemap index file to link to all 3 sitemaps.
International SEO | | Alex.Weintraub0 -
Multilingual Site with 2 Separate domains and hand-translated
I have 2 separate domains: .com & .jp
International SEO | | khi5
I am having a professional translator translate the English written material from .com. However, the .jp will have same pictures and videos that I have on the .com which means alt tags are in English and video titles are in English. I have some dynamic pages where I use Google Translate and those pages I place as "no index follow" to avoid duplicate issues and they are not very important pages for me any way. Question: since I am doing a proper translating - no machines involved - can I leave pages as is or should I include any format of these: ISO language codes
2) www.example/com/” /> Even though hand translated, the translation will probably be 85% similar to that if I used Google Translate. Will that potentially be seen as duplicate content or not at all since I have not used the Google Translate tool? I wonder from which angle Google analyses this. Thank you,0 -
URL Structure for Multilingual Site With Two Major Locations
We're working on a hotel site that has two major locations. Locations currently live in separate domains. The sites target users from around the world and offer content in multiple languages. The client is looking into migrating all content into one domain and creating sub-folders for each location. The sites are strong in organic search, but they want to expand the keyword portfolio to broader keywords regarding activities, which they also market on their sites. The goal is to scale their domain authority as they have a really strong brand. The question is which would be a preferred URL structure in case content is finally migrated into one domain? - (we have doubts about were the lang folder should be placed as each location has different amenities and services). Here is what we had in mind: domain.com – this is the homepage domain.com/location-1 – to target English visitors domain.com/location-2 – to target English visitors domain.com/es/location-1 – to target Spanish visitors domain.com/es/location-2 – to target Spanish visitors
International SEO | | burnseo0 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1 -
Multilingual site - separate domain or all under the same umbrella
this has been asked before with not clear winner. I am trying to sum up pros and cons of doing a multilingual site and sharing the same domain for all languages or breaking it into dedicated subdomains e.g. as an example lets assume we are talking about a french property portal with an english version as well. Assume most of the current incoming links and traffic is from France. A) www.french-name.fr/fr/pageX for the french version www.english-name.com/en/pageX for the english version B) www.french-name.fr/fr/ for the french name (as is) www.french-name.fr/en for the english version the client currently follows approach A but is thinking to move towards B we see the following pros and cons for B take advantage of the french-name.fr domain strength and incoming links scalable: can add more languages without registering and building SE position for each one individually potential issues with duplicate content as we are not able to geotarget differenly on web master tools of google potential dilution of each page's strength as we will now have much more pages under the same domain (double the pages basically) - is this a valid concern? usability/marketing concerns as the name of the site is not in english (but then people looking for a house in France would be at least not completely alien to it) what are your thoughts on this? thanks in advance
International SEO | | seo-cat0