<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: How to handle a machine-readable pandemic that search engines cannot control</title>
	<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/</link>
	<description>If you've read my articles somewhere on the Internet, expect something different here.</description>
	<pubDate>Thu, 02 Sep 2010 11:55:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: aimClear&#8217;s 2009 Daily Training Link Library &#187; aimClear Search Marketing Blog</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-2119</link>
		<dc:creator>aimClear&#8217;s 2009 Daily Training Link Library &#187; aimClear Search Marketing Blog</dc:creator>
		<pubDate>Fri, 01 Jan 2010 17:30:50 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-2119</guid>
		<description>[...] NoFollow Funeral Party [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] NoFollow Funeral Party [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1760</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Tue, 01 Sep 2009 15:40:41 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1760</guid>
		<description>&lt;p&gt;Daniel, although Google can and does interpret JavaScript to some extent, especially onclick trigger code, I consider "strong links" safe (of course you can abuse any other X/HTML element allowed within a P element too). By avoiding the A element the "linking" site makes perfectly clear that it doesn't vouch for the link. I assume that Google doesn't count such artificial links in their link graph. Also, the "strong link" is in fact a client sided redirect, equivalent to a 302 HTTP response code. Thus, even when counted in any way, Google should index the issuing URI. Of course all that is theory, and HTML5 providing proper syntax for such stuff will shredder it once the engines will have completely implemented HTML5.&lt;/p&gt;

&lt;p&gt;As for cloaking, the answer is no. Of course technically that's cloaking, but not deceptive cloaking in the lines of search engine quality guidelines. Usually I would quote some search engine policies to back up my allegation, but I'm kinda sick of search engines trying to rule the Web. Therefore, inspired by &lt;a href="http://twitter.com/pageoneresults/statuses/3606491628"&gt;Edward&lt;/a&gt;, I'll bring my point home by calling a higher instance, the &lt;a href=""&gt;W3C&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;&lt;strong&gt;Content is "equivalent" to other content when both fulfill essentially the same function or purpose upon presentation to the user&lt;/strong&gt; [emphasis mine].  In the context of this document, the equivalent must fulfill essentially the same function for the person with a disability (at least insofar as is feasible, given the nature of the disability and the state of technology), as the primary content does for the person without any disability. For example, the text "The Full Moon" might convey the same information as an image of a full moon when presented to users.&lt;/blockquote&gt;

&lt;p&gt;Well, a search engine crawler's disease is that it's just another algo faking a human user. As long as robots aren't more savvy than humans, there's nothing wrong with feeding them with what they can actually digest, instead of the real and high sophisticated stuff aiming at a human audience.&lt;/p&gt;


&lt;p&gt;A search engine shouldn't penalize a site for user agent optimization. There's not much difference to serving browser optimized code and contents as well. So, as said before, my suggestion is not meant to get implemented across the boards, but it's quite safe with the engines. The real shame is, that search engines force webmasters to bother with their faulty algos at all.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Daniel, although Google can and does interpret JavaScript to some extent, especially onclick trigger code, I consider &#8220;strong links&#8221; safe (of course you can abuse any other X/HTML element allowed within a P element too). By avoiding the A element the &#8220;linking&#8221; site makes perfectly clear that it doesn&#8217;t vouch for the link. I assume that Google doesn&#8217;t count such artificial links in their link graph. Also, the &#8220;strong link&#8221; is in fact a client sided redirect, equivalent to a 302 HTTP response code. Thus, even when counted in any way, Google should index the issuing URI. Of course all that is theory, and HTML5 providing proper syntax for such stuff will shredder it once the engines will have completely implemented HTML5.</p>
<p>As for cloaking, the answer is no. Of course technically that&#8217;s cloaking, but not deceptive cloaking in the lines of search engine quality guidelines. Usually I would quote some search engine policies to back up my allegation, but I&#8217;m kinda sick of search engines trying to rule the Web. Therefore, inspired by <a href="http://twitter.com/pageoneresults/statuses/3606491628">Edward</a>, I&#8217;ll bring my point home by calling a higher instance, the <a href="">W3C</a>:</p>
<blockquote><p><strong>Content is &#8220;equivalent&#8221; to other content when both fulfill essentially the same function or purpose upon presentation to the user</strong> [emphasis mine].  In the context of this document, the equivalent must fulfill essentially the same function for the person with a disability (at least insofar as is feasible, given the nature of the disability and the state of technology), as the primary content does for the person without any disability. For example, the text &#8220;The Full Moon&#8221; might convey the same information as an image of a full moon when presented to users.</p></blockquote>
<p>Well, a search engine crawler&#8217;s disease is that it&#8217;s just another algo faking a human user. As long as robots aren&#8217;t more savvy than humans, there&#8217;s nothing wrong with feeding them with what they can actually digest, instead of the real and high sophisticated stuff aiming at a human audience.</p>
<p>A search engine shouldn&#8217;t penalize a site for user agent optimization. There&#8217;s not much difference to serving browser optimized code and contents as well. So, as said before, my suggestion is not meant to get implemented across the boards, but it&#8217;s quite safe with the engines. The real shame is, that search engines force webmasters to bother with their faulty algos at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Martin</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1758</link>
		<dc:creator>Daniel Martin</dc:creator>
		<pubDate>Tue, 01 Sep 2009 09:47:56 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1758</guid>
		<description>Hmm, I agree with most of this, but I have some worries. 

First of all, you hack together your own nofollow link using strong. Given that Google seems to be able to interpret javascript to some extent is this a good idea? Might it be considered spammy? What is wrong with using a nofollow link in this case?

Secondly, you suggest that people redirect GoogleBot away from forums and guestbooks etc... Is this not a form of cloaking? Could you not get penalised for this?

Interesting article though...</description>
		<content:encoded><![CDATA[<p>Hmm, I agree with most of this, but I have some worries. </p>
<p>First of all, you hack together your own nofollow link using strong. Given that Google seems to be able to interpret javascript to some extent is this a good idea? Might it be considered spammy? What is wrong with using a nofollow link in this case?</p>
<p>Secondly, you suggest that people redirect GoogleBot away from forums and guestbooks etc&#8230; Is this not a form of cloaking? Could you not get penalised for this?</p>
<p>Interesting article though&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Thomas</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1734</link>
		<dc:creator>Michael Thomas</dc:creator>
		<pubDate>Fri, 14 Aug 2009 12:07:43 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1734</guid>
		<description>I thought no follow links were so we don't lose any valuable link juice??</description>
		<content:encoded><![CDATA[<p>I thought no follow links were so we don&#8217;t lose any valuable link juice??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spamming Assclown</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1678</link>
		<dc:creator>Spamming Assclown</dc:creator>
		<pubDate>Tue, 30 Jun 2009 23:44:58 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1678</guid>
		<description>I completely agree with your point that all blogs should become moderated ones and should be do follow, which would keep spammers in the bay and help people who chip in with quality comments. It should be a win-win game isn't it?

[Unlinked "Yuva_payday@moerpoundstillpayday.co.uk" spamming me from &lt;a href="mailto:bendonnash@yahoo.co.uk"&gt;203.76.139.118&lt;/a&gt;. The same goes for Joan Loan, Ben Mortgage and the whole McViagra family as well. Don't bother.]</description>
		<content:encoded><![CDATA[<p>I completely agree with your point that all blogs should become moderated ones and should be do follow, which would keep spammers in the bay and help people who chip in with quality comments. It should be a win-win game isn&#8217;t it?</p>
<p>[Unlinked &#8220;Yuva_payday@moerpoundstillpayday.co.uk&#8221; spamming me from <a href="mailto:bendonnash@yahoo.co.uk">203.76.139.118</a>. The same goes for Joan Loan, Ben Mortgage and the whole McViagra family as well. Don&#8217;t bother.]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I Guess We Are A Dofollow Blog Again (Sort Of&#8230;) &#124; Hobo</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1673</link>
		<dc:creator>I Guess We Are A Dofollow Blog Again (Sort Of&#8230;) &#124; Hobo</dc:creator>
		<pubDate>Tue, 30 Jun 2009 05:28:12 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1673</guid>
		<description>[...] Andy Beard comments too here &#8211; Pageranks Sculpting &#38; Blog Comments and another of my favourite bloggers, Sebastian, pipes in with this gem &#8211; http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Andy Beard comments too here &#8211; Pageranks Sculpting &amp; Blog Comments and another of my favourite bloggers, Sebastian, pipes in with this gem &#8211; <a href="http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/">http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/</a> [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1672</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Mon, 29 Jun 2009 11:52:55 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1672</guid>
		<description>Timo, of course you know that's not true. Blog comment spammers don't care whether you condomize their links or not.</description>
		<content:encoded><![CDATA[<p>Timo, of course you know that&#8217;s not true. Blog comment spammers don&#8217;t care whether you condomize their links or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melanie Prough</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1670</link>
		<dc:creator>Melanie Prough</dc:creator>
		<pubDate>Sun, 28 Jun 2009 23:12:17 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1670</guid>
		<description>Your blog post tag is an excellent idea.... I was a bit curious so I played around with it a bit and found that it can even be made valid by using a pre or similar old school tag.

You know, in case I link to some who is my worst enemy =-)</description>
		<content:encoded><![CDATA[<p>Your blog post tag is an excellent idea&#8230;. I was a bit curious so I played around with it a bit and found that it can even be made valid by using a pre or similar old school tag.</p>
<p>You know, in case I link to some who is my worst enemy =-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Weekly Insider 6-22-09 to 2-26-09</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1669</link>
		<dc:creator>The Weekly Insider 6-22-09 to 2-26-09</dc:creator>
		<pubDate>Fri, 26 Jun 2009 19:18:25 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1669</guid>
		<description>[...] How to handle a machine-readable pandemic that search engines cannot control  [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] How to handle a machine-readable pandemic that search engines cannot control  [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timo</title>
		<link>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1667</link>
		<dc:creator>Timo</dc:creator>
		<pubDate>Thu, 25 Jun 2009 12:38:47 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/rip-rel-nofollow-funeral-party/#comment-1667</guid>
		<description>Hmmm I still feel much better using the nofollow tag in my blog. It definitely deters people from spamming me. It also saves me a lot of work when moderating comments.</description>
		<content:encoded><![CDATA[<p>Hmmm I still feel much better using the nofollow tag in my blog. It definitely deters people from spamming me. It also saves me a lot of work when moderating comments.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
