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
-
Good day team.. have problem with my website i lost all ranking and lost 10x times traffic in 1 day without reason...
Good day everybody. My website is www.evilrpm.com and ii have drop in rank and traffic in 1 day without reason... still fighting with that issue .. from that moment i starts to get the errors and in search console if i make testing pages .. after test they can show like warning or error page but in console its green.. i was check everything, and i think that problem in server.. because it happened when i write the truth about my experience with Shopify... this is extraordinary organization i feel like they from the starts was don't give me the way to grow... any idea what the problem? thanks for your support!
International SEO | | EvilTIGER0 -
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 -
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 -
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 -
How do I get a UK website to rank in Dubai?
We are trying to get a UK-based children's furniture website to rank in Dubai. We have had a couple of orders from wealthy expats in Dubai and it seems to be the correct target market. Does anyone have any specific knowledge of this area? We are promoting the same website as for the UK market. Also does anyone know any user behaviour stats on expatriates using search engines? Do they carry on using the version of Google they are used to, or do most change to the local version of Google? Thanks in advance
International SEO | | Wagada0 -
Best way to enter Canada, SEO-wise?
We are thinking of splitting our e-Commerce site into a Canadian site w/ localized content, a potential French version and for additional relevance w/ localized currency. What would be the best way to go about this if we were wanting to gain traction as soon as possible on the organic side? Split the domain into domain.com and domain.com/ca/ (subfolders) Split the domain into ca.domain.com and domain.com Or split the domain into domain.com & wirelessemporium.ca Also, what are some key best practices we need to keep in mind to avoid duplicate content issues, etc?
International SEO | | eugeneku0 -
Website Target in Europe
Hi, I am planning a site to target in Europe and I expect to translate my site into ten different languages namely English, French, Spanish, Italian, German, Russian, Greek, Portuguese, Dutch and Swedish. I am doing some study of this case in targeting different countries for SEO, most of the advise are the following: a. Build 10 different websites and target different geographical location in Google Webmaster b. Get 10 different country specific domains for 10 different websites I would like to hear any suggestion if there is anything better than this ? I had all the materials and translation ready but building 10 different websites or getting 10 different domains are very time consuming and costly. I would be appreciated if any one had any advise for me to make the website more management friendly. Thank you. Tom
International SEO | | Stevejobs20110 -
What’s the best way to convert ccTLD to global TLD?
We started out as a Canadian site targeting Canadian users. Now our site http://iCraft.ca has a lot of international buyers and sellers and .ca TLD doesn’t make sense anymore, as we are not performing well on Google.com We are doing a complete site redesign right now, which will address a lot of coding and content specific issues, but we suspect .ca domain will always hold us back in achieving good positions on Google.com. Since Google doesn’t allow ccTLDs to set geo-targeting, what are our options? a) Migrating to a brand new .com site and setting up 301 redirects for all links from iCraft.ca. Would we lose all rankings in this example and pretty much start building them from scratch? Or would PR be transferred page by page from one domain to another through 301 redirects? b) Setup a separate .com site with mirrored content to target global audience and keep .ca site to target Canada. Not sure if splitting PR for the same pages between 2 sites is a good idea. Also, how would you address duplicate content properly in our situation?
International SEO | | MarinaUX
In this video that I found here on forum http://www.youtube.com/watch?v=Ets7nHOV1Yo Matt Cutts says that it’s ok to have duplicate content on different ccTLDs, but he says - make sure you localize your content on those domains. What if you can’t? Most of the content on our site is meant for anyone, not just Canadian users. So, for the most part, we’d have exactly same content on .com site, as we have on .ca site. We could display prices in different currencies on product pages, but the rest of the content – blogs, forum etc. are not country-specific and can’t be localized easily. Also, it’s not clear from the video if all mirrored sites should sit on the same domain name for each country, like example.com and example.ca or is it ok to have example.com and icraft.ca? c) Is there a better option? Thanks for your help!0