<?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: Making the world (and your site) flat—via a Reverse Proxy</title>
	<atom:link href="http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/feed/" rel="self" type="application/rss+xml" />
	<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/</link>
	<description>Advanced Search Engine Marketing Tips to Succeed Online</description>
	<pubDate>Tue, 18 Nov 2008 15:12:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Matt</title>
		<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2831</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 02 Oct 2007 13:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2831</guid>
		<description>This is actually exactly what Google recommends for getting AJAX and Flash sites indexed. I'm sure that by now they have some method for detecting obvious black hat stuff using this technique, but they are going to have to compromise until they figure out how to deal with rich interfaces.</description>
		<content:encoded><![CDATA[<p>This is actually exactly what Google recommends for getting AJAX and Flash sites indexed. I&#8217;m sure that by now they have some method for detecting obvious black hat stuff using this technique, but they are going to have to compromise until they figure out how to deal with rich interfaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamlet Batista</title>
		<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2487</link>
		<dc:creator>Hamlet Batista</dc:creator>
		<pubDate>Tue, 25 Sep 2007 22:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2487</guid>
		<description>WDN - Thanks for all your comments. I don't have problems with comments with keyword rich names, but I'd appreciate if you ended at least one comment with your real name. It is a little bit awkward to call people by their website names. ;-)</description>
		<content:encoded><![CDATA[<p>WDN - Thanks for all your comments. I don&#8217;t have problems with comments with keyword rich names, but I&#8217;d appreciate if you ended at least one comment with your real name. It is a little bit awkward to call people by their website names. <img src='http://hamletbatista.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamlet Batista</title>
		<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2486</link>
		<dc:creator>Hamlet Batista</dc:creator>
		<pubDate>Tue, 25 Sep 2007 22:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2486</guid>
		<description>David - The difference is that they detect both robots and users clicking from the search results, so they present the 'optimized' content to both.

Sorry about the confusion. Adam's comment prompted me to re-read the PA.</description>
		<content:encoded><![CDATA[<p>David - The difference is that they detect both robots and users clicking from the search results, so they present the &#8216;optimized&#8217; content to both.</p>
<p>Sorry about the confusion. Adam&#8217;s comment prompted me to re-read the PA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hopkins</title>
		<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2484</link>
		<dc:creator>David Hopkins</dc:creator>
		<pubDate>Tue, 25 Sep 2007 21:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2484</guid>
		<description>This is definitely one to scare away people with low attention spans.

So the only difference is that it changes the URLs? This post has got a bit confusing with the conflicts.</description>
		<content:encoded><![CDATA[<p>This is definitely one to scare away people with low attention spans.</p>
<p>So the only difference is that it changes the URLs? This post has got a bit confusing with the conflicts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamlet Batista</title>
		<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2474</link>
		<dc:creator>Hamlet Batista</dc:creator>
		<pubDate>Tue, 25 Sep 2007 17:59:13 +0000</pubDate>
		<guid isPermaLink="false">http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2474</guid>
		<description>Sam - Thanks for your comment. It is good to disagree every once in a while as it becomes more of a conversation than a speech. 

You are right. I read the full patent again, more carefully, and found out that they are presenting the same 'optimized' content to the spiders and search engine users. It is not cloaking. I will update the post to reflect this. Thanks.

From the patent:

&lt;blockquote&gt;19… creating proxy web pages on the proxy website for web pages on the commercial website, each of the proxy web pages including substantially the same information as the corresponding commercial web page, the proxy web pages having a simplified URL and simplified hyperlinks compared to the corresponding commercial web page; adding optimized content to the proxy web pages that is not present on the corresponding commercial web page; serving the proxy web pages including the optimized content to a search engine spider upon request; &lt;b&gt;and serving the proxy web pages including the optimized content to a web browser when the web browser selects the search results listing for the proxy web page from the search engine results page.&lt;/b&gt;
&lt;/blockquote&gt;

My initial assumption came from the fact that when you want to present the same content to spiders and users, you don't need to detect spiders. In their case, they only present the 'optimized' content to spiders and users coming from search results, as explained in the claims. This means that users going directly to the site will still see the non-optimized version of the pages. The question is: When Google says don't present different content to users than you present search engines, do they mean search engine users only?</description>
		<content:encoded><![CDATA[<p>Sam - Thanks for your comment. It is good to disagree every once in a while as it becomes more of a conversation than a speech. </p>
<p>You are right. I read the full patent again, more carefully, and found out that they are presenting the same &#8216;optimized&#8217; content to the spiders and search engine users. It is not cloaking. I will update the post to reflect this. Thanks.</p>
<p>From the patent:</p>
<blockquote><p>19… creating proxy web pages on the proxy website for web pages on the commercial website, each of the proxy web pages including substantially the same information as the corresponding commercial web page, the proxy web pages having a simplified URL and simplified hyperlinks compared to the corresponding commercial web page; adding optimized content to the proxy web pages that is not present on the corresponding commercial web page; serving the proxy web pages including the optimized content to a search engine spider upon request; <b>and serving the proxy web pages including the optimized content to a web browser when the web browser selects the search results listing for the proxy web page from the search engine results page.</b>
</p></blockquote>
<p>My initial assumption came from the fact that when you want to present the same content to spiders and users, you don&#8217;t need to detect spiders. In their case, they only present the &#8216;optimized&#8217; content to spiders and users coming from search results, as explained in the claims. This means that users going directly to the site will still see the non-optimized version of the pages. The question is: When Google says don&#8217;t present different content to users than you present search engines, do they mean search engine users only?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Design Newcastle</title>
		<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2472</link>
		<dc:creator>Web Design Newcastle</dc:creator>
		<pubDate>Tue, 25 Sep 2007 16:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2472</guid>
		<description>I get what Sam is saying but thats a different impression to the one I got reading the article.  Maybe I read it wrong?

If it is as Sam points out then I just can't see the point of it - or atleast any ethical reason for it.</description>
		<content:encoded><![CDATA[<p>I get what Sam is saying but thats a different impression to the one I got reading the article.  Maybe I read it wrong?</p>
<p>If it is as Sam points out then I just can&#8217;t see the point of it - or atleast any ethical reason for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Daams</title>
		<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2461</link>
		<dc:creator>Sam Daams</dc:creator>
		<pubDate>Tue, 25 Sep 2007 11:31:27 +0000</pubDate>
		<guid isPermaLink="false">http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2461</guid>
		<description>I usually agree with your assessments, which is why it's hard for me to understand that you see "additional content and HTML optimization can be added to the proxy web pages that are not included on the corresponding web pages on the commercial site" as cloaking. Only IF what is being shown to the search engine is different than what is being shown to the visitor would this be cloaking. I'm 99.99% sure they intend to do some kind of framing of the original source and rewrite that framed page in such a way that it is better optimized with a better url. But that whole 'new page' would be the same to visitors and search engines so how is this cloaking?

Duplicate content it certainly is though and also more likely to cause the original article to be dumped by SE's than other proxy methods used... 

Either way I don't agree with the method because it is essentially stealing the content and with the way SE's currently work can get the original site penalized but it's still not cloaking :)</description>
		<content:encoded><![CDATA[<p>I usually agree with your assessments, which is why it&#8217;s hard for me to understand that you see &#8220;additional content and HTML optimization can be added to the proxy web pages that are not included on the corresponding web pages on the commercial site&#8221; as cloaking. Only IF what is being shown to the search engine is different than what is being shown to the visitor would this be cloaking. I&#8217;m 99.99% sure they intend to do some kind of framing of the original source and rewrite that framed page in such a way that it is better optimized with a better url. But that whole &#8216;new page&#8217; would be the same to visitors and search engines so how is this cloaking?</p>
<p>Duplicate content it certainly is though and also more likely to cause the original article to be dumped by SE&#8217;s than other proxy methods used&#8230; </p>
<p>Either way I don&#8217;t agree with the method because it is essentially stealing the content and with the way SE&#8217;s currently work can get the original site penalized but it&#8217;s still not cloaking <img src='http://hamletbatista.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Design Newcastle</title>
		<link>http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2451</link>
		<dc:creator>Web Design Newcastle</dc:creator>
		<pubDate>Tue, 25 Sep 2007 10:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://hamletbatista.com/2007/09/24/making-the-world-and-you-site-flat%e2%80%94via-a-reverse-proxy/#comment-2451</guid>
		<description>Hehe.  This relly is just cloaking using a slightly different method.  Redirecting search engines to a proxy site with additional content - who are they kidding?  I can't believe this stuff gets patented.

Asking Google about this would be interesting but I think I might already know their answer lol.</description>
		<content:encoded><![CDATA[<p>Hehe.  This relly is just cloaking using a slightly different method.  Redirecting search engines to a proxy site with additional content - who are they kidding?  I can&#8217;t believe this stuff gets patented.</p>
<p>Asking Google about this would be interesting but I think I might already know their answer lol.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
