<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Commenti a: Google, Yahoo e MSN alleati</title>
	<link>http://www.controrete.com/2006/11/16/google-yahoo-e-msn-alleati/</link>
	<description>Shedding light on Search</description>
	<pubDate>Fri, 16 May 2008 07:54:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>di SITEBASES.ORG</title>
		<link>http://www.controrete.com/2006/11/16/google-yahoo-e-msn-alleati/#comment-3854</link>
		<pubDate>Fri, 08 Dec 2006 19:49:52 +0000</pubDate>
		<guid>http://www.controrete.com/2006/11/16/google-yahoo-e-msn-alleati/#comment-3854</guid>
					<description>&lt;strong&gt;Sitebases, the next protocol after Sitemaps&lt;/strong&gt;

It can save the time and press for the search engine, also for the websites.
It can bring new search engine that named Search Engin 2.0.
Using Sitebase protocol, will save 95% bandwidth above. It is anthother sample for long tail thery.
In this protoco...</description>
		<content:encoded><![CDATA[<p><strong>Sitebases, the next protocol after Sitemaps</strong></p>
<p>It can save the time and press for the search engine, also for the websites.<br />
It can bring new search engine that named Search Engin 2.0.<br />
Using Sitebase protocol, will save 95% bandwidth above. It is anthother sample for long tail thery.<br />
In this protoco&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>di &#187; Standard Sitemaps: Google, Yahoo! e Microsoft insieme - Web Marketing e Posizionamento</title>
		<link>http://www.controrete.com/2006/11/16/google-yahoo-e-msn-alleati/#comment-2225</link>
		<pubDate>Fri, 17 Nov 2006 14:59:56 +0000</pubDate>
		<guid>http://www.controrete.com/2006/11/16/google-yahoo-e-msn-alleati/#comment-2225</guid>
					<description>[...] Controrete [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Controrete [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
