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.
Multilingual Ecommerce Product Pages Best Practices
-
Hi Mozzers,
We have a marketplace with 20k+ products, most of which are written in English. At the same time we support several different languages. This changes the chrome of the site (nav, footer, help text, buttons, everything we control) but leaves all the products in their original language.
This resulted in all kinds of duplicate content (pages, titles, descriptions) being detected by SEOMoz and GWT. After doing some research we implemented the on page rel="alternate" hreflang="x", seeing as our situation almost perfectly matched the first use case listed by Google on this page http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077.
This ended up not helping at all. Google still reports duplicate titles and descriptions for thousands of products, months after setting this up. We are thinking about changing to the sitemap implementation rel="alternate" hreflang="X", but are not sure if this will work either. Other options we have considered include noindex or blocks with robots.txt when the product language is not the same as the site language. That way the feature is still open to users while removing the duplicate pages for Google.
So I'm asking for input on best practice for getting Google to correctly recognize one product, with 6 different language views of that same product. Can anyone help?
Examples:
(Site in English, Product in English) http://website.com/products/product-72
(Site in Spanish, Product in English) http://website.com/es/products/product-72
(Site in German, Product in English) http://website.com/de/products/product-72
etc...
-
Hi Gianluca,
Thanks for responding. I took a look at your guide, and I definitely understand the gold standard would be to get everything translated professionally, and provide a completely native experience.
Unfortunately due to our catalog size that would be prohibitively expensive, so I need to think of another solution. It sounds like from your guide that we are doing more harm than good, even with alternate language syntax in place.
Based on your answer, my thought would be to meta noindex any product page where the site language is not the same as the product. That way every page in the index will be 100% localized for potential visitors.
So if its a Spanish product index: site.com/es/product, but meta noindex site.com/de/product, site.com/product, etc.
If we follow that path, does it make sense to remove the alternate language syntax, since all the linked URLs will be no index?
Thanks again for your help.
-
Hi Scott,
sorry to tell you that you're doing International SEO quite bad. No offence, but what you describe is how not to do International SEO.
If you are targeting Spanish end users, you must localize in Spanish everything:
- template elements;
- URLs
- products description
- Titles
- e.v.e.r.y.t.h.i.n.g
It is not just a question of SEO, but of usability too. Just revert the situation: what would be your reaction if you enter in a site, click on the english version and everything is written in Spanish?
Obviously, if you have the spanish version of your all in spanish, that will help a lot ranking for spanish queries.
In order to find an answer to your doubts, I warmly suggest you to read this guide to International SEO I wrote here on SEOmoz few time ago: http://www.seomoz.org/blog/international-seo-dropping-the-information-dust
Ciao
-
Your answer is conceptually correct, but the implementation not that much.
This kind of URL is not the ideal: http://www.rentalinrome.com/trevifountainapartments_spa/treviluxurypenthouse
The best is to put every language mirror of your multilingual site in a subfolder: i.e. /es/ in the above cited case.
Google, in fact, understands better that the /es/, /de/, /fr/ subfolders are targeting Spanish, German and French, as those are the ISO codes for those languages.
The subfolders way, then, is even more suggested if you are targeting a country, because you can geotarget a subfolder in Google Webmasters Tools.
Finally, a warm suggestion: if you really want to be sure to rank in Russia, then you should think about Yandex SEO... which means:
- Having the site in a .ru domain name (Yandex is biased toward russian domain terminations);
- Have the site in russian.. also the URLs (yours is in english)
-
Hi
For me it is wrong to present a product with the navigation in different languages and the description always in English
We work in travel and i want show you how we work with the same apartment
http://www.rentalinrome.com/trevifountainapartments/treviluxurypenthouse english default language
http://www.rentalinrome.com/trevifountainapartments_ita/treviluxurypenthouse
http://www.rentalinrome.com/trevifountainapartments_spa/treviluxurypenthouse
http://www.rentalinrome.com/fontainedetreviappartements/treviluxurypenthouse
http://www.rentalinrome.com/trevifountainapartments_de/treviluxurypenthouse
http://www.rentalinrome.com/trevifountainapartments_ru/treviluxurypenthouse
we change all, navigation and content
This is the best way for index the same product in different language avoid duplicate content
Ciao
Maurizio
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
-
Hreflang tag on every page?
Hello Moz Community, I'm working with a client who has translated their top 50 landing pages into Spanish. It's a large website and we don't have the resources to properly translate all pages at once, so we started with the top 50. We've already translated the content, title tags, URLs, etc. and the content will live in it's own /es-us/ directory. The client's website is set up in a way that all content follows a URL structure such as: https://www.example.com/en-us/. For Page A, it will live in English at: https://www.example.com/en-us/page-a For Page A, it will live in Spanish at https://www.example.com/es-us/page-a ("page-a" may vary since that part of the URL is translated) From my research in the Moz forums and Webmaster Support Console, I've written the following hreflang tags: /> For Page B, it will follow the same structure as Page A, and I wrote the corresponding hreflang tags the same way. My question is, do both of these tags need to be on both the Spanish and English version of the page? Or, would I put the "en-us" hreflang tag on the Spanish page and the "es-us" hreflang tag on the English page? I'm thinking that both hreflang tags should be on both the Spanish and English pages, but would love some clarification/confirmation from someone that has implemented this successfully before.
International SEO | | DigitalThirdCoast0 -
Multi Regional Website Best Practices
Hi there, I have a website that is targeting 3 countries AU/US & NZ. I have set up hreflang tags for each page on each of the site however I am having difficulties getting it work right. I read this article which was a great insight into the hreflang tags. https://a-moz.groupbuyseo.org/blog/hreflang-behaviour-insights and as a result I have implemented hreflang tags in the following manner: When users access the root domain http://[website] it will redirect the user to their locale with a 302 redirect. I have a few questions:
International SEO | | nathanfranklin
1. When building my external link profiles, I'm not sure if I should be building link profiles for http://[website]/ or for the geo graphical pages (http://[website]/aus/ etc..). Note that the http://[website]/ is never used, it just issues a 302 to the actual geographical location. 2. It seems that the hreflang tags are not working correctly. Perhaps its the result of the 302 on the root page, but in google.com.au (using the link http://www.google.com.au/search?hl=en&gl=au&pws=0&q=[branded search]) I would expect that I should see the search results for /aus/ given the fact that the hreflang tags are setup as en-au. Instead I am seeing the root domain page. Is that correct or should it be showing all the pages with /aus/. ALSO If I do a search in google thailand (http://www.google.com.au/search?hl=en&gl=th&pws=0&q=[branded search]) it returns the /aus/ version where it should be showing the /us/ using the x-default hreflang tag. In google webmaster tools I have setup 4 site profiles:
http://[website]/
http://[website]/us/
http://[website]/aus/ (Targeted to Australia)
http://[website]/nz/ (Targeted to New Zealand) Any help would be appreciated. Thanks Nathan1 -
Country subfolders showing as sitelinks in Google, country targeting for home page no longer working
Hi There, Just wondering if you can help. Our site has 3 region versions (General .com, /ie/ for Ireland and /gb/ for UK), each submitted to Google Webmaster Tools as seperate sites with hreflang tags in the head section of all pages. Google was showing the correct results for a few weeks, but I resubmitted the home pages with slight text changes last week and something strange happened, though it may have been coincidental timing. When we search for the brand name in google.ie or google.co.uk, the .com now shows as the main site, where the sitelinks still show the correct country versions. However, the country subdirectories are now appearing as sitelinks, which is likely causing the problem. I have demoted these on GWT, but unsure as to whether that will work and it seems to take a while for sitelink demotion to work. Has anyone had anything similar happen? I thought perhaps it was a markup issue breaking the head section so that Google can no longer see the hreflangs pointing to each other as alternates. I checked the source code in w3 validator and it doesn't show any errors. Anyway, any help would be much appreciated - and thanks to anyone who gets back, it's a tricky type of issue to troubleshoot. Thanks, Ro
International SEO | | romh0 -
Are my translated pages damaging my ranking?
Hi there, I have a site in English but with duplicates in different languages. The first problem is that these translated versions of my site receive no ranking on google stars (while the english does) - why is this? The second problem is that SEOmoz counts the errors on my site and then duplicates this error count for all the translated versions of my site - meaning I have a huge amount of errors (too many on-page links). Add this to the fact that I use affilite ID´s to track different types of traffic to my site - so all page urls in english and other languages, with an affiliate id on the end of the url, count as an error. This means I have a huge amount of on page errors indicated by SEOmoz, plus no ranking for my translated pages - I think this is really harming my overall ranking and site trust. What are your opinions on this?
International SEO | | sparkit0 -
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 -
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 -
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 -
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