<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Should I have Mutiple Domains Names</title>
	<atom:link href="http://www.michaelwall.co.uk/seo/mutiple-domains-names/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michaelwall.co.uk/seo/mutiple-domains-names/</link>
	<description>Internet Marketing, SEO, Web Design and Web development</description>
	<lastBuildDate>Wed, 21 Jul 2010 03:20:08 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul Anthony</title>
		<link>http://www.michaelwall.co.uk/seo/mutiple-domains-names/comment-page-1/#comment-2785</link>
		<dc:creator>Paul Anthony</dc:creator>
		<pubDate>Fri, 27 Mar 2009 12:47:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelwall.co.uk/?p=80#comment-2785</guid>
		<description>Sorry Michael, fired and forgot on this comment - no - it was a dotcom and an ie. 

BTW subscribe to comments plugin for WP is great. ;o)</description>
		<content:encoded><![CDATA[<p>Sorry Michael, fired and forgot on this comment &#8211; no &#8211; it was a dotcom and an ie. </p>
<p>BTW subscribe to comments plugin for WP is great. ;o)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.michaelwall.co.uk/seo/mutiple-domains-names/comment-page-1/#comment-2779</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 16 Mar 2009 15:37:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelwall.co.uk/?p=80#comment-2779</guid>
		<description>Hi Paul,

Was the original a .co.uk name?</description>
		<content:encoded><![CDATA[<p>Hi Paul,</p>
<p>Was the original a .co.uk name?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Anthony</title>
		<link>http://www.michaelwall.co.uk/seo/mutiple-domains-names/comment-page-1/#comment-2778</link>
		<dc:creator>Paul Anthony</dc:creator>
		<pubDate>Mon, 16 Mar 2009 09:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelwall.co.uk/?p=80#comment-2778</guid>
		<description>Michael,

I came up against this problem before a few years back, with alot of users in the south using ESAT as there homepage. 

The programmers had defaulted the google box on esat&#039;s homepage to Google.ie, meaning a large chunk of ROI traffic was getting pushed towards Google&#039;s i.e. domain - that in combination with Google geo-targetting meant that we were missing some traffic opportunities in the south. With this being a big market for the company (based in the North) - we had to come up with some solution.

My advice would be to register a .ie and chase different keywords, putting different content on it. For the client in question we linked heavily between the two domains, and ran quirky linkbaity (competitions etc) on the IE, to try and gain traction faster. Google Webmaster tools allows you to target each market for each domain, but this is something I personally feel Google needs to address. We achieved moderate success with this approach, and started to rank for phrases more on the .IE - works particularly well for geographic related phrases. Which you&#039;ve mentioned.

&quot;Furniture in Monaghan&quot; for example.

Geo targetting from a user perspective should be optional, and the results set is the same unless you specify you want it to be GEO specific. It would mean sending someone a link to a Google result would be universally the same. Throw google&#039;s approach to personal results, and there&#039;s another spanner in the works. 

I can see what they are doing, but I don&#039;t necessarily agree with it.</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>I came up against this problem before a few years back, with alot of users in the south using ESAT as there homepage. </p>
<p>The programmers had defaulted the google box on esat&#8217;s homepage to Google.ie, meaning a large chunk of ROI traffic was getting pushed towards Google&#8217;s i.e. domain &#8211; that in combination with Google geo-targetting meant that we were missing some traffic opportunities in the south. With this being a big market for the company (based in the North) &#8211; we had to come up with some solution.</p>
<p>My advice would be to register a .ie and chase different keywords, putting different content on it. For the client in question we linked heavily between the two domains, and ran quirky linkbaity (competitions etc) on the IE, to try and gain traction faster. Google Webmaster tools allows you to target each market for each domain, but this is something I personally feel Google needs to address. We achieved moderate success with this approach, and started to rank for phrases more on the .IE &#8211; works particularly well for geographic related phrases. Which you&#8217;ve mentioned.</p>
<p>&#8220;Furniture in Monaghan&#8221; for example.</p>
<p>Geo targetting from a user perspective should be optional, and the results set is the same unless you specify you want it to be GEO specific. It would mean sending someone a link to a Google result would be universally the same. Throw google&#8217;s approach to personal results, and there&#8217;s another spanner in the works. </p>
<p>I can see what they are doing, but I don&#8217;t necessarily agree with it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
