Forum Moderators: Robert Charlton & goodroi
I would expect that the Google staff is going to test and tweak and test until they get the update to do what they want it to do. They have some goal and surely some standards against which they are testing.
You know they have to make it right. If not, they get one big black eye.
So I guess we will see up and down and around while they try to make it right.
So we just wait and work on that which we control. As for the SERPS, for now they are just leaves in a Google data storm.
If GG said that 66.102.9.104 is going to be the DC from where Jagger's final update will come from, what does the fluctuating of all those other DC's have to do with anything? Unless you think those "post-jagger" DC's are now going to be the de facto results?
Wish GG would get in here to clear this up.
Let's say I have a site that has been indexed by Google for years. Let's also say that I just completely changed the content (2 days ago) of one of the top level pages (PR6) of this site. I see today that Google's cache of this page shows the updated content.
My first question is, how long should it be before this page starts ranking in the SERPS based on this NEW content? Should it be as soon as the cache shows the new content (which is now) or will there be a little bit of a delay? Maybe even until the next big update?
My second question is exactly the same, but instead of updated content of an already indexed page, I'm wondering about a completely new page that has just been indexed yesterday which is part of a site already indexed.
I've been sort of out of the SEO world for little while, so the answers to these questions have changed since I last knew them. =]
The reason I ask is that I notice throughout this update that you two have had problems at exactly the same time as me...
Not really noticing anything much - I have so far to come back from that I dont know where the first signs of a recovery would be - I would assume Googlebot actually crawling my homepage and not just internals for my main site.
I doubt if anything you have done as a result of the update has had any impact yet.
Thanks for the reply.
Am I right in that this is the first time the two sets of results have matched? maybe I should perform more keyword tests to be sure that they do actually match. Googleguy appeared to suggest that the two would merge in some manner, or feed one another. If they are now identical, maybe that suggests that the results will now propogate. What do others think?
Also, it seems my site was dramatically "weakened" as I can type into Google: "competitive keyword" domain.com, and sometimes other sites will appear in front. But I type "not so competitive keyphrase" domain.com, and I will rank number one. So I come to the conclusion this new update really affects newer sites, and weakens them severely.
So I would like to say, I was clearly a case affected by Bourbon, and my site "seems" to be ok now. Keep in mind, I abandoned this site completely for 6 months too (while working on another site).
[edited by: chopin2256 at 7:31 pm (utc) on Nov. 17, 2005]
Same here, I couldn't believe to see my website back on the first page after many months of nowhere to be found. Now the results have reverted back and I'm actually starting to wonder if this was a dream:(
Now the results have reverted back and I'm actually starting to wonder if this was a dream:(
There actually is an antidote for this.
First you need to find a result page you particularly like on Google.
Then if you are on windows or most X's on linux just hit Print Screen; which is a key just next to the very useful and nobody-knows-why-it's-still-there key called Scroll Lock.
On Windows you will need to paste your work to the Paint application. On linux you'll be asked if you wish to save a jpeg to your home folder.
Place this JPEG as your background image.
Whenever you feel you miss your old position just clear your desktop and stare at the marvellous SERP you capture.
This will surely fix the "i had a dream this afternoon" SERP effect.
Hi Folks
It seems that we have reached a point where guess and suggestions are all what we have. However, a short "analysis" of the few lines that Matt "Inigo" Cutts wrote on his blog on 10th November 2005 might help us understand the current situation of update Jagger (nickname update Saga :-)).
Matt wrote: ( [mattcutts.com...] )
As Jagger1 and Jagger2 wind down and Jagger3 is visible at 66.102.9.104, I wanted to recap where things stand.
* Jagger1 was visible at most data centers starting around 10/16/05. A second, refreshed version of Jagger1 was visible recently at 66.102.7.104 and was at all data centers by 11/7/05.
Which means that Jagger1 is at all the DCs at present.
* Jagger2 was visible starting at 66.102.9.104 starting around 10/27/05. Jagger2 was visible at all data centers by 11/6/05.
And that means that Jagger2 is at all the DCs at present too.
What is left of Jagger update to migrate to the other DCS is only Jagger3. Lets take a look at what Inigo wrote about that
* Jagger3 was visible starting at 66.102.9.104 around 11/4/2005. Jagger3 is not widely visible yet (it might also be at 216.239.51.104), but I expect it migrate to other data centers over time.
Matt hasn't given a specific date or period of time for the migration of Jagger3. I.e it could take any time!
Q: Is the update winding down?
A: It’s starting to. Recall that all of Jagger1/2/3 are separate changes. Jagger1 and 2 are done, and you can see what Jagger3 will look like at 66.102.9.104.
Again Matt underline that Jagger1 & Jagger2 are done. And again nothing about how long it will take Jagger3 to migrate to other DCs! Now why is Matt not so sure of that?
Not even a weather report to say for examples: Hi Folks! At present Jagger3 has reached the following DCs ...
And thats what I regard as food for the thought ;-)
Now why is Matt not so sure of that?
Because his job is to disinform you....
And he's not complaining about the wages.
>>Because his job is to disinform you...<<
I don't think so. In fact Matt has already informed us, as per my previous post, about the destiny of Jagger3, and I have also wrote about it in my msg #:813 Nov 16, 2005
[webmasterworld.com...]
====================================================
reseller
Preferred Member
view member profile
send local msg
joined:Feb 6, 2005
posts:416
msg #:813 4:48 am on Nov 16, 2005 (utc 0)
Ladies & Gentlemen
Our brother jagger3 has died in the 4 DCs - May god bless his soul! (:(
Please lets pray together:
Depart, O jagger3 soul, out of this world;
In the Name of the plex who created you;
In the Name of the plex who redeemed you;
In the Name of the plex who sanctifies you.
May your rest be this day in peace,
and your dwelling place in the Paradise of the plex.
Amen.
==================================================
It was food for thought when Matt Cutts posted it over a week ago. I, for one, had read the post and digested the same at that time.
As for now, it no longer holds any new news. But, of course, you guys need something to write about, so you might as well bring up old news to rehash again since you have rehashed everything else 50 times.
Good grief ... I've created two more websites over the past week. I am amazed at the incredible amount of time spent flappin gums about the unknown around here. There is no use guessing.
Just wait until J3 is settled and then take a look at your positioning, then take appropriate actions based on your analysis.
But, trying to analyze and adjust sites during propogation of a new algo is folly ... you'll never know what the issue(s) are/were with your site.
As for me, I'll continue to check in here once a week and read the last page of posts. It is there that I can find all I need to know! Once I hear J3 is fully propogated, I'll do my analysis. So far, I like what I see.
Now, for gosh sakes, go do something!