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
-
Best way to interlink 25 different language versions of a website?
I have a website which has 25 different language versions on 16 different domains. Hreflan are setup to point to different language versions. In the footer we have deeplinks to the 25 language versions. Site is not spammy but in small niche and many language versions have very few other external links. For some time this site had lost rankings for reasons that are unclear till now. I see that large international sites such as booking.com, tripadvisor, apple all use different approaches to interlink their language versions. Interestingly Tripadvisor is nowadays loading the links to their other language versions dynamically only upon click so that these links do not show up in source code, deviating from their former implementation of static deeplinks to all language versions. Matt Cutts mentioned back in 2013 “If you have 50 different sites, I wouldn’t link to all 50 sites down in the footer of your website, because that can start to look pretty spammy to users. Instead you might just link to no more than three or four or five down in the footer, that sort of thing, or have a link to a global page, and the global page can talk about all the different verions and country versions of your website.” But in their webmaster guidelines google recommends: "Consider cross-linking each language version of a page. That way, a French user who lands on the German version of your page can get to the right language version with a single click." I assume for SEO anyway these links have no value, but for user experience it would certainly be better to provide somewhere deeplinks to other language versions. Also the fact that language versions are on different domains and have few external backlinks may increase a bit the risk in our case. I guess in doubt I would prefer to be safe and load deeplinks only upon click same as tripadvisor. Any thoughts/suggestions on best interlinking in our specific case?
International SEO | | lcourse0 -
Is it advisable to show additionally also English ciity names of American cities in website versions of non-western languages such as Chinese, Japanese etc?
To my understanding in many Asian languages city names are transcribed as they sound and this can cause confusion especially in the case of lesser known American city names. So I was planning to put in our international website versions (Chinese, Japanese, Korean etc. ) the English name in brackets after the translated city name in meta title and H1.
International SEO | | lcourse
However when I checked Tripadvisor and Booking.com I noticed that they do not show the English city name anywhere on their Asian language versions. Any thoughts?
Would you recommend to put the English city name in brackets after the translated city name or may it rather hurt our ranking and traffic?0 -
What are the SEO implications of having a website hosted in Singapore (as a subdomain of the global website) when the website is targeting the UK audience?
What are the SEO implications of having a website hosted in Singapore (as a subdomain of the global website) when the website is targeting the UK audience? Will it be hard to get it to rank? Will there be problems with search console?
International SEO | | ToniFarrington-Allthingsweb0 -
Website Domains, Geographical targeting and Duplicate Content
My colleagues in Holland have 2 websites. I've copied and pasted their question - my comments are at the bottom "www.ancoferwaldram.nl with NL, EN and FR language www.ancoferwaldram.com with only EN language The EN versions Google sees as “duplicate content” so we have to get rid of that. I think we better use 1 website: www.ancoferwaldram.com with NL, EN, FR and maybe other languages and deactivate www.ancoferwaldram.nl Or keep the www.ancoferwaldram.nl with only the NL language? Or keep the www.ancoferwaldram.nl with direct links to www.ancoferwaldram.com and no content?" The focus is to get the site to rank in Non-eu countries for export. So given the .nl has higher DA (though only about 15) would it be better to have seperate .fr, .be, .com sites for specific languages and geo targeting. Or would it be better to keep everything on the same site? If so which domain? i assume that the duplicate content can be resolved by stating which is the canonical version, once the domain strategy is resolved welcome any thoughts here. 🙂
International SEO | | Zippy-Bungle0 -
For a website in portuguese what would you use? pt.domain.com, br.domain.com or domain.com.br
Hello We are a company with a website in several languages, one of them is portuguese. Our market is 2 times bigger in Brazil than in Portugal, but obviously Brazil has more potential in the future. In domain.com we have our main site in English. What would you use? pt.domain.com, br.domain.com or domain.com.br? In the first case, it means just portuguese, in the second Brazil but it is not geolocalized, and in the third, you are almost ignoring Portugal users... Duplicating content, doesn't seem to make sense... The content is basically international, so it is just the language that matters. Any help will be very much appreciated.
International SEO | | forex-websites0 -
International websites : hreflang
Hi, i'm looking for good examples with 'href lang' tag (rel="alternate" hreflang="x") Have you examples of websites with this tag? Thanks D.
International SEO | | android_lyon0 -
Rel alternate use for multi regional website with english language and same content
I have a website targeting multi language and multi regional users. For example, my main site is www.abcd.com which is in English and targeting US. I have the same content in English which is targeting UK and India with www.uk.abcd.com and www.india.abcd.com. I want to avoid content duplication and help search engines to show the right pages on the country level searches. I have researched a bit and have come to conclusion of using re alternate tag. Can someone help me with how to place the codes for the same. Many thanks Mozers!
International SEO | | HiteshBharucha0 -
Website optimization - highly competitive keyword in german
Hey guys, this is the website: www.mediavideoconverter.de We need to optimize this website for a bunch of keywords such as: VIDEO CONVERTER in google.de which is highly competitive and some others for ipad, iphone software's. Can someone give me a advise where should I start? I know the design isn't great, unfortunately in this part there is nothing I can do about it. Thanks in advance 😃
International SEO | | augustos0