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
-
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 -
Which pages to put hreflang on?
Hi, we are running a site which is a directory consisting of numbers of phone spammers. It contains descriptions, comments and so on. We are currently present in 9 countries. The websites all have the same structure, but, of course, the spam numbers in each country are different ones. If I want to tell Google that our website is available is several locations/languages, do I only put my hreflang tag on the start page then? Thanks
International SEO | | Roverandom
Thomas0 -
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 -
Hreflang vs canonical
I'm having an international Drupal website and the hreflang module is in use. However, I'm still not sure how to optimize the pages. Perhaps it's easier to ask with an example **International: **www.example.com/products/product1
International SEO | | Teklan
Here we have the master content of the product **US: **www.example.com/us/products/product1
Here we have exactly the same content as international. Nothing is localized. **UK: **www.example.com/uk/products/product1
Here we have almost the same content as on International. Here and there some local terms and extra text. **German: **www.example.com/de/products/product1
Here we have a translated version of the international page. Questions Do I add hreflang from all to all pages + to itself? Where do I add canonicals? How should I optimize the content on the US and UK pages?0 -
Hreflang no return tags error in GWT
Hello everybody, It has been 2 month since I'm trying to figure out the cause of increasing "no return tags" error count in GWT. I have checked the syntax several times and even switched from meta tags method to including language versions in sitemap without any luck. Below is a screen shot of GWT error and a sitemap excerpt that shows original and alternate URL both having return tags pointing to each other. The full sitemap can be found here: http://wordsru.com/sitemap.xml Any help or insight about whats going on here much appreciated. Thanks! RKP6AhZ.jpg KFluNCC.jpg
International SEO | | Icemax0 -
Hreflang hindering performance?
I want to add hreflang on my website but the dev guys think it will hinder performance? Any thoughts/experience with this one way or the other? Thanks!
International SEO | | theLotter0 -
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 -
Ranking well internationally, usage of hreflang, duplicate country content
I'm trying to wrap my head around various options when it comes to international SEO, specifically how to rank well in countries that share a language, and the risk of duplicate content in these cases. We have a chance to start from scratch because we're switching to a new e-commerce platform, and we were looking into using hreflang. Let's assume an example of a .com webshop that targets both Austria and Germany. One option is to include both language and region in the URL, and mark these as such using hreflang: webshop.com/de-de/german-language-content (with hreflang de-de)
International SEO | | DocdataCommerce
webshop.com/de-at/german-language-content (with hreflang de-at) Another option would be to only include the language in the URL, not the region, and let Google figure out the rest: webshop.com/de/german-language-content (with hreflang de) Which would be better? The risk of inserting a country, of course, is that you're introducing duplicate content, especially since for webshops there are usually only minor differences in content (pricing, currency, a word here and there). If hreflang is an effective means to make sure that visitors from each country get the correct URL from the search engines, I don't see any reason not to use this way. But if search engines get it wrong, users will end up in the wrong page and will have to switch country, which could result in conversion loss. Also, if you only use language in the URL, is it useful at all to use hreflang? Aren't engines perfectly able to recognize language already? I don't mention ccTLDs here because most of the time we're required to use a .com domain owned by our customer. But if we did, would that be much better? And would it still be useful to use hreflang then? webshop.de/german-language-content (with hreflang de-de)
webshop.at/german-language-content (with hreflang de-at) Michel Hendriks
Docdata Commerce0