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
-
How should I handle hreflang tags if it's the same language in all targeting countries?
My company is creating an international version of our site at international.example.com. We are located in the US with our main site at www.example.com targeting US & Canada but offering slightly different products elsewhere internationally. Ideally, we would have hreflang tags for different versions in different languages, however, it's going to be an almost duplicate site besides a few different SKUs. All language and content on the site is going to be in English. Again, the only content changing is slightly different SKUs, they are almost identical sites. The subdomain is our only option right now. Should we implement hreflang tags even if both languages are English and only some of the content is different? Or will having just canonicals be fine? How should we handle this? Would it make sense to use hreflang this way and include it on both versions? I believe this would be signaling for US & Canda visitors to visit our main site and all other users go to the international site. Am I thinking this correctly or should we be doing this a different way?
International SEO | | tcope250 -
When should hreflang be deployed in this situation; now or later ?
Hi I have a question in regard to point 1 in Gianluca Fiorelli first comment on Aleyda Solis old but great international targeting article in regard to hreflang: https://moz.com/blog/using-the-correct-hreflang-tag-a-new-generator-tool it would obvs be amazing if either Gianlucca or Aleyda can answer but if anyone else feels they can do so confidently then that would be great too 🙂 I'm advising someone in similar situation as that (their main brand is USA based on a .com showing up in UK searches too) and they have launched .co.uk sites (without any seo) to target UK brand searches, so obviously the .com is still dominating UK serps for brand, and the .co.uk is ranking on page 4 on average for a brand search. **BUT **before I tell them to roll out hreflang shouldn't they build up some authority etc first for their new country specific (.co.uk) site ? since they are very new and have no authority or even basic SEO and don't rank higher than page 4 for brand searches (the .com is in no1 in both usa and uk). I know hreflang needs to be used correctly here but im not sure when it should be, now or later (after authority has built up for the new uk focused sites) ? In other words I take it deploying the hreflang correctly wont simply cause these home pages to swap positions for brand search in uk (or will it) ? Im worried deploying it immediately could actually destroy the brands current page 1 serps for brand term (since will remove the .com page from the uk serp). Hence i take it its best to build up the new .co.uk sites seo/authority etc first and at least get that sites brand ranking moving up the listings before deploying hreflang on the .com, to then hopefully remove the .com listing in place of the .co.uk for brand ? OR does Gianlucca point in his comment suggest that correct hreflang usage on both sites should swap the high authority .com no1 position with the low authority .co.uk for a brand search ? Many Thanks Dan
International SEO | | Dan-Lawrence0 -
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 -
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 tag on every page?
Hello Moz Community, I'm working with a client who has translated their top 50 landing pages into Spanish. It's a large website and we don't have the resources to properly translate all pages at once, so we started with the top 50. We've already translated the content, title tags, URLs, etc. and the content will live in it's own /es-us/ directory. The client's website is set up in a way that all content follows a URL structure such as: https://www.example.com/en-us/. For Page A, it will live in English at: https://www.example.com/en-us/page-a For Page A, it will live in Spanish at https://www.example.com/es-us/page-a ("page-a" may vary since that part of the URL is translated) From my research in the Moz forums and Webmaster Support Console, I've written the following hreflang tags: /> For Page B, it will follow the same structure as Page A, and I wrote the corresponding hreflang tags the same way. My question is, do both of these tags need to be on both the Spanish and English version of the page? Or, would I put the "en-us" hreflang tag on the Spanish page and the "es-us" hreflang tag on the English page? I'm thinking that both hreflang tags should be on both the Spanish and English pages, but would love some clarification/confirmation from someone that has implemented this successfully before.
International SEO | | DigitalThirdCoast0 -
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 -
Will website with tag hreflang pass link juice to other country/language version of website?
For example, I have a website XXX.com and I made hreflang tags to other country/language versions of website: ru.XXX.com (for Russia/Russian) XXX.com.ua (for Ukraine/Russian) ua.XXX.com (for Ukraine/Ukraine) Then I will acquire links to XXX.com. The question is: will XXX.com pass link juice to websites ru.XXX.com, XXX.com.ua and ua.XXX.com. Will these websites rank in their countries if I will acquire links ONLY to XXX.com? I looked at https://support.google.com/webmasters/answer/189077?hl=en, but haven't found what google think about that. Thank you in advance. I will appreciate your help.
International SEO | | Kabanchik0