Correct site internationalization strategy
-
Hi,
I'm working on the internationalization of a large website; the company wants to reach around 100 countries. I read this Google doc: https://support.google.com/webmasters/answer/182192?hl=en in order to design the strategy.
The strategy is the following:
For each market, I'll define a domain or subdomain with the next settings:
- Leave the mysitename.com for the biggest market in which it has been working for years, and define the geographic target in Google search console.
- Reserve the ccTLD domains for other markets
- In the markets where I'm not able to reserve the ccTLD domains, I'll use subdomains for the .com site, for example us.mysitename.com, and I'll define in Google search console the geographic target for this domain.
Each domain will only be in the preferred language of each country (but the user will be able to change the language via cookies).
The content will be similar in all markets of the same language, for example, in the .co.uk and in .us the texts will be the same, but the product selections will be specific for each market.
Each URL will link to the same link in other countries via direct link and also via hreflang. The point of this is that all the link relevance that any of them gets, will be transmitted to all other sites.
My questions are:
- Do you think that there are any possible problems with this strategy?
- Is it possible that I'll have problems with duplicate content? (like I said before, all domains will be assigned to a specific geographic target)
- Each site will have around 2.000.000 of URLs. Do you think that this could generate problems? It's possible that only primary and other important locations will have URLs with high quality external links and a decent TrustRank.
- Any other consideration or related experience with a similar process will be very appreciated as well.
Sorry for all these questions, but I want to be really sure with this plan, since the company's growth is linked to this internationalization process.
Thanks in advance!
-
Thanks so much Gianluca, I'll take all your ideas into account.
-
You wrote this, and I'd like you to explain it better:
Each domain will only be in the preferred language of each country (but the user will be able to change the language via cookies).
Why people - for instance Italians - should be even feeling the need to switch the language from Italian to English?
Sincerely, I find it useless.
What you should do is doing like Amazon does: let people visit whatever version they want. For instance (I live in Spain), when I am in the UK and I want to buy something in Amazon, I visit amazon.es. Even if Amazon knows that I'm in the UK, and advices me that maybe I may prefer to shop in the .co.uk website, it lets me stay, navigate and buy from the .es one.
You, then, say this:
Each URL will link to the same link in other countries via direct link and also via hreflang. The point of this is that all the link relevance that any of them gets, will be transmitted to all other sites.
This is not that true. At least, not literally. In fact, the PageRank any page of yours will earn via internal and external links will just partly be passed to the other country versions corresponding pages. This because the PageRank flows through every link present in a page, both internal and external links, and "evaporates" in case of nofollow links.
About your questions:
- Do you think that there are any possible problems with this strategy?
Overall it is correct (being the only doubt the "cookie" thing you talked about)
Is it possible that I'll have problems with duplicate content? (like I said before, all domains will be assigned to a specific geographic target)
If you use the hreflang, you should not have issues related to duplicated content.
Each site will have around 2.000.000 of URLs. Do you think that this could generate problems? It's possible that only primary and other important locations will have URLs with high quality external links and a decent TrustRank.
Having millions of URLs should not be a problem... if it was so sites like Etsy, Home Depot or Amazon would be suffering it, wouldn't they? When it comes to Big Sites, the most important thing is having a very solid architecture and work very well everything internal linking.
Any other consideration or related experience with a similar process will be very appreciated as well.
When implementing the hreflang annotations, try not using as many hreflang as country versions are present.
In other words, apart the home page (for obvious localized brand visibility and for avoiding having, for instance, the .com version outranking the local one for being more authoritative), in the internal pages use only the hreflang annotation in order to suggest Google what version to show in case of countries sharing the same language.
For instance, let's take that www.dominio.com/page-a is in English and targeting the USA, then the hreflang annotation would be only relative to all the others URLs of pages in English and targeting others English speaking countries, but you should not add the annotation for the spanish speaking versions or italian.
Why? Because the languages are different and such a strong signal that you don't need to explain to Google that it should present to Spanish speaking users in Spain the URL of the spanish country version instead of the American English one.
-
Thanks Dmitrii.
Any other opinions will be appreciated aswell, this process is really important for this webpage.
-
Hi there.
Everything seems good to me. Just make sure that you use proper hreflangs or canonicals for content, which can potentially be duplicate, make sure that you have proper/correct sitemap and there are no problems with crawlability and accessability.
Good luck
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
-
Setting up international site subdirectories in GSC as separate properties for better geotargeting?
My client has an international website with a subdirectory structure for each country and language version - eg. /en-US. At present, there is a single property set up for the domain in Google Search Console but there are currently various geotargeting issues I’m trying to correct with hreflang tags. My question is, is it still recommended practise and helpful to add each international subdirectory to Google Search Console as an individual property to help with correct language and region tagging? I know there used to be properly sets for this but haven’t found any up to date guidance on whether setting up all the different versions as their own properties might help with targeting. Many thanks in advance!
International SEO | | MMcCalden0 -
Redirect to 'default' or English (/en) version of site?
Hi Moz Community! I'm trying to work through a thorny internationalization issue with the 'default' and English versions of our site. We have an international set-up of: www.domain.com (in english) www.domain.com/en www.domain.com/en-gb www.domain.com/fr-fr www.domain.com/de-de and so on... All the canonicals and HREFLANGs are set up, except the English language version is giving me pause. If you visit www.domain.com, all of the internal links on that page (due to the current way our cms works) point to www.domain.com/en/ versions of the pages. Content is identical between the two versions. The canonical on, say, www.domain.com/en/products points to www.domain.com/products. Feels like we're pulling in two different directions with our internationalization signals. Links go one way, canonical goes another. Three options I can see: Remove the /en/ version of the site. 301 all the /en versions of pages to /. Update the hreflangs to point the EN language users to the / version. **Redirect the / version of the site to /en. **The reverse of the above. **Keep both the /en and the / versions, update the links on / version. **Make it so that visitors to the / version of the site follow links that don't take them to the /en site. It feels like the /en version of the site is redundant and potentially sending confusing signals to search engines (it's currently a bit of a toss-up as to which version of a page ranks). I'm leaning toward removing the /en version and redirecting to the / version. It would be a big step as currently - due to the internal linking - about 40% of our traffic goes through the /en path. Anything to be aware of? Any recommendations or advice would be much appreciated.
International SEO | | MaxSydenham0 -
Web Site Migration - Time to Google indexing
Soon we will do a website migration .com.br to .com/pt-br. Wi will do this migration when we have with lower traffic. Trying to follow Google Guidelines, applying the 301 redirect, sitemap etc... I would like to know, how long time the Google generally will use to transfering the relevance of .com.br to .com/pt-br/ using redirect 301?
International SEO | | mobic0 -
SEO Strategy for international website with similar content
Hello, If a company is in different countries and has same content in most of the countries does it hurt SEO? For Ex. fibaro.com is the website that I am researching and I have seen the indexed pages to be about 40,000 however there is not much content on it. On further inspection I noticed that for every country the sub folder is different. So for us it will be fibaro.com/us/motion-sensor and for Europe fibaro.com/en/motion-sensor. Now both of these pages have same content on it and the company is in 86 countries so imagine the amount of duplicate content it has. Does anybody have any ideas on what should be an ideal way to approach this? Thanks
International SEO | | Harveyspecter0 -
Multilingual Site with 2 Separate domains and hand-translated
I have 2 separate domains: .com & .jp
International SEO | | khi5
I am having a professional translator translate the English written material from .com. However, the .jp will have same pictures and videos that I have on the .com which means alt tags are in English and video titles are in English. I have some dynamic pages where I use Google Translate and those pages I place as "no index follow" to avoid duplicate issues and they are not very important pages for me any way. Question: since I am doing a proper translating - no machines involved - can I leave pages as is or should I include any format of these: ISO language codes
2) www.example/com/” /> Even though hand translated, the translation will probably be 85% similar to that if I used Google Translate. Will that potentially be seen as duplicate content or not at all since I have not used the Google Translate tool? I wonder from which angle Google analyses this. Thank you,0 -
Homepage URL for multi-language site
Hi, We are setting up a new site, and currently considering the URL and folder structure of the site. We will have 2-3 different language versions, and we have decided to use sub folders for this. My question is regarding the homepage URL. We want the English language site (en) to be the default one, from where you can then change the language. Should I have a folder for each of the language versions (as described below)? www.mydomain.com/en
International SEO | | Awaraman
(this would be the default page where everyone would always come if they type www.mydomain.com to webrowser) www,mydomain.com/ru www.mydomain.com/es Or, would it be better for SEO to have www.mydomain.com as the default URL where we would have the English version of the site, and then have two other folders (as below) where we would have the 2 other language versions: www,mydomain.com/ru www.mydomain.com/es Thank you in advance, BR Sam0 -
Multi Language / target market site
What is the best way to deal with multiple languages and multiple target markets? Is it better to use directories or sub-domains: English.domain.com Portuguese.domain.com Or Domain.com Domain.com/Portuguese Also should I use language meta tags to help the different language versions rank in different geographic areas e.g. Are there any examples of where this has been done well?
International SEO | | RodneyRiley0 -
Site structure for multi-lingual hotel website (subfolder names)
Hi there superMozers! I´ve read a quite a few questions about multi-lingual sites but none answered my doubt / idea, so here it is: I´m re-designing an old website for a hotel in 4 different languages which are all** hosted on the same .com domain** as follows: example.com/english/ for english example.com/espanol/ for **spanish ** example.com/francais/ for french example.com/portugues/ for portuguese While doing keyword search, I have noticed that many travel agencies separate geographical areas by folders, therefor an **agency pomoting beach hotels in South America **will have a structure as follows: travelagency.com/argentina-beach-hotels/ travelagency.com/peru-beach-hotels/ and they list hotels in each folder, therefor benefiting from those keywords to rank ahead of many independent hotels sites from those areas. What **I would like to **do -rather than just naming those folders with the traditional /en/ for english or /fr/ for french etc- is take advantage of this extra language subfolder to_´include´_ important keywords in the name of the subfolders in the following way (supposing the we have a beach hotel in Argentina): example.com/argentina-beach-hotel/ for english example.com/hotel-playa-argentina/ for **spanish ** example.com/hotel-plage-argentine/ for french example.com/hotel-praia-argentina/ for portuguese Note that the same keywords are used in the name of the folder, but translated into the language the subfolders are. In order to make things clear for the search engines I would specify the language in the html for each page. My doubt is whether google or other search engines may consider this as ´stuffing´ although most travel agencies do it in their site structure. Any Mozers have experience with this, any idea on how search engines may react, or if they could penalise the site? Thanks in advance!
International SEO | | underground0