"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
-
Targeting/Optimising for US English in addition to British English (hreflang tags)
Hi, I wonder if anyone can help? We have an e-commerce website based in the UK. We sell to customers worldwide. After the UK, the US is our second biggest market. We are English language only (written in British English), we do not have any geo-targeted language versions of our website. However, we are successful in selling to customers around the world on a regular basis. We have developers working on a new site due to launch in Winter 2021. This will include a properly managed site migration from our .net to a .com domain and associated redirects etc. Management are keen to increase sales / conversions to the US before the new site launches. They have requested that we create a US optimised version of the site. Maintaining broadly the same content, but dynamically replacing keywords: Example (clothing is not really what we sell): Replacing references to “trainers” with “sneakers”
International SEO | | IronBeetle
Replacing references ‘jumpers with “sweaters”
Replacing UK phone number with a US phone number It seems the wrong time to implement a major overhaul of URL structure, considering the planned migration from .net to .com in the not too distant future. For example I’m not keen to move British English content on to https://www.example.com/en-gb Would this be a viable solution: 1. hreflang non-us visitors directed to the existing URL structure (including en-gb customers): https://www.example.com/
2. hreflang US Language version of the site: https://www.example.com/en-us/ As the UK is our biggest market It is really important that we don’t negatively affect sales. We have extremely good visibility in SERPS for a wide range of high value/well converting keywords. In terms of hreflang tags would something like this work? Do we need need to make reference to en-gb being on https://www.example.com/ ? This seems a bit of a ‘half-way-house’. I recognise that there are also issues around the URL structure, which is optimised for British English/international English keywords rather than US English e.g. https://www.example.com/clothing/trainers Vs. https://example.com/clothing/sneakers Any advice / insight / guidance would be welcome. Thanks.0 -
How do hreflang attributes affect ranking?
We have a site in English. We are considering translating the site into Dutch. If we use a hreflang attribute does that mean we have to create a duplicate page in Dutch for each English page, or does Google auto-translate? How would duplicate pages, even if they are in a different language, affect ranking?
International SEO | | Substance-create0 -
Worldwide and Europe hreflang implementation.
Hi Moz ! We're having quite a discussion here and I'd like to have some inputs. Let me explain the situation and what we plan to do so far. One of our client has two separate markets : World and Europe. Both pages versions will be mostly the same, except for the fact that they will have their own products. So basically, we'd want to show only the European EN version to Europe and the standard EN version to the rest of the world, same goes for FR and ES. As far as IT, DE, CS and SK, they will only be present within the european version. Since we cannot target all Europe with a single hreflang tag, we might have to do it for every single european countries. Regarding this subject, SMX Munich recently had quite an interesting session about this topic with a confirmation coming from John Mueller saying that we can target a single URL more than once with different hreflang tags. You can read more here : http://www.rebelytics.com/multiple-hreflang-tags-one-url/ So having all this in mind, here's the implementation we plan to do : www.example.com/en/ Self canonical www.example.com/fr/ - hreflang = fr www.example.com/es/ - hreflang = es www.example.eu/it/ - hreflang = it www.example.eu/de/ - hreflang = de www.example.eu/cs/ - hreflang = cs www.example.eu/sk/ - hreflang = sk www.example.eu/fr/ - hreflang = be-fr www.example.eu/fr/ - hreflang = ch-fr www.example.eu/fr/ - hreflang = cz-fr www.example.eu/fr/ - hreflang = de-fr www.example.eu/fr/ - hreflang = es-fr www.example.eu/fr/ - hreflang = fr-fr www.example.eu/fr/ - hreflang = uk-fr www.example.eu/fr/ - hreflang = gr-fr www.example.eu/fr/ - hreflang = hr-fr etc… . This will be done for all european countries (FR, EN and ES). www.example.com/en/ - x-default Let me know what you guys think. Thanks!
International SEO | | Netleaf.ca0 -
International SEO Question: Using hreflang tags across two different TLDs.
Hi! My UK based company just recently made the decision to let the US market operate their ecommerce business independently. Initially, both markets were operating off the same domain using sub-directories (i.e: www.brandname.com/en-us/ , www.brandname.com/en-gb/ ) Now that the US team have broken away from the domain - they are now using www.brandnameUSA.com while the UK continues to use www.brandname.com/en-gb/. The content is similar across both domains - however, the new US website has been able to consolidate several product variations onto single product pages where the UK website is using individual product pages for each variation. We have placed a geo-filter on the main domain which is 301 redirecting North American traffic looking for www.brandname.com to www.brandnameUSA.com However, since the domain change has taken place, product pages from the original domain are now indexing alongside the new US websites product pages in US search results. The UK website wants to be the default destination for all international traffic. My question is - how do we correctly setup hrlang tags across two separate TLDs and how do we handle a situation where multiple product pages on the "default" domain have been consolidated into one product page on the new USA domain? This is how we are currently handling it: "en-us" href="https://www.BRANDNAMEUSA.com/All-Variations" /> href="https://www.BRANDNAMEUSA.com/All-Variations" />
International SEO | | alexcbrands0 -
How well does Google's "Locale-aware crawling by Googlebot" work?
Hello, In January of this year Google introduced "Locale-aware crawling by Googlebot." https://support.google.com/webmasters/answer/6144055?hl=e Google uses different crawl settings for sites that cannot have separate URLs for each locale. ......... This is basically for sites that dynamically render contend on the same URL depending on the locale and language (IP) of the visitor. If e.g. a visitor was coming from France, the targeted page would load in french. If a visitor was coming from the US the same page would load in English on the same URL. Does anyone have any experience with this setup and how well it works? How well do the different versions of a page get indexed, and how well do those pages rank? In the example above, does the french content get indexed correctly? Many thanks!
International SEO | | Veva0 -
Backlinks to URLs with Language Parameters (for Chinese version of website) and SEO?
Hey all, We run a large eCommerce site in Australia and are preparing to launch to the Chinese market. Our site has been fully converted to Chinese and displays the version of the site detected as default in the user's browser unless they manually select otherwise. This is done by appending the parameter "?la=zh" onto the end of the URL, so for example the Chinese version would be: **www.example.com/australia?la=zh ** This then forces the product catalogue to display the relevant language version. My question is, for SEO purposes and back links in particular, since they aren't really a "true URL" (i.e: strictly speaking they aren't different "pages", just the same page being populated with different characters), would getting links from Chinese websites to the URL "www.example.com/australia?la=zh" really be viewed as any different from just "www.example.com/australia"? Do they pass the same amount of juice and is the difference detected by the engines (thinking mainly about Baidu in particular but of course Google as well)? Feedback from anyone with experience in SEO for multi-lingual sites would be much appreciated, thanks.
International SEO | | ExperienceOz0 -
Upper case or/and lower case in rel="alternate" hreflang
Hi Mozzers, I have a question about the rel="alternate" hreflang tag, with an example. When I use two subfolders for two different countries/languages, for instance www.domain.com/nl-nl/ and www.domain.com/nl-en/ (for the English version) and I want to use the rel="alternate" hreflang tag, do I need to follow the ISO standards concerning Uppercase country code and Lowercase language code (en-NL)? Or is it okay to use the Lowercase country and language code (en-nl), since we also use this in the URL of the Subfolder. What does Google prefer? Thanks in advance.
International SEO | | MartijnHoving820 -
Multi-National Website Demarcation in Organic Search
We launched our business in the UK many years ago using a .com domain and have built up good link equity back to our www site. Last year, we launched the same business in the US and host the US site on a "us." sub domain. We have used Google Webmaster Tools to demarcate the two websites so that the www site is set to target the UK and the "us." sub domain is set to target the US. Our organic search results from Google UK for the UK business are fine but when our US customers Google brand terms the www UK site takes precedence in organic search. To complicate this further, the sitelinks within the search results include a mixture of pages from the www UK site and the "us." US site. Google clearly has some difficulty understanding that the two sites are for two different geographic audiences. We have a good relationship with Google and they have indicated (with appropriate disclaimers) that we might consider aligning the URL structures for both sites to reduce the precedence that the www site currently receives. The www home page will become an International portal and the UK and US URL structures will be aligned. We have two options: Change both sites to subdomains so that we have "uk.xxxxx.com" and "us.xxxxx.com" linked to an International portal at the www subdomain Use sub folders so that we have "www.xxxxx.com/uk/" and "www.xxxxx.com/us/" again linked from the www subdomain We're comfortable with use of 301 redirects and canonicals to change the structure in a search engine friendly way but cannot agree internally whether sub domains or sub folders is the way to go. Unfortunately we're to far down the line to seperate by tld. Anyone have a strong opinion on the best approach? Thanks, Jeremy
International SEO | | www.webuyanycar.com0