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
-
Localization best practice
Hi Guys, I have a question about localization versions of my websites. Currently for other languages we use folders like /de/, /es/ and we have implemented hreflang. But it will be in any help if I add all those localization versions in Search Console as separate properties and specify there which language is it for? Can this help more that just leave it as it is? Thanks, Florin
International SEO | | VeeamSoftware0 -
Can a Global Website Rely on Browser Settings for Translation?
Our website serves a global market and over a year ago, we launched 8 language variations of the site and implemented hreflang tags. These language variation pages are proving difficult to maintain, and in Search Console they're triggering thousands of errors. I have double checked our implementation and it's not perfect, so I understand the errors. Here's the question though... the 8 language variations of the site are receiving less than 1% of our web traffic despite 40% of our web traffic coming from countries outside of North America every month. I want to know if we can eliminate the headache of these 8 language variations altogether, remove our attempt at hreflang, and simply rely on the browser settings of the user to dictate what language the website appears in for them? If not, is there a simpler solution than hreflang and attempting to maintain a very large website in 8 languages? Thank for your input! Niki
International SEO | | NikelleClark0 -
Hreflang for bilingual website in the same region/location
Hi everyone, got a quick question concerning the hreflang tag. I have a website with 2 different language versions targeting to the same region(Reason: The area is bilingual however not everyone speaks the other language fluently) Question:
International SEO | | ennovators
Can I use hreflang in that case like: Many thanks in advance0 -
Different urls for the homepage on an international website
Hi! I was wondering what would be the best strategy to solve duplicated content generated by the homepage and its differents URLS This is an international website. Now it only has one language working: Spanish, but the url structure is already ready to work with the language approach So we have now www.brand.com -> Spanish Homepage (canonical www.brand.com/es)
International SEO | | teconsite
www.brand.com/es -> Spanish Homepage (canonical www.brand.com/es)
www.brand.com/index.php -> Spanish Homepage (canonical www.brand.com/es) I would like to know if this is the correct approach of if we should add 301 redirects instead of canonical. Let's image that they want to active the /en language, so they will have www.brand.com
www.brand.com/index.php
www.brand.com/es
www.brand.com/en now what? I image they have to use hreflang, but I am a little lost with how this should work. 301? canonical? hreflang? Could you help me? Thank you! Victoria0 -
Best International Rank Checker?
Anyone have a recommendation for the best international ranking tool. I'm looking to gather accurate ranking trends and am looking for a service that will return rankings in as many localized countries as possible.
International SEO | | marcbn0 -
Sitemap for multilanguage website
Hello sorry silly question but prefer to be sure 🙂 I have an international website with different subfolders .com/es .com .com/fr etc All of them have independant sitemap, but i'd like to add in .com/robot.txt a sitemap with language. Do you know how I can do this ? Tks a lot !
International SEO | | AymanH0 -
Multi Regional website - Folder strategy
Hello Seomoz people ! I've been struggling for some time now with an international website project. It's gonna be an:international website with joomla. To sum up: We have an international company The company has 13 subsidiaries worldwide (same products, different names) The company doesn't have enough resources to get 13 independent websites Some subsidiaries work in one country / one language, some others on a region (several countries, several languages) Thanks to your community we decided to: Get a main website company.com Get subsidiaries folders (middle east, oceania and south america will be easier to link to their subsidiary) .com/asia .com/middle-east .com/oceania .com/south-america .com/uk .com/usa .com/fr .com/es .com/de .com/ma .com/dz .com/it We also need to: Get some websites in different languages .com/asia-cn .com/asia-en etc. Now how do we do to manage: Regional websites (the first 4th on the upper list) Google allows to affect a website to a country not region Will they compete with the .com ? How do we set up them for google ? How do we avoid duplicate content and keep local ranking .com/asia-en/services1.html will have the exact same content that_.com/services1.html_ If we use canonical from _.com/asia-en/services1.htm_l to _.com/services1.html , d_oes that mean /asia will not rank in asia ? Hope you can help us to figure us the best solution for this good project ! Thanks a lot. Florian
International SEO | | AymanH1 -
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