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.
How to interlink 16 different language versions of site?
-
I remember that Matt Cutts recommended against interlinking many language versions of a site.
Considering that google now also crawls javascript links, what is best way to implement interlinking?I still see otherwhise extremely well optimized large sites interlinking to more than 10 different language versions e.g. zalando.de, but also booking.com (even though here on same domain).
Currently we have an expandable css dropdown in the footer interlinking 16 different language versions with different TLD. Would you be concerned?
What would you suggest how to interlink domains (for user link would be useful)?
-
Gianluca. that is excellent news. Just curious since this is quite an important issue for us.
Do you speak from own experience with a similar case?
I did not find anywhere other references that contextual links should be fine. Do you remember anybody who wrote about it in the past?Just noticed that tripadvisor actually removed now all their contextual links to alternative language versions that they used to have in their footer. Instead they now implemented a flag drodpown where contextual links are not showing up anymore in the sourcecode.
-
If they are contextual links, then you should not have any problem and can maintain them as they are.
No need "to hide" them to Google.
-
Gianluca, thanks.
The footer links are currently contextual deep links.
Since I am interlinking here 16 TLD, I was just concerned that google may penalize this and that I better hide the links from google. -
There are two good ways to do interlinking between different country sites:
-
The first one is offering somehow similar to the one you described, but not making it sitewide (as saying, not having the footer links always linking to the home pages), but contextual linking, which means that domain.com/page-a will link in the footer to domain.co.uk/page-a, domain.it/pagina-a, domain.es/pagina-a et al.
-
Doing like Apple does. Having in the footer a link to a country selector page, where you can find all the link to all the different websites. This option is conservative, in the sense that you have just one page linking to all the international sites, hence you don't have to fear Google deciding to penalize sitewide interlinking.
-
-
Hi there
The most natural way I can think to do this from a linking perspective - I would have a URL that is the "main" URL of the website. I would have on this page a way for users to select their country or language for the most optimal experience.
Otherwise, I would read the following:
International SEO (Moz)
The International SEO Checklist (Moz)You should read these anyway. The resources above will tell you how to properly tag your websites for regional targeting, and also how to let Google know in WMT which regions should see what version of your site.
Hope this helps! Good luck!
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
-
Changing the language of the website meta title and description?
Hello, Moz community! I'm planning to change the language of my website title and description from English to rank better for queries on the local language. Do you think this would increase the local language ranking? And in case I need to switch back to English, let's say in 2021, would it be difficult to regain the current rankings? Please let me know if you have any thoughts on this. Thank you!
International SEO | | vhubert2 -
Schema for languages Subfolders
I'm using static Schema for each language subfolder in my website, Should i use the same "URL, description" for every language? or i have to use the URL and description according to the language? I'm using that schema for english should i change URL and description in the other languages? for example
International SEO | | MTBE0 -
International SEO Question: Using hreflang tags across two different TLDs.
Hi! My UK based company just recently made the decision to let the US market operate their ecommerce business independently. Initially, both markets were operating off the same domain using sub-directories (i.e: www.brandname.com/en-us/ , www.brandname.com/en-gb/ ) Now that the US team have broken away from the domain - they are now using www.brandnameUSA.com while the UK continues to use www.brandname.com/en-gb/. The content is similar across both domains - however, the new US website has been able to consolidate several product variations onto single product pages where the UK website is using individual product pages for each variation. We have placed a geo-filter on the main domain which is 301 redirecting North American traffic looking for www.brandname.com to www.brandnameUSA.com However, since the domain change has taken place, product pages from the original domain are now indexing alongside the new US websites product pages in US search results. The UK website wants to be the default destination for all international traffic. My question is - how do we correctly setup hrlang tags across two separate TLDs and how do we handle a situation where multiple product pages on the "default" domain have been consolidated into one product page on the new USA domain? This is how we are currently handling it: "en-us" href="https://www.BRANDNAMEUSA.com/All-Variations" /> href="https://www.BRANDNAMEUSA.com/All-Variations" />
International SEO | | alexcbrands0 -
If I redirect based on IP will Google still crawl my international sites if I implement Hreflang
We are setting up several international sites. Ideally, we wouldn't set up any redirects, but if we have to (for merchandising reasons etc) I'd like to assess what the next best option would be. A secondary option could be that we implement the redirects based on IP. However, Google then wouldn't be able to access the content for all the international sites (we're setting up 6 in total) and would only index the .com site. I'm wondering whether the Hreflang annotations would still allow Google to find the International sites? If not, that's a lot of content we are not fully benefiting from. Another option could be that we treat the Googlebot user agent differently, but this would probably be considered as cloaking by the G-Man. If there are any other options, please let me know.
International SEO | | Ben.JD0 -
Showing different content according to different geo-locations on same URL
We would like our website to show different content according to different Geo-locations (but in the same language). For example, if www.mywebsite.com is accessed from the US, it would show text (in English) appealing to North Americans, but, if accessed from Japan, it would show text (also in English) that appeals more to Japanese people. In the Middle East, we would like the website to show different images than those shown in the US and Asia. Our main concern is that we would like to keep the same URL. How will Google index these pages? Will it index the www.mywebsite.com (Japan version) in its Asia archives and the www.mywebsite.com (US version) in its North American archives? Will Google penalise us for showing different content across Geo-locations on the same URL? What if a URL is meant to show content only in Japan? Are there any other issues that we should be looking out for? Kindest Regards L.B.
International SEO | | seoec0 -
Subdomains or subfolders for language specific sites?
We're launching an .org.hk site with English and Traditional Chinese variants. As the local population speaks both languages we would prefer not to have separate domains and are deciding between subdomains and subfolders. We're aware of the reasons behind generally preferring folders, but many people, including moz.com, suggest preferring subfolders to subdomains with the notable exception of language-specific sites. Does this mean subdomains should be preferred for language specific sites, or just that they are okay? I can't find any rationale to this other than administrative simplification (e.g. easier to set up different analytics / hosting), which in our case is not an issue. Can anyone point me in the right direction?
International SEO | | SOS_Children0 -
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 domains pointing to a .com site
Hello, I am new to seo so please be easy if this happens to be a "silly" question. My company has a .com site. We are expanding into global markets, focusing on specific countries right now. General question: Would I be penalized for duplicate content if I purchased country-specific domains and pointed them to the .com site? Thanks, Jim
International SEO | | jimmer0