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
-
'Mini' versions of our website for overseas markets. Does it matter?
Hi Guys. I work for an e-commerce site called TOAD Diaries, we make bespoke diaries and journals. In essence we allow people to design their own diary online, then we make it and send it. We have already sold some products to poeple in many European countries, (Malta, France, Germany) but we want to have a better online presence for those overseas markets. So….. We're want to do an overseas ‘test case’, to see if we can sell more products in Europe. Out thinking is this: We’ll buy a subdomain for a specific country. Then we’ll then build a ‘mini’ version of our site in the appropriate language. This be a country specific landing page with links to our ‘design your own diary’ pages, basket and checkout. All in the language we’re targeting. Question: Will having such a small number of pages in the targeted countries language effect out ability to rank well? It will be maybe 10 – 15 pages in size. Or is it much more to do with on page optimization and quality backlinks? i.e) the site's size has no impact. What other factors should we consider when trying to rank well in other European countries? Many thanks in advance.
International SEO | | isaac6630 -
Are Subdomains better or SubDirectories better for an international website ?
Can anyone explain why the structure of your website: yourbrand.com/es/category is better than es.yourbrand.com for multi language and multi country website.
International SEO | | Tushar_P0 -
Two versions of a website with different languages - Best way to do it?
I'm working on a website for a Swedish artist and her page is in Swedish, everything is in Swedish on the site, even though it's not a lot of text on the site. We would like to have the site in English too, or another version of the site in English on a separate domain, what's the best way to proceed from here? The domain name is a .se (swedish domain), would it be better to create a another domain and host the english version of the site on a .com domain? Or will we bump into problems with duplicate content if we create a replica of the swedish site in english. We're using wordpress and I know that there's translation plugins out there, is that a good option? I'm a bit clueless on how to proceed and would love some help or guidance here.
International SEO | | Fisken0 -
What are the best practices for translation of city/state names for international SEO? (ie. New York in English vs. Nueva York in Spanish)
I'm working on international SEO / translation of a global travel site. While we have a global keyword research and translation strategy in process for each market they serve, I've run into a unique question. Overall, we are translating (and localizing) content for each market but aren't sure what to do with location names. Each country/state has cities and locations that have their own dedicated pages. I see three options for these location names (when titling a page and writing content): keep them in English, translate the names in the market languages, or use a combination of the two. The challenge with altering the location names to the market languages is that they are truly not known by those names. Though there are some instances where it may make sense…for instance **New York **in Spanish would be "Nueva York" with **‘**Nueva' being the Spanish translation of ‘new’. There are other instances, where no translation exists. If you’ve had a similar experience I'd love to hear your approach/recommendation.
International SEO | | JonClark150 -
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 -
What is the best NAP format to use?
Canadian client with a suite number in a shopping center. Does it matter if the NAP is the way it's displayed on Google Maps? Canada Post (or in the US, USPS)? Or does it only matter that all the citations are as similar as possible to one another? Canada Post says: 400-3033 IMMEL ST
International SEO | | rayvensoft
ABBOTSFORD BC V2S 6S2 But if I look that up on maps.google.com, it defaults to: 3033 Immel St Abbotsford, BC V2S 4L3, CanadaAnd the client does not appear in the list of about 20+ businesses at this address.Which should I use for Places (and I assume any other citation)?1 -
How well does Google's crawlers understand foreign websites?
I speak 5 languages and therefore have the opportunity to do on-page SEO and content writing for 5 different cultures. This question to me has much to do with the way Google translator works. It doesn't, trust me! Which then makes me wonder how the web crawlers, which are designed with English in mind, can fairly and equally attribute the same ranking points to a foreign website. Since Google seems to use sematic search technology I'm wondering if foreign sites have it easier or not. Any ideas?
International SEO | | MassivePrime0 -
Best URL for international domain
Hello SEomozers We have a site with this structure: -www.xyz.com US customers, limited content in12 languages, -global.xyz.com for International customers, full content in 12 languages. The global site is the hub for the rest of the world. We are creating a new site from scratch and want to consolidate the two domains in one by using subfolders, such as: www.xyz.com for USA, www.wyz.com/jp for US customers reading in japanese and www.xyz.com/int-jp for customers from Japan (international - will set geo location with webmastertool) What do you think would be the best naming convention for the international?
International SEO | | FXDD
www.xyz.com/int-jp or
www.xyz.com/eu-jp or
www.xyz.com/eu/jp or
www.xyz.com/ ...any other suggestions?0