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.
Subdomains or subfolders for language specific sites?
-
We're launching an .org.hk site with English and Traditional Chinese variants. As the local population speaks both languages we would prefer not to have separate domains and are deciding between subdomains and subfolders. We're aware of the reasons behind generally preferring folders, but many people, including moz.com, suggest preferring subfolders to subdomains with the notable exception of language-specific sites.
Does this mean subdomains should be preferred for language specific sites, or just that they are okay? I can't find any rationale to this other than administrative simplification (e.g. easier to set up different analytics / hosting), which in our case is not an issue.
Can anyone point me in the right direction?
-
Just something to add if you want to consider this in your planning scope. My proffesional opinion is surely sub-folders, keeping away from sub-domains (unless for a very specific reason needed).
1. If you are building a multilingual site, you should also consider how you will be building back-links through various methods (content development, company blog, etc) and will those be done in each language to support the authority needed to build rankings in each language you are working to expand on?
2. If you are going to be building different divisions of the domain (Chinese, and perhaps later going French, German, etc), consider building out TLD's for each domain that's needed in specific languages and focus on building those separate sites. That way you can focus on content development, social media and marketing efforts specific to each language, thus improving your options for the search in each country.
Just some thoughts to think about depending on the scope of your project and sites.
Cheers!
-
What Tuzzell quoted is true. Subdomains is not for languages. It is mainly for SEO value and structuring of your site.
-
In respect to Google and other search engines they will determine the language based on the content. So other than having unique URLs for the different content normal site structure considerations come into play. I would also be inclined to use a subfolder and Google's webmaster guidelines for multi lingual sites show no preference.
Heres the relevant bit:
Google uses the content of the page to determine its language, but the URL itself provides human users with useful clues about the page’s content. For example, the following .ca URLs use
fr
as a subdomain or subdirectory to clearly indicate French content: http://example.ca/fr/vélo-de-montagne.html http://fr.example.ca/vélo-de-montagne.htmlSignaling the language in the URL may also help you to discover issues with multilingual content on your site.
Hope this helps.
-
Thanks William - just to clarify, the rationale I don't have is why moz.com mentions that the "notable exception to preferring subfolders is language specific sites".
My inclination is to go with subfolders (as we would if we were e.g. launching a blog), but since the standard advice has a caveat for language specific sites, I'd like to understand why this is so before making a decision.
-
You can go with either one. Your question is probably the number 1 asked question on Moz. LOL
I would do folders "if" creating a multi-lingual site. Let's take WordPress for example. 1 folder, 1 install, 2 languages, no multiple logins, 1 database.
For subdomains, there is no passing of PR. A subdomain is like having a brand new site. subdomain.example.com and example.com are completely different sites. The only reason I would run subdomains is if I am doing something where the "site search" algorithm will be tweaked a little... like craigslist.org. Every city has a subdomain and the algorithm may be just a little different. Maybe you may need a subdomain for security issues, but in general go with folders.
Also, the stronger example.com/english becomes, the more likely example.com/mandarin becomes. It shares link juice. This example doesn't happen when you use subdomains.
Hope that helps!
-
Subfolder is the way to go.
The rationale is that subfolders will have links from all parts of the site including from the different language section. For subdomains your ranking might fluctuate between different languages.
Subdomains are not used very often except to differentiate a primary domains core business and purpose. If it is usually just language, a subfolder is what everyone normally uses.
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
-
Setting up international site subdirectories in GSC as separate properties for better geotargeting?
My client has an international website with a subdirectory structure for each country and language version - eg. /en-US. At present, there is a single property set up for the domain in Google Search Console but there are currently various geotargeting issues I’m trying to correct with hreflang tags. My question is, is it still recommended practise and helpful to add each international subdirectory to Google Search Console as an individual property to help with correct language and region tagging? I know there used to be properly sets for this but haven’t found any up to date guidance on whether setting up all the different versions as their own properties might help with targeting. Many thanks in advance!
International SEO | | MMcCalden0 -
CcTLD vs subfolder for international SEO
In what situations is subfolder better than ccTLD, and vice versa.
International SEO | | MedicalSEOMarketing1 -
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 -
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 -
How to interlink 16 different language versions of site?
I remember that Matt Cutts recommended against interlinking many language versions of a site.
International SEO | | lcourse
Considering that google now also crawls javascript links, what is best way to implement interlinking? I still see otherwhise extremely well optimized large sites interlinking to more than 10 different language versions e.g. zalando.de, but also booking.com (even though here on same domain). Currently we have an expandable css dropdown in the footer interlinking 16 different language versions with different TLD. Would you be concerned? What would you suggest how to interlink domains (for user link would be useful)?0 -
Can you target the same site with multiple country HREFlang entries?
Hi, I have a question regarding the country targeting aspect of HREFLANG. Can the same site be targeted with multiple country HREFlang entries? Example: A global company has an English South African site (geotargeted in webmaster tools to South Africa), with a hreflang entry targeted to "en-za", to signify English language and South Africa as the country. Could you add entries to the same site to target other English speaking South African countries? Entries would look something like this: (cd = Congo, a completely random example) etc... Since you can only geo-target a site to one country in WMT would this be a viable option? Thanks in advance for any help! Vince
International SEO | | SimonByrneIFS0 -
What is the proper way to setup hreflang tags on my English and Spanish site?
I have a full English website at http://www.example.com and I have a Spanish version of the website at http://spanish.example.com but only about half of the English pages were translated and exist on the Spanish site. Should I just add a sitemap to both sites with hreflang tags that point to the correct version of the page? Is this a proper way to set this up? I was going to repeat this same process for all of the applicable URLs that exist on both versions of the website (English and Spanish). Is it okay to have hreflang="es" or do I need to have a country code attached as well? There are many Spanish speaking countries and I don't know if I need to list them all out. For example hreflang="es-bo" (Bolivia), hreflang="es-cl" (Chile), hreflang="es-co" (Columbia), etc... Sitemap example for English website URL:
International SEO | | peteboyd
<url><loc>http://www.example.com/</loc></url> Sitemap example for Spanish website URL:
<url><loc>http://spanish.example.com/</loc></url> Thanks in advance for your feedback and help!0 -
Australia specific SEO tips?
For those who are conducting SEO here in Australia: A lot of the info I read, and there is a lot, is generally from the States or UK it seems. Are there any things in particular I should look out for when doing SEO in Australia? Are there any SEO tips that are particular to Australia only? What directories are a must in Australia?
International SEO | | iSenseWebSolutions0