What strategy is better for a multilingual site for the SEO point of view?
-
Hi everyone, in a case for a site with two languages like spanish and english, how would do you deal with it?
I can see 4 cases, which is better??
1. With differents domains: mydomain.es (for spanish version) and mydomain.com (for english version).
2. With subfolder mydomain.com/es/ and mydomain.com/en/
3. With Subdomain: es.mydomain.com and en.mydomain.com
4 With URL translation (any url is translated in ther languages but not use of subdomain or subfolder): mydominain.com/hola and mydomiain.com/hello
Thanks very much for your answers (i love this forum).
-
Does it make sense to target my Portuguese translation for Brazil to Portugal as well? Or do I create another version of the site that is hreflang=pr so that people that speak Portuguese in other locations throughout the world will at least get a Portuguese translation?
-
After doing some more research I'm going to go with your suggestion...thanks!
-
By using en-US would I be leaving out English speaking users in other countries? I'm wondering if I should use this format:
For English
For Portuguese
-
Hey Brandon,
I would just do en-US and not bother about having just en. See below for example.
For English
For Portuguese
-
So when implementing hreflang in the head section, do you call out the alternative and main language on every single page?
So for example if I'm implementing Brazilian Portuguese where the main language is English, for my English site it would be:
Then for the Portuguese site it would be:
-
Yup, I think as long as you specify the hreflang for all languages including the principale one you'll be fine.
-
Thanks very much for the answer, i know about the hreflanf, with sub-folder i think for the principal language you can omitted the sub-folder: example.com for spanish and example.com/en for english, but not so sure if that is good.
-
Hi,
I've actually had to deal with the same issue this year. From the research I did a while ago there's one solution that stood out for me.
I went with the sub-folder. example.com/en & example.com/es and made sure that all my pages add the hreflang attribute that points the page with its language info.
The main benefits of using a subfolder is that you don't have to share your domain authority between the different language sites.
Here's some resource to get you started
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
-
Who is the best SEO expert in the World?
Hey everyone, i am creating a blog post on Top SEO Experts in the World. I need your recommendation who is in the top 10 list? Your suggestions is highly appreciated for me. Thanks!
International SEO | | gxpl090 -
Is this approach of returning different content depending on IP beneficial for international SEO?
I've decided to use sub folders for my site, and from everything I've read online it seems I shouldn't change the page content depending on IP, yet I know of a successful well funded site that hires full time SEO staff that does just that, and I'm wondering whether they know something I don’t which is helping their SEO. From everything I've read online this is the format I think I should use: mysite.com/us/red-wigs mysite.com/gb/red-wigs mysite.com/red-wigs does not exist This is the format the other site is using: othersite.com/red-wigs (from US IP address) othersite.com/red-wigs (from UK IP address) othersite.com/gb/red-wigs The content on othersite.com/red-wigs is identical to othersite.com/gb/red-wigs when loading from a UK IP address, and a lot of URLs without /gb/ are being returned when searching google. The benefit I can think of that they are gaining is US pages which are being returned for UK based searches will return the correct content. Are their any other gains to this approach? I'm concerned that if I use this approach for different languages then the radically differing content of othersite.com/red-wigs depending on the location of the crawler might confuse google - also generally changing content depending on IP seems to be recommended against. Thanks
International SEO | | Mickooo0 -
International SEO & redirects - do these solutions make sense?
I’m currently working on SEO for an international website with subdirectories set up for each international version. The site is has never had any SEO previously and is having a lot of indexing and visibility issues. Also geotargeting seems very off in search results. I’ve diagnosed various issues and want to check my assumptions and solutions below make sense... The root domain uses a 302 redirect to display content from the /en-GB page. (302 redirects seem to be a default language fallback setting configured in the CMS) and they’re used for most key pages. I’m concerned these redirects are contributing to a lot of the issues with incorrect indexing. The en-GB is the default language version of the site. So far, the en-GB has been set as the canonical version too. Both the root domain and this subdirectory URL display the same content. (en-US is also a near duplicate page). All other international homepages appear only on their subfolder URL. Various SEO tools have been showing redirect loops (caused by language changing parameter versions of URLs being crawled that don’t have redirects on them) and issues with hreflang and canonicals. I believe the hreflang tags and canonicals have been ignored due to relative URLs being used for each, as search results don’t always contain the desired versions of the URLs (in terms of regional version and preferred canonical versions). My questions are: Could these 302 redirects be conflicting with hreflang tags? If so, I’m thinking they should be removed (if not made 301s). GSC doesn’t like the fact these are on key pages, as redirected pages are listed in the sitemap. Will changing hreflang tags and canonical tags to absolute URLs possibly be enough to fix these issues from what you can tell? (Or will redirects need to go too?) Is the en-GB correctly set as the canonical when the root domain is also accessible, indexed and using this page’s content within the CMS too? (I feel like the root domain should be the canonical version, but not sure that works together with other language version subfolders or with a redirect in place from root to subfolder). As an extra point to the last question, GSC has recently chosen the root domain as the canonical (despite en-GB being set as user preference) and is now choosing to deindex some international versions of the homepage as a result. Hoping that getting the hreflang tags fixed and possibly redirects removed should correct this ASAP. But perhaps this also confirms en-GB should be the canonical and marked X-default too. I hope that all makes sense and sorry it’s a small collection of related questions. Really appreciate any replies.
International SEO | | MMcCalden0 -
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 -
Splitting a site into 2 international sites
Hi all, I have a client that currently has a .com domain that ranks in both the US and the UK for various search terms. They have identified a need to provide different information for UK and US visitors which will require 2 versions of all pages. If we set up a .co.uk domain and keep the .com obviously that will be a brand new UK site which will have zero rankings. Any suggestions as to the best way to introduce this second version of the content without losing UK rankings? Thanks
International SEO | | danfrost0 -
International SEO question domain.com vs domain.com/us/ , domain.com/uk etc.
Hi Mozzers, I am expanding a website internationally. I own the .com for the domain. I need to accommodate multiple countries and I'm not sure if I should build a folder for /us/ for United States or just have the root domain .com OPTION 1:
International SEO | | jeremycabral
domain.com/page-url -- United States
domain.com/de/page-url -- Denmark
domain.com/jp/page-url -- Japan OPTION 2:
domain.com/us/page-url -- United States
domain.com/de/page-url -- Denmark
domain.com/jp/page-url -- Japan My concern with option 2 is there will be some dilution and we wouldn't get the full benefit of inbound links compared to Option 1 as we would have geo ip redirection in place to redirect users etc. to the relative sub-folder. Which option is better from an SEO perspective? Cheers, Jeremy0 -
International SEO - auto geo-targetting
I read with interest the recent post on international SEO and the top level domain architecture approaches to local content: http://www.seomoz.org/ugc/folders-vs-subdomains-vs-cctld-in-international-seo-an-overview#jtc135670 The issue I have is a little more complex: The business sells a wide variety of products (37) but one is by far and away the biggest and most popular. This means that due to the link profile of the various country sites and HQ site, search engines categorise the site according to this product (this is easily seen with the Google Adplanner) and the other product lines suffer as a result. The current architecture is to have a .com site and then individual ccTLD country sites, again with all products on each site. This creates an issue as in most countries the brand is not strong (compared to the keyword names and search volumes of the products) and so it is not that effective in generating organic traffic. The .com hogs much of the inbound links and the country sites themselves are not that well optimised for a number of reasons. A proposed solution has been to leverage the strength of the .com and the search volume for the product names, and to produce thematic sites based on each product: productA.brand.com
International SEO | | StevieCC
productB.brand.com
productC.brand.com In this way, the sites, content and link profiles are aligned around the more desirable products and we can expect improved organic search performance as a result (or at least ensure relevant traffic finds the relevant content fast). In terms of providing localised content, the plan was to use content mirroring and to then assign each content mirror to a specific geo-location using the webmaster tools console (and other SE equivilents). This is shown I think in one of Rand's videos. ProductA.brand.com/de/de Germany site for product A with unique German content
ProductA.brand.com/fr/fr French site for product A with unique French content This makes economic sense to me as to utilise the ccTLDs would result in hundreds of separate sites with all the licence and server considerations that entails. For example, for product A alone we would have to produce: productA.brand.de
productA.brand.fr
productA.brand.cn
productA.brand.jp
ect ect ect This just would not be sustainable in license/server costs alone across 37 products and 24 countries. However, I saw in a recent presentation at SES London that (auto) geo-targeting is risky, often doesn't work well for SEO and can even be seen as cloaking. I think the above strategy could still work, but perhaps we should avoid the use of auto-geotargetting altogether and hope the search engines alone do their job in getting users to the right content as we optimise the unique content for each country (and if they don't, ensure our desgn, UX and country selectors do the job instead). SEO guru consensus is to use the ccTLD if you own it, but as described above, in the real world that just isn't possible or practical given the company's strategic position. Which leads to the final question- we do own the brand ccTLDs- if they are directed back to the content mirror for the country on the .com, is there any SEO benefit in doing so aside from directing back any link juice associated with the domain)?0 -
Do non-english(localized) URLs help Local SEO and user experience?
Hi Everyone, This question is about URL best practice for multilingual websites. We have www.example.com in English and we are building the exact replica of English site in German www.example.de. On the Geman site, we are considering to translate some portions of the URLs for example last folder and file name as seen below: example.de/folder1-in-english/folder2-in-english/folder3-in-german/filename-in-german.html Is this a good idea? Will this help SEO and user experience both? or the mixed languagues in URL will confuse the users? Google guidelines say that this should be ok. Would love to get feedback from SEOMOZ community! Thanks, Supriya.
International SEO | | Amjath0