<?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>SEO &#124; SEM &#124; Website Promotion &#124; Online Advertising &#124; SEO Training &#187; robots exclusion protocol</title>
	<atom:link href="http://infoyogis.com/blog/tag/robots-exclusion-protocol/feed/" rel="self" type="application/rss+xml" />
	<link>http://infoyogis.com/blog</link>
	<description>Expert Consulting and Services for Search Engine Optimization (SEO), Search Marketing (SEM), Internet Marketing, Website Promotion, Online Advertising, Content Development and Training</description>
	<lastBuildDate>Thu, 11 Feb 2010 07:08:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Robots Exclusion Protocol (REP)</title>
		<link>http://infoyogis.com/blog/2009/06/robots-exclusion-protocol-rep/</link>
		<comments>http://infoyogis.com/blog/2009/06/robots-exclusion-protocol-rep/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 09:42:39 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[SEO News]]></category>
		<category><![CDATA[rep]]></category>
		<category><![CDATA[robots exclusion protocol]]></category>

		<guid isPermaLink="false">http://infoyogis.com/blog/?p=745</guid>
		<description><![CDATA[Web publishers often ask how they can maximize their visibility on the web. Much of this has to do with search engine optimization &#8212; making sure a publisher&#8217;s content shows up on all the search engines.
However, there are some cases in which publishers need to communicate more information to search engines &#8212; like the fact [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />Web publishers often ask how they can maximize their visibility on the web. Much of this has to do with search engine optimization &#8212; making sure a publisher&#8217;s content shows up on all the search engines.</p>
<p>However, there are some cases in which publishers need to communicate more information to search engines &#8212; like the fact that they <em id="by0r0">don&#8217;t</em> want certain content to appear in search results. And for that they use something called the Robots Exclusion Protocol (REP), which lets publishers control how search engines access their site: whether it&#8217;s controlling the visibility of their content across their site (via robots.txt) or down to a much more granular level for individual pages (via META tags).</p>
<p>Since it was introduced in the early &#8217;90s, REP has become the de facto standard by which web publishers specify which parts of their site they want public and which parts they want to keep private. Today, millions of publishers use REP as an easy and efficient way to communicate with search engines. Its strength lies in its flexibility to evolve in parallel with the web, its universal implementation across major search engines and all major robots, and in the way it works for any publisher, no matter how large or small.</p>
<p>Source:<br />
<strong><a href="http://googleblog.blogspot.com/2008/06/more-on-robots-exclusion-protocol-rep.html" target="_blank">More On Robots Exclusion Protocol</a></strong></p>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Finfoyogis.com%2Fblog%2F2009%2F06%2Frobots-exclusion-protocol-rep%2F&amp;linkname=Robots%20Exclusion%20Protocol%20%28REP%29"><img src="http://infoyogis.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://infoyogis.com/blog/2009/06/robots-exclusion-protocol-rep/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
