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)?
-
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
-
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 -
How do you optimise a website for European traffic?
I have a design portfolio website here https://www.nicholsoncreative.com/ which uses a .com but is currently configured through the Search Console to appear in results for Google.co.uk. I am going to be restructuring the website and optimisation and I want to bring in more traffic/enquiries/business from around Europe. As there's no Google.eu, and as Google also serves results based on the searchers geographic location it would seem difficult to structure and optimise content so that results can be found across all of Europe. I assume simply switching to a .eu domain extension for my own website wouldn't solve the problem? I also assume that creating content in different languages would be a logical (if time consuming) option? Are there any other tried and trusted techniques that can be used to target traffic throughout Europe? I'd appreciate any advice.
International SEO | | JCN-SBWD0 -
International SEO setup issues canonical URL
My site is www.grocare.com for one region and in.grocare.com for another region. Both of them have the same content except the currency for particular regions. Someone told me that google will take the content as duplicate and not rank either. I have setup hreflang and targeted different regions for both in the search console. I read many article which say canonical urls need to be setup for international seo sites. But Im not sure how to setup canonical urls and whether they are the right way to go . i just don't want my content deranked. Now i have setup hreflang properly after asking the moz community itself. So im hoping to get some help with this query too. TIA
International SEO | | grocare0 -
Which Google does a .ie website get shown in?
Hi all, I am working on a .ie website and I was under the understanding that if you have a regional domain, like .ie you will limited to being shown in a search engine like google.ie When I go to International Targeting in Google SEarch Console it says the site is associated with: Ireland Am I limiting my ability to rank well in worldwide Google searches with this domain and if so, how can I counter this? Many thanks.
International SEO | | Bee1590 -
Auto-Redirecting Homepage on Multilingual Site
The website has an auto-redirecting homepage on a multilingual site. Here is some background: User visits the site for first time > sent to javascript age verification page with country of origin selector. If selects "France" then served French page (.com/fr-fr/). If selects any other country, then served English page (.com/en-int/). A cookie is set, and next time the user visits the site, they are automatically served the appropriate language URL. 1st Question: .com/ essentially does not exist. It is being redirected to .com/en-int/ as this is the default page. Should this be a 301 redirect since I want this to serve as the new homepage? 2nd Question:. In the multilingual sitemap, should I still set .com/ as the hreflang="x-default" even though the user is automatically redirected to a language directory? According to Google, as just released here: http://googlewebmastercentral.blogspot.com/2014/05/creating-right-homepage-for-your.html "automatically serve the appropriate HTML content to your users depending on their location and language settings. You will either do that by using server-side 302 redirects or by dynamically serving the right HTML content. Remember to use x-default rel-alternate-hreflang annotation on the homepage / generic page even if the latter is a redirect page that is not accessible directly for users." So, this is where I am not clear. If use a 302 redirect of .com/ to either .com/en-int/ or .com/fr-fr/, won't I then lose the inbound link value and DA/PA of .com/ if I just use a 302? Note: there is no .com/ at this moment. Any advice is appreciated. Thanks,Alex
International SEO | | Alex.Weintraub0 -
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 -
How to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
Dear all, what is the best way to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries? What must I add to my code of websites my .nl domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? What must I add to my code of websites my .be domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? Thanks in advance!
International SEO | | HMK-NL3 -
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