Best URL structure for Multinational/Multilingual websites
-
Hi
I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.)
As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product?
To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format:
hotelsite.com/en/hotel-name (for english) and
hotelsite.com/se/hotel-name (for swedish content of that same product)
and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc.
Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name?
Any thoughts on best practice would be greatly appreciated.
-
I have a multilingual & multi-country website : http://www.asaan.com
It runs on a subdomain structure, which I want to convert to subdirectory, for SEO benefits. So, ae.asaan.com would become http://www.asaan.com/ae/
However, I need to understand how best to integrate the language code into the new structure.
So, should it be http://www.asaan.com/ae/en/ (for English for UAE) OR
http://www.asaan.com/ae-en/ (for English in UAE)?
As UAE would also have Arabic, its important for me to understand the benefits of such a structure from SEO perspective
Please advice -
hello,
Nice article. I have a questions:
If you have a multi lang site with Subdirectory:
would you use Subdirectory:
domain.com for the english version or its bertetr to use straight a redirect from domain.com to .com/en/ ? -
Thanks Aleyda, this is great!
I'm wondering, if on a TLD, is it necessary to have both the country code and language in the URL? Or would it be possible to just use language and use href lang in the code to specify the where it's relevant?
I do have each venue in the local language AND in english (though I would prefer both of these languages aimed at the local country - this is because nobody outside the countries search for these venues, but many do also search in english rather than just their local lang)
I have:
- .com/se/sv/venue-name (Venue in Sweden, in Swedish)
- .com/se/en/venue-name (Venue in Sweden, in English)
Or is it better to just use language?
- .com/se-sv/venue-name
- (not sure how to do the english version here)
Would country code be more relevant to use in this case?
Thanks!
-
Hi there!
To target countries the best way to go is with ccTLDs and if you don't have the ccTLDs then it is with subdirectories within a generic TLD, so you'll have:
- For the US: yourbrand.com/category-a/
- For the UK: yourbrand.com/en-gb/category-a/
- For Spain: yourbrand.com/es-es/categoria-a/
- For Mexico: yourbrand.com/es-mx/categoria-a/
Please keep in mind that the "name" of the directory here it's not important but is just to keep it usable and short and follow the language naming conventions. What it is important is that each country has its own consistent directory structure.
It's fundamental that the look and feel as well as all of the elements of each ones of your different country versions (in the different directories) are localized to target their audience: From the translation of the URLs, titles, descriptions, headings, text, etc. to the appropriate language, using the right currency, etc.
In order to geolocate each directory and inform Google that they're targeting different countries you can do it through Google Webmaster Tools with the "Geolocate" option by registering each directory independently and targeting it.
Additionally, if you have many country versions with the same language (US & UK or Spain & Mexico), in order to avoid having content duplication issues, informing Google that each one of these pages are in these languages but targeting different audiences you should use the hreflang tags as specified here.
By doing this you'll make sure you'll have the base set to target your different country search audiences with Google without running into content duplication issues.
For more information about how to establish and identify the best strategy to follow take a look at this post I wrote some time ago about International SEO strategy.
If you have any question just let me know!
-
Thanks for your reply, Stephen.
Is www.example.com/se/en/hotel-name the shortest, best possible way to do this?
So for the swedish language version it would be www.example.com/se/se/hotel-name (to keep the format consistent)?
-
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
-
Using same URL for both "en" and "en-us" hreflang tags
Hi,I have a question. Is it okay if I use the same URL for both "en" and "en-us" hreflang tags? For example, for my en-us page: Is this okay with Google? What are your thoughts on this?
International SEO | | Avid_Demand0 -
Is there a Risk Around Creating a Website for Each Country in The World?
Is there a risk around creating a website for each country in the world with similar to identical content depending on the language? We need to serve prices and the local currencies and be compliant with regulations. We're planning to use rel=canonical and HREFLANG tags to help with consolidation and GEO-targeting.
International SEO | | ari_seo0 -
International SEO Sub folder Structure
Hi Could anyone offer some advice on the best way to structure sub folders on a website that we are launching worldwide. We are a UK based business and currently run a UK site on www.website.com and we are planning on launching into Europe using a sub folder structure. We will use /de, /fr, /es for the new countries that are coming on board but the question is should the UK site url be: www.website.com or www.website.com/uk As have an established web presence in the UK I'm thinking it should remain as www.wewbsite.com but are there any advantages / disadvantages to changing it to .com/uk Many Thanks
International SEO | | SmiffysUK0 -
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 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 -
When is it best to use a ccTLD or TLD?
I understand that the relative importance of domain extensions - .com is better than .biz, etc. - is a bit of a myth. I also believe that using a ccTLD is likely to affect rankings for that site outwith that country. But, is the opposite true? Will giving a site a ccTLD help improve its SEO in that country? If you have a global organisation, is it better to establish a series of country specific sites - ccTLD - or to purchase the country specific domains and point them to the.com (if only to stop cyber-squatting)? What if the company wanted to establish regional microsites that feature content about products only available within that region? Many thanks, Iain
International SEO | | iain0 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1 -
International (foreign language) URL's best practices
I'm curious if there is a benefit or best practice with regards to using the localized language on international sites (with specific ccTLDs). For example, should my french site (site.fr) use the french language as keywords within the URLs or should they be in english? e.g. www.site.fr/nourriture vs. www.site.fr/food Is that considered best practice for SEO (or just for brand perception those markets?). Is there a tangible loss in SEO if we do not use the correct language for those URLs and just stick with English around the world? I recall seeing a Matt Cutts video on the topic and he said that google does support i18n URL's but other SE's might not support them as gracefully but he didn't come down with a hard recommendation to go with i18n URL's or just English. Would love a strong ruling in favor one direction based on best practices.
International SEO | | mongillo0