Forum Moderators: Robert Charlton & goodroi
I don't know why I find it so funny.. But I do. Although this should reinforce the idea that this are distinct and non-related changes for those who seem to believe otherwise.
We will likely see some of Jagger 3 on some dc's before Jagger 2 has gotten to all of them.
Matt Said,
November 3, 2005 @ 1:39 pmLet’s see. Multiple data centers are now showing Jagger2, but I don’t think every data center is. I believe Jagger2 is at the cluster of data centers that includes 66.102.9.104. Stephen, I don’t think we support crawl-delay in robots.txt. But you might check out sitemaps–it might allow you more control.
Paul, the objective of Jagger is to improve our index results. The three stages are actually three independent launches.
urdudesamy, there are some Jagger1-related changes going on at 66.102.7.104.
Ahhhh, the DC I mentioned, 66.102.11.99, is showing the same results as above mention by MC. At least I sort of got the real Jagger 2 pegged. Everything will move from there. I still think I know the direction this is headed.
Hi Folks
Just for the benifit of our new kind fellow members.
Jagger Update, which was announced officially on 18 October 2005, but which might have started already on 22nd September 2005, is divided to 3 individual separate stages:
- Jagger1 (PR & Backlinks update)
- Jagger2 (dealing with spam issues)
- Jagger3 (dealing with index issues including canonicals and maybe supplementals issues)
In Matt's own words:
"Jagger1, Jagger2, and Jagger3 are mostly independent changes, but they�re occurring closely enough in time (plus they interact to some degree) that it�s clearer just to act as if they were one update for feedback purposes."
Which means, IMO, that Jagger3, in order to start, it doesn't need to wait for Jagger1 or Jagger2 to spread to all the DCs.
I hope this helps.