Take a break guys and gals and have a look at some FREE beautiful horney guys and
young girls from all around the world!
Free "bella ladies and dudes, from all around the world"
Look at em, enjoy em, and if you like you can even go out with one.
Choose the beau you like, their all available!
Note: There is no charge to view, and no pop-up ads!
or try: NEW-BEAUTIFUL
**********************
Let your site earn you money right from the start!
Did Google Unleash Additional Googlebots?
Apparently, Google has begun using another spider in their
scanning and indexing of web sites. News of a second
Googlebot was discovered by a number of site owners
who, while studying their site logs, noticed two Google
spiders; with different IP address ranges; visited and
scanned their respective sites.
Have you had visits from more than one Googlebot?
Discuss at WebProWorld.
News of the additional Googlebot was first noticed on the
DigitalPoint forums, posted by digitalpoint himself. In his
post, digital noticed that two Googlebots had visited his site
and that each one had different IP addresses:
"The normal one:
66.249.64.47 - - [15/Sep/2004:18:59:12 -0700] "GET
/robots.txt HTTP/1.0" 404 1227 "-" "Googlebot/2.1
(+http://www.google.com/bot.html)"
and also this one:
66.249.66.129 - - [15/Sep/2004:18:12:51 -0700] "GET /
HTTP/1.1" 200 38358 "-" "Mozilla/5.0 (compatible;
Googlebot/2.1; +http://www.google.com/bot.html)"
Aside from the slightly different user agent, it's also HTTP
1.1. The IP address it uses is an IP block is normally just
used for Mediapartners (AdSense spider), but it's spidering
a site without any AdSense."
Once this thread was launched,
scores of other posters shared their
encounters with the second
Googlebot. A DigitalPoint member
named Redleg also noticed several
visits from the new spider and also
recorded the IP ranges of the new
visitors, "Don't remember the exact IP
addresses (about 15-20 of them) but here's the IP ranges:
66.249.78.* 66.249.64.* 66.249.79.*…"
Many who checked their server logs noticed a number of
visits from both Googlebots, with various IP ranges. Not
only were there numerous visits, but also each bot
performed a different kind of crawl than its "partner". Over
at the WebmasterWorld forums, a poster named Gomer
noticed that one bot performed a complete site crawl while
the other did more of a surface-type crawl. According to
Gomer:
"The 66.249.64.X series was requesting pages that were
fully indexed i.e., they have a page title and description.
The 66.249.65.X series was requesting pages that were
only partially indexed… In my case, the 66.249.65.X were
pages that exist on my server but I am trying to get
Googlebot to stop indexing."
As the realization of an additional Googlebot set in,
speculation began concerning the motive of having two
bots performing site scans. Because Google likes to keep
the business concerning their search index, spiders, and
anything having to with their search engine under tight
wraps, educated guesses are all that can be done.
Brett Tabke posted an interesting
thought concerning Google's extensive
crawling, "looks like "panic" based
spidering… as if an index needs to be
rebuilt from the ground up in a short
time period (aka: the old index didn't
work)." Another member believed
these scans are apart of the PR
re-calculation for the next PageRank
update. Another poster, idoc, had
also had an intriguing look at Google actions:
"I expect a lot of cloaking and redirect sites will be
dropped soon from these new bot IPs and this crawl. It's
what I had in mind in the post about hijacks when I said I
think Google is on it. They have been asking for file paths
and filenames with extensions I have never used before. I
am hopeful anyway."
Longtime WMW poster claus suggested that these events
might be because Google is preparing a new datacenter,
while others thought the index may contain a glitch.
However, Liane, in agreeing with Brett about these deep
crawls being out of the ordinary. She stated, "Something
must be causing this feeding frenzy and it wouldn't surprise
me if there was a glitch with the index. Google went nuts
every day this past week on my site, but in the last 24
hours… only one hit. Never had that before. Not that I can
remember anyway… I smell a "major" update in the
offing... once they get things sorted."
As it stands, the reasons behind Google's scanning efforts
are unknown. The only things that are certain is they are
using more than one crawler and that at least one of them
performs a complete site scan. Is Google repopulating their
index, or are they hunting out cloaked/doorway pages? Or
are they finally getting around to doing another PR update?
--------------------------------------------------------
Much more info gan be gleaned from the search engine signatures
than simply the name of the search engine! depending on the code
on the line, we can determine if a translation was done, if the
search was done in child safety mode, language, etc. depending on
the code that is on the line!
@rem Sed program e-comm.ex
@rem Different Search Engines have different signatures
@rem need to capture and remove their signatures
@rem {
@rem /6&layer=/d aol layer has no search data (so delete line)
@rem /browse.psp?/d netscape with this signature has no search data
@rem s/.*query?q=//g ALTAVISTA
@rem s/.*query?p=//g GOOGLE.YAHOO Visited by Crawler SE BOT
@rem s/.*query_ca?p=//g ca.google.yahoo
@rem s/.*query?pg=//g ALTAVISTA Visited by Scooter, Mercator or Scrub
@rem s/.*showmore&query=//g aolsearch.aol
@rem s/.*prevq=//g ALTAVISTA
@rem s/.*query=//g AOL LYCOS Visited by T-Rex spider BOT
@rem Had to replace this one here with the next 7 versions @rem s/.*search=//g
@rem s/.*8&search=//g netscape utilizes namely or trivial as BOT
@rem s/.*es&search=//g |
@rem s/.*op&search=//g |
@rem s/.*xr&search=//g |
@rem s/.*rc&search=//g |
@rem s/.*ll&search=//g |
@rem s/.*psp&search=//g |
@rem s/.*bot&search=//g |
@rem s/.*psp?search=//g |
@rem s/.*scnetscape?search=//g netscape
@rem s/.*?keywords=//g |
@rem s/.*_psp&Keywords=//g earthlink
@rem s/.*MT=//g Hotbot.lycos
@rem s/.*?MT=//g search.msn
@rem s/.*adp?//g teensearch (AOL)
@rem s/.*search?z//g visisimo
@rem s/.*search?hl//g google canada, germany
@rem s/.*search?q=//g google uk, zdnet, alltheweb
@rem s/.*www.google.com\/search?q=//g google uses crawler as SE bot
@rem s/.*search?as_q=//g google
@rem s/.*&q=//g google
@rem s/.*ie?q=//g google
@rem s/.*as_q=//g google
@rem s/.*q=cache://g google
@rem s/.*url=//g google images
@rem s/.*images%3Fq//g google images
@rem s/.*html?q=//g radarvol.vol.com
@rem s/.*gw?=web//g excite visited by Architext spider
@rem s/.*search.gw?c=//g excite also atext
@rem s/.*search.gw?//g excite also multitext
@rem s/.*web?q=//g altavista
@rem s/.*aq&q=//g fr.altavista
@rem s/.*q&q=//g uk.altavista
@rem s/.*q?pg=//g uk.altavista
@rem s/.*?c=//g excite.com
@rem s/.*?wf,//g webferret
@rem s/.*cc%3A//g redaruol.uol
@rem s/.*srch&qt=//g search.com
@rem s/.*cgi?keywords=//g search.com
@rem s/.*search?channel//g search.com
@rem s/.*ch&q=//g search.com channel
@rem s/.*php?qry=//g directhit
@rem s/.*results.asp?q=//g msn
@rem s/.*&title=//g websearch.cs.com
@rem s/.*&ask=//g askjeeves
@rem s/.*dir.asp?cat=//g open directory
@rem s/.*fir&search=//g netscape
@rem
@rem s/.infoseek uses sidewinder and WISEnotbot
@rem
@rem s/.*?cat=//g netmenu.nl
@rem slurp@inktomi spider feeds inktomi
@rem to many search engines.
@rem
@rem infoseek uses sidewinder BOT
@rem
@rem s/.*search?cat=//g alltheweb uses FAST-search as BOT
@rem
@rem s/.*nlquery.fcg?cb=0&qr=//g northernlight Visited by Gulliver BOT
@rem
@rem
@rem s/.*www.openfind.com/tw//g openfind chineese BOT
@rem
@rem
@rem s/.*nlquery.fcg?cb=0&qr=//g northernlight Visited by Gulliver BOT
@rem
@rem
@rem s/.*nlquery.fcg?cb=0&qr=//g northernlight Visited by Gulliver BOT
@rem
@rem
@rem s/+/ /g And clean up various CGI control codes
@rem s/%20/ /g
@rem s/%22/ /g
@rem s/%26/ /g
@rem s/%27/ /g
@rem s/%28/ /g
@rem s/%29/ /g
@rem s/%2b/ /g
@rem s/%2c/ /g
@rem s/%2d/-/g
@rem s/%2D/-/g
@rem s/%2e/ /g
@rem s/%2F/ /g
@rem s/%2B/ /g
@rem s/%2f/ /g
@rem s/%3A/ /g
@rem s/%3b/ /g
@rem s/%3D/ /g
@rem s/%3F/-/g
@rem s/%40/(/g
@rem s/%60/'/g
@rem s/%B4/ /g
@rem s/%E9/ /g
@rem
@rem }
@rem s/&.*// sub routine, Clean up everything after & on all lines
@rem s/^ *// get rid of white spaces at beginning of lines
@rem s/[,,].*// get rid of EOL starting with ,,
@rem s/num.*// get rid of anoying EOL that start with num
"Windows XP turning out to be something of a Trojan horse ...
Note: other sites (SE's) with too many
JavaScript errors include:
MSN, google.yahoo (USA only), iwon errors
include javascript errors and blank screens upon loading
Search Engine (SE) results. Netscape will
not even serve you results from people
who visited your site (not follow links)
unless you update your browser to Netscape 6
The same is true with excite.ca, except
they at least give you the choice between
MSIE or Netscape communicator ver. 4 or greater!
AOL will not even let you visit their
search engine results page that sent
a customer to your site, (ie. reverse IP).
You need a password to do a search on AOL!
Not only that! When search.aol.com sends
someone to your site, it looks like 2 people
visited, since it leaves behind a double
hit signature, about 3/100 of a second appart.
Not only that. The same SEs' that have
all those JavaScript errors, also have
the least reliable and accurate results!
Yahoo.Google, Netscape and MSN have very
poor results when conducting a search
or in fact seeing what customers wanted
from your site, VS what they were sent to!
It almost seems their DataBases are mis-keyed
so as you have the info the surfer was
looking for on your general URL, but not
on the exact page they were sent to.
Unless the surfer using these SEs' is
web savvy (knows how to use your local SE)
and also persistant, he/she will invariably
move on! Lately, Altavista is also F.U.
Either bringing no visitors, or bringing
visitors for VERY few keywords!
Not only that! When I follow a link search
to my site from Altavista, i constantly
get a message "TRANSFER INTERRUPTED" and
must click on re-load to get the search to
resume.
To date, the only search engines that consistantly
have no problems (ie. No JavaScript errors,
Mo cookie bullshit, no crashing your browser,
No blank pages, No need to hit reload, No
funny stuff are Google.com and C|net Search.com
All the major SE's are crap and non Browser
friendly!