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.
-
Confusing Search Engine by sending two different signal about one URL. You must keep it simple by applying 301 redirect from domain.com/en to domain.com. Domain.com/en version is little confusing for user as well, they will think that domain.com has a different default Language.
-
For me redirect will be the right way.
Why? Because in another way you will have a duplicate content issue. Remember yoursite.com and www.yoursite.com will be indexed as differents pages.
Have the same Issue in the past. And I resolved the problem
1- redirections
2- setting the right URL on Search Console
(Search Console > Site Settings > Preferred domain)
3- Submit a sitemap for every language
(Search Console > Sitemaps)
4- And Finally config the language on search console
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
-
GeoIP Redirects & hreflang
Hello, We believe we've had some issues with hreflang tags not remaining validated due to the implementation of geoIP redirects. Previously, if a user clicked a landing page on Google search that was not targeted for their territory, they would instantly be redirected to a sub path that targets their territory using geoIP redirects. We're planning to remove the initial geoIP redirects and have messaging that prompts the user to either stay on the page they've landed on, or be redirected to page that is right for their territory. However, if a user has selected to be redirected to a sub path that is targeted for their territory, they will have a cookie preference set for the IP location they've selected, and will continue to be redirected to their chosen sub path. My question is, will a crawler follow and trigger the geo preference cookie, which could potentially cause complexities in validating hreflang tags and ranking of content for the right market. Thanks.
International SEO | | SEONOW1230 -
Using .ag for agriculture site with global targeting
Would using .ag with a short punchy domain like farm.ag, that was targeting a global audience be a wise decision? Versus say an 11 character descriptive ".com". Is there any benefit to using a ".ag" if the site is for agriculture? Note, this is a heavy content site so SEO important, with plans to serve different languages later.
International SEO | | mag7770 -
International website sharing with .com/.au/.uk
I have a small business in the United States and would like to copy our main website for my international partners. My website is a .com. I think that their domains will end in their country codes: .au and .uk. We are open to using different domains. We plan to share blog articles and other content, but do not wish to be penalized for duplication. I have tried to read articles on this topic, but am unfamiliar with a lot of the terms. Is there any way to do this simply? Many thanks, Steph
International SEO | | essential_steph0 -
What language to use for URL's for Russian language?
Hi, Our site is in English, Spanish, Danish and Russian - the URL's are individual to the language they are in, but of course, Russian contains some strange characters so I decided not to use them in the URL's Any advice on how to create the URL's for russian language pages? thanks
International SEO | | bjs20100 -
CcTLDs 301 redirected to subfolders
My client has an international website and currently has a mixture of ccTLDs, subdomains, and subfolders for the country specific pages. We are trying to change this however they want to have ccTLDS because of the SEO benefit but 301 redirect them to subfolders because of the simplicity of management that subfolders provide. I believe that if they are really just working with subfolders, why don't they just use subfolders and use Google Webmaster Tools and XML Sitemaps to help Google understand each targeted country. My questions are: 1. Does having aht ccTLD example.ca 301 redirected to example.com/ca really benefit anything? 2. This client tends to spell out the name of the country even with country specific TLDs, and they can't change it, will this affect SEO? Ex: example.ca/canada. 3. What the best practice? example.ca/canada/en-ca/city or example.ca/canada/city/en-ca? Thanks!
International SEO | | nrv0 -
Delaying Redirection - Possible loss of Domain Authority?
Hey guys, I was hoping somebody might be help with my current dilema. We have a international website due to go live soon which has changed its brand name. The organisation whom we are working for want to leave the old site live for around 6 months after the new site goes live. The reason for keeping the site live is for users to be able to access many of the resources which will not be transferred over in time for when the new site goes live.The plan is to have a message on old site letting visitors know we have moved site. I'm concerned about this approach in terms of loosing some of the domain authority if the sites bounce rate starts increase due to people clicking over to the new site. Then in 6 months time when we finally redirect to the new site we might loose out on some of the domain authority. Is this something to be concerned about?The site currently has PR of 7 and Domain Authority score of 70.Cheers,Rob
International SEO | | daracreative0 -
Multinational Sites - The main SEO issues
I currently work for the UK arm of a Company with headquarters in Germany - The have outlets in half-a-dozen European countries, and up until now each country has had it's own website. The group has decided that from next year they will close all the individual country sites and then run new sites each from a central .location, I guess with a shared database of products. I see the sense in having central stock control etc, but I'm worried about the SEO impact. I have searched Q&A and the blog but could not find much to help me. What I would like to do is to provide some advice and pointers at to what they should be aiming for, both in terms website structure and on-going SEO for each country. Any advice welcome, thanks in advance.
International SEO | | cottamg0 -
Multi-lingual SEO: Country-specific TLD's, or migration to a huge .com site?
Dear SEOmoz team, I’m an in-house SEO looking after a number of sites in a competitive vertical. Right now we have our core example.com site translated into over thirty different languages, with each one sitting on its own country-specific TLD (so example.de, example.jp, example.es, example.co.kr etc…). Though we’re using a template system so that changes to the .com domain propagate across all languages, over the years things have become more complex in quite a few areas. For example, the level of analytics script hacks and filters we have created in order to channel users through to each language profile is now bordering on the epic. For a number of reasons we’ve recently been discussing the cost/benefit of migrating all of these languages into the single example.com domain. On first look this would appear to simplify things greatly; however I’m nervous about what effect this would have on our organic SE traffic. All these separate sites have cumulatively received years of on/off-site work, and even if we went through the process of setting up page-for-page redirects to their new home on example.com, I would hate to lose all this hard-work (and business) if we saw our rankings tank as a result of the move. So I guess the question is, for an international business such as ours, which is the optimal site structure in the eyes of the search engines; Local sites on local TLD’s, or one mammoth site with language identifiers in the URL path (or subdomains)? Is Google still so reliant on TLD for geo targeting search results, or is it less of a factor in today’s search engine environment? Cheers!
International SEO | | linklater0