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
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
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
-
Problem to get multilingual posts indexed on Google
Last year on June I decided to make my site multi-lingual. The domain is: https://www.dailyblogprofits.com/ The main language English and I added Portuguese and a few posts on Spanish. What happened since then? I started losing traffic from Google and posts on Portuguese are not being indexed. I use WPML plugin to make it multi-lingual and I had Yoast installed. This week I uninstalled Yoast and when I type on google "site:site:dailyblogprofits.com/pt-br" I started seeing Google indexing images, but still not the missing posts. I have around 145 posts on Portuguese, but on Search Console it show only 57 hreflang tags. Any idea what is the problem? I'm willing to pay for an SEO Expert to resolve this problem to me.
International SEO | | Cleber0090 -
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 -
Multiregional / Multilingual SEO - What do you do when there is no equivalent page?
Hello, We're building out a small number of pages for the US in a sub-folder .com/us. The idea is to show US specific pages to users in that location. However, we also have a number of pages which we will not be creating for the US as they're not relevant. I am planning on geo-targeting the US folder to instruct the search engines that this subfolder should appear in the US SERPS but since it isn't an exact science, there is a chance that US visitors may land on these non-us pages which could potentially give them a bad user experience. What should we do in instances where a US user lands on a non-us page with no equivalent page? Any help would be much appreciated!
International SEO | | SEOCT1 -
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 - Best choice?
Quick question for a site that has the same content but in a different language (not machine translated) on seperate pages.
International SEO | | Crunchii
Say I have:www.mydomain.com (which is in English)
www.mydomain.com/ES (which is in Spanish)
www.mydomain.com/NL (which is in Dutch) I don't want to limit the ie. Spanish to only Spain so geotargeting isn't necessary What is the best/correct setup for the pages?0 -
Best URL structure for Multinational/Multilingual websites
Hi I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.) As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product? To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format: hotelsite.com/en/hotel-name (for english) and hotelsite.com/se/hotel-name (for swedish content of that same product) and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc. Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name? Any thoughts on best practice would be greatly appreciated.
International SEO | | pikka0 -
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