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
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
-
Best practice for Spanish version of English website?
I'm doing an audit for a site that has all of its English pages under the same roof with Spanish pages in Wordpress. It is intended for Chicago, not Mexico. I suspect this is not a good thing, but I only have instinct to rely on here. What is the best practice for having the same website in two languages? http://www.enhancedform.com/ and http://www.enhancedform.com/spanish/
International SEO | | realpatients0 -
URL Structure - Homepage, Country and State Pages
Hello, I am creating a website (or websites if best format) that will have state-specific boating license courses for every state in the US, Canada and Australia. I would like the content to be available on the website in English, French and Spanish. I want to be the global leader in providing boat test courses. For the (1) homepage, (2) country pages, and (3) state pages, what is best SEO format I should use for:
International SEO | | Monologix
(a) URL structure
(b) "href lang" code
(c) rel canonical code
(d) will meta content with non-English pages need to also be in the non-English language of that page? Also, what server company do you recommend I host my website with? I am a non-programmer and learning SEO, so any and all help will be greatly appreciated! Thank you very much in advance!!!0 -
What are the best practices for translation of city/state names for international SEO? (ie. New York in English vs. Nueva York in Spanish)
I'm working on international SEO / translation of a global travel site. While we have a global keyword research and translation strategy in process for each market they serve, I've run into a unique question. Overall, we are translating (and localizing) content for each market but aren't sure what to do with location names. Each country/state has cities and locations that have their own dedicated pages. I see three options for these location names (when titling a page and writing content): keep them in English, translate the names in the market languages, or use a combination of the two. The challenge with altering the location names to the market languages is that they are truly not known by those names. Though there are some instances where it may make sense…for instance **New York **in Spanish would be "Nueva York" with **‘**Nueva' being the Spanish translation of ‘new’. There are other instances, where no translation exists. If you’ve had a similar experience I'd love to hear your approach/recommendation.
International SEO | | JonClark150 -
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 URL structure for Multinational/Multilingual websites
Hi I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.) As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product? To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format: hotelsite.com/en/hotel-name (for english) and hotelsite.com/se/hotel-name (for swedish content of that same product) and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc. Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name? Any thoughts on best practice would be greatly appreciated.
International SEO | | pikka0 -
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 -
Should product-pages with different currencies have different URLs?
Here is a question that should be of interest for small online merchants selling internationally in multiple currencies. When, based on geolocation, a product-page is served with different currencies, should a product-page have a different URL for each currency? Thanks.
International SEO | | AdrienOLeary0 -
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