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
-
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 -
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 -
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 -
Mixed English and Arabic URLs
I'm currently working with a global brand who need localisation in each of their territories. They're operating on a single .com domain name, with different language versions in separate directories. Example:
International SEO | | Guyboz
domain.com/en/
domain.com/fr/
domain.com/ar/ We're using ahreflang tags to make sure Google shows the correct language version for each region. Now onto my question... As the domain is a .com with an English company name, when it comes to the Arabic version of the website, will having a completely mixed language URL like this be detrimental to the site's performance in searches from the middle east? Currently we're coming up with URLs like the following: domain.com/blog/عنوان بلوق عربية طويلة حقا على شيء مثير جدا للاهتمام Is this a bad thing?0 -
URL Structure - Homepage, Country and State Pages
Hello, I am creating a website (or websites if best format) that will have state-specific boating license courses for every state in the US, Canada and Australia. I would like the content to be available on the website in English, French and Spanish. I want to be the global leader in providing boat test courses. For the (1) homepage, (2) country pages, and (3) state pages, what is best SEO format I should use for:
International SEO | | Monologix
(a) URL structure
(b) "href lang" code
(c) rel canonical code
(d) will meta content with non-English pages need to also be in the non-English language of that page? Also, what server company do you recommend I host my website with? I am a non-programmer and learning SEO, so any and all help will be greatly appreciated! Thank you very much in advance!!!0 -
For a website in portuguese what would you use? pt.domain.com, br.domain.com or domain.com.br
Hello We are a company with a website in several languages, one of them is portuguese. Our market is 2 times bigger in Brazil than in Portugal, but obviously Brazil has more potential in the future. In domain.com we have our main site in English. What would you use? pt.domain.com, br.domain.com or domain.com.br? In the first case, it means just portuguese, in the second Brazil but it is not geolocalized, and in the third, you are almost ignoring Portugal users... Duplicating content, doesn't seem to make sense... The content is basically international, so it is just the language that matters. Any help will be very much appreciated.
International SEO | | forex-websites0 -
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