From: Peteris Krumins <newsgroups@lf.lv>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Search engines
Date: Wed, 31 Dec 2003 14:51:49 +0000 [thread overview]
Message-ID: <1148933004.20031231165149@lf.lv> (raw)
In-Reply-To: <marc-lartc-107271456812523@msgid-missing>
Hello Sjaak,
Monday, December 29, 2003, 5:10:51 PM, you wrote:
SN> Hi
SN> Does anyone have expirience or advice and set me on the wright track if it
SN> is usefull to slowdown search engine spiders.
SN> I want to limit some spider how eating lott's of bandwith from my server.
SN> Is it possible and a good idea to do this with TC and what would be the
SN> wright script.
It is a bad idea.
Read about Internet Robots and the special robots.txt file.
Put these lines in your webroot, 'robots.txt' file:
User-agent: *
Disallow: /
It will disallow all robots who implement 'robots.txt'.
P.Krumins
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-12-31 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 15:10 [LARTC] Search engines Sjaak Nabuurs
2003-12-31 14:51 ` Peteris Krumins [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1148933004.20031231165149@lf.lv \
--to=newsgroups@lf.lv \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox