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 :
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!
-
In general that kind of implementation is correct.
I do something similar for a client, who has a similar problem but more on the logistic side (different warehouse depending on the continent).
Said that, considering that some products are only for the European market, I don't see useful to use an hreflang like the "de", which would target all the German speaking users no matter from the where they are... I mean, if they are in the USA, I believe that they are not allowed to buy products that are meant only for the EU geography even if they are German or Austrian.
Regarding IP redirection, it's not an alternative... moreover, it's not an alternative obliging people to be sticked to one country/website because that it not allowed by legislation now.
For instance, if someone from the USA want to see the EU site, he should be allowed to do it (this is also valid - obviously for Googlebot, as it is a user at the end).
What you can do is working on the basket process, and there using the IP recognition for allowing or not a bought depending from the country someone is trying to buy a product or not.
Doing so, you will also avoid the frequent dumping issue (e.g.: European buying in the USA because it is cheaper).
-
Hi Thomas,
Thanks for the in depth answer. The only problem remaining here is about the products related to Europe only - and this is why we came up with the .eu solution. Since we need to show a few products to Europe only, we can't use a single gTLD (.com).
Theoretically we could achieve this with geo IP targeting, but this option means that if someone from France is within the US and searching a specific product appearing only to Europe, he would not be able to see it - and we don't want that to happen.
The dev company working for this client made it clear that they can't and don't want to produce multiple directories for each countries (website.com/fr-fr/, website.com/fr-en/, website.com/de-en/, website.com/de-fr/, etc.). Same goes for subdomains (ca.website.com, fr.website.com, etc.).
Don't get me wrong, I'm not a huge fan of using two gTLDs (.com and .eu), but I don't see how we could resolve the European products problem without this option. I'm also worried about the sitemap, using two gTLDs. If you have an other solution in mind, it'd be more than welcome.
-
I would put them all on one domain I would not worry about people and your caring about the EU tag on the domain .com's are far more common over there then .eu
I would put it all under one Domain I would not break it up over to Domains using sub folders just target the rest of the world with English but you're basically making that all to your alternate ask for default which is the one design for if there is no proper language to fit the browser language.
Yes you absolutely can target The same URL with multiple tags. In your case because you're going to have so many hreflang tags I would recommend implementing them through the site map it tends to be faster although you'll need a tool like DeepCrawl or Screaming Frog Prod or to make sure that they're all right.
http://www.aleydasolis.com/en/international-seo-tools/hreflang-tags-generator/
you don't need to add a sub folder to the alternative xt tag.
Obviously you can use/DE for Germany and then use the German language/DE – DE and so forth until you target each country with the specific language that you want to target them with. It seems like you're not interested in selling outside do yo selling outside the Europe as each piece of content I'm sure you know this will have to be written by somebody that is native to the country that you are targeting.
I really think it's just as important do you have the correct content is well is the correct tags. But most of the time people do not use the subfolder for their ex you could theoretically do it if you were not going to use English at all
http://www.acronym.com/bebrilliant/seo/hreflang-sitemaps-free-tool/
I would use a single domain or I would use depending on your resources and what you can put into this a separate TLD neither one of those teal these offer any benefit for Ranking what I'm saying is.edu.com or not as powerful is .CO.UK in the United Kingdom or .de in Germany.
My thoughts would be it would save you a lot of time not to have to use to generic Domains for just the sake of aesthetics. When they have no added trust I honestly feel in Europe people do not think don't you is something more trustworthy than.com though this is only one person's opinion mine.
Make sure that if you're splitting up your domains you do not try to run them as one domain. With the tags as shown.
-
Hi Thomas,
Any updates on your thoughts ?
-
I think I have a good answer for you give me about four hours.
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 -
Using same URL for both "en" and "en-us" hreflang tags
Hi,I have a question. Is it okay if I use the same URL for both "en" and "en-us" hreflang tags? For example, for my en-us page: Is this okay with Google? What are your thoughts on this?
International SEO | | Avid_Demand0 -
Hreflang for selected pages?
My English site example.com has 1300 Pages I have launched a Russian transasation of the site example.ru This site has only 20 pages so far. Doubt: I need to set hreflang for all 1300 pages or only for 20 Pages of example.com that are converted to russian? Due to the limitations of the plugins avaialable I need to MANUALLY set hreflang for all 1300 pages of example.com Please guide
International SEO | | Janki990 -
International SEO & Duplicate Content: ccTLD, hreflang, and relcanonical tags
Hi Everyone, I have a client that has two sites (example.com & example.co.uk) each have the same English content, but no hreflang or rel="canonical" tags in place. Would this be interpreted as duplicate content? They haven't changed the copy to speak to specific regions, but have tried targeting the UK with a ccTLD. I've taken a look at some other comparable question on MOZ like this post - > https://moz.com/community/q/international-hreflang-will-this-handle-duplicate-content where one of the answers says **"If no translation is happening within a geo-targeted site, HREFLANG is not necessary." **If hreflang tags are not necessary, then would I need rel="canonical" to avoid duplicate content? Thanks for taking the time to help a fellow SEO out.
International SEO | | ccox10 -
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 -
International websites : hreflang
Hi, i'm looking for good examples with 'href lang' tag (rel="alternate" hreflang="x") Have you examples of websites with this tag? Thanks D.
International SEO | | android_lyon0 -
Links metrics & rel="alternate" hreflang="x"
Bonjour! If with rel="alternate" hreflang="x" we can indicate to Google that an URL have translated equivalents of a page, are the links metrics splited between all pages or Google considers all the pages as only one? Thanks! Maxime
International SEO | | Maxoulala0