<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The SEO Aspect of Country-Specific Domain Extensions</title>
	<link>http://www.translationjm.com/the-seo-aspect-of-country-specific-domain-extensions/</link>
	<description>We Speak Your Language</description>
	<pubDate>Tue, 06 Jan 2009 01:35:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Charles</title>
		<link>http://www.translationjm.com/the-seo-aspect-of-country-specific-domain-extensions/#comment-35</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Wed, 09 Jul 2008 21:58:28 +0000</pubDate>
		<guid>http://www.translationjm.com/the-seo-aspect-of-country-specific-domain-extensions/#comment-35</guid>
		<description>You're absolutely right, it is basic; the article was mostly meant to make people realize that there are other things to think about when deciding to translate a website. The point you bring up is very interesting - having your foreign domain hosted on a corresponding foreign IP is probably something that can have a significant impact SE-wise.

However, if you're based in the US, Canada etc., getting a domain with a foreign TLD might not even be an option, since some countries require that the administrative contact be a resident of said country (of the top of my head, I think it's the case with Germany's .de).

Still, some other small details can make a difference; for instance, if you plan on hosting the translated version on a subdomain of your main site, the language of the subdomain is relevant as well. Take French for example, for your French visitors, it'd be more logic and efficient to have the French version as francais.yoursite.com rather than french.yoursite.com

I'll try to have someone more experienced with the SEO aspect of localization make a guest blog post here. It's an interesting topic.</description>
		<content:encoded><![CDATA[<p>You&#8217;re absolutely right, it is basic; the article was mostly meant to make people realize that there are other things to think about when deciding to translate a website. The point you bring up is very interesting - having your foreign domain hosted on a corresponding foreign IP is probably something that can have a significant impact SE-wise.</p>
<p>However, if you&#8217;re based in the US, Canada etc., getting a domain with a foreign TLD might not even be an option, since some countries require that the administrative contact be a resident of said country (of the top of my head, I think it&#8217;s the case with Germany&#8217;s .de).</p>
<p>Still, some other small details can make a difference; for instance, if you plan on hosting the translated version on a subdomain of your main site, the language of the subdomain is relevant as well. Take French for example, for your French visitors, it&#8217;d be more logic and efficient to have the French version as francais.yoursite.com rather than french.yoursite.com</p>
<p>I&#8217;ll try to have someone more experienced with the SEO aspect of localization make a guest blog post here. It&#8217;s an interesting topic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iGuide</title>
		<link>http://www.translationjm.com/the-seo-aspect-of-country-specific-domain-extensions/#comment-34</link>
		<dc:creator>iGuide</dc:creator>
		<pubDate>Wed, 09 Jul 2008 21:19:21 +0000</pubDate>
		<guid>http://www.translationjm.com/the-seo-aspect-of-country-specific-domain-extensions/#comment-34</guid>
		<description>Well-written article, but the information seems very basic.  I imagine properly creating a website for a country outside the U.S. is much more involved than this.  What about the geographic location of your IP?</description>
		<content:encoded><![CDATA[<p>Well-written article, but the information seems very basic.  I imagine properly creating a website for a country outside the U.S. is much more involved than this.  What about the geographic location of your IP?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
