<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Todd Huss &#187; Search Engine Optimization</title>
	<atom:link href="http://gabrito.com/post/category/technical/search-engine-optimization/feed" rel="self" type="application/rss+xml" />
	<link>http://gabrito.com</link>
	<description>Anecdotes on Technology Leadership, Ruby, Java, Scala, Cloud Computing, Open-Source, SEO, and Design</description>
	<lastBuildDate>Thu, 08 Dec 2011 00:21:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Search engine cloaking, it&#8217;s the intent that matters</title>
		<link>http://gabrito.com/post/search-engine-cloaking-its-the-intent-that-matters</link>
		<comments>http://gabrito.com/post/search-engine-cloaking-its-the-intent-that-matters#comments</comments>
		<pubDate>Tue, 17 Apr 2007 01:01:32 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/search-engine-cloaking-its-the-intent-that-matters</guid>
		<description><![CDATA[Back at the end of 2005 I wrote a short post titled Cloaking, no need to be ashamed and now in 2007 even more big sites are practicing some form of search engine crawler targeted cloaking. Yet still most SEO&#8217;s &#8230; <a href="http://gabrito.com/post/search-engine-cloaking-its-the-intent-that-matters">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Back at the end of 2005 I wrote a short post titled <a href="http://gabrito.com/post/cloaking-no-need-to-be-ashamed">Cloaking, no need to be ashamed</a> and now in 2007 even more big sites are practicing some form of <a href="http://en.wikipedia.org/wiki/Cloaking">search engine crawler targeted cloaking</a>. Yet still most SEO&#8217;s will give you a blanket answer and tell you to avoid cloaking so you don&#8217;t get delisted. I take a more pragmatic view and experience has taught me that certain forms of cloaking can be good!<br />
<span id="more-174"></span><br />
Cloaking all comes down to intent and to that end I&#8217;d like to illustrate a few legitimate (in my opinion) forms of cloaking in the real world:</p>
<p><!--adsense--></p>
<p>1. <strong><a href="http://www.amazon.com">Amazon.com</a></strong>: set your user agent to Googlebot and you won&#8217;t see a search box anymore. Crawlers don&#8217;t do forms and Amazon saves some bandwidth.<br />
2. <strong><a href="http://www.yahoo.com">Yahoo.com</a></strong>: almost every link is rewritten to go through a click tracking redirect but not so for crawlers. Yahoo doesn&#8217;t count the clicks from crawlers which is good for their metrics and the sites they link to get non redirected inbound links.<br />
3. <strong><a href="http://www.salon.com">Salon.com</a></strong>: crawlers get the real home page without having to see a full page ad first. I think I&#8217;ll start surfing Salon as Googlebot from now on <img src='http://gabrito.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /><br />
4. <strong><a href="http://www.cnn.com">CNN.com</a>, <a href="http://www.msn.com">MSN</a>, <a href="myspace.com">Myspace</a>, and <a href="http://www.ebay.com">EBay.com</a></strong>: crawlers don&#8217;t get served ad serving code saving bandwidth.</p>
<p>In all of the above cases these sites are serving adjusted content targeted to search engine user agents and generally it&#8217;s for the good. In the end the decision to cloak or not all comes down to good judgment and intent. If it helps crawlers avoid duplicate content or saves bandwidth then we shouldn&#8217;t be so quick to write off cloaking just because it has such a negative connotation. That said, if there&#8217;s any doubt in your mind be very weary and seek expert opinions because getting delisted for bad cloaking can result in a lot of lost revenue!</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/search-engine-cloaking-its-the-intent-that-matters/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Search Engine Friendly URLs with Ruby on Rails</title>
		<link>http://gabrito.com/post/search-engine-friendly-urls-in-rails</link>
		<comments>http://gabrito.com/post/search-engine-friendly-urls-in-rails#comments</comments>
		<pubDate>Mon, 05 Feb 2007 04:58:53 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Ruby on Rails]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[Software Engineering]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/search-engine-friendly-urls-in-rails</guid>
		<description><![CDATA[Update 2/5/07: I&#8217;ve since discovered five plugins that address this very problem with slightly different approaches (the latter two store a permalink in the table, good for mutable titles): acts_as_sluggable acts_as_urlnameable acts_as_slugable acts_as_friendly_param permalink_fu Obie&#8217;s recent post on search engine &#8230; <a href="http://gabrito.com/post/search-engine-friendly-urls-in-rails">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><strong>Update 2/5/07</strong>: I&#8217;ve since discovered five plugins that address this very problem with slightly different approaches (the latter two store a permalink in the table, good for mutable titles):</p>
<ul>
<li><a href="http://tore.darell.no/pages/5-acts-as-sluggable">acts_as_sluggable</a></li>
<li><a href="http://gabriel.gironda.org/articles/2006/03/09/acts_as_urlnameable-released">acts_as_urlnameable</a></li>
<li><a href="http://multi-up.ca/code/">acts_as_slugable</a></li>
<li><a href="http://www.chrisfarms.com/2007/2/11/seo-friendly-urls-in-rails">acts_as_friendly_param</a></li>
<li><a href="http://mephistoblog.com/2007/1/14/improved-url-escaping-for-permalinks">permalink_fu</a>
</ul>
<p><a href="http://www.jroller.com/page/obie?entry=seo_optimization_of_urls_in">Obie&#8217;s recent post on search engine friendly URL&#8217;s in Ruby on Rails 1.2 and greater</a> couldn&#8217;t have been more timely. I was about to tackle search engine friendly URL&#8217;s on my little local <a href="http://gearandboats.com/">san francisco bay area boating classifieds</a> site and after reading his blog post, 15 minutes later it was done. Here&#8217;s the old URL structure:<br />
<span id="more-172"></span><br />
<a href="http://gearandboats.com/forums/1/topics/51">http://gearandboats.com/forums/1/topics/51</a></p>
<p>and the new (longer for humans but much better for SEO):</p>
<p><a href="http://gearandboats.com/forums/1-boats/topics/51-fantasia-35-mark-ii-cruiser">http://gearandboats.com/forums/1-boats/topics/51-fantasia-35-mark-ii-cruiser</a></p>
<p>The most important thing is that the URL&#8217;s are backwards compatible because everything after the ID is ignored which is key for pages that are already in the search engines!</p>
<p><!--adsense--></p>
<p>To achieve this I combined <a href="http://www.jroller.com/page/obie?entry=seo_optimization_of_urls_in">Obie&#8217;s approach</a> with <a href="http://mephistoblog.com/2007/1/14/improved-url-escaping-for-permalinks">Ricks Permalink_fu plugin</a> (for converting text to permalinks):</p>
<pre>script/plugin install http://svn.techno-weenie.net/projects/plugins/permalink_fu</pre>
<p>Then in my topic.rb model object I do:</p>
<div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">def to_param<br />
&amp;nbsp;&amp;nbsp;&quot;#{id}-#{PermalinkFu.escape(title)}&quot;<br />
end</div></div>
<p>and I double checked to make sure that the views always call link_to passing the model object rather than the ID (so that the to_param method has access to the id and the title). Fortunately <a href="http://beast.caboo.se/">beast.caboo.se</a> (which is what I based my site on) make heavy use of named routes:</p>
<div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">&lt;%= link_to h(topic.title), topic_path(@forum, topic) %&gt;</div></div>
<p>After that I was pretty much done but I had some really long URL&#8217;s so I truncated the title to the first 5 words by changing</p>
<div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">PermalinkFu.escape(title)</div></div>
<p>to</p>
<div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">PermalinkFu.escape(title.split[0..4].join(' '))</div></div>
<p>.</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/search-engine-friendly-urls-in-rails/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Tracking your SEO pagerank</title>
		<link>http://gabrito.com/post/tracking-your-seo-pagerank</link>
		<comments>http://gabrito.com/post/tracking-your-seo-pagerank#comments</comments>
		<pubDate>Wed, 12 Apr 2006 18:59:48 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Search Engine Optimization]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/tracking-your-seo-pagerank</guid>
		<description><![CDATA[I&#8217;ve started using Sitening&#8217;s free SEO SERP tracker to track the position of GreatSchools.net for terms we want to rank for in Google. If you rely on search traffic and want to keep track of how you&#8217;re ranking for certain &#8230; <a href="http://gabrito.com/post/tracking-your-seo-pagerank">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve started using <a href="http://www.sitening.com/tools/serp-tracker/">Sitening&#8217;s free SEO SERP tracker</a> to track the position of <a href="http://www.greatschools.net">GreatSchools.net</a> for terms we want to rank for in Google. If you rely on search traffic and want to keep track of how you&#8217;re ranking for certain keywords I highly recommend checking it out, they&#8217;ve done a great job!</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/tracking-your-seo-pagerank/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using image tags (for style elements) in HTML is bad design</title>
		<link>http://gabrito.com/post/using-image-tags-in-html-is-bad-design</link>
		<comments>http://gabrito.com/post/using-image-tags-in-html-is-bad-design#comments</comments>
		<pubDate>Tue, 11 Apr 2006 15:56:37 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/using-image-tags-in-html-is-bad-design</guid>
		<description><![CDATA[Update 4/11/06: I&#8217;ve received some criticism on this post from people who assumed I was saying you should never use image tags in HTML. My bad for the misleading title, I&#8217;ve added to the title in parens to be more &#8230; <a href="http://gabrito.com/post/using-image-tags-in-html-is-bad-design">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><strong>Update 4/11/06:</strong> I&#8217;ve received <a href="http://weblog.halogenlabs.com/?p=489">some criticism</a> on this post from people who assumed I was saying you should never use image tags in HTML. My bad for the misleading title, I&#8217;ve added to the title in parens to be more concise! For those that didn&#8217;t read the whole post, in the last paragraph I say that it&#8217;s <strong>fine to use HTML image tags for content</strong>, I just think it&#8217;s bad design to use image tags for style elements. Anyhow, thanks for all the feedback (postive and negative) and here&#8217;s the original post:</p>
<p>CSS offers us a lot of power to style and decorate our pages with images, however, replacing text with an image is one gap not well addressed by CSS such that you often see sites doing: </p>
<p><strong>&lt;a href=&#8221;/&#8221;&gt;&lt;img alt=&#8221;Home&#8221; src=&#8221;home.gif&#8221;/&gt;&lt;/a&gt;</strong> </p>
<p>which is obviously bad for 2 reasons:<br />
<span id="more-127"></span><br />
1. It violates the separation of content and design by including a design element in your HTML<br />
2. Your SEO will suffer because image alt tags don&#8217;t carry as much weight as real text</p>
<p>As a result a number of people have come up with <a href="http://www.mezzoblue.com/tests/revised-image-replacement/">clever image replacement techniques in CSS</a>. It began in 2003 with the <a href="http://www.stopdesign.com/also/articles/replace_text/">Fahrner Image Replacement technique (or Classic FIR)</a>, however, the technique I currently favor is the <a href="http://phark.typepad.com/phark/2003/08/accessible_imag.html">Mike Rundle&#8217;s Phark revised method</a> which:</p>
<p><!--adsense--></p>
<p>1. Works well cross browser (but be sure to test in IE 5 for possible issues if you&#8217;re still supporting it)<br />
2. Works with a <a href="http://www.freedomscientific.com/fs_products/software_jaws.asp">screen reader such as JAWS</a> for accessibility<br />
3. Works well for SEO (many techniques style the text with display:none which likely won&#8217;t work with the next generation of crawlers such as Google&#8217;s new Mozilla based crawler)</p>
<p>Taking the example above, the correct approach would be as follows:</p>
<p><strong>&lt;a id=&#8221;home&#8221; href=&#8221;/&#8221;&gt;Home&lt;/a&gt;</strong></p>
<p>Then apply the Phark revised method via CSS:</p>
<p><strong>#home {<br />
&#160;	display: block;<br />
&#160;	text-indent: -9000px;<br />
&#160;	background: url(/images/home.gif) no-repeat;<br />
&#160;	height: 25px;<br />
&#160;	width: 100px;<br />
}</strong>	</p>
<p>Here&#8217;s the result: </p>
<p><a style="display: block; text-indent: -9000px;background: url(http://gabrito.com/files/home.gif) no-repeat;height: 25px;width: 100px;" href="/">About Us</a></p>
<p>Now we&#8217;ve replaced the text with an image yet still kept the separation of content and design clean. I stated that it&#8217;s bad design to use image tags in your HTML but I&#8217;d like to qualify that, it&#8217;s fine if your &#8220;content&#8221; is an image such as a product photograph in a web catalog, a graph, or a headshot in your user profile. Also I think it&#8217;s fine to bail on image replacement if you start wasting a lot of time in CSS layout land, it&#8217;s just good to start with the clean text based approach first and use it until it becomes impractical.</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/using-image-tags-in-html-is-bad-design/feed</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Crawler side effects of using XHTML entity references</title>
		<link>http://gabrito.com/post/crawler-side-effects-of-using-xhtml-entity-references</link>
		<comments>http://gabrito.com/post/crawler-side-effects-of-using-xhtml-entity-references#comments</comments>
		<pubDate>Thu, 06 Apr 2006 01:20:29 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/crawler-side-effects-of-using-xhtml-entity-references</guid>
		<description><![CDATA[We&#8217;re slowly moving towards making GreatSchools XHTML compliant (we have a long way to go though)! To start we&#8217;ve begun using proper XHTML entity references for URL&#8217;s with &#38;amp; as a separator instead of plain old &#38; in a few &#8230; <a href="http://gabrito.com/post/crawler-side-effects-of-using-xhtml-entity-references">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We&#8217;re slowly moving towards making GreatSchools XHTML compliant (we have a long way to go though)! To start we&#8217;ve begun using proper XHTML entity references for URL&#8217;s with &amp;amp; as a separator instead of plain old &amp; in a few places.<br />
<span id="more-125"></span><br />
What&#8217;s interesting about this is that we&#8217;re seeing some errors in our weblogs of IP&#8217;s with modern user agents trying to access pages via: <strong>GET /foo.page?param1=value1&amp;amp;param2=value2</strong> instead of <strong>GET /foo.page?param1=value1&amp;param2=value2</strong>.</p>
<p><!--adsense--></p>
<p>I&#8217;ve tested extensively in modern browsers across platforms and haven&#8217;t found a single browser that doesn&#8217;t translate the entity references properly. I suspect most of these are actually email harvesting crawlers just taking the value of the HREF and throwing it into a GET request without properly translating entity references.</p>
<p>I think we may have found one more way to identify crawlers masquerading behind real looking user agents!</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/crawler-side-effects-of-using-xhtml-entity-references/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Java&#8217;s SEO blunder: jsessionid</title>
		<link>http://gabrito.com/post/javas-seo-blunder-jsessionid</link>
		<comments>http://gabrito.com/post/javas-seo-blunder-jsessionid#comments</comments>
		<pubDate>Wed, 05 Apr 2006 03:46:28 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/javas-seo-blunder-jsessionid</guid>
		<description><![CDATA[Update: Bryce pointed out a servlet filter you can implement to disable JSESSIONID&#8217;s&#8230; very nice! When we started moving GreatSchools from Perl to Java + SpringMVC + Hibernate one of the first things we had to figure out was how &#8230; <a href="http://gabrito.com/post/javas-seo-blunder-jsessionid">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><strong>Update:</strong> <a href="http://www.obviously.com/">Bryce</a> pointed out a <a href="http://randomcoder.com/articles/jsessionid-considered-harmful">servlet filter you can implement</a> to disable JSESSIONID&#8217;s&#8230; very nice!</p>
<p>When we started moving GreatSchools from Perl to Java + SpringMVC + Hibernate one of the first things we had to figure out was how to disable <strong>jsessionid</strong>&#8216;s from getting appended to URL&#8217;s when using c:url in a JSP page. <a href="http://www.webmasterworld.com/forum3/5624.htm">Jsessionid is terrible for search engine optimization</a> because crawlers that don&#8217;t have cookies enabled will get URL&#8217;s from your pages with a jsessionid parameter appended. This makes it virtually impossible for a crawler to match the URL from an inbound link to your site with a page it has already crawled. What&#8217;s worse is that you risk having your page rank hurt with Google because it thinks you&#8217;re serving duplicate content, ouch!<br />
<span id="more-124"></span><br />
Take one look on Google and you&#8217;ll see <a href="http://www.google.com/search?hl=en&#038;lr=&#038;q=inurl%3Ajsessionid&#038;btnG=Search">millions of results that contain jsessionid in the URL</a>, those pages will have a tougher time ranking well against competitors that have consistent URL&#8217;s for users and crawlers. </p>
<p><!--adsense--></p>
<p>The intention is good: allow sessions to work for users that don&#8217;t have cookies enabled. In reality it never worked that well though because most sites use c:url sporadically to properly encode URL&#8217;s and most sites require cookies as a site policy anyhow. The <a href="http://theserverpages.com/php/manual/en/ref.session.php">PHP session handling code has the same issue</a> which many folks have battled with, fortunately for PHP users, it&#8217;s an option you can disable in your php.ini by setting session.use_only_cookies.</p>
<p>At GreatSchools we wrote our own version of c:url since we couldn&#8217;t find any way to disable c:url from writing out jsessionid&#8217;s. I think the time is right to make <em>session handling with cookies only</em> the default because it&#8217;s the more common scenario and that particular <em>&#8220;feature&#8221;</em> has caused more problems than the good it was initially intended to do. </p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/javas-seo-blunder-jsessionid/feed</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Search engine market share changing is an understatement</title>
		<link>http://gabrito.com/post/search-market-share-changing-is-an-understatement</link>
		<comments>http://gabrito.com/post/search-market-share-changing-is-an-understatement#comments</comments>
		<pubDate>Thu, 30 Mar 2006 17:10:02 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Search Engine Optimization]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/search-market-share-changing-is-an-understatement</guid>
		<description><![CDATA[The market share change between Google and Yahoo has been breathtaking this past year! The article Google gains search share, widens lead on Yahoo (over at Yahoo news) indicates Google&#8217;s market share was 36.3% a year ago and now it&#8217;s &#8230; <a href="http://gabrito.com/post/search-market-share-changing-is-an-understatement">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The market share change between Google and Yahoo has been breathtaking this past year! The article <a href="http://news.yahoo.com/s/nm/20060328/bs_nm/google_search_dc_1">Google gains search share, widens lead on Yahoo</a> (over at Yahoo news) indicates Google&#8217;s market share was 36.3% a year ago and now it&#8217;s up to 42.3% while Yahoo was 31.1% and is now down to 27.6%. </p>
<p><span id="more-123"></span></p>
<p>What I&#8217;ve been seeing at GreatSchools is a lot more dramatic! For example our traffic from Google now accounts for 69% of search traffic (up from 49% a year ago) and Yahoo now accounts for 23% (down from 40% a year ago). That&#8217;s not just a slight market change, it&#8217;s a drastic market shift!</p>
<p><!--adsense--></p>
<p>Jeremy wrote an <a href="http://jeremy.zawodny.com/blog/archives/005575.html">interesting article on referrer traffic</a> last October and how in his case it varies so dramatically from the publicly stated market share numbers. To be honest, I&#8217;ve never come across a site that gets as much traffic from Yahoo, AOL, or MSN as the published market share numbers indicate one should and many of the websites I&#8217;ve worked on are not technology focused at all. I suspect in reality Google has more market share than the publicly available numbers really indicate!</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/search-market-share-changing-is-an-understatement/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Keeping current with SEO</title>
		<link>http://gabrito.com/post/keeping-current-with-seo</link>
		<comments>http://gabrito.com/post/keeping-current-with-seo#comments</comments>
		<pubDate>Fri, 24 Mar 2006 18:41:44 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/keeping-current-with-seo</guid>
		<description><![CDATA[Keeping current with SEO has always been a challenge for me, it reminds me of paying bills, you have to do it but you don&#8217;t always want to. However, as the majority of our traffic comes from search, staying on &#8230; <a href="http://gabrito.com/post/keeping-current-with-seo">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Keeping current with SEO has always been a challenge for me, it reminds me of paying bills, you have to do it but you don&#8217;t always want to. However, as the majority of our traffic comes from search, staying on top of it is important and as a result we&#8217;ve seen massive traffic growth<span id="more-117"></span> to old pages that we&#8217;ve optimized. </p>
<p>For the most part SEO is a simple equation of inbound links, keyword density, proper HTML, and URL structure. Do <a href="http://dottactics.blogspot.com/2006/03/21-fastest-seo-tips.html">these SEO practices</a> well and ethically (what they call <a href="http://www.alistapart.com/articles/accessibilityseo">white hat</a>) long enough with a great web product that users like and you&#8217;ll rank well, period. </p>
<p><!--adsense--></p>
<p>Where it gets tricky is keeping current with subtle changes such as moving URLs via 301 redirect (which you should probably hold off on until <a href="http://www.mattcutts.com/blog/bigdaddy/">Big Daddy</a> settles in), the importance of contextual relevance in inbound links, using a long lived domain name over a new domain, etc&#8230;</p>
<p>A while back I discovered the <a href="http://www.webmasterradio.fm/episodes/index.php?showId=16">SEO Rockstars</a> podcast and as a result now I spend much less time each month having to piece together blogs, webmasterworld, searchenginewatch, etc&#8230; However, if you&#8217;ve ever had any doubt as to whether SEO belongs in the sales/marketing department of a company, the intro theme song says it all&#8230; &#8220;jammin and spammin&#8221;&#8230; uh&#8230; the 80&#8242;s called and they want their <a href="http://www.defleppard.com/">Def Leppard</a> tune back. Seriously though, <a href="http://www.webguerrilla.com/">Greg &#8220;Webguerrilla&#8221; Boser</a> and <a href="http://www.oilman.ca/">Todd &#8220;Oilman&#8221; Friesen</a> really know their stuff and if you too have to stay on top of SEO then I&#8217;d recommend <a href="http://www.webmasterradio.fm/episodes/index.php?showId=16">subscribing to their podcast</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/keeping-current-with-seo/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Nofollow hurts bloggers more than spammers</title>
		<link>http://gabrito.com/post/nofollow-hurts-bloggers-more-than-spammers</link>
		<comments>http://gabrito.com/post/nofollow-hurts-bloggers-more-than-spammers#comments</comments>
		<pubDate>Fri, 03 Feb 2006 23:00:19 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/nofollow-hurts-bloggers-more-than-spammers</guid>
		<description><![CDATA[Nofollow really took off in the blogging community as a means to stop comment spammers and I think at this point it&#8217;s safe to say that it&#8217;s had absolutely no effect on that front. What&#8217;s worse is that it&#8217;s the &#8230; <a href="http://gabrito.com/post/nofollow-hurts-bloggers-more-than-spammers">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.linkcondom.com/">Nofollow</a> really took off in the blogging community as a means to <a href="http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html">stop comment spammers</a> and I think at this point it&#8217;s safe to say that it&#8217;s had <a href="http://www.ioerror.us/2005/05/23/nofollow-revisited/">absolutely no effect on that front</a>. What&#8217;s worse is that it&#8217;s the wrong approach to prevent spam as it punishes readers who leave insightful comments or trackbacks by withholding the link value they get in exchange for participating. If someone is willing to take the time to leave a comment we should be more than happy to give them the link value. The only thing nofollow does effectively is hurt the pagerank of active blog participants which was never the desired effect! For comment spam we need to stick with less draconian approaches like <a href="http://akismet.com/">Akismet</a> and Captcha.</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/nofollow-hurts-bloggers-more-than-spammers/feed</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>SEO Toolbox</title>
		<link>http://gabrito.com/post/seo-toolbox</link>
		<comments>http://gabrito.com/post/seo-toolbox#comments</comments>
		<pubDate>Mon, 09 Jan 2006 19:28:28 +0000</pubDate>
		<dc:creator>Todd Huss</dc:creator>
				<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://gabrito.com/post/seo-toolbox</guid>
		<description><![CDATA[At work when we design a new page that we hope to drive people to via search engines we often consult with our search engine consultant to ensure we&#8217;ve thought through the page design and that the HTML is up &#8230; <a href="http://gabrito.com/post/seo-toolbox">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>At work when we design a new page that we hope to drive people to via search engines we often consult with our search engine consultant to ensure we&#8217;ve thought through the page design and that the HTML is up to snuff (e.g. proper use of the title, h1, h2, etc&#8230; tags). We&#8217;ve also seen dramatic increases to older pages when we&#8217;ve gone through a round of search optimization on the page so I&#8217;m convinced that SEO work is time well spent.</p>
<p>A coworker recently sent me a link to the free <a href="http://www.sitening.com/tools/seo-analyzer/">SEO Analyzer tool</a> which looks like it might be helpful in the process. I don&#8217;t think it will ever replace our SEO consultant but it&#8217;s good to have tools like this in the arsenal. The other tools we use regularly are the <a href="https://adwords.google.com/select/KeywordSandbox">Google Adwords Selector tool</a> and the <a href="http://inventory.overture.com/d/searchinventory/suggestion/">Overture Keyword Selector tool</a> for helping us get the most effective wording to convey the content of the page.</p>
<p>If you&#8217;re interested in learning more about SEO or are curious which blogs you should be reading I&#8217;d recommend starting with <a href="http://www.mattcutts.com/blog/best-seo-blog-of-2005/">this post</a> on <a href="http://www.mattcutts.com/blog/">Matt Cutts excellent blog</a> as he lists some great resources!</p>
]]></content:encoded>
			<wfw:commentRss>http://gabrito.com/post/seo-toolbox/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

