<?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: Updated robots.txt for WordPress</title>
	<atom:link href="http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html</link>
	<description>Advanced Web Development</description>
	<lastBuildDate>Wed, 18 Nov 2009 23:28:48 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robertino</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-109510</link>
		<dc:creator>Robertino</dc:creator>
		<pubDate>Sat, 14 Nov 2009 09:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-109510</guid>
		<description>My previous posts are from October 1st/2nd 2009.
You shouldn&#039;t worry about, this information is very static.
It&#039;s not like they are changing the WordPress directory names, nor what&#039;s in them frequently.
If it would change frequently, the theme designers, plugin coders, blog owners, and search engines wouldn&#039;t bother.
What&#039;s most likely to change (frequently) are your own directory names and their content.
If you don&#039;t update that part of the robots.txt file, then it will be old information.

Off Topic 1:
Tip : Be careful with robots.txt. It&#039;s a simple text file, that anyone can show in their browser.
Don&#039;t giveaway your whole site structure, use meaningless names for the directories that you wish to protect.

Off Topic 2:
Bloody Hell, I see that Mehmet of GabfireThemes posted in here. How could I have missed that before ?</description>
		<content:encoded><![CDATA[<p>My previous posts are from October 1st/2nd 2009.<br />
You shouldn&#8217;t worry about, this information is very static.<br />
It&#8217;s not like they are changing the WordPress directory names, nor what&#8217;s in them frequently.<br />
If it would change frequently, the theme designers, plugin coders, blog owners, and search engines wouldn&#8217;t bother.<br />
What&#8217;s most likely to change (frequently) are your own directory names and their content.<br />
If you don&#8217;t update that part of the robots.txt file, then it will be old information.</p>
<p>Off Topic 1:<br />
Tip : Be careful with robots.txt. It&#8217;s a simple text file, that anyone can show in their browser.<br />
Don&#8217;t giveaway your whole site structure, use meaningless names for the directories that you wish to protect.</p>
<p>Off Topic 2:<br />
Bloody Hell, I see that Mehmet of GabfireThemes posted in here. How could I have missed that before ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dick Raney</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-109395</link>
		<dc:creator>Dick Raney</dc:creator>
		<pubDate>Fri, 13 Nov 2009 22:48:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-109395</guid>
		<description>How old is this information? Why don&#039;t you show dates on the post or the comments?</description>
		<content:encoded><![CDATA[<p>How old is this information? Why don&#8217;t you show dates on the post or the comments?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hpnugroho</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-105154</link>
		<dc:creator>hpnugroho</dc:creator>
		<pubDate>Mon, 12 Oct 2009 14:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-105154</guid>
		<description>hi ..
I have question about this file, can we use on free blog on wordpress.com or blogspot.com ?
Thanks for your information</description>
		<content:encoded><![CDATA[<p>hi ..<br />
I have question about this file, can we use on free blog on wordpress.com or blogspot.com ?<br />
Thanks for your information</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ujjwol</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104836</link>
		<dc:creator>Ujjwol</dc:creator>
		<pubDate>Fri, 02 Oct 2009 04:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104836</guid>
		<description>Thanks Guys</description>
		<content:encoded><![CDATA[<p>Thanks Guys</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robertino</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104834</link>
		<dc:creator>Robertino</dc:creator>
		<pubDate>Fri, 02 Oct 2009 03:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104834</guid>
		<description>&lt;strong&gt;@Ujjwol&lt;/strong&gt;
If you really want archive.org to duplicate your content remove the following.

&lt;blockquote&gt;
&lt;pre&gt;User-agent: ia_archiver-web.archive.org
Disallow: /&lt;/pre&gt;
&lt;/blockquote&gt;

&lt;blockquote&gt;
&lt;pre&gt;User-agent: ia_archiver
Disallow: /&lt;/pre&gt;
&lt;/blockquote&gt;

But archive.org is a reasonably good way to proof that your site&#039;s content existed at a certain date and was not parked with a an all ads page, or had the content first (in case of plagiarism).</description>
		<content:encoded><![CDATA[<p><strong>@Ujjwol</strong><br />
If you really want archive.org to duplicate your content remove the following.</p>
<blockquote>
<pre>User-agent: ia_archiver-web.archive.org
Disallow: /</pre>
</blockquote>
<blockquote>
<pre>User-agent: ia_archiver
Disallow: /</pre>
</blockquote>
<p>But archive.org is a reasonably good way to proof that your site&#8217;s content existed at a certain date and was not parked with a an all ads page, or had the content first (in case of plagiarism).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ujjwol</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104803</link>
		<dc:creator>Ujjwol</dc:creator>
		<pubDate>Thu, 01 Oct 2009 05:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104803</guid>
		<description>Archive.org says it cannot crawl my website due to this &lt;code&gt;robots.txt&lt;/code&gt; ?
How to fix this ?</description>
		<content:encoded><![CDATA[<p>Archive.org says it cannot crawl my website due to this <code>robots.txt</code> ?<br />
How to fix this ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robertino</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104266</link>
		<dc:creator>Robertino</dc:creator>
		<pubDate>Tue, 22 Sep 2009 08:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104266</guid>
		<description>Forgot to add the following from robotstxt.org. I&#039;m going with the format of your robots.txt file for now. ( &lt;a href=&quot;http://www.robotstxt.org/robotstxt.html&quot; rel=&quot;nofollow&quot;&gt;http://www.robotstxt.org/robotstxt.html&lt;/a&gt; )

&lt;blockquote&gt;Note also that globbing and regular expression are not supported in either the User-agent or Disallow lines. The &#039;*&#039; in the User-agent field is a special value meaning &quot;any robot&quot;. Specifically, you cannot have lines like &quot;User-agent: *bot*&quot;, &quot;Disallow: /tmp/*&quot; or &quot;Disallow: *.gif&quot;.&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>Forgot to add the following from robotstxt.org. I&#8217;m going with the format of your robots.txt file for now. ( <a href="http://www.robotstxt.org/robotstxt.html" rel="nofollow">http://www.robotstxt.org/robotstxt.html</a> )</p>
<blockquote><p>Note also that globbing and regular expression are not supported in either the User-agent or Disallow lines. The &#8216;*&#8217; in the User-agent field is a special value meaning &#8220;any robot&#8221;. Specifically, you cannot have lines like &#8220;User-agent: *bot*&#8221;, &#8220;Disallow: /tmp/*&#8221; or &#8220;Disallow: *.gif&#8221;.</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robertino</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104263</link>
		<dc:creator>Robertino</dc:creator>
		<pubDate>Tue, 22 Sep 2009 07:06:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-104263</guid>
		<description>I&#039;m setting up a new blog and this time wanted to use a proper robots.txt file. So I started reasearching.

Over at wordpress.org, where this page is linked from ( just above the grey box : &lt;a href=&quot;http://codex.wordpress.org/Search_Engine_Optimization_for_WordPress&quot; rel=&quot;nofollow&quot;&gt;Search Engine Optimization for WordPress&lt;/a&gt; ) I see that wildcards are used in the robots.txt file sample.

Then I clicked the link and landed here, and this robots.txt file is &lt;strong&gt;not using wildcards&lt;/strong&gt; at all.

This, and the examples over at robotstxt.org, are the first and only robots.txt file for WordPress which I have seen that are not using the asterisk * sign as a wildcard.

This is I *think* a good thing, because I read over at : &lt;a href=&quot;http://www.robotstxt.org/faq/robotstxt.html&quot; rel=&quot;nofollow&quot;&gt;robotstxt.org&lt;/a&gt;  the following :

&lt;blockquote&gt;&lt;p&gt;Note the &#039;*&#039; is a special token, meaning &quot;any other User-agent&quot;; you cannot use wildcard patterns or regular expressions in either User-agent or Disallow lines.&lt;/p&gt;

&lt;h4&gt;Two common errors:
&lt;/h4&gt;
&lt;ol&gt;&lt;li&gt;Wildcards are _not_ supported: instead of &#039;Disallow: /tmp/*&#039; just say &#039;Disallow: /tmp/&#039;.
&lt;/li&gt;&lt;li&gt;You shouldn&#039;t put more than one path on a Disallow line (this may change in a future version of the spec)&lt;/li&gt;&lt;/ol&gt;&lt;/blockquote&gt;

But still I see countless of other sites using wildcards in paths.
  Was this changed so that wildcards are supported, and maybe the robotstxt.org site just not updated?

One other thing, I see the lines &#039;Disallow: /i/&#039; etc in your robots.txt file.
Do these have to do with the fact that typing the first letter of a page take you to that page ?

For example :
&lt;code&gt;domain.com/c/&lt;/code&gt; and &lt;code&gt;domain.com/c&lt;/code&gt; goes to the contact page.

When I enter for instance &lt;code&gt;domain.com/i/&lt;/code&gt; in my browser&#039;s address bar, I get a &quot;No posts found&quot; message with a &quot;Nothing found for I&quot; in the title.
  Should I stll be adding those lines ?
  Or should I just go for the whole alphabet ? :)

Apologies for the lengthy post.</description>
		<content:encoded><![CDATA[<p>I&#8217;m setting up a new blog and this time wanted to use a proper robots.txt file. So I started reasearching.</p>
<p>Over at wordpress.org, where this page is linked from ( just above the grey box : <a href="http://codex.wordpress.org/Search_Engine_Optimization_for_WordPress" rel="nofollow">Search Engine Optimization for WordPress</a> ) I see that wildcards are used in the robots.txt file sample.</p>
<p>Then I clicked the link and landed here, and this robots.txt file is <strong>not using wildcards</strong> at all.</p>
<p>This, and the examples over at robotstxt.org, are the first and only robots.txt file for WordPress which I have seen that are not using the asterisk * sign as a wildcard.</p>
<p>This is I *think* a good thing, because I read over at : <a href="http://www.robotstxt.org/faq/robotstxt.html" rel="nofollow">robotstxt.org</a>  the following :</p>
<blockquote><p>Note the &#8216;*&#8217; is a special token, meaning &#8220;any other User-agent&#8221;; you cannot use wildcard patterns or regular expressions in either User-agent or Disallow lines.</p>
<h4>Two common errors:<br />
</h4>
<ol>
<li>Wildcards are _not_ supported: instead of &#8216;Disallow: /tmp/*&#8217; just say &#8216;Disallow: /tmp/&#8217;.
</li>
<li>You shouldn&#8217;t put more than one path on a Disallow line (this may change in a future version of the spec)</li>
</ol>
</blockquote>
<p>But still I see countless of other sites using wildcards in paths.<br />
  Was this changed so that wildcards are supported, and maybe the robotstxt.org site just not updated?</p>
<p>One other thing, I see the lines &#8216;Disallow: /i/&#8217; etc in your robots.txt file.<br />
Do these have to do with the fact that typing the first letter of a page take you to that page ?</p>
<p>For example :<br />
<code>domain.com/c/</code> and <code>domain.com/c</code> goes to the contact page.</p>
<p>When I enter for instance <code>domain.com/i/</code> in my browser&#8217;s address bar, I get a &#8220;No posts found&#8221; message with a &#8220;Nothing found for I&#8221; in the title.<br />
  Should I stll be adding those lines ?<br />
  Or should I just go for the whole alphabet ? :)</p>
<p>Apologies for the lengthy post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon @ IBM Engineering</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-95239</link>
		<dc:creator>Jon @ IBM Engineering</dc:creator>
		<pubDate>Fri, 14 Aug 2009 22:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-95239</guid>
		<description>thanks :)  It seems I was really thinking to much into robots.txt files,  they are really just a simple old school method to block search engine crawlers in a very simple way.   I was all confused with wordpress robots .txt files but they really are that simple.

Thanks and have a great day!

Jon @ IBM Core</description>
		<content:encoded><![CDATA[<p>thanks :)  It seems I was really thinking to much into robots.txt files,  they are really just a simple old school method to block search engine crawlers in a very simple way.   I was all confused with wordpress robots .txt files but they really are that simple.</p>
<p>Thanks and have a great day!</p>
<p>Jon @ IBM Core</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mr. T</title>
		<link>http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-92313</link>
		<dc:creator>Mr. T</dc:creator>
		<pubDate>Sun, 02 Aug 2009 09:52:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/seo/updated-robotstxt-for-wordpress.html#comment-92313</guid>
		<description>Excellent post. I shall be using your robots.txt on my site and hopefully I&#039;ll see good results enough to make write a short post on this and link to your site. Thanks a lot.</description>
		<content:encoded><![CDATA[<p>Excellent post. I shall be using your robots.txt on my site and hopefully I&#8217;ll see good results enough to make write a short post on this and link to your site. Thanks a lot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
