<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: User Contributed- Typos</title>
	<link>http://www.BlueHatSEO.com/user-contributed-typos/</link>
	<description>Advanced SEO Tactics and Techniques</description>
	<pubDate>Wed, 20 Aug 2008 08:28:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: neil strauss</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-202755</link>
		<pubDate>Thu, 31 Jan 2008 16:38:59 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-202755</guid>
					<description>I have been using some common misspellings to come up top.  I just put it in my meta description tag.  Its very easy to get top position for these.</description>
		<content:encoded><![CDATA[<p>I have been using some common misspellings to come up top.  I just put it in my meta description tag.  Its very easy to get top position for these.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Vyom</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-16449</link>
		<pubDate>Tue, 20 Feb 2007 09:56:08 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-16449</guid>
					<description>You might not get much traffic even if you rank first on Google for a particular typo.Google's suggests the right spelling and it is quite efficient.

And according to me people correct their searches and  search for the right (spelled) Keyword, atleast i do that (coz it hardly takes a few seconds).</description>
		<content:encoded><![CDATA[<p>You might not get much traffic even if you rank first on Google for a particular typo.Google&#8217;s suggests the right spelling and it is quite efficient.</p>
<p>And according to me people correct their searches and  search for the right (spelled) Keyword, atleast i do that (coz it hardly takes a few seconds).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: George</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-10657</link>
		<pubDate>Tue, 16 Jan 2007 14:23:18 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-10657</guid>
					<description>http://adlab.msn.com/keyMut/default.aspx

Another helpful tool (free!) for discovering misspellings.</description>
		<content:encoded><![CDATA[<p><a href="http://adlab.msn.com/keyMut/default.aspx" rel="nofollow">http://adlab.msn.com/keyMut/default.aspx</a></p>
<p>Another helpful tool (free!) for discovering misspellings.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Robert DeVore</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-9198</link>
		<pubDate>Sat, 30 Dec 2006 14:31:12 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-9198</guid>
					<description>I've been working with artist/celeb misspellings for some time now. Great to generate some money each day from them (1-5 dollars per site). I'm in the process of doing 50 more right now before the new year. Great post.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been working with artist/celeb misspellings for some time now. Great to generate some money each day from them (1-5 dollars per site). I&#8217;m in the process of doing 50 more right now before the new year. Great post.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rose Water</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-8161</link>
		<pubDate>Mon, 18 Dec 2006 14:16:41 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-8161</guid>
					<description>I also like good keywords, it's a nice little all-in-one keyword lookup utility.

http://www.goodkeywords.com/products/updates.php?gkw2</description>
		<content:encoded><![CDATA[<p>I also like good keywords, it&#8217;s a nice little all-in-one keyword lookup utility.</p>
<p><a href="http://www.goodkeywords.com/products/updates.php?gkw2" rel="nofollow">http://www.goodkeywords.com/products/updates.php?gkw2</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: miserable failure</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-8080</link>
		<pubDate>Sun, 17 Dec 2006 23:37:06 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-8080</guid>
					<description>I promise to donate 10$ to this tool.

concerning the demand, all the other typo tools suck!@!

hey, tudor, why not target nintendo pee? 500k vs 18000k for wii. heh.

To eli: I think a bluehat-style misspelling tool would be nice. In my experience, when I mispell words its only from typing too fast and hitting a nearby key, though if someone wasn't nearly as good a speller as me, its hard to imagine how they misspell stuff. Although hooking into the google api would probably be awesome.</description>
		<content:encoded><![CDATA[<p>I promise to donate 10$ to this tool.</p>
<p>concerning the demand, all the other typo tools suck!@!</p>
<p>hey, tudor, why not target nintendo pee? 500k vs 18000k for wii. heh.</p>
<p>To eli: I think a bluehat-style misspelling tool would be nice. In my experience, when I mispell words its only from typing too fast and hitting a nearby key, though if someone wasn&#8217;t nearly as good a speller as me, its hard to imagine how they misspell stuff. Although hooking into the google api would probably be awesome.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tudor Mateeescu</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-8018</link>
		<pubDate>Sun, 17 Dec 2006 14:14:50 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-8018</guid>
					<description>Interesting.

I had some traffic from the typos.. but small.. at most 50 visitors.

I tried the common technique, and made a list with all the typos possible for that word.. no big traffic.

Maybe is important the domain of the type too.

Taking kansieo example, for &lt;a href="http://www.google.com/search?hl=en&#38;lr=&#38;safe=off&#38;client=firefox-a&#38;rls=org.mozilla%3Aen-US%3Aofficial&#38;q=nintendo+wei&#38;btnG=Search" rel="nofollow"&gt;this search&lt;/a&gt; Google has no suggestion.</description>
		<content:encoded><![CDATA[<p>Interesting.</p>
<p>I had some traffic from the typos.. but small.. at most 50 visitors.</p>
<p>I tried the common technique, and made a list with all the typos possible for that word.. no big traffic.</p>
<p>Maybe is important the domain of the type too.</p>
<p>Taking kansieo example, for <a href="http://www.google.com/search?hl=en&amp;lr=&amp;safe=off&amp;client=firefox-a&amp;rls=org.mozilla%3Aen-US%3Aofficial&amp;q=nintendo+wei&amp;btnG=Search" rel="nofollow">this search</a> Google has no suggestion.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eli</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7957</link>
		<pubDate>Sat, 16 Dec 2006 13:56:57 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7957</guid>
					<description>I don't do a lot of typo marketing or anything. I really don't put any thought into it.  However on my screensaver project(part of the 100/day post) I accidently typoed two celeb names in my rush to make all the pages. One was Jessica Alba. I didn't realize it till i started getting a ton of search traffic coming from the typo. Which of course made me decide to keep the typos on the page.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t do a lot of typo marketing or anything. I really don&#8217;t put any thought into it.  However on my screensaver project(part of the 100/day post) I accidently typoed two celeb names in my rush to make all the pages. One was Jessica Alba. I didn&#8217;t realize it till i started getting a ton of search traffic coming from the typo. Which of course made me decide to keep the typos on the page.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: kansieo</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7940</link>
		<pubDate>Sat, 16 Dec 2006 07:41:22 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7940</guid>
					<description>definitely not a waste of time...especially when targeting a high traffic/high search area.  I made a lot of money off of the nintendo wii launch from typos (and only typos--do you think me, a little guy, has any chance to rank for the term 'nintendo wii' anywhere in the top 10--let alone the top 100--against nintendo, gamestop, gamespot or any other large retailer or review site with kajillions of natural links? not likely...).  My point is, most people are bad spellers and will search on phonics (hmmm, new product?) rather than proper spelling.  terms like nntendo wii, nintendo wei, etc. generated thousands of hits for me and probably will continue to do so over the next month.

We're not even talking low hanging fruit, we're talking about the stuff that's already fallen to the ground.  While maybe not as pristine as the stuff at the top of the tree, there is plenty of it around...</description>
		<content:encoded><![CDATA[<p>definitely not a waste of time&#8230;especially when targeting a high traffic/high search area.  I made a lot of money off of the nintendo wii launch from typos (and only typos&#8211;do you think me, a little guy, has any chance to rank for the term &#8216;nintendo wii&#8217; anywhere in the top 10&#8211;let alone the top 100&#8211;against nintendo, gamestop, gamespot or any other large retailer or review site with kajillions of natural links? not likely&#8230;).  My point is, most people are bad spellers and will search on phonics (hmmm, new product?) rather than proper spelling.  terms like nntendo wii, nintendo wei, etc. generated thousands of hits for me and probably will continue to do so over the next month.</p>
<p>We&#8217;re not even talking low hanging fruit, we&#8217;re talking about the stuff that&#8217;s already fallen to the ground.  While maybe not as pristine as the stuff at the top of the tree, there is plenty of it around&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tudor Mateeescu</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7938</link>
		<pubDate>Sat, 16 Dec 2006 07:08:59 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7938</guid>
					<description>Example:
http://www.google.com/search?hl=en&#38;lr=&#38;safe=off&#38;q=Caffiene&#38;btnG=Search

Google will correct you if you misspell a word.

In my opinion generated typos are a waste of time because of google suggestion. I agree dropping a typo each and there but I wouldn't waste much time with them.</description>
		<content:encoded><![CDATA[<p>Example:<br />
<a href="http://www.google.com/search?hl=en&amp;lr=&amp;safe=off&amp;q=Caffiene&amp;btnG=Search" rel="nofollow">http://www.google.com/search?hl=en&amp;lr=&amp;safe=off&amp;q=Caffiene&amp;btnG=Search</a></p>
<p>Google will correct you if you misspell a word.</p>
<p>In my opinion generated typos are a waste of time because of google suggestion. I agree dropping a typo each and there but I wouldn&#8217;t waste much time with them.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eli</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7913</link>
		<pubDate>Fri, 15 Dec 2006 19:48:59 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7913</guid>
					<description>I'd use the google api.
search for the correct spelling and then the typo. Grab the total results. (typo/correct)*100+delimiter=percentage of occurance.

The delimiter will be a small percentage that weighs the difference between what people put up on a website and what they type naturally while searching. People tend to spell check and proof read before they put up text on a website so the typorate of a word or person name will naturally be lower than the natural. The delimiter will attempt to guess the difference.
That aside the sorting from most typoed to least typoed should be about as accurate as it can get.

All in all it should come out fairly accurate and it should work for everything(names, places, phrases) not just english words.

The other typo tools just give typo possibilties. Am I missing something or would that make this the most accurate typo tool out there? The only question that remains is, is there even a demand for a tool like this?</description>
		<content:encoded><![CDATA[<p>I&#8217;d use the google api.<br />
search for the correct spelling and then the typo. Grab the total results. (typo/correct)*100+delimiter=percentage of occurance.</p>
<p>The delimiter will be a small percentage that weighs the difference between what people put up on a website and what they type naturally while searching. People tend to spell check and proof read before they put up text on a website so the typorate of a word or person name will naturally be lower than the natural. The delimiter will attempt to guess the difference.<br />
That aside the sorting from most typoed to least typoed should be about as accurate as it can get.</p>
<p>All in all it should come out fairly accurate and it should work for everything(names, places, phrases) not just english words.</p>
<p>The other typo tools just give typo possibilties. Am I missing something or would that make this the most accurate typo tool out there? The only question that remains is, is there even a demand for a tool like this?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jon</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7912</link>
		<pubDate>Fri, 15 Dec 2006 19:26:00 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7912</guid>
					<description>How would you estimate a percentage of occurence?</description>
		<content:encoded><![CDATA[<p>How would you estimate a percentage of occurence?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eli</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7893</link>
		<pubDate>Fri, 15 Dec 2006 15:10:30 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7893</guid>
					<description>Would it be worth it for you guys if i built a typo generator/analyzer tool Blue Hat style? If you guys think you might actually use it often I'd probably be willing to build it.
Basically what it would do is, you enter a word/pronoun and it would do the qwerty thing and find all the combinations of typos. Then it would analyze each type and estimate a percentage of the time that, that particular typo happens. Then it would sort the typos by popularity.
Ie.
The- teh - Happens 13% of the time.
The- hte - Happens 7% of the time.
etc....

Whats the interest level on a tool like this?</description>
		<content:encoded><![CDATA[<p>Would it be worth it for you guys if i built a typo generator/analyzer tool Blue Hat style? If you guys think you might actually use it often I&#8217;d probably be willing to build it.<br />
Basically what it would do is, you enter a word/pronoun and it would do the qwerty thing and find all the combinations of typos. Then it would analyze each type and estimate a percentage of the time that, that particular typo happens. Then it would sort the typos by popularity.<br />
Ie.<br />
The- teh - Happens 13% of the time.<br />
The- hte - Happens 7% of the time.<br />
etc&#8230;.</p>
<p>Whats the interest level on a tool like this?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eli</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7891</link>
		<pubDate>Fri, 15 Dec 2006 15:02:56 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7891</guid>
					<description>good advice kansieo</description>
		<content:encoded><![CDATA[<p>good advice kansieo
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: kansieo</title>
		<link>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7780</link>
		<pubDate>Wed, 13 Dec 2006 10:30:08 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/user-contributed-typos/#comment-7780</guid>
					<description>Using typos what is suggested: a. a new page for each typo (including content), or b. typos included in the original (non-typoed) keyword's page? I've used both methods, and while more traffic seems to come from method a, but those pages seem to get put into supplemental index or removed altogether fairly quickly.

Also, I use a custom-made tool to generate my typos.  Currently it does the following: wrong key--replaces a letter based on nearby keyboard keys,  missed character--removes a character completely, transposed character--switches two characters around, double character--repeats a character.  It spits out a huge list (73 with "rose water" as input) but shortcomings are as Rose Water pointed out.  Hate to think of the length of the resulting keyword list if I went even deeper with multiple mispellings per keyword or adding letters in differing positions.  It will do 2/3 of the mispellings in his sentence, though...</description>
		<content:encoded><![CDATA[<p>Using typos what is suggested: a. a new page for each typo (including content), or b. typos included in the original (non-typoed) keyword&#8217;s page? I&#8217;ve used both methods, and while more traffic seems to come from method a, but those pages seem to get put into supplemental index or removed altogether fairly quickly.</p>
<p>Also, I use a custom-made tool to generate my typos.  Currently it does the following: wrong key&#8211;replaces a letter based on nearby keyboard keys,  missed character&#8211;removes a character completely, transposed character&#8211;switches two characters around, double character&#8211;repeats a character.  It spits out a huge list (73 with &#8220;rose water&#8221; as input) but shortcomings are as Rose Water pointed out.  Hate to think of the length of the resulting keyword list if I went even deeper with multiple mispellings per keyword or adding letters in differing positions.  It will do 2/3 of the mispellings in his sentence, though&#8230;
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
