Multinational website - best practice
-
Hello,
I am researching a lot on this subject and have read several articles here on Moz and elsewhere about the best practices for multinational websites. But I'm not yet convinced on what would be the best solution in my case.
Today we have the following websites (examples):
website.com which function as a global website.
website.dk which is for the danish market
website.no which is for the norwegian marketSome of the content on these websites are the same (but different languages; english, danish and norwegian). We want to expand the business to more countries and work with ccTLDs. Both to countries which speaks languages that we don't have content for yet (an example could be Poland), but also more countries that speaks english, like Great Britain (with a .co.uk domain) and Australia (with a .com.au domain). We expect to expand in many countries (as many as it makes sense to do).
I have read a lot about the alternative hreflang tag which would look like and that seems like a good solution, but I have a couple of questions that I hope you guys can answer:
- Should the alternate hreflang tags show every existing language versions including the one you're on or only show the alternative versions?
- Do we risk penalty by having identical or almost identical content for same language websites (could be UK and the global .com one) if we use the alternate hreflang tags? I'm aware that we should use the native spellings and sentences in each country.
- Would the sitemap solution be better in our case?
- We have the same link structure for all websites, but the sub-directories can differ due to their language (like /articles/ is /artikler/ in danish) - is that an issue?
- Will hreflang="en" function as global english? (so searching users that we don't have a local website for will see that).
-
I have an additional question, that I haven't been able to find an answer for elsewhere.
How does Google determine which version is the right one to show for each user? Is it by IP? I mean, in my example we could have an american user that is on vacation in UK. Would he see the .com or .uk result?
It could also be a norwegian user on vacation in Denmark, would he see the .no or .dk results? (danish and norwegian is fairly similar and has a lot of common spellings). -
Thank you for this in depth answer. It's a great help (yours too, Marie).
-
Marie... you're answers are not totally correct.
Please, see my answer below.
-
Here my answers, that partly correct what others answered already (not that they were wrong, but not totally exact).
- Should the alternate hreflang tags show every existing language versions including the one you're on or only show the alternative versions?
Not really. Let me explain.
-
In the case of websites/subfolders/subdomains, which share the same language (eg: USA, UK, AU or ES, MX, AR), using hreflang for every language-country is a must.
-
In the case you have also single websites/subfolders/subdomains that use a unique language (eg.: Italian, which is practically used only in Italy), than you can avoid to add its related hreflang annotation in internal URLs. You should still use it for the home page and every page that may target a not-Italian keyword: I say this so to not see the local site outranked by the most powerful version (usually the English-USA one).
-
In every case you must always implement the hreflang the self-referral annotation (the one you're on, as you defined it).
- Do we risk penalty by having identical or almost identical content for same language websites (could be UK and the global .com one) if we use the alternate hreflang tags? I'm aware that we should use the native spellings and sentences in each country.
No! The hreflang annotation is substantially telling Google that the versions are different and target different users/countries. Even though the differences are very tiny, they are very important (eg.: currencies)
- Would the sitemap solution be better in our case?
It depends. Both the sitemaps and code solutions are valid. The problem of the sitemaps solutions is that it may be harder to update the sitemaps.
- We have the same link structure for all websites, but the sub-directories can differ due to their language (like /articles/ is /artikler/ in danish) - is that an issue?
No! On the contrary, that's the correct thing to do. In fact, also the URLs must be localized.
- Will hreflang="en" function as global english? (so searching users that we don't have a local website for will see that).
Yes, but not with the consequences you are thinking. The "en" only hreflang annotation is telling Google to show that URL to all the English speaking users all over the world (this suggestion is override if exists, for instance, another en-US hreflang annotation).
For having also Spanish users seeing the generic English version of the website, then you should use the hreflang x-default annotation (see here: http://googlewebmastercentral.blogspot.com.es/2013/04/x-default-hreflang-for-international-pages.html)
-
- Should the alternate hreflang tags show every existing language versions including the one you're on or only show the alternative versions?
Yes, show all versions including the one that the user is on
2. Do we risk penalty by having identical or almost identical content for same language websites (could be UK and the global .com one) if we use the alternate hreflang tags? I'm aware that we should use the native spellings and sentences in each country.
Google wouldn't penalize this as duplicate content as there really isn't a duplicate content penalty. But, they'll try to pick the best version to rank. They won't rank all of them for all searches.
3. Would the sitemap solution be better in our case?
I'd still use hreflang. Your case sounds like exactly why hreflang was created.
4. We have the same link structure for all websites, but the sub-directories can differ due to their language (like /articles/ is /artikler/ in danish) - is that an issue?
I don't think so, but it's hard to say without digging in. Again, I'd use hreflang wherever appropriate.
5. Will hreflang="en" function as global english? (so searching users that we don't have a local website for will see that).
Here's from the official documentation from Google:
"
It's a good idea to provide a generic URL for geographically unspecified users if you have several alternate URLs targeted at users with the same language, but in different locales. For example, you may have specific URLs for English speakers in Ireland (en-ie), Canada (en-ca), and Australia (en-au), but want all other English speakers to see your generic English (en) page, and everyone else to see the homepage. In this case you should specify the generic English-language (en) page for searchers in, say, the UK. You can annotate this cluster of pages using a Sitemap file or using HTML link tags like this:
"
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
-
Correct Hreflang & Canonical Tags for Multi-Regional Website English Language Only having URL Parameters
Dear friends, We have a multi-regional website in English language only having the country selector on the top of each page and it adds countrycode parameters on each url. Website is built in Magento 1.8 and having 1 store with multiple store views. There is no default store set in Magento as I discussed with developer. Content is same for all the countries and only currency is changed. In navigation there are urls without url parameters but when we change store from any page it add parameters in the url for same page hence there are total 7 URLs. 6 URLs for each page (with country parameters) and 1 master url (without parameters) and making content duplicity. We have implemented hreflang tags on each page with url parameters but for canonical we have implemented master page url as per navigation without url parameters Example on this page. I think this is correct for master page but we should use URL parameters in canonical tags for each counry url too and there should be only 1 canonical tag on each country page url. Currently all the country urls are having master page canoncial tag as per the example. Please correct me if I am wrong and **in this case what has to be done for master page? **as google is indexing the pages without parameters too. We are also using GEOIP redirection for each store with country IP detection and for rest of the countries which are not listed on the website we are redirecting to USA store. Earlier it was 301 but we changed it to 302. Hreflang tags are showing errors in SEMRush due to redirection but in GWT it's OK for some pages it's showing no return tags only. Should I use **x-default tags for hreflang and country selector only on home page like this or should I remove the redirection? **However some of the website like this using redirection but header check tool doesn't show the redirection for this and for our website it shows 302 redirection. Sorry for the long post but looking for your support, please.
International SEO | | spjain810 -
Hreflang on non 1:1 websites
Hi. I have a client with international websites targeting several different countries. Currently, the US (.com) website outranks the country-specific domain when conducting a search within that country (i.e. US outranks the UK website in the UK). This sounds like a classic case for hrelang. However, the websites are largely not 1:1. They offer different content with a different design and a different URL structure. Each country is on a country-specific domain (.com, .co.uk, .com.au, etc.). As well, the country-specific domains have lower domain authority than the US/.com website - fewer links, lower quality content, poorer UX, etc. Would hreflang still help in this scenario if we were to map it the closest possible matching page? Do the websites not sharing content 1:1 add any risks? The client is worried the US/.com website will lose ranking in the country but the country-specific domain won't gain that ranking. Thanks for any help or examples you can offer!
International SEO | | Matthew_Edgar0 -
Multilingual website - Url problem (sitemap)
At this moment our website both uses the language in the url like "en" and localizes the url itself ("books" in english and "boeken" in dutch). Because of the history of making our website multilingual we have a system that takes the browser language for the localization if the url doesn't contain a language like "en". This means: www.test.com/books = browser language www.test.com/en/books = english language www.test.com/boeken = browser language www.test.com/nl/boeken = dutch language Now for the sitemap this makes it a little troublesome for me because which hreflang is used for which url? 1) The first thing I thought of was using x-default for all urls that get the language of the browser. <code><url><loc>http://www.test.com/books</loc></url></code> But as you can see we now got 2 times x-default. 2) Another solution I thought of was just use the localization of the url to determine the language like: <code><url><loc>http://www.test.com/books</loc></url></code> But now we got 2 of each language for the same page. 3) The last solution I thought of was removing links without a language in the url (except for the homepage, which will still have an x-default) like: <code><url><loc>http://www.test.comen/books</loc></url></code> But for this solution I need to put 301's at pages that are "deleted" and also need to change the system to 301 to the right page. Although the last point isn't really a problem I'm kind of worried that I will lose some of the "seo points" with a 301. (When we changed our domain in the past we had a bad experience with the 301 of our old domain) What do you think would be the best solution for SEO? Or do you have any other suggestions or solutions I haven't thought of.
International SEO | | Anycoin0 -
Duplicate content on multistore Magento website
Hello there, We run a Magento based e-commerce site in the UK for example: domain.com We are looking to launch a USA and Australian version of the website: usa.domain.com and au.domain.com Obviously the currency will be different and so will some of the content. Will we be penalised for having duplicate content across these 3 sites? (As some pages will be very similar or the same) Thanks Robert
International SEO | | roberthseo0 -
Url for Turkish, Russian, Chinese, Arabic, Vietnamese and Arabic websites
Hello ! We gonna release our next website with new amazing languages. However I was wondering, is it better to keep the url in English or I can translate them in : Turkish (should be fine) Chinese Arabic Vietnamese Arabic Russian All websites are properly translated but I'm hesitating for the url. Tks a lot !
International SEO | | AymanH0 -
Best practice for WPML, Yoast and sitemap for google
Hi Mozzers, I have a wordpress installation and work on a hotel website in three different languages: English, German, Spanish. In order to manage each language as a regional or global website, I started to give the website the names like: de.hotelnamen.com, es.hotelname.com (Hotel is in Costa Rica, maybe cr.hotelname.com is even better???) and hotelname.com. The possibility of WPML to manage my multilingual blog is good and the Yoast plugin gives me the sitemaps I want for each language. Because it is a hotel I have to have a global page which should serve the world if they try to find the hotel, right? That's why i put hotelname.com as a global page in English and registered the sitemaps and page on my webmaster account in countries as "not listed". For de.hotelname.com I choose Germany on another webmaster account and for es.hotelname.com Costa Rica (the country in which the Hotel is located). Unfortunately, after three month I don't receive good results with that methode. The hotelname.com adress is always the page which comes up in all search engines. I my tactic wrong? Where is my mistake? I would like to have hotelname.com in the rankings of all search engines beside of google Germany because for the German market I have the German version. Same in Costa Rica. Thanks for some ideas...
International SEO | | reisefm0 -
When is it best to use a ccTLD or TLD?
I understand that the relative importance of domain extensions - .com is better than .biz, etc. - is a bit of a myth. I also believe that using a ccTLD is likely to affect rankings for that site outwith that country. But, is the opposite true? Will giving a site a ccTLD help improve its SEO in that country? If you have a global organisation, is it better to establish a series of country specific sites - ccTLD - or to purchase the country specific domains and point them to the.com (if only to stop cyber-squatting)? What if the company wanted to establish regional microsites that feature content about products only available within that region? Many thanks, Iain
International SEO | | iain0 -
Interlinking 60 ccTLD country versions of website
We will be launching 60 new ccTLD country versions of an established core website.
International SEO | | lcourse
Quality, human translated content in 35 languages.
We have a CSS dropdown menu with the 60 country flags and country/language name as anchor text. Formatted as deeplinks to the corresponding pages in the 60 country versions, that we planned to add on each page. How would you recommend to implement the interlinking between these 60 ccTLD? My concerns are: won't we dillute the link value of our links in the main page content too much with links to 60ccTLD on each page? may we trigger a google penalty as the new ccTLD have no other links yet and each page will have the same anchor text and links from exactly the same 60 domains. would you place the country dropdown rather at the bottom of the page (e.g. footer) to avoid that google will not crawl all links in main content page. Any thoughts or suggestions are appreciated1