"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
-
Google Search Console "International Targeting" is reporting errors that are not present on my site
We are currently handling search for a global brand www.example.com/ which has presence in many countries worldwide. To help Google understand that there is an alternate version of the website available in another language, we have used hreflang tags. These hreflang tags are implemented only via the XML sitemap across all geo-locations. Under the “Search Analytics -> International Targeting” section, in Google Search Console, for the Malaysian website (www.example.com/my/), there are a number of “no-return tags (sitemaps)” errors arising. For example, for India as a geo-location, there is one ‘en-IN’ – no return tags (sitemaps) errors listed. The error is listed below: Originating URL - www.example.com/my/xyz/ Alternate URL - www.example.com/in/xyz/ When the XML sitemap for the URL – www.example.com/in/ was checked for the hreflang tags, it was noticed that the implementation of hreflang tags for the URL – www.example.com/in/xyz/ was perfectly fine and it was providing a return tag to the URL – www.example.com/my/xyz/. After the code level verification, it was identified that the implementation of hreflang tags was perfectly fine via the XML sitemap. Even though at the code level it was verified that the implementation is fine, the error still persists in Google Search Console. Kindly suggest a solution to this situation, and also advise the effects of these errors on search engine performance
International SEO | | Starcom_Search0 -
Is it advisable to show additionally also English ciity names of American cities in website versions of non-western languages such as Chinese, Japanese etc?
To my understanding in many Asian languages city names are transcribed as they sound and this can cause confusion especially in the case of lesser known American city names. So I was planning to put in our international website versions (Chinese, Japanese, Korean etc. ) the English name in brackets after the translated city name in meta title and H1.
International SEO | | lcourse
However when I checked Tripadvisor and Booking.com I noticed that they do not show the English city name anywhere on their Asian language versions. Any thoughts?
Would you recommend to put the English city name in brackets after the translated city name or may it rather hurt our ranking and traffic?0 -
What are the SEO implications of having a website hosted in Singapore (as a subdomain of the global website) when the website is targeting the UK audience?
What are the SEO implications of having a website hosted in Singapore (as a subdomain of the global website) when the website is targeting the UK audience? Will it be hard to get it to rank? Will there be problems with search console?
International SEO | | ToniFarrington-Allthingsweb0 -
Will hreflang with a language and region allow Google to show the page to all users of that language regardless of region?
I'm launching translations on a website with the first translation being Brazilian Portuguese. If I use the following hreflang: If a user is outside of Brazil and has their browser language set to just Portuguese (Not Portuguese (Brazil)) will Google still serve them the Portuguese version of my pages in search results?
International SEO | | Brando160 -
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 -
SEO for .com vs. .com.au websites
I have a new client from Australia who has a website on a .com.au domain. He has the same domain name registered for .com. Example: exampledomain.com.au, and exampledomain.com He started with the .com.au site for a product he offers in Australia. He's bringing the same product to the U.S. (it's a medical device product) and wants us to build a site for it and point to the .com. Right now, he has what appears is the same site showing on the .com as on the .com.au. So both domains are pointing to the same host, but there are separate sections or directories within the hosting account for each website - and the content is exactly the same. Would this be viewed as duplicate content by Google? What's the best way to structure or build the new site on the .com to get the best SEO in the USA, maintain the .au version and not have the websites compete or be viewed as having duplicate content? Thanks, Greg
International SEO | | gregelwell0 -
Website Translation
Hi All, I know its not an SEO question, but....................... Can anyone suggest a few good website translation "widgets" I would like to give those who are not fluent in English and option to choose another language in which to view the page text. Thank You!!!
International SEO | | APICDA0 -
Site structure for multi-lingual hotel website (subfolder names)
Hi there superMozers! I´ve read a quite a few questions about multi-lingual sites but none answered my doubt / idea, so here it is: I´m re-designing an old website for a hotel in 4 different languages which are all** hosted on the same .com domain** as follows: example.com/english/ for english example.com/espanol/ for **spanish ** example.com/francais/ for french example.com/portugues/ for portuguese While doing keyword search, I have noticed that many travel agencies separate geographical areas by folders, therefor an **agency pomoting beach hotels in South America **will have a structure as follows: travelagency.com/argentina-beach-hotels/ travelagency.com/peru-beach-hotels/ and they list hotels in each folder, therefor benefiting from those keywords to rank ahead of many independent hotels sites from those areas. What **I would like to **do -rather than just naming those folders with the traditional /en/ for english or /fr/ for french etc- is take advantage of this extra language subfolder to_´include´_ important keywords in the name of the subfolders in the following way (supposing the we have a beach hotel in Argentina): example.com/argentina-beach-hotel/ for english example.com/hotel-playa-argentina/ for **spanish ** example.com/hotel-plage-argentine/ for french example.com/hotel-praia-argentina/ for portuguese Note that the same keywords are used in the name of the folder, but translated into the language the subfolders are. In order to make things clear for the search engines I would specify the language in the html for each page. My doubt is whether google or other search engines may consider this as ´stuffing´ although most travel agencies do it in their site structure. Any Mozers have experience with this, any idea on how search engines may react, or if they could penalise the site? Thanks in advance!
International SEO | | underground0