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
-
Website relaunched: Both old pages and new pages indexed
Hi all, We have recently made major changes to our website and relaunched it. We have changed URLs of some pages. We have redirected old URLs to new before taking website live. When I check even after one week, still the same old and new pages also indexed at Google. I wonder why still old pages cache is there with Google. Please share your ideas on this. Thanks
International SEO | | vtmoz0 -
What's the best strategy for acquisition?
Hi All, Recently acquired a competitor company. This acquired company is small in size but is the exclusive UK distributor for a gigantic Swedish company. This is the way the current domain structure is divided. swedish-supplier.se (Not owned by us - swedish supplier ) Swedish-supplier.co.uk (owned by us, operating as the swedish supplier in the UK) New-acquired-company.com (owned by us) The supplier doesn't want us to have two websites as they keep getting confused customers. Because of this we have agreed to remove www.swedish-suplier.co.uk and solely sell the product at www.new-aqquired-company.com. However, because of the sheer size of the Swedish supplier, a lot of traffic comes through to swedish-supplier.co.uk. My question is, how can we work together with the supplier to remove this domain and still maintain a good amount of UK traffic? Should we point swedish-supplier.co.uk back to the suppliers original translated web site and have them pass enquiries onto us or should we point it to our website? & What's the best way to go about it? Thanks, Danny
International SEO | | DannyHoodless0 -
How to best set up international XML site map?
Hi everyone, I've been searching about a problem, but haven't been able to find an answer. We would like to generate a XML site map for an international web shop. This shop has one domain for Dutch visitors (.nl) and another domain for visitors of other countries (Germany, France, Belgium etc.) (.com). The website on the 2 domains looks the same, has the same template and same pages, but as it is targeted to other countries, the pages are in different languages and the urls are also in different languages (see example below for a category bags). Example Netherlands:
International SEO | | DocdataCommerce
Dutch domain: www.client.nl
Example Dutch bags category page: www.client.nl/tassen Example France:
International domain: www.client.com
Example French bags category page: www.client.com/sacs When a visitor is on the Dutch domain (.nl) which shows the Dutch content, he can switch country to for example France in the country switch and then gets redirected to the other, international .com domain. Also the other way round. Now we want to generate a XML sitemap for these 2 domains. As it is the same site, but on 2 domains, development wants to make 1 sitemap, where we take the Dutch version with Dutch domain as basis and in the alternates we specify the other language versions on the other domain (see example below). <loc>http://www.client.nl/tassen</loc>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="http://www.client.com/sacs"
/></xhtml:link<br> Is this the best way to do this? Or would we need to make 2 site maps, as it are 2 domains?0 -
How To Rank A UK Website On Google.com (US)
Hi, I've done some research on this but couldn't find any definitive answer I can trust! We have a client who resides in the UK. They have '.com' domain, hosted on a UK server, using UK spelling. Their business objective for this year is to expand in the USA, including the opening of a warehouse over there. They are wanting us to rank their website on both Google.co.uk and Google.com (North America); besides changing the geolocation settings in GWT's, and building links from .com websites is there anything else we can do to increase their visibility on Google.com? Many thanks in advance, appreciated!
International SEO | | Webpresence
Lee.0 -
Multinational URLs
Hi I'm wondering if the following URL structure using subdirectories would be alright to use on a multinational site. I have local products only in the local language and english. I plan to use: /uk/ - UK product in English (geo target in GWT to UK, href lang="en") /fr/ - French product in French (would geo target this in GWT to France, and hreflang="fr-FR") /fr-en/ - French product in English (no geo-targeting, hreflang ="en") /de/ - German product in German (would geo target this in GWT to Germany, and hreflang="de-DE") /de-en/ - German product in English (no geo-targeting, hreflang ="en") /at-de/ - Austrian product in German (would geo target this in GWT to Austria, and hreflang="at-DE") /at-en/ - Austrian product in English (no geo-targeting, hreflang ="en") Does the name of the subfolder matter? I've tried to keep the URL's shorter, so german users in Germany would get just /de/ rather than /de-de/, and have made the english version of the content the more ugly URL as it's used much, much less. The URL structures aren't really consistent here (ie. uk and fr-en are for english content, but are different in URL format) but I'm wondering if this is an issue, or if the above would be fine. Thanks!
International SEO | | pikka0 -
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 -
Alternate tag. Anybody had success getting English websites only with localized currency served with alternate tag?
I have an English website with USD prices and US phone.
International SEO | | lcourse
Via currency dropdown visitors in Ireland can choose EUR as currency, visitors from Denmark Danish crown etc and via GEO IP I also serve local contact phone numbers. So I though it made sense to define this with the alternate tags, but now after several months google still does not pickup these pages in local searches. Did anybody have success with getting a website just with currency parameter ranked locally using the alternate tag? Does it help to have also static links (not only dropdown links) to currency versions on the page? Any other thing that could help to have google pick these up? Below my code sample:0 -
Am I doing this right? Same website, content and similar domains.
I have 5 sites with the same exact content. I have a separate webmastertool for each one and I have targeted them to each country on WebMastertools? Iam I missing something or did I do it right.Thankswww.abc.com (USA)www.abc.com.ar (argentina)www.abc.com.mx (mexico)www.abc.com.co (colombia)
International SEO | | M_80