Forum Moderators: open
You can tell that because of the IP.
Freshbot starts with 64 or 66 if i am not wrong
And the "normal" Googlebot's ip is something like:
216.239.*.*
So if you have any last changes you want to have in the upcomming index, you better hurry.
[Edit]It should really be spidering (in title) if we are talking correct terms, sorry about that[/edit]
At the moment we have a page uploaded 5 days ago still hanging in there on all the updated data servers up till now. Time will tell if its just freshbot, or if we really made it into the new perm index in a few days.
Also noticed similar in previous updates but never really followed it closely.
That MAY mean that for established freshbotted sites, the cut-off time is far less and no crazy update schedule around reindex time.
Anybody else noticing similar?
I sure like the sound of that! Freshbot loves my "recent additions" page, that I added last month, and just got indexed at PR5. Hopefully this will be enough to get the freshbot to follow to the new content pages later in the month.
It sure is nice when you do something for the users, and you find out that it might help you in the SERPs. :)
I will be sure to keep an eye on this with the January update.
I haven't had the same luck with fresh listings and I do follow them closely. For me they will disappear 2-3 days after freshbot's last visit consistently. I'm looking to see if the timeframe starts with the last GET for the page or if it matters whether the server returns a 304 or 200. To be safe I update regularly any new important pages as well as any pages along freshbot's route just to be sure a 200 is returned. Of course, mysite.com is smallish so I can do that.
The deep crawler has shown up and for some reason asked for my robots.txt and / twice before heading on.
Google visited our site this am at 5:36 am but only stayed for 2 seconds and visited two pages...the home page and robots.txt. Why only stay for two seconds? Is this just the freshbot? Google first ever visit to the site was Dec 7. Had never been indexed before then, but it has been completley redesigned since then and relaunced last week. Any input? Thanks.
216.239.32.0 - 216.239.63.255
CIDR: 216.239.32.0/19
NetName: GOOGLE
NetHandle: NET-216-239-32-0-1
Parent: NET-216-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.GOOGLE.COM
NameServer: NS2.GOOGLE.COM
NameServer: NS3.GOOGLE.COM
NameServer: NS4.GOOGLE.COM
Comment:
RegDate: 2000-11-22
Updated: 2001-05-11
2. 216.239.46.36 Jan. 4, 2003 at 5:36 a.m. 2 seconds 2 (0.8%) 1 (1.5%
Last 10 Visitors
Time (EST) IP Address
12:58:10 PM 68-117-211-119.charterga.net (68.117.211.119)
12:58:10 PM 68-117-211-119.charterga.net (68.117.211.119)
12:57:50 PM 68-117-211-119.charterga.net (68.117.211.119)
12:57:50 PM 68-117-211-119.charterga.net (68.117.211.119)
12:45:10 PM crawl2.googlebot.com (216.239.46.**)
12:44:00 PM pool0553.cvx34-bradley.dialup.earthlink.net (216.244.8.43)
01:17:00 PM ip68-8-210-222.sd.sd.cox.net (68.8.210.222)
01:16:50 PM ip68-8-210-222.sd.sd.cox.net (68.8.210.222)
01:16:50 PM ip68-8-210-222.sd.sd.cox.net (68.8.210.222)
01:13:40 PM crawl5.googlebot.com (216.239.46.***)