<?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: What&#8217;s in a domain name</title>
	<atom:link href="http://www.web-ramblings.co.uk/whats-in-a-domain-name/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.web-ramblings.co.uk/whats-in-a-domain-name/</link>
	<description>Ramblings of a web designer / developer</description>
	<lastBuildDate>Sat, 27 Mar 2010 15:49:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: kirstyburgoine</title>
		<link>http://www.web-ramblings.co.uk/whats-in-a-domain-name/comment-page-1/#comment-89</link>
		<dc:creator>kirstyburgoine</dc:creator>
		<pubDate>Fri, 29 Jan 2010 22:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-ramblings.co.uk/?p=45#comment-89</guid>
		<description>Personally, I think that if you want to protect all of those domain names, buy them and forward them to the main website. That&#039;s perfectly fine.

The danger with this technique is if you forward them to less relevant pages that have been optimised for keywords that are not relevant, that&#039;s when you will be penalized by search engines.

:)</description>
		<content:encoded><![CDATA[<p>Personally, I think that if you want to protect all of those domain names, buy them and forward them to the main website. That&#8217;s perfectly fine.</p>
<p>The danger with this technique is if you forward them to less relevant pages that have been optimised for keywords that are not relevant, that&#8217;s when you will be penalized by search engines.</p>
<p> <img src='http://www.web-ramblings.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Everard</title>
		<link>http://www.web-ramblings.co.uk/whats-in-a-domain-name/comment-page-1/#comment-88</link>
		<dc:creator>Ben Everard</dc:creator>
		<pubDate>Fri, 29 Jan 2010 22:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-ramblings.co.uk/?p=45#comment-88</guid>
		<description>Ok but how many aliases are too many? For example with the name Joe Bloggs I would probably want the following:

joebloggs.co.uk
joebloggs.com
joe-bloggs.co.uk
joe-bloggs.com

This may seem a bit excessive, but I can&#039;t help but think they are all too similar, purchasing all will protect ones name and thus their brand. 

Just a thought, be good to think what you all think :-)</description>
		<content:encoded><![CDATA[<p>Ok but how many aliases are too many? For example with the name Joe Bloggs I would probably want the following:</p>
<p>joebloggs.co.uk<br />
joebloggs.com<br />
joe-bloggs.co.uk<br />
joe-bloggs.com</p>
<p>This may seem a bit excessive, but I can&#8217;t help but think they are all too similar, purchasing all will protect ones name and thus their brand. </p>
<p>Just a thought, be good to think what you all think <img src='http://www.web-ramblings.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kirstyburgoine</title>
		<link>http://www.web-ramblings.co.uk/whats-in-a-domain-name/comment-page-1/#comment-17</link>
		<dc:creator>kirstyburgoine</dc:creator>
		<pubDate>Sun, 18 Oct 2009 14:38:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-ramblings.co.uk/?p=45#comment-17</guid>
		<description>Thanks for your comments guys,

Some of those domain names are disastrous! ~ grin! 

The Experts Exchange url is a good example of why hyphenated domain names are sometimes a very good idea!</description>
		<content:encoded><![CDATA[<p>Thanks for your comments guys,</p>
<p>Some of those domain names are disastrous! ~ grin! </p>
<p>The Experts Exchange url is a good example of why hyphenated domain names are sometimes a very good idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Randall</title>
		<link>http://www.web-ramblings.co.uk/whats-in-a-domain-name/comment-page-1/#comment-16</link>
		<dc:creator>Paul Randall</dc:creator>
		<pubDate>Sun, 18 Oct 2009 13:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-ramblings.co.uk/?p=45#comment-16</guid>
		<description>Some really interesting points here. It&#039;s something that is sometimes taken for granted (with sometimes disasterous consequences!)

http://www.msmobilenews.com/windows-mobile/news/bad-choice-of-domain-names-its-silly.html

The advantage of choosing a brand as the domain name, is that it is (possibly) easy to spell; The story of the Kodak brand name came to mind (here is a potted version):

Why the name Kodak? It was short, and easy to pronounce. In the 1920s Eastman wrote: The letter &quot;K&quot; had been a favourite with me - it seems a strong, incisive sort of letter. It became a question of trying out a great number of combinations of letters that made words starting and ending with &quot;K&quot;.

But what I dislike at the moment is the current trend of removing vowels, or making up domains with so called &#039;domain hacks&#039; - great for a unique name, but harder when a domain is just heard and not written down.

Regarding hyphens in a domain, I think Matt Cutts of Google sums it up best: &quot;Google doesn’t algorithmically penalize for dashes in the url&quot; - http://www.mattcutts.com/blog/dashes-vs-underscores/</description>
		<content:encoded><![CDATA[<p>Some really interesting points here. It&#8217;s something that is sometimes taken for granted (with sometimes disasterous consequences!)</p>
<p><a href="http://www.msmobilenews.com/windows-mobile/news/bad-choice-of-domain-names-its-silly.html" rel="nofollow">http://www.msmobilenews.com/windows-mobile/news/bad-choice-of-domain-names-its-silly.html</a></p>
<p>The advantage of choosing a brand as the domain name, is that it is (possibly) easy to spell; The story of the Kodak brand name came to mind (here is a potted version):</p>
<p>Why the name Kodak? It was short, and easy to pronounce. In the 1920s Eastman wrote: The letter &#8220;K&#8221; had been a favourite with me &#8211; it seems a strong, incisive sort of letter. It became a question of trying out a great number of combinations of letters that made words starting and ending with &#8220;K&#8221;.</p>
<p>But what I dislike at the moment is the current trend of removing vowels, or making up domains with so called &#8216;domain hacks&#8217; &#8211; great for a unique name, but harder when a domain is just heard and not written down.</p>
<p>Regarding hyphens in a domain, I think Matt Cutts of Google sums it up best: &#8220;Google doesn’t algorithmically penalize for dashes in the url&#8221; &#8211; <a href="http://www.mattcutts.com/blog/dashes-vs-underscores/" rel="nofollow">http://www.mattcutts.com/blog/dashes-vs-underscores/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Kinsey</title>
		<link>http://www.web-ramblings.co.uk/whats-in-a-domain-name/comment-page-1/#comment-15</link>
		<dc:creator>Andy Kinsey</dc:creator>
		<pubDate>Sun, 18 Oct 2009 13:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-ramblings.co.uk/?p=45#comment-15</guid>
		<description>ohhhh bug bear of mine... dates in url&#039;s .... but lets not go there ;)</description>
		<content:encoded><![CDATA[<p>ohhhh bug bear of mine&#8230; dates in url&#8217;s &#8230;. but lets not go there <img src='http://www.web-ramblings.co.uk/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Kinsey</title>
		<link>http://www.web-ramblings.co.uk/whats-in-a-domain-name/comment-page-1/#comment-14</link>
		<dc:creator>Andy Kinsey</dc:creator>
		<pubDate>Sun, 18 Oct 2009 13:24:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.web-ramblings.co.uk/?p=45#comment-14</guid>
		<description>Given this is the second time i&#039;ve wrote this due to my silly internet i will keep it short and sweet.

This is a pretty damn good article, the only thing i&#039;d be careful of is not linking your domain with your audience, certain words will alienate certain members of your audience! such as using &quot;hip&quot; or &quot;slang&quot; words will turn off the older population generally... 

secondly use of hyphens... ok has no effect on search engines but again remember the user in this having seven or eight of them means you won&#039;t be remembered... keep domains short if including them... also as part of branding attempt to keep the same structure such that if you have a domain with hyphens for one part of your company have it for another even if its only a redirect (301). 

otherwise superb article ... wrote one not to dissimilar in april - http://andykinsey.co.uk/designing-urls-top-10-rules/2009/

nice post.</description>
		<content:encoded><![CDATA[<p>Given this is the second time i&#8217;ve wrote this due to my silly internet i will keep it short and sweet.</p>
<p>This is a pretty damn good article, the only thing i&#8217;d be careful of is not linking your domain with your audience, certain words will alienate certain members of your audience! such as using &#8220;hip&#8221; or &#8220;slang&#8221; words will turn off the older population generally&#8230; </p>
<p>secondly use of hyphens&#8230; ok has no effect on search engines but again remember the user in this having seven or eight of them means you won&#8217;t be remembered&#8230; keep domains short if including them&#8230; also as part of branding attempt to keep the same structure such that if you have a domain with hyphens for one part of your company have it for another even if its only a redirect (301). </p>
<p>otherwise superb article &#8230; wrote one not to dissimilar in april &#8211; <a href="http://andykinsey.co.uk/designing-urls-top-10-rules/2009/" rel="nofollow">http://andykinsey.co.uk/designing-urls-top-10-rules/2009/</a></p>
<p>nice post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
