"Hreflang=x" tag and multinational websites
-
Hello,
We have multiple websites targeted at multiple countries and languages, each with the correct country extension. We have a corporate blog for each of these websites, where the blogs are subdomains of the main website. Currently we have a process of rewriting our blog posts completely – while keeping the same subjects – in order to have original content on each of our blogs, although we have up to 3 blogs in the same language.
These are the languages we target:
- French – FRANCE
- French – SWITZERLAND
- French – BELGIUM
- Italian – ITALY
- Italian – SWITZERLAND
- German – GERMANY
- German – SWITZERLAND
- German – AUSTRIA
- Spanish – SPAIN
- Spanish – COLOMBIA
- Spanish – PANAMA
- Czech – CZECH REPUBLIC
- Swedish – SWEDEN
- Dutch – BELGIUM / NETHERLANDS
- English – UK
- English – INTERNATIONAL
The process is obviously very tedious, and not always applied rigorously – i.e. some of the texts are posted on 2-3 different blogs, creating duplicate content.
The questions :- Would there be any reason for us to privilege the use the rel="canonical" tag over the "hreflang=x" tag, thus giving privilege to a "master" version for each language?
- Are there any risks in using the "hreflang="x" tag for our blogs considering that the posts would be very similar, except for references to additional content? Could there be any risk that Google would consider our sites as duplicate content after all?
- Should we specify on each blog that we have all the above versions, or should we only specify the other markets versions in each language? For example, should we specify on our French, Swiss and Belgium blog that we have 3 different French versions, on our UK blog that we also have an international version, and so on, or should we list all versions on each of the blogs?
- Does the "hreflang="x" tag facilitate the indexation of each of the versions in the SERPs of their targeted market?
- Lastly, are there any precautions we should take in order to put this in place?
Looking forward to your feedback.
Best wishes,
Maëlle
-
Take a look at this video from Matt Cutts outlining their position on translated content.
In addition, as to the question of canonical element and hreflang you'll see that Google removed this portion from their guidelines with an update saying 'to simplify implementation, we no longer recommend using rel=canonical.' Check out the piece for the current position.
I also had advice direct from Christopher Semturs from Google who said directly to me "the golden rule I personally recommend to everybody using hreflang: In doubt, don't use rel-canonical."
-
Thank you very much for your response, Simon.
Having the international version of our site showing in the UK would not be a critical issue, as we make it easy to switch to the other languages/markets versions.
It is quite odd that Google does not view translated content as duplicate, I wasn't aware of this – would you be able to provide with some source where this is explained, please?
Also, do you have a view on my question re the rel="canonical" tag – would there be any reason not to use the "hreflang="x" tag but use instead the rel="canonical" tag, thus specifying a "master" version out of our 3 French versions, for instance?
-
Since Google does not view translated content as duplicate I would suggest that you would only need to specify the alternate language versions of the same language. For example on your France, Switzerland and Belgium pages using hreflang to specify all 3 alternate French language versions, and then doing the same for your German language pages, English language pages etc. You would not need to reference all alternative URLs regardless of language.
Using hreflang in this way should ensure that your intended version is displayed in the correct country SERPs. This is usually the case although on occasions I have found that the international versions may occasionally be shown in the UK instead of the UK version, but these occasions are rare.
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
-
Hreflang on non 1:1 websites
Hi. I have a client with international websites targeting several different countries. Currently, the US (.com) website outranks the country-specific domain when conducting a search within that country (i.e. US outranks the UK website in the UK). This sounds like a classic case for hrelang. However, the websites are largely not 1:1. They offer different content with a different design and a different URL structure. Each country is on a country-specific domain (.com, .co.uk, .com.au, etc.). As well, the country-specific domains have lower domain authority than the US/.com website - fewer links, lower quality content, poorer UX, etc. Would hreflang still help in this scenario if we were to map it the closest possible matching page? Do the websites not sharing content 1:1 add any risks? The client is worried the US/.com website will lose ranking in the country but the country-specific domain won't gain that ranking. Thanks for any help or examples you can offer!
International SEO | | Matthew_Edgar0 -
Hreflang tags and canonical tags - might be causing indexing and duplicate content issues
Hi, Let's say I have a site located at https://www.example.com, and also have subdirectories setup for different languages. For example: https://www.example.com/es_ES/ https://www.example.com/fr_FR/ https://www.example.com/it_IT/ My Spanish version currently has the following hreflang tags and canonical tag implemented: My robots.txt file is blocking all of my language subdirectories. For example: User-agent:* Disallow: /es_ES/ Disallow: /fr_FR/ Disallow: /it_IT/ This setup doesn't seem right. I don't think I should be blocking the language-specific subdirectories via robots.txt What are your thoughts? Does my hreflang tag and canonical tag implementation look correct to you? Should I be doing this differently? I would greatly appreciate your feedback and/or suggestions.
International SEO | | Avid_Demand0 -
For My International Sites only Homepage in other Language rest Pages are in English. Hreflang required here?
Hello All, For my ecommerce site at my homepage there is an Language option of 9 different countries. My main site - abcd.co.uk and other sites are like this se.abcd.co.uk, fr.abcd.co.uk, es.abcd.co.uk etc From my main site if user clicks on fr.abcd.co.uk then France site will open but when he click on any link it will redirect to my UK site. On France site homepage if user hover the cursor then links are visible of UK site only. My query is ;- Do it required here to implement hreflang? As only homepage is in different language? Do it anything wrong in google point of view? Thanks!
International SEO | | wright3350 -
Are my hreflang and canonical link tags set correctly?
Currently we have a website in english but over time we will roll out parts of the whole site in different languages for different countries which will also result in country specific English versions of the website. The goal is that Google shows the country specific version of a page in a native language or English if available or falls back to the default English version of the same page otherwise. I listed below how we plan to use hreflang and canonical link tags to achieve this and was hoping to get some feedback from the Moz community if this will work as expected. (1) A page (www.mysite.com/page1) exists only in English as default. Users should be able to find it in every country unless there is an English version specifically for this country. We would use the following tags: (2) A page exists in English (www.mysite.com/id/en/page2) and Bahasa (www.mysite.com/id/id/page2) for a specific country (Indonesia in this case). Users in Indonesia searching in English should find the country specific English page. Indonesians searching in Bahasa should find the Bahasa version of that page. We would use the following tags on the English version: and therefor the following tags on the Bahasa version: In this case there wouldn't be a default English version available for the page. (3) If a page exists in English global, English for Indonesians and Bahasa for Indonesians we would use: on www.mysite.com/id/en/page3 on www.mysite.com/id/id/page3 on www.mysite.com/page3 If www.mysite.com/id/en/page3 and www.mysite.com/page3 are very similar we would risk google picking the page they want to rank for an english keyword searched in Indonesia, correct? (4) If a page in (1) and (2) can be reached with a different URL, we would only use a canonical and don't specify any hreflang tags e.g.: www.mysite.com/en/other-url-to-page1 or
International SEO | | ddspg
www.mysite.com/id/en/other-url-to-page2-english-indonesia (5) If a page that exists as global English page becomes available in English for a specific country as e.g. www.mysite.com/uk/en/page1 we would use the following tags: and also add one more hreflang to www.mysite.com/page1: The assumption here is that Google would rank the localized page instead of the global page after crawling our site again. But since this will be a new page, are we going to lose traffic because www.mysite.com/uk/en/page1 won't rank as well in the beginning (e.g. no offsite optimization)?0 -
Can multiple hreflang tags point to one URL? International SEO question
Moz, Hi Moz, Can multiple hreflang tags point to a single URL? For example, if I have a Canadian site (www.example.com/ca) that targets French and English speakers can I have the following: or would I use: Any insight would be very helpful and greatly appreciated! Thank you in advance!
International SEO | | DA20131 -
Hreflang link is always going to the homepage
Hey there fellow Mozzers, I'm currently performing some work for a webshop which is located at two different TLD's.
International SEO | | WesleySmits
example.com and example.nl. In the head of both websites the hreflang tags have been added to tell Search Engines which site is targeted at which country. That's good 🙂 However, the hreflang links are pointing to the homepages of both websites from every page on the websites. Isn't example.nl/blog/ not supposed to link the hreflang tag to example.com/blog/?0 -
External URLs in hreflang sitemap questions
I'm currently putting together an international sitemap for a website that has an set up like the following: example.com/us
International SEO | | Guyboz
example.com/au
example.com/ca
example.co.uk
example.se I'm planning on including the hreflang tags within sitemaps for each domain, to make sure google serves up the right version. However, I'm a bit sceptical about including the non .com domains within the .com sitemap - and the other way round for .co.uk and .se sitemaps. The way I've been doing it follows the following example: <url><loc>http://www.example.com/us/</loc></url> Putting in the .co.uk and .se domains within the .com sitemap just doesn't feel right - is this actually the right way to do it? Thanks in advance 🙂0 -
.com or .ca for my Canadian website that is the question...
I have a US based company that is expanding to Canada, would it matter if I have a .com or .ca for my website?
International SEO | | BCA0