I've seen several postings about this now in the last few days, although this is my first actual experience of it.
I'm being hit very hard by google's freshbot at the moment, and going deep too. At first glance at what is currently going on with the little guys, I had to check and double check that the IP's were 64.... (they are).
It's behaviour, in terms of hard hitting and depth of crawl (it's going through the entire site) is more like the character of the old deepbot.
In fact, it's identical behaviour to deepbot the last time it crawled this site back in April.
I'm interested in hearing from others who are seeing the same.
Here's some weird freshbot-related behavior I've noticed on one of my sites:
For the past week and a half or so, google's cache of my site has been from April 2nd, and it would show up in SERPs corresponding to the content it had at that time. This obviously was quite undesirable for everyone involved. All this was despite fresh content and frequent freshbot visits to both my homepage and deeper pages. Just now it was updated to a version maybe 36 hours old (just the homepage, all other pages are still old caches), but doing an allinurl:mydomain.com search, the homepage shows up as the very last result. I can't be 100% sure since I haven't bothered watching SERPs for 2+ months old content, but I believe my SERPs are lower for everything occuring on the homepage as well.
I realize this is something of a transitional period, but if this is what we can expect from a supposedly deepfreshbot/continuous update system, then something is broken. Its like a freshbot penalty...WTH?
[edited by: Dolemite at 7:46 am (utc) on June 13, 2003]