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
-
How should I handle hreflang tags if it's the same language in all targeting countries?
My company is creating an international version of our site at international.example.com. We are located in the US with our main site at www.example.com targeting US & Canada but offering slightly different products elsewhere internationally. Ideally, we would have hreflang tags for different versions in different languages, however, it's going to be an almost duplicate site besides a few different SKUs. All language and content on the site is going to be in English. Again, the only content changing is slightly different SKUs, they are almost identical sites. The subdomain is our only option right now. Should we implement hreflang tags even if both languages are English and only some of the content is different? Or will having just canonicals be fine? How should we handle this? Would it make sense to use hreflang this way and include it on both versions? I believe this would be signaling for US & Canda visitors to visit our main site and all other users go to the international site. Am I thinking this correctly or should we be doing this a different way?
International SEO | | tcope250 -
For My International Sites only Homepage in other Language rest Pages are in English. Hreflang required here?
Hello All, For my ecommerce site at my homepage there is an Language option of 9 different countries. My main site - abcd.co.uk and other sites are like this se.abcd.co.uk, fr.abcd.co.uk, es.abcd.co.uk etc From my main site if user clicks on fr.abcd.co.uk then France site will open but when he click on any link it will redirect to my UK site. On France site homepage if user hover the cursor then links are visible of UK site only. My query is ;- Do it required here to implement hreflang? As only homepage is in different language? Do it anything wrong in google point of view? Thanks!
International SEO | | wright3350 -
Which will rank higher: Non-mobile friendly site in native language vs. mobile friendly global site in English?
Hi, we are currently implementing a mobile site, e.g. m.company.com. The global mobile site will only be available in English. We have local subsites of the desktop site, e.g. company.com/fr. The local subsites are not mobile friendly. If a user does a search for a brand term in France, **which site will rank higher in SERPs? **If it will be the global site, is there anything we can do (other than making them mobile friendly) to make the local sites rank higher? Would it be the mobile-friendly site, even though it is only in English, because the local site would be penalized for not being mobile friendly? Or would it be the local site, because Google will give priority to the fact that it's in French, which matches the language of the person searching?
International SEO | | jennifer.new0 -
Block access to site from everywhere but north america
I have a site that is being attacked very hard by bots, malware, etc. Most of it seems to be originating from Asia and Eastern Europe so I want to block off access to the site to everybody but people in North America. We do not ship out of the country anyways so it really does not need to be seen by people around the world. How can I set this up?
International SEO | | Atomicx0 -
Sub-domains or sub-directories for country-specific versions of the site?
What approach do you think would be better from an SEO perspective when creating country-targeted versions for an eCommerce site (all in the same language with slight regional changes) - sub-domains or sub-directories? Is any of the approaches more cost effective, web development-wise? I know this topic's been under much debate and I would really like to hear your opinion. Many thanks!
International SEO | | ramarketing0 -
Multi country targeting for listing site, ccTLD, sub domain or .com/folder?
Hi I know this has been covered in a few questions but seen nothing recent that may take into account changes google may have applied. We would like to target multiple english speaking counties with a new project and I'm a little unsure as to whether ccTLD, subdomain or subfolders are the best way to publish country specific information. Can anyone shed some light on this?
International SEO | | Mulith0 -
What is the best SEO site structure for multi country targeting?
Hi There, We are an online retailer with four (and soon to be five) distinct geographic target markets (we have physical operations in both the UK and New Zealand). We currently target these markets like this: United Kingdom (www.natureshop.co.uk) New Zealand (www.natureshop.co.nz) Australia (www.natureshop.com/au) - using a google web master tools geo targeted folder United States (www.natureshop.com) - using google web master tools geo targeted domain Germany (www.natureshop.de) - in german and yet to be launched as full site We have various issues we want to address. The key one is this: our www.natureshop.co.uk website was adversely affected by the panda update on April 12. We had some external seo firms work on this site for us and unfortunately the links they gained for us were very low quality, from sometimes spammy sites and also "keyword" packed with very littlle anchor text variation. Our other websites (the .co.nz and .com) moved up after the updates so I can only assume our external seo consultants were responsible for this. I have since managed to get them to remove around 70% of these links and we have bought all seo efforts back in house again. I have also worked to improve the quality of our content on this site and I have 404'ed the six worst affected pages (the ones that had far too many single phrase anchor text links coming into them). We have however not budged much in our rankings (we have made some small gains but not a lot). Our other weakness's are not the fastest page load times and some "thin" content. We are on the cusp (around 4 weeks away) of deploying a brand new platform using asp.net MVP with N2 and this looks like it will address our page load speed issues. We also have been working hard on our content building and I believe we will address that as well with this release. Sorry for the long build up, however I felt some background was needed to get to my questions. My questions are: Do you think we are best to proceed with trying to get our www.natureshop.co.uk website out of the panda trap or should we consider deploying a new version of the site on www.natureshop.com/uk/ (geo targeted to the UK)? If we are to do this should we do the same for New Zealand and Germany and redirect the existing domains to the new geo targeted folders? If we do this should we redirect the natureshop.co.uk pages to the new www.natureshop.com/uk/ pages or will this simply pass on the panda "penalty". Will this model build stronger authority on the .com domain that benefit all of the geo targeted sub folders or does it not work this way? Finally can we deploy the same pages and content on the different geo targeted sub folders (with some subtle regional variations of spelling and language) or will this result in a duplicate content penalty? Thank you very much in advance to all of you and I apologise for the length and complexity of the question. Kind Regards
International SEO | | ConradC
Conrad Cranfield
Founder: Nature Shop Ltd0 -
Same language many countries
Hello, I live in Belgium and in this country you've 3 languages : french, dutch and german. I've customers from many countries : France, Nederlands,... and for my website in ".be" (we'll say www.mysite.be for example) I've choosen the french language. My question is can I've the same content on my site : www.mysite.be and www.mysite.fr without duplicate content or should I forgot using www.mysite.fr to avoid the D.C. problem? And with my site : www.mysite.be should I've more difficult to rank in France for example? Thank you for your answer, Jonathan
International SEO | | JonathanLeplang0