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 a-moz.groupbuyseo.org, 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
fras 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 a-moz.groupbuyseo.org 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
-
Multilang site: Auto redirect 301 or 302?
We need to establish if 301 or 302 response code is to be used for our auto redirects based on Accept-Language header. https://domain.com
International SEO | | fJ66doneOIdDpj
30x > https://domain.com/en
30x > https://domain.com/ru
30x > https://domain.com/de The site architecture is set up with proper inline HREFLANG.
We have read different opinions about this, Ahrefs says 302 is the correct one:
https://ahrefs.com/blog/301-vs-302-redirects/
302 redirect:
"You want to redirect users to the right version of the site for them (based on location/language)." You could argue that the root redirect is never permanent as it varies based on user language settings (302)
On the other hand, the lang specific redirects are permanent per language: IF Accept-Language header = en
https://domain.com > 301 > https://domain.com/en
IF Accept-Language header = ru
https://domain.com > 301 > https://domain.com/ru So each of these is 'permanent'. So which is the correct?0 -
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 -
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 -
If I redirect based on IP will Google still crawl my international sites if I implement Hreflang
We are setting up several international sites. Ideally, we wouldn't set up any redirects, but if we have to (for merchandising reasons etc) I'd like to assess what the next best option would be. A secondary option could be that we implement the redirects based on IP. However, Google then wouldn't be able to access the content for all the international sites (we're setting up 6 in total) and would only index the .com site. I'm wondering whether the Hreflang annotations would still allow Google to find the International sites? If not, that's a lot of content we are not fully benefiting from. Another option could be that we treat the Googlebot user agent differently, but this would probably be considered as cloaking by the G-Man. If there are any other options, please let me know.
International SEO | | Ben.JD0 -
Redirect the main site to keyword-rich subfolder / specific page for SEO
Hi, I have two questions. Question 1: is it worthwhile to redirect the main site to keyword-rich subfolder / specific page for SEO? For example, my company's webpage is www.example.com. Would it make sense to redirect (301) the main site to address www.example.com/service-one-in-certain-city ? I am asking this as I have learned that it is important for SEO to have keywords in the URL, and I was thinking that we could do this and include the most important keywords to the subfolder / specific URL. What are the pros and cons of this? Should I create folders or pages just the sake of keywords? Question 2: Most companies have their main URL shown as www.example.com when you access their domain. However, some multi-language sites show e.g. www.example.com/en or www.example.com/en/main when you type the domain to your web browser to access the site. I understand that this is a common practice to use subdomains or folders to separate different language versions. My question is regarding subfolders. Is it better to have only the subfolder shown (www.example.com/en) or should I also include the specific page's URL after the subfolder with keywords (www.example.com/en/main or www.example.com/en/service-one-in-certain-city)? I don't really understand why some companies show only the subfolder of a specific language page and some the page's URL after the subfolder. Thanks in advance, Sam
International SEO | | Awaraman1 -
Best domain for spanish language site targeting ALL spanish territories?
hi, we're have a strong .com domain and are looking to launch a site for spanish speakers (ie latin america + spain). we already have various subdirectories for some foreign language sites (eg. ourdomain.co.uk, us.ourdomain.com, ca.ourdomain.com, ourdomainchina.com, ourdomainindia.com etc) we already have a B2B site ourdomain.com-es which will remain the same. I'm thinking best practice would be to launch translated copy for the following: ourdomain.com/es ourdomain.com/cl ourdomain.com/mx ourdomain.com/pt etc etc firstly is this the best option? secondly, i'm really interested to hear whether there is a less time/resource intensive route that would give us visibility in ALL spanish speaking territories? Also - if we go with just one of the above (eg ourdomain.com/cl) how likely are we to get traction in other spanish speaking territories? any help much appreciated!
International SEO | | KevinDunne0 -
Country specific landing pages
I have a client who wants to put a re-direct on his landing pages based on the visitors IP address. The landing page will be a sub domain relevant to the country their IP is located in. I am a little concerned this will effect the SEO. Appreciate any advice. Dylan 🙂
International SEO | | gomyseo0 -
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