Yet another "Cache, Freshbot, Everflux, Index" Q.

(I still don't get it :)

[verbum]

On March 19 I moved my site to another server, and hence to another IP. I left the original, basically identical (it's a forum so...) content on the old IP until the googlebot had a cache of the new site, which was displayed in every pertinent SERP beginning about two weeks ago. Satisfied that Google was now "aware" of the IP change, I deleted the old site about a week ago. Yesterday, Google suddenly reverted to the old cache in the index; the new one, which I thought indexed, is nowhere to be found (of course.). I'm guessing that this phemonenon is owing to the fact that, while the freshbot visited the new site (and continues to do so), the deepbot has not. OK. But then why would the freshbot's cache suddenly be ignored? I also noticed (just after the IP change) that the PR on the http:// site.com dropped from 5 to 3 while www.site.com increased from 1 to 3. The backlinks have not changed in number; the only change I can figure might be significant here is that the DMOZ page where my site is indexed dropped from 5 to 4 during this time.

While hardly frantic, I'm nevertheless puzzled by the Google Machine's "behavior" and wonder if some kind soul might care to explain (to whatever extent) what's going on. Looking over past posts on this forum, I realize that part of the problem might be that I deleted the old site before the new one was actually indexed (not just crawled) by the deepbot--but I thought it was indexed because the new site was in the..um..index. Some sort of penalty maybe?

Thanks!

[mipapage]

verbum,

I just moved my site over this weekend - seems like a good time!

Anyway, from what I know your cache problems seem to me to simply be everflux. It happens all the time that an old cash shows up, and in fact for me it is coming in quite handy - see, when I moved sites, I forgot to delete the 'this site has not moved in yet' index.html file. Freshy came along and grabbed that file instead of my index.htm file, and now that is my cache! Google seems to be quite smart though, as it is referring back to an old description so at least I haven't dropped right off the page.

WRT deepbot, I would imagine that it may be a good idea to leave your site up in the old spot, just to make sure. From what I gather it has one dns for your site, and one only. So the whole scare of duplicate content only applies if you in fact have two domains with duplicate content.

whoo boy I hope that makes sense...

[Oaf357]

Welcome to Webmaster World, verbum!

It's everflux. Sadly enough, Google does this quite often. SERPs change constantly due to this fact (as well as the Google cache). I honestly think it's great because it let's you know how powerful content might be ahead of time. It does have its side effects (in your case) but give it a month (or two) and everything will be back to normal.

[verbum]

Everflux it is, then.

Google seems to be quite smart though, as it is referring back to an old description so at least I haven't dropped right off the page.

Good point, mipapage: Albeit with a slightly older cache (actually, the one corresponding to the last update), my site does remain in the index.

I honestly think it's great because it let's you know how powerful content might be ahead of time.

Interesting observation, Oaf357. I hadn't seriously considered that the Everflux listing(s) might foreshadow SERPs in the "permanent" index.

Thank you both!