J3 is moving along to more DC's for a few of the KW's that we watch. I use: http://www.mcdar.net/q-check/datatool.asp with these two options: * Check across Datacenter IP C-Block(Group A) * Check across Datacenter IP C-Block(Group B)
How many times? Pr is irrelevant, SERPs are all that matter. Thats what to check out and what people should be looking at. SERPs across data centers.
I hate to say, but I see 3 sets myself. 64.233.179.104 and 64.233.183.99 seem very similar, almost like normal flux, but there are several sites that missing from one or the other. 64.233.161.99 seems to be jagger2 results. For the kw phrase web hosting paypal they show quite differently. Notice thewhir.com in the top 10 on 64.233.179.104. They used to show up consistently in the top 20 before the whole 302 redirect bug came to town, usually from articles about PayPal from a web hosting perspective. They are at #40 on 64.233.183.99. #39 and #40 on 64.233.161.99, jagger2 results. Are we seeing some updating, perhaps some filters applied, or is this more jagger foot dragging?
Man this update is so messed up. It makes no sense it's kind of like Vermont weather If you don't like what it is doing now wait 5 minutes and it will change..
NetMidWest, I hope it isn't over yet I lost a lot of positions check this link: http://www.searchenginejournal.com/index.php?p=2563
I find the article interesting however I do not believe Jagger is over based on this persons assumptions. If it is over then my belief is this update has hurt Google as far as the results being pulled. I am seeing for some search words okay results with some rellevancy however for others I am seeing complete spam. I also noticed by following the above link that the site is engaging in violating adsense TOS atleast as I now understand it. The hands pointing to the ad's to me seem to be encouraging people to click on the ad's am I wrong?
Looks like rehashed BS, IMHO. I am still of the belief that they lost or dumped purposely pre-scored data (McDar's theory). I feel this was to correct for tweaks made to the algo and filters made to hide the insidious 302 redirect hijack bug, and to filter out scrapers and link pages served to multiple sites from the same database. (In this, I somewhat agree with the article.) The problem with 'Information retrieval based on historical data' is that the historical data is corrupt due to the 302 redirect bug (and other schemes). I was caught early in the bug, did flips and twists to get out from under it, only to get 'jacked by another site. I have been hosting sites through www.netmidwest.com since 2001, I am in the DMOZ, but due to the 302 redirect bugs, the historical data on my site is incomplete. In order to implement the historical data patent, they had to fix the bug and begin with new data, or go back over the old raw data with a fixed algo and filters. The former is the easiest, but delays the implementation unless compared to the old raw data, the latter would take forever and ALOT of server power. Without doing so, they only further compound the problems, bugs fixed or not. I think that these posts: http://forums.digitalpoint.com/showpost.php?p=448971&postcount=31 http://forums.digitalpoint.com/showthread.php?p=439801#post439801 bear out what I am saying - sites that were ranking for a term before the 302 redirect are reappearing, and the seemingly irrelevant listings can be backtracked to a site that mentions the keywords and links out to the site. In the case of php.net, the discussion was about using shopping carts provided by a web hosting company with PayPal, and suggesting the poster read up on php... php.net does mention PayPal on the homepage briefly, but the density is not there to rank it in the top 10. At this time, Google seems to have dropped the piece of the algo that decides who to credit a link for - the site that links out, or the site linked to. The forum linking out was probably more relevant to the query, but not deserving of a top 10 ranking. php.net and it's sheer PR and perhaps historical data - without that piece of the algo - won out, but is irrelevant. I don't think that we can declare jagger truly finished until the next update, even if the serps stabilize. I feel the changes I see happening in the algos and filters will not become fully evident until then. I really regret starting this thread, but I thought I saw it rolling out over several datacenters, and miscounted the number. I thought it was going for sure.
To Add I am now seeing some major Flux on 2 main DC's again this morning...(Flux if that is what you want to call it) 64.233.189.104 66.102.7.104