Welcome to the Q&A Forum

Hello, We're looking to internationalise our site so that US visitors will see the US branded version while everyone else will see the global version (currently at .com). This question specifically is about location-based auto-redirects. The literature I've read (including Google) recommends against auto-redirection: "Avoid automatic redirection based on the user’s perceived language. These redirections could prevent users (and search engines) from viewing all the versions of your site." Insofar as I understand it the theory goes as follows. Google crawls mainly from the US Auto-redirecting by US IP to the US domain will also redirect the Googlebot crawlers Because of this the crawlers will only see the US site / domain and not original .com website Crawlers can't index what they can't see Drop in rankings for the original site However, one of my colleagues has pointed out to me a company which does use auto-redirects. If a user is in the UK and type in their website they will be redirected to the UK version of the site, US will be US etc. I have checked their rankings and they are still ranking highly for relevant terms. I have been asked why they have been able to do this without impacting their visibility. Any ideas? Given their success have the risks of auto-redirecting have been overstated? How can we ensure US visitors land on the correct internationalised domain without auto-redirects in place? Looking forward to your thoughts on this as well as your experiences. Thanks in advance!

Hello all, I'm looking for opinions on this. Imagine there is a website example.com in English and the company 'Example' wanted to translate some of the pages (not not all) in to Russian. So they set up example.com/ru and translate the key pages into Russian. But half of the pages on.com/ru are left in English and there are no plans to translate them. How would you handle the pages in Engish on .com/ru? My thoughts are that they should: Canonicalise to the same versions on .com, and... Remove RU hreflang tags from the pages on .com/ru which are in English Otherwise, users searching in English with Russian browser settings could land on a page in English but then navigate to a translated page in Russian (+the menu navigation items will be in Russian) = bad UX. Not to mention they would be telling Google a page is in Russain but Google would be crawling English. So IMO, the best option is to use canonicals for this so that the .com version of the page is indexed. Then when a user lands after searching in English they will always be served English pages within that session. If English speakers/searchers land on the .com/ru page that would lead to a website half in one lang and half in another. I'm aware that Google recommends not using rel="canonical" across country or language versions of your site, but I believe they are making that recommendation based on an assumption that all pages are going to be translated to another language. In this case, there is no intention to do that, ever. Thanks for your thoughts and opinions. Cheers, Gill.

Hello World! Background: I am evaluating a tool/service that a company wants to use for managing the translated versions of their international/multi-lingual websites: https://www.transifex.com/product/transifexlive/ Transifex is asking webmaster to "simply add a snippet of JavaScript" to their website(s); the approved translations are added by the business in the back-end; and the translated sites are made live with the click of a button (on/to the proper ccTLD, sub-domain, or sub-directory, which is specified). CONCERN: Even though I know Google reads JavaScript for crawling and ranking,
I am concerned because I see the "English text" when I view the source-code on the "German site", and I wonder if this is really acceptable? QUESTION: Is a service like this (such as Transifex using JavaScript to render translations client-side) safe for indexing and ranking for my clients' international search engine visibility, especially via Google? Thank you!

So, we have a website in 18 or so different languages. bluewidgets.com/br bluewidgets.com/cn etc I have added each sub folder in Google Webmaster Tools and 'pointed' them to be at their respective geographic specific. However, the United States version of the website is sitting on the root domain. Is there any issue with me pointing the root domain at United States Google, considering there are 18 sub folders already pointed at different regions?

My website is currently hosted with Go-daddy and the hosting server is in the USA on a Linux platform. The problem is, the response time for my Australian Customers, is too slow, as a result, I decided to move to another Go Daddy Hosting server in the Asia Pacific Region. This has been completed successfully, however I think there may be some impact on my rankings. Can you advise if there are any specific things that I must do, when I move to a different hosting server with the same company or an alternative company. Note: We are not changing domain names or content, purely just moving to a hosting server closer to where our customers are based. Looking forward to your response.

Hi there! We have similar websites in different countries (it's an ecommerce site). Some times, those websites share the same language and, for example, people from Mexico end up in a page from our website in Argentina. Therefore they see our products in their language buy in a foreign currency. We would like to show them a pop-up (like a shadowbox) depending on their IP to allow them to go to their local website. There wouldn't be any redirect. Would that affect our rankings in any way? Would Googlebots see that as well? Thanks!

I have a HTML site hosted in Netherlands, i use Could Files from Rackspace and Cloudfront from Amazon as CDN. My target audience are in Portugal Is it worth to have a DNS Manage service in terms of seo? If so what are the benefits? Thank you Paulo

I read with interest the recent post on international SEO and the top level domain architecture approaches to local content: http://www.seomoz.org/ugc/folders-vs-subdomains-vs-cctld-in-international-seo-an-overview#jtc135670 The issue I have is a little more complex: The business sells a wide variety of products (37) but one is by far and away the biggest and most popular.  This means that due to the link profile of the various country sites and HQ site, search engines categorise the site according to this product (this is easily seen with the Google Adplanner) and the other product lines suffer as a result. The current architecture is to have a .com site and then individual ccTLD country sites, again with all products on each site.  This creates an issue as in most countries the brand is not strong (compared to the keyword names and search volumes of the products) and so it is not that effective in generating organic traffic.  The .com hogs much of the inbound links and the country sites themselves are not that well optimised for a number of reasons. A proposed solution has been to leverage the strength of the .com and the  search volume for the product names, and to produce thematic sites based on each product: productA.brand.com
productB.brand.com
productC.brand.com In this way, the sites, content and link profiles are aligned around the more desirable products and we can expect improved organic search performance as a result (or at least ensure relevant traffic finds the relevant content fast). In terms of providing localised content, the plan was to use content mirroring and to then assign each content mirror to a specific geo-location using the webmaster tools console (and other SE equivilents).  This is shown I think in one of Rand's videos. ProductA.brand.com/de/de  Germany site for product A with unique German content
ProductA.brand.com/fr/fr   French site for product A with unique French content This makes economic sense to me as to utilise the ccTLDs would result in hundreds of separate sites with all the licence and server considerations that entails.  For example, for product A alone we would have to produce: productA.brand.de
productA.brand.fr
productA.brand.cn
productA.brand.jp
ect ect ect This just would not be sustainable in license/server costs alone across 37 products and 24 countries. However, I saw in a recent presentation at SES London that (auto) geo-targeting is risky, often doesn't work well for SEO and can even be seen as cloaking. I think the above strategy could still work, but perhaps we should avoid the use of auto-geotargetting altogether and hope the search engines alone do their job in getting users to the right content as we optimise the unique content for each country (and if they don't, ensure our desgn, UX and country selectors do the job instead). SEO guru consensus is to use the ccTLD if you own it, but as described above, in the real world that just isn't possible or practical given the company's strategic position. Which leads to the final question- we do own the brand ccTLDs- if they are directed back to the content mirror for the country on the .com, is there any SEO benefit in doing so aside from directing back any link juice associated with the domain)?