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
(this would be the default page where everyone would always come if they type www.mydomain.com to webrowser)www,mydomain.com/ru
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
Thank you in advance,
BR
Sam
-
I mean that www.site.com should be accessible as is (returning a 200 status) and not 301 redirect users to a page like www.site.com/en.
So the home page would be www.site.com and the rest will be www.site.com/en/page1, www.site.com/en/page2 etc. This might cause problems to implement with some CMS' but try if it can be done that way.
-
Thanks. Could you clarify more in detail what you mean by the below, if I use www.mydomain.com/en
Make sure the home page is actually www.mydomain.com (and not www.mydomain.com/en). Not using the root domain means throwing away backlinks and thereby site authority, so make sure it's available whether you use /en on the rest of the site or not.
-
Sam,
There is alos this whiteboard Friday that touches on the pros and cons of your options here: http://moz.com/blog/international-seo-where-to-host-and-how-to-target-whiteboard-friday
-
Hi Sam
IMO SEO is not the most crucial factor for this question. Yes, you have some slight benefits by using www.mydomain.com without /en for english. On the other hand, think usability and user interaction: Users who recognise the language patterns such as /ru and /es in the URL might want to reproduce the same thing for /en.
I think those are the two points of view that should be taken into account, but both are not that central and either way is okay. Some standard CMS's might not allow the special case for one language easily and you might have to use /en in order to be consistent. But personally, I would use www.mydomain.com without /en if the majority of your audience is english. That makes the site a little little bit "flatter" with one less subfolder in the URL.
That being said, one thing I absolutely recommend: Make sure the home page is actually www.mydomain.com (and not www.mydomain.com/en). Not using the root domain means throwing away backlinks and thereby site authority, so make sure it's available whether you use /en on the rest of the site or not.
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
-
In the U.S., how can I stop the European version of my site from outranking the U.S. version?
I've got a site with two versions – a U.S. version and a European version. Users are directed to the appropriate version through a landing page that asks where they're located; both sites are on the same domain, except one is .com/us and the other is .com/eu. My issue is that for some keywords, the European version is outranking the U.S. version in Google's U.S. SERPs. Not only that, but when Google displays sitelinks in the U.S. SERPs, it's a combination of pages on the European site and the U.S. site. Does anyone know how I can stop the European site from outranking the U.S. site in the U.S.? Or how I can get Google to only display sitelinks for pages on the U.S. site in the U.S. SERPs? Thanks in advance for any light you can shed on this topic!
International SEO | | matt-145670 -
Different urls for the homepage on an international website
Hi! I was wondering what would be the best strategy to solve duplicated content generated by the homepage and its differents URLS This is an international website. Now it only has one language working: Spanish, but the url structure is already ready to work with the language approach So we have now www.brand.com -> Spanish Homepage (canonical www.brand.com/es)
International SEO | | teconsite
www.brand.com/es -> Spanish Homepage (canonical www.brand.com/es)
www.brand.com/index.php -> Spanish Homepage (canonical www.brand.com/es) I would like to know if this is the correct approach of if we should add 301 redirects instead of canonical. Let's image that they want to active the /en language, so they will have www.brand.com
www.brand.com/index.php
www.brand.com/es
www.brand.com/en now what? I image they have to use hreflang, but I am a little lost with how this should work. 301? canonical? hreflang? Could you help me? Thank you! Victoria0 -
Can we use similar images on multi regional websites?
I have couple of questions regarding multi regional websites. Right now, We're working on http://www.canvaschamp.com/ and planning to design new website for Australia region. I have read Google's official guidelines regarding duplicate content on following URL. https://support.google.com/webmasters/answer/182192?hl=en Now, I have biggest question regarding images and videos. We're going to use all photo gallery images on Australia website. http://www.canvaschamp.com/canvas-prints We may use similar name, title tag, meta description for all images. So, Will it work for us? I want to save my website from duplicate content penalty. I am looking forward for any additional help which may help me to perform better on different region with similar images.
International SEO | | CommercePundit0 -
Multinational URLs
Hi I'm wondering if the following URL structure using subdirectories would be alright to use on a multinational site. I have local products only in the local language and english. I plan to use: /uk/ - UK product in English (geo target in GWT to UK, href lang="en") /fr/ - French product in French (would geo target this in GWT to France, and hreflang="fr-FR") /fr-en/ - French product in English (no geo-targeting, hreflang ="en") /de/ - German product in German (would geo target this in GWT to Germany, and hreflang="de-DE") /de-en/ - German product in English (no geo-targeting, hreflang ="en") /at-de/ - Austrian product in German (would geo target this in GWT to Austria, and hreflang="at-DE") /at-en/ - Austrian product in English (no geo-targeting, hreflang ="en") Does the name of the subfolder matter? I've tried to keep the URL's shorter, so german users in Germany would get just /de/ rather than /de-de/, and have made the english version of the content the more ugly URL as it's used much, much less. The URL structures aren't really consistent here (ie. uk and fr-en are for english content, but are different in URL format) but I'm wondering if this is an issue, or if the above would be fine. Thanks!
International SEO | | pikka0 -
URL Structure for Multilingual Site With Two Major Locations
We're working on a hotel site that has two major locations. Locations currently live in separate domains. The sites target users from around the world and offer content in multiple languages. The client is looking into migrating all content into one domain and creating sub-folders for each location. The sites are strong in organic search, but they want to expand the keyword portfolio to broader keywords regarding activities, which they also market on their sites. The goal is to scale their domain authority as they have a really strong brand. The question is which would be a preferred URL structure in case content is finally migrated into one domain? - (we have doubts about were the lang folder should be placed as each location has different amenities and services). Here is what we had in mind: domain.com – this is the homepage domain.com/location-1 – to target English visitors domain.com/location-2 – to target English visitors domain.com/es/location-1 – to target Spanish visitors domain.com/es/location-2 – to target Spanish visitors
International SEO | | burnseo0 -
My site is not showing on google.com ?
My website is not showing at all on google.com searches under search terms. It is showing if i search for my domain (xyz.com) but not by keywords. Searching by keywords and search terms shows my website on yahoo , bing and non US oogle as google.co.uk or google.com.pk on first page. Would appreciate any help in trying to understand why this is happening? The website is medicare.md. if you search for term "medicare doctors PG county maryland" it is #1 in bing and yahoo but not even showing on google.com first TEN pages, although not banned. Interestingly if you do that search on google.co.pk it is #4. Quite Puzzuling !! Would appreciate any help or advice . Sherif Hassan
International SEO | | sherohass0 -
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 -
Multilingual site - separate domain or all under the same umbrella
this has been asked before with not clear winner. I am trying to sum up pros and cons of doing a multilingual site and sharing the same domain for all languages or breaking it into dedicated subdomains e.g. as an example lets assume we are talking about a french property portal with an english version as well. Assume most of the current incoming links and traffic is from France. A) www.french-name.fr/fr/pageX for the french version www.english-name.com/en/pageX for the english version B) www.french-name.fr/fr/ for the french name (as is) www.french-name.fr/en for the english version the client currently follows approach A but is thinking to move towards B we see the following pros and cons for B take advantage of the french-name.fr domain strength and incoming links scalable: can add more languages without registering and building SE position for each one individually potential issues with duplicate content as we are not able to geotarget differenly on web master tools of google potential dilution of each page's strength as we will now have much more pages under the same domain (double the pages basically) - is this a valid concern? usability/marketing concerns as the name of the site is not in english (but then people looking for a house in France would be at least not completely alien to it) what are your thoughts on this? thanks in advance
International SEO | | seo-cat0
