Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
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 ToolsChat with the community about the Moz tools. 
- 
		
		SEO TacticsDiscuss the SEO process with fellow marketers 
- 
		
		CommunityDiscuss industry events, jobs, and news! 
- 
		
		Digital MarketingChat about tactics outside of SEO 
- 
		
		Research & TrendsDive into research and trends in the search industry. 
- 
		
		SupportConnect on product support and feature requests. 
Related Questions
- 
		
		
		
		
		
		Problem to get multilingual posts indexed on Google
 Last year on June I decided to make my site multi-lingual. The domain is: https://www.dailyblogprofits.com/ The main language English and I added Portuguese and a few posts on Spanish. What happened since then? I started losing traffic from Google and posts on Portuguese are not being indexed. I use WPML plugin to make it multi-lingual and I had Yoast installed. This week I uninstalled Yoast and when I type on google "site:site:dailyblogprofits.com/pt-br" I started seeing Google indexing images, but still not the missing posts. I have around 145 posts on Portuguese, but on Search Console it show only 57 hreflang tags. Any idea what is the problem? I'm willing to pay for an SEO Expert to resolve this problem to me. International SEO | | Cleber0090
- 
		
		
		
		
		
		How to Localise per Region (Europe, America, APAC, EMEI) and not per country as best SEO practise?
 Hi SEO expertises! I am currently working with a client that initially have an English website targeting UK users but want to expand their market into four new regions (Europe, America, APAC and EMEI) keeping English as a main language. I would like to request your help here as I told the client ISO location and hreflang it will be just possible per language and they must need to localise each English region with local keywords, however I would like to double check if it will be any way (Sitemap, Hreflang) we can tell Google we are targeting per region and not per country? Thanks a lot! International SEO | | Atalig20
- 
		
		
		
		
		
		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
- 
		
		
		
		
		
		Country and Language Specific URL Paths
 Wanted to ask everyone a questions: So our company is going to be doing a website that is going to be full of videos. The url path will be country.domain.com/language/slug/content-id. We redirect the user when they go to the different country. So if you're in spain on a train to france your URL will change from es.domain.com/es/slug/content-id to fr.domain.com/es/slug/content-id. Each country can listen to each video in all languages. My question is with hreflang tags and canonicals. Aside from targeting users in a certain country via Google Search Console, how do I eliminate duplication and tell Google which I'd like to show up via which country. In spain I would like es.domain.com/es/slug/content-id to show in Google and would have hreflang tags on each of the es.domain pages but what about fr.domain.com/es/slug/content-id since it would show the same content? I can't canonical to one of them since I need them to show in their respective country. How do I show the difference in language and country without showing duplication? International SEO | | mattdinbrooklyn0
- 
		
		
		
		
		
		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
- 
		
		
		
		
		
		International SEO Subfolders / user journey etc
 Hi According to all the resources i can find on Moz and elsewhere re int seo, say in the context of having duplicate versions of US & UK site, its best to have subfolders i.e. domain.com/en-gb/ & domain.com/en-us/ however when it comes to the user journey and promoting web address seems a bit weird to say visit us at: domain.com/en-us/ !? And what happens if someone just enters in domain.com from the US or UK ? My client wants to use an IP sniffer but i've read thats bad practice and should employ above style country/language code instead, but i'm confused about both the user journey and experience in the case of multiple sub folders. Any advice much appreciated ? Cheers Dan International SEO | | Dan-Lawrence0
- 
		
		
		
		
		
		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
 
			
		 
			
		 
			
		 
			
		 
			
		 
					
				 
					
				 
					
				 
					
				 
					
				 
					
				 
					
				