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
-
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 -
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 -
Auto-Redirecting Homepage on Multilingual Site
The website has an auto-redirecting homepage on a multilingual site. Here is some background: User visits the site for first time > sent to javascript age verification page with country of origin selector. If selects "France" then served French page (.com/fr-fr/). If selects any other country, then served English page (.com/en-int/). A cookie is set, and next time the user visits the site, they are automatically served the appropriate language URL. 1st Question: .com/ essentially does not exist. It is being redirected to .com/en-int/ as this is the default page. Should this be a 301 redirect since I want this to serve as the new homepage? 2nd Question:. In the multilingual sitemap, should I still set .com/ as the hreflang="x-default" even though the user is automatically redirected to a language directory? According to Google, as just released here: http://googlewebmastercentral.blogspot.com/2014/05/creating-right-homepage-for-your.html "automatically serve the appropriate HTML content to your users depending on their location and language settings. You will either do that by using server-side 302 redirects or by dynamically serving the right HTML content. Remember to use x-default rel-alternate-hreflang annotation on the homepage / generic page even if the latter is a redirect page that is not accessible directly for users." So, this is where I am not clear. If use a 302 redirect of .com/ to either .com/en-int/ or .com/fr-fr/, won't I then lose the inbound link value and DA/PA of .com/ if I just use a 302? Note: there is no .com/ at this moment. Any advice is appreciated. Thanks,Alex
International SEO | | Alex.Weintraub0 -
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 -
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 -
Multilingual Ecommerce Product Pages Best Practices
Hi Mozzers, We have a marketplace with 20k+ products, most of which are written in English. At the same time we support several different languages. This changes the chrome of the site (nav, footer, help text, buttons, everything we control) but leaves all the products in their original language. This resulted in all kinds of duplicate content (pages, titles, descriptions) being detected by SEOMoz and GWT. After doing some research we implemented the on page rel="alternate" hreflang="x", seeing as our situation almost perfectly matched the first use case listed by Google on this page http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077. This ended up not helping at all. Google still reports duplicate titles and descriptions for thousands of products, months after setting this up. We are thinking about changing to the sitemap implementation rel="alternate" hreflang="X", but are not sure if this will work either. Other options we have considered include noindex or blocks with robots.txt when the product language is not the same as the site language. That way the feature is still open to users while removing the duplicate pages for Google. So I'm asking for input on best practice for getting Google to correctly recognize one product, with 6 different language views of that same product. Can anyone help? Examples: (Site in English, Product in English) http://website.com/products/product-72 (Site in Spanish, Product in English) http://website.com/es/products/product-72 (Site in German, Product in English) http://website.com/de/products/product-72 etc...
International SEO | | sedwards0 -
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