<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Multiple URL strategies</title>
	<atom:link href="http://xebidy.com/2008/05/multiple-url-strategies/feed/" rel="self" type="application/rss+xml" />
	<link>http://xebidy.com/2008/05/multiple-url-strategies/</link>
	<description>Web 2.0 eCommerce Strategy Design and Implementation</description>
	<pubDate>Wed, 20 Aug 2008 13:07:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: xebidy</title>
		<link>http://xebidy.com/2008/05/multiple-url-strategies/#comment-4641</link>
		<dc:creator>xebidy</dc:creator>
		<pubDate>Sun, 04 May 2008 08:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://xebidy.com/?p=154#comment-4641</guid>
		<description>I guess the first place to start is to look at all the different language keyword searches to that which you are optimising the sites for to determine that what the users are in fact searching for is what your sites are truly optimsed as.  I guess you are not simply translating the sites word for word but rather rewriting the sites in the different language for your targeted keywords in that language.  Things like image names, alt text and headings in the different languages will help as will recognition of the fact that search terms in different countries might be vastly different to searches that you are expecting in English.

There is also the argument that search engines take into account where your server is actually placed, so if you have a site in Australia about Australian stuff and the server is in the US then the site may not do so well in Australia.  We don't have any idea what sort of weighting this sort of thing has in the Google algorithm.

I did a bit of a quick research to see what other sites were doing.  &lt;a href="http://www.sony.com" rel="nofollow"&gt;Sony&lt;/a&gt; has completely different URLs for each country, as did &lt;a href="http://www.airnewzeland.com" rel="nofollow"&gt;Air New Zealand&lt;/a&gt;, &lt;a href="http://www.apple.com" rel="nofollow"&gt;Apple&lt;/a&gt; on the other hand keeps the user in the .com and adds the language, &lt;a href="http://www.hostelworld.com" rel="nofollow"&gt;Hostel World&lt;/a&gt; creates a sub domain for each language, &lt;a href="http://www.hertz.com" rel="nofollow"&gt;Hertz&lt;/a&gt; rent a car made the translations dynamically, &lt;a href="http://www.crownrelo.com/web/relo.nsf/index.htm" rel="nofollow"&gt;Crown Relocations&lt;/a&gt; don't seem to offer any multi-languages at all from their .com site (and their .co.uk redirected to .com) and Avis rentals recognised I was in New Zealand based on my IP address and showed me a NZ specific site - I hate that!

Unless I am missing something very obvious the Avis site drives me crazy.  The NZ specific site is all in English and does not have anywhere obvious for me to change languages - but what if I was a German tourist already in NZ wanting to rent a car!  Apparently Lycos did this in the early days and one of the biggest outcrys was in Belgium where there are a disproportionate amount of international workers yet Lycos displayed every time in Flemish.  Whatever strategy you choose make sure it is obvious to your users how to change languages, especially if you are going to default to their local site based on IP addresses.

I think if I was to build large sites that were multi-lingual and cross-border in operation I would be inclined to create whole new sites on regional URLs.  It is one thing translating a tourism site where you are operating in a specific area although selling across multiple markets and how Google looks at those translations compared to a site such as &lt;a href="http://www.interdean.com" rel="nofollow"&gt;yours&lt;/a&gt; where you are selling essentially a different product in each market - albeit the same service.  Relocating from Portugal to New Zealand is a quite different product than relocating from Germany to England and I would think that Google is therefore treating the translated pages all as independent sites sort of - bad explanation, but I hope you know what I mean.  I think from a search engine and user point of view it would be better if you created different sites for each operating area and rather than simply translating the original you completely rewrote the content to reflect the nuisances of the specific markets.</description>
		<content:encoded><![CDATA[<p>I guess the first place to start is to look at all the different language keyword searches to that which you are optimising the sites for to determine that what the users are in fact searching for is what your sites are truly optimsed as.  I guess you are not simply translating the sites word for word but rather rewriting the sites in the different language for your targeted keywords in that language.  Things like image names, alt text and headings in the different languages will help as will recognition of the fact that search terms in different countries might be vastly different to searches that you are expecting in English.</p>
<p>There is also the argument that search engines take into account where your server is actually placed, so if you have a site in Australia about Australian stuff and the server is in the US then the site may not do so well in Australia.  We don&#8217;t have any idea what sort of weighting this sort of thing has in the Google algorithm.</p>
<p>I did a bit of a quick research to see what other sites were doing.  <a href="http://www.sony.com" rel="nofollow">Sony</a> has completely different URLs for each country, as did <a href="http://www.airnewzeland.com" rel="nofollow">Air New Zealand</a>, <a href="http://www.apple.com" rel="nofollow">Apple</a> on the other hand keeps the user in the .com and adds the language, <a href="http://www.hostelworld.com" rel="nofollow">Hostel World</a> creates a sub domain for each language, <a href="http://www.hertz.com" rel="nofollow">Hertz</a> rent a car made the translations dynamically, <a href="http://www.crownrelo.com/web/relo.nsf/index.htm" rel="nofollow">Crown Relocations</a> don&#8217;t seem to offer any multi-languages at all from their .com site (and their .co.uk redirected to .com) and Avis rentals recognised I was in New Zealand based on my IP address and showed me a NZ specific site - I hate that!</p>
<p>Unless I am missing something very obvious the Avis site drives me crazy.  The NZ specific site is all in English and does not have anywhere obvious for me to change languages - but what if I was a German tourist already in NZ wanting to rent a car!  Apparently Lycos did this in the early days and one of the biggest outcrys was in Belgium where there are a disproportionate amount of international workers yet Lycos displayed every time in Flemish.  Whatever strategy you choose make sure it is obvious to your users how to change languages, especially if you are going to default to their local site based on IP addresses.</p>
<p>I think if I was to build large sites that were multi-lingual and cross-border in operation I would be inclined to create whole new sites on regional URLs.  It is one thing translating a tourism site where you are operating in a specific area although selling across multiple markets and how Google looks at those translations compared to a site such as <a href="http://www.interdean.com" rel="nofollow">yours</a> where you are selling essentially a different product in each market - albeit the same service.  Relocating from Portugal to New Zealand is a quite different product than relocating from Germany to England and I would think that Google is therefore treating the translated pages all as independent sites sort of - bad explanation, but I hope you know what I mean.  I think from a search engine and user point of view it would be better if you created different sites for each operating area and rather than simply translating the original you completely rewrote the content to reflect the nuisances of the specific markets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://xebidy.com/2008/05/multiple-url-strategies/#comment-4616</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 02 May 2008 06:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://xebidy.com/?p=154#comment-4616</guid>
		<description>I currently run a multi lingual website which in effect sells the same thing in lots of different languages which are all hosted on one domain.  The problem that I have found is that in each of the respective countries where the language is relevant, the Google rankings that I have optimised for have relatively poor results. 

After some consultation I have come to realise that there is an arguement towards having a different URL for each language, and perhaps even localised hosting.  The other option is of course straight redirects to the relevant page, but I have also heard on several occassions that Google prefers to have content attached to a URL rather than redirects.

At the moment I am at a cross roads.  Any idea on which strategy would work best for a multilingual, multi url site?</description>
		<content:encoded><![CDATA[<p>I currently run a multi lingual website which in effect sells the same thing in lots of different languages which are all hosted on one domain.  The problem that I have found is that in each of the respective countries where the language is relevant, the Google rankings that I have optimised for have relatively poor results. </p>
<p>After some consultation I have come to realise that there is an arguement towards having a different URL for each language, and perhaps even localised hosting.  The other option is of course straight redirects to the relevant page, but I have also heard on several occassions that Google prefers to have content attached to a URL rather than redirects.</p>
<p>At the moment I am at a cross roads.  Any idea on which strategy would work best for a multilingual, multi url site?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
