Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
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 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 -
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 -
GeoIP Redirects & hreflang
Hello, We believe we've had some issues with hreflang tags not remaining validated due to the implementation of geoIP redirects. Previously, if a user clicked a landing page on Google search that was not targeted for their territory, they would instantly be redirected to a sub path that targets their territory using geoIP redirects. We're planning to remove the initial geoIP redirects and have messaging that prompts the user to either stay on the page they've landed on, or be redirected to page that is right for their territory. However, if a user has selected to be redirected to a sub path that is targeted for their territory, they will have a cookie preference set for the IP location they've selected, and will continue to be redirected to their chosen sub path. My question is, will a crawler follow and trigger the geo preference cookie, which could potentially cause complexities in validating hreflang tags and ranking of content for the right market. Thanks.
International SEO | | SEONOW1230 -
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 you target the same site with multiple country HREFlang entries?
Hi, I have a question regarding the country targeting aspect of HREFLANG. Can the same site be targeted with multiple country HREFlang entries? Example: A global company has an English South African site (geotargeted in webmaster tools to South Africa), with a hreflang entry targeted to "en-za", to signify English language and South Africa as the country. Could you add entries to the same site to target other English speaking South African countries? Entries would look something like this: (cd = Congo, a completely random example) etc... Since you can only geo-target a site to one country in WMT would this be a viable option? Thanks in advance for any help! Vince
International SEO | | SimonByrneIFS0 -
International hreflang - will this handle duplicate content?
The title says it all - if i have duplicate content on my US and UK website, will adding the hreflang tag help google figure out that they are duplicate for a reason and avoid any penalties?
International SEO | | ALLee1 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1 -
What countries does Google crawl from? Is it only US or do they crawl from Europe and Asia, etc.?
Where does Google crawl the web from? Is it in the US only, or do they do it from a European base too? The reason for asking is for GeoIP redirection. For example, if a website is using GeoIP redirection to redirect all US traffic to a .com site and all EU traffic to a .co.uk site, will Google ever see the .co.uk site?
International SEO | | Envoke-Marketing2