Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

RE: [wp-hackers] Robots.txt

  • To: wp-hackers@xxxxxxxxxxxxxxxxxxxx
  • Subject: RE: [wp-hackers] Robots.txt
  • From: Roy Schestowitz <r@xxxxxxxxxxxxxxx>
  • Date: Thu, 24 Nov 2005 04:24:53 +0000
  • Delivery-date: Thu, 24 Nov 2005 04:24:55 +0000
  • Envelope-to: s@schestowitz.com
  • In-reply-to: <001501c5f04d$807f1f90$6501a8c0@DB>
  • References: <001501c5f04d$807f1f90$6501a8c0@DB>
  • User-agent: Internet Messaging Program (IMP) H3 (4.0.3)
_____/ On Wed 23 Nov 2005 16:46:50 GMT, [Denis de Bernardy] wrote : \_____

-----Original Message-----
From: wp-hackers-bounces@xxxxxxxxxxxxxxxxxxxx
[mailto:wp-hackers-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of
David Munn
Sent: Wednesday, November 23, 2005 5:45 PM
To: wp-hackers@xxxxxxxxxxxxxxxxxxxx
Subject: [wp-hackers] Robots.txt

I was thinking it would be a good idea to include a simple robots.txt file within the Wordpress release to block of bot access to the wp-admin, wp-includes, and wp-content directories.


David Munn

make that a robots-sample.txt

I'd hate to loose my robots.txt by mistake.


Not everyone installs WordPress at the top level either. The implication of multiple robots.txt files would be user confusion. I suggest prepending to the top of each administration page e.g.



Roy S. Schestowitz
http://Schestowitz.com  |    SuSE Linux     |     PGP-Key: 0x74572E8E
 4:15am  up 21 days  0:09,  4 users,  load average: 0.18, 0.33, 0.26

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index