<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Don&#8217;t use Robots.txt to control indexing</title>
	<atom:link href="http://www.jlh-design.com/2008/08/dont-use-robotstxt-to-control-indexing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jlh-design.com/2008/08/dont-use-robotstxt-to-control-indexing/</link>
	<description>Terrible writing and mere conjecture</description>
	<pubDate>Sun, 14 Mar 2010 11:36:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Patrick Daly</title>
		<link>http://www.jlh-design.com/2008/08/dont-use-robotstxt-to-control-indexing/comment-page-1/#comment-6044</link>
		<dc:creator>Patrick Daly</dc:creator>
		<pubDate>Tue, 19 Aug 2008 19:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/?p=492#comment-6044</guid>
		<description>Great post. Often the ease of a one-liner in the robots.txt seems the easiest and quickest solution, but you convinced me otherwise.</description>
		<content:encoded><![CDATA[<p>Great post. Often the ease of a one-liner in the robots.txt seems the easiest and quickest solution, but you convinced me otherwise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everett</title>
		<link>http://www.jlh-design.com/2008/08/dont-use-robotstxt-to-control-indexing/comment-page-1/#comment-6017</link>
		<dc:creator>Everett</dc:creator>
		<pubDate>Mon, 04 Aug 2008 20:56:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/?p=492#comment-6017</guid>
		<description>That's all fine until you start dealing with eCommerce sites that have a ton of duplicate content created from dynamic functions that are out of your control, for which the "system" is unable or unwilling to allow dynamic insertion of a noindex meta tag (i.e. if you add one to the dynamic variable page ?sort=bestsellers it also adds it to the unsorted page). In those cases, you have to block the content from being indexed by whatever means you have at your disposal - namely robots.txt with wildcard disallows. Ideally, one would have enough control over their site, or their clients' site to do a dynamic insertion, but with big eCommerce soutions this is not often the case.</description>
		<content:encoded><![CDATA[<p>That&#8217;s all fine until you start dealing with eCommerce sites that have a ton of duplicate content created from dynamic functions that are out of your control, for which the &#8220;system&#8221; is unable or unwilling to allow dynamic insertion of a noindex meta tag (i.e. if you add one to the dynamic variable page ?sort=bestsellers it also adds it to the unsorted page). In those cases, you have to block the content from being indexed by whatever means you have at your disposal - namely robots.txt with wildcard disallows. Ideally, one would have enough control over their site, or their clients&#8217; site to do a dynamic insertion, but with big eCommerce soutions this is not often the case.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
