<?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: Securing a Marketing-Rich Domain Name</title>
	<atom:link href="http://www.polepositionmarketing.com/emp/securing-a-marketing-rich-domain-name/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.polepositionmarketing.com/emp/securing-a-marketing-rich-domain-name/</link>
	<description>Search Marketing Information to Render Your Competition Powerless!</description>
	<pubDate>Thu, 04 Dec 2008 00:56:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Stoney deGeyter</title>
		<link>http://www.polepositionmarketing.com/emp/securing-a-marketing-rich-domain-name/#comment-33664</link>
		<dc:creator>Stoney deGeyter</dc:creator>
		<pubDate>Mon, 16 Apr 2007 14:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.polepositionmarketing.com/emp/securing-a-marketing-rich-domain-name/#comment-33664</guid>
		<description>I think the problem with using hyphens for long domains is the long domain itself. I would never want domains PolePositionMarketingAdviseOnline or Pole-Position-Marketing-Advise-Online. They are too long and too hard to remember and especially using the hyphens, too complicated to type in the search box.

You're right about the 301 redirects for type-in traffic. I believe I hit on that in other articles but its always worth mentioning.</description>
		<content:encoded><![CDATA[<p>I think the problem with using hyphens for long domains is the long domain itself. I would never want domains PolePositionMarketingAdviseOnline or Pole-Position-Marketing-Advise-Online. They are too long and too hard to remember and especially using the hyphens, too complicated to type in the search box.</p>
<p>You&#8217;re right about the 301 redirects for type-in traffic. I believe I hit on that in other articles but its always worth mentioning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Jackson</title>
		<link>http://www.polepositionmarketing.com/emp/securing-a-marketing-rich-domain-name/#comment-33169</link>
		<dc:creator>Tom Jackson</dc:creator>
		<pubDate>Sat, 14 Apr 2007 14:42:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.polepositionmarketing.com/emp/securing-a-marketing-rich-domain-name/#comment-33169</guid>
		<description>Hi,
I enjoyed your articles.  I agree with most of what you have written, and they are short....

I think the discussion of hypenation can be enhanced.  The trade-off (hyphen intended) favors using hyphenated names  as one increases as the length and the number of words in the names.  For example, PolePositionMarketingAdviseOnline is not as desirable as Pole-Position-Marketing-Advise-Online.  The search engines can parse a longer hyphenated name better than a shorter one.  

The other thing I wanted to mention is that your piece on type-in names should include recommending 301-redirect for anyone using that strategy.  Use one 'landing' domain, to which all type-in names are pointed.  Then do a 301-redirect to the landing domain.  Otherwise, Google et.al. take a dim view of the arrangement.  

Looking forward to your thoughts.
Best,
tj
Nameboy</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I enjoyed your articles.  I agree with most of what you have written, and they are short&#8230;.</p>
<p>I think the discussion of hypenation can be enhanced.  The trade-off (hyphen intended) favors using hyphenated names  as one increases as the length and the number of words in the names.  For example, PolePositionMarketingAdviseOnline is not as desirable as Pole-Position-Marketing-Advise-Online.  The search engines can parse a longer hyphenated name better than a shorter one.  </p>
<p>The other thing I wanted to mention is that your piece on type-in names should include recommending 301-redirect for anyone using that strategy.  Use one &#8216;landing&#8217; domain, to which all type-in names are pointed.  Then do a 301-redirect to the landing domain.  Otherwise, Google et.al. take a dim view of the arrangement.  </p>
<p>Looking forward to your thoughts.<br />
Best,<br />
tj<br />
Nameboy</p>
]]></content:encoded>
	</item>
</channel>
</rss>
