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.
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
-
Spanish word as English domain name
hi anyine any issues with using Spanish, and other non English words, as domain names when trying to rank in Google uk. We launched a number of websites a while back but finding it hard to get much traction in Google uk. We are getting a reasonable number of impressions but cannot seem to get very high in the rankings. All the names are foreign words for their service. Our homeware website, for example, uses the basque word for furniture as its name. other than potential branding issues of having domains people might struggle to spell, is there any serp issues we would face with these names. thanks
International SEO | | Arropa0 -
How to best set up international XML site map?
Hi everyone, I've been searching about a problem, but haven't been able to find an answer. We would like to generate a XML site map for an international web shop. This shop has one domain for Dutch visitors (.nl) and another domain for visitors of other countries (Germany, France, Belgium etc.) (.com). The website on the 2 domains looks the same, has the same template and same pages, but as it is targeted to other countries, the pages are in different languages and the urls are also in different languages (see example below for a category bags). Example Netherlands:
International SEO | | DocdataCommerce
Dutch domain: www.client.nl
Example Dutch bags category page: www.client.nl/tassen Example France:
International domain: www.client.com
Example French bags category page: www.client.com/sacs When a visitor is on the Dutch domain (.nl) which shows the Dutch content, he can switch country to for example France in the country switch and then gets redirected to the other, international .com domain. Also the other way round. Now we want to generate a XML sitemap for these 2 domains. As it is the same site, but on 2 domains, development wants to make 1 sitemap, where we take the Dutch version with Dutch domain as basis and in the alternates we specify the other language versions on the other domain (see example below). <loc>http://www.client.nl/tassen</loc>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="http://www.client.com/sacs"
/></xhtml:link<br> Is this the best way to do this? Or would we need to make 2 site maps, as it are 2 domains?0 -
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 -
Mixed English and Arabic URLs
I'm currently working with a global brand who need localisation in each of their territories. They're operating on a single .com domain name, with different language versions in separate directories. Example:
International SEO | | Guyboz
domain.com/en/
domain.com/fr/
domain.com/ar/ We're using ahreflang tags to make sure Google shows the correct language version for each region. Now onto my question... As the domain is a .com with an English company name, when it comes to the Arabic version of the website, will having a completely mixed language URL like this be detrimental to the site's performance in searches from the middle east? Currently we're coming up with URLs like the following: domain.com/blog/عنوان بلوق عربية طويلة حقا على شيء مثير جدا للاهتمام Is this a bad thing?0 -
How to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
Dear all, what is the best way to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries? What must I add to my code of websites my .nl domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? What must I add to my code of websites my .be domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? Thanks in advance!
International SEO | | HMK-NL3 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1 -
International (foreign language) URL's best practices
I'm curious if there is a benefit or best practice with regards to using the localized language on international sites (with specific ccTLDs). For example, should my french site (site.fr) use the french language as keywords within the URLs or should they be in english? e.g. www.site.fr/nourriture vs. www.site.fr/food Is that considered best practice for SEO (or just for brand perception those markets?). Is there a tangible loss in SEO if we do not use the correct language for those URLs and just stick with English around the world? I recall seeing a Matt Cutts video on the topic and he said that google does support i18n URL's but other SE's might not support them as gracefully but he didn't come down with a hard recommendation to go with i18n URL's or just English. Would love a strong ruling in favor one direction based on best practices.
International SEO | | mongillo0 -
Google Webmaster Tools - International SEO Geo-Targeting site with Worldwide rankings
I have a client who already has rankings in the US & internationally. The site is broken down like this: url.com (main site with USA & International Rankings) url.com/de url.com/de-english url.com/ng url.com/au url.com/ch url.com/ch-french url.com/etc Each folder has it's own sitmap & relative content for it's respective country. I am reading in google webmaster tools > site config > settings, the option under 'Learn More': "If you don't want your site associated with any location, select Unlisted." If I want to keep my client's international rankings the way it currently is on url.com, do NOT geo target to United States? So I select unlisted, right? Would I use geo targeting on the url.com/de, url.com/de-english, url.com/ng, url.com/au and so on?
International SEO | | Francisco_Meza0