| 7:43 am on May 23, 2006 (gmt 0)|
I think that the update has not yet finished...
I see movements every day. No big movements but sometimes it seems that some sites using "spammy" technics are loosing ranking.
For spammy technics I mean exchange of links.
In these days "trust" rank is very important.
| 10:21 am on May 23, 2006 (gmt 0)|
My God how the fear, uncertainty and doubt campaign of Google is working. Now "link exchanges" are considered "spammy"?
LOL, Matt Cutts has a devestating impact for a guy who posts once in a blue moon.
| 11:01 am on May 23, 2006 (gmt 0)|
My 2 cents: for me 220.127.116.11 is one month old results (before latest backlink recalculation)
| 11:15 am on May 23, 2006 (gmt 0)|
Do you mean 18.104.22.168 perhaps?
You can also subsitute 201, 203, 205 and 209 for the 207 too.
| 11:25 am on May 23, 2006 (gmt 0)|
>> The supplemental result (Which shows up as number 8) is from a directory that my site has not had since last august.... It is a 404 page.... from almost a year ago.... <<
Google HAS updated their Supplemental Results, but Matt Cutts has said that the process is not finished and will continue for several months.
Pages that went 404, and sites that went domain expired, before 2005 June no longer show up in the search results. Those Supplemental Results have been completely cleaned out.
New Supplemental Results have appeared for any pages that have changed their status or their content at any time since 2005 June.
For pages that are gone (404), or domain expired, the Supplemental Result has a cache of the final version that was online. For pages that have been updated, the Supplemental Result shows the previous content in the snippet, and the normal result shows current content in the snippet. In both cases the cache is usually only a few days or weeks old.
Google used to hold on to old data for almost three years. It looks like that maybe they only hold on to it for 9 to 12 months now.
They do this so that you can still find sites that recently went offline. They may also use the data to defeat domain-hopping spammers who put the same content up on a new domain when the old one is found and penalised.
For surfers trying to find fast vanishing information the Supplemental index can hold very useful data. For webmasters trying to get old data off the screen, it is often a pain in the neck. At least Google seems to have seen some sense in cutting back the timescale that they hold on to thaty data for.
| 12:15 pm on May 23, 2006 (gmt 0)|
Very easy to spam Google these days.
All one would have to do is make ten myspace accounts link them together and you'll have the number 1-10 ranking on a 20million+ keyword, that's spam rank for ya!.
You could also create 20-50 blogger accounts and do the same SPAM RANK.
| 3:18 pm on May 23, 2006 (gmt 0)|
Google now only has two of my pages listed, and one of them is index.asp. I run on a Linux server and I don't even have ASP. The index.asp (as well as any page that does not exist) gets redirected to a custom 404 error page. Looks like Google is having serious issues.
| 3:35 pm on May 23, 2006 (gmt 0)|
You had better check that the HTTP/1.1 response code really is 404 and not 302 or 200 or something equally daft.
A 404 page is never a redirect.
| 4:22 pm on May 23, 2006 (gmt 0)|
On all the 66.102. dc's I have dissapeared.. If that is what's going to happen I am mightily pissed off.
My site is squeaky clean after being penalised about this time last year. I have been on the sitemaps program since it's inception..
| 11:04 pm on May 23, 2006 (gmt 0)|
Hmm. I have been pondering this for several days. I can't work out what is happening.
I have a site where I have recently removed a word from both the title tag and from the on-page content. That special word was placed there some time ago, ready for this experiment.
The last cache of the page was on May 11th, just a few days before the words were removed.
After just a few days, things started to happen. When searching for the old words, they still appear in the title and snippet. When doing a site: search, the title and snippet reflected only the new content.
Some datacentres were still showing the old May 11th cache with the old words still in there. Other datacentres were showing a cache from May 18th with them gone.
When doing a site: search you always get the new title and description, irrespective of whether the cache is from May 11th (with the words in) or from May 18th (with the words removed).
It is very obvious that the indexing data, the cache copy, and the snippet are all separate pieces of data that are updated at different times. It is also obvious that different datacentres have a different cycle and different priorities.
The May 18th cache was later replaced by a May 20th cache in most (but not all) datacentres, and the cache is being updated to a May 23rd cache right now in most of those.
There are still some datacentres showing a May 11th cache for the page, while others show either May 20th or May 23rd.
It is still true that when searching for the words that are no longer on the page, the page is still returned as a match, and the words still show in the title and in the snippet for that occasion. The site: search shows only the new title and snippet, irrepective of what is in the linked cache.
Google has adopted some sort of short-term "sticky results" where the page is still returned for stuff that was recently on the page (much in the same way that Supplemental Results return a page for what was on it many weeks or months ago (if it has been edited) or was on it many months to years ago (if the page or the domain no longer exists at all).
I am wondering how long it will take Google to forget that those words were ever on that page, and whether it will slip that page into the Supplemental Index for that search time (while leaving it as a normal result for the current indexed content).
I have several of these experiments running, so will compare them all to see what happens. So far they all give the same sort of result.
| 11:21 pm on May 23, 2006 (gmt 0)|
Very interesting post g1smd, thanks. I can't see what benefit a 'sticky results' feature has. I mean if a search phrase is not on a page and the page has no links pointing to it with the search phrase in it then it really has no place in the top 10. Unless of course the page in on topic and still qualifies as a relevant result, LSI style.
| 11:27 pm on May 23, 2006 (gmt 0)|
I guess you would think that Google was broken if a page that you could easily find yesterday is nowhere to be found today - so they continue to rank it for a while after the content is changed, even after they have reindexed and ranked the new content too. When you visit the page itself, it is only then that you find out that the content has changed.
If the stickyness is very short, then very few people will be misled by out of data information that shows in the snippet.
If the stickyness is long, then you can rank for keywords that are not on your page long after you have removed them and changed your content to something else.
| 11:30 pm on May 23, 2006 (gmt 0)|
anyone else seeing higher than average spider activity? About 2-3 times average and enough for about 50% of my pages.
| 12:01 am on May 24, 2006 (gmt 0)|
|I guess you would think that Google was broken if a page that you could easily find yesterday is nowhere to be found today - so they continue to rank it for a while after the content is changed, even after they have reindexed and ranked the new content too. When you visit the page itself, it is only then that you find out that the content has changed. |
If this is indeed what they want to achieve by this then it is surely being ruined anyways by the erratic nature of the SERPs these days. It would also annoy me to find that what I as promised via the snippet when clicking a result wasn't actually on the page. This to means sounds like a search engine is not doing its job. I want consistent, reliable and fresh results. I'm not getting this from the big G.
| 12:38 am on May 24, 2006 (gmt 0)|
|It is still true that when searching for the words that are no longer on the page, the page is still returned as a match ... |
It is likely too soon to determine if the page will continue to be served up for searches containing the word you removed .... but are you sure that your page has no IBL's using that word in text links? If there are any such links, the page may continue to show up in search results.
I have a page on one site which contained the name of a person both in the title and on the page. That person since died, but his business (which has been sold) still exists. Despite the fact that his name has been removed, that page continues to show up when searching for the name of the deceased because there were several IBL's containing text links for the title of the page.
Just food for thought.
| 11:09 pm on May 24, 2006 (gmt 0)|
You all know deep down Google will get it right...
I now see the good results spreading slowly to:
"So Big - It deserves its own category."
Don't let us down...
[edited by: petehall at 11:33 pm (utc) on May 24, 2006]
| 11:19 pm on May 24, 2006 (gmt 0)|
Good point about the IBL anchor text, but no, in this case I know about all the IBLs: there are just three, and they do not have those words as anchor text. This is a carefully controlled experiment.
| 11:45 pm on May 24, 2006 (gmt 0)|
These have very different results
I'm becoming more convinced that quoting datacenters has gotten close to useless because they have so many machines on each datacenter that the results served up are often not the same, with the most obvious differences regularly seeable when comparing the search?/regular way versus the ie?/mcdar way.
| 12:20 am on May 25, 2006 (gmt 0)|
|I'm becoming more convinced that quoting datacenters has gotten close to useless because they have so many machines on each datacenter that the results served up are often not the same |
Agreed but not when you see the results change for a long period, which I had prior to posting.
| 10:01 am on May 25, 2006 (gmt 0)|
Just to observe that I have seen similar results.
Broadly speaking, I think you have identified some aspect of the way Google is currently operating which is different to pre-big Daddy.
I'm not sure it is intentional, though: maybe it is just a side-effect of rolling so many experments through so many data centers.
| 12:24 pm on May 25, 2006 (gmt 0)|
A site I track (that suffers the symptoms associated with the "sandbox" syndrome) is jumping from sub 100 to position #7 (for its site name) on these DCs:
but isn't visible on
| 12:37 pm on May 25, 2006 (gmt 0)|
|You all know deep down Google will get it right... |
Yeah right. When? When is the "weather report" coming out. Where is Harith/Reseller to guide us "in advance" of the current updation.
Are we running out of steam dudes?
| 1:18 pm on May 25, 2006 (gmt 0)|
|but isn't visible on |
This one has reverted to it's previous state.
| 4:00 pm on May 25, 2006 (gmt 0)|
Running out of steam...?
.....well, maybe. This CAN be exhausting! The lack of information, the confusion, the worry about one's business, etc..
I also note that the promised increase in communication seems to have fizzled out. Even a "we're still looking at it" or "we're sure there's nothing wrong" or "have patience, guys" would be a step forward from this bizarrely uncommunicative culture Google have created.
| 4:10 pm on May 25, 2006 (gmt 0)|
I am seeing better results on the following DC's as well:
Is it something to be excited about?
| 4:13 pm on May 25, 2006 (gmt 0)|
"I also note that the promised increase in communication seems to have fizzled out."
Maybe because the folks at the plex have no good news to announce. Or continue to have unresloved problems.
Personally, I prefer now communications of my kind WebmasterWorld fellows and their feedback than the latest generic no value communications from Google's folks.
| 5:00 pm on May 25, 2006 (gmt 0)|
this is what's live since yesterday from my area (NW usa)
| 8:48 pm on May 25, 2006 (gmt 0)|
For a page where the content was changed on May 15th, some datacentres remained stuck on the old May 11th cache, while some updated to a new cache dated May 18th. Most of the May 18th cache copies updated to a May 20th date a few days later.
The search results showed only the new content in both the title and snippet in a site: search, but always showed the old (deleted) content in both the title and the snippet if you made a keyword search for that old content.
Yesterday, all cache copies reverted back to the May 11th date again, and show the old content.
The title and snippet continues to operate as above; what you see depends on what you searched for. In a site: search the title and snippet do NOT match the old cache content.
Previously it was only Supplemental Results that showed this "stickyness" of old content - and kept that content was kept for several years.
Now, normal results show this too; and it will be interesting to see if the stickyness is a reasonable 2 or 3 weeks or an unreasonable 2 or 3 months or more...
| 1:27 am on May 26, 2006 (gmt 0)|
I'm surpised no one has mentioned that this is another biiiig holiday weekend in the USA and a great opportunity to see major tweaking by Google. Many were in love with the idea of an Easter update with all it's rebirth symbolism but this is a 3 or 4 day holiday which should see many Americans hit the road and turn off their computers.
Nothing may actually happen but this is something for the conspiracy theorists to chew on.
| 7:21 pm on May 26, 2006 (gmt 0)|
>> I am seeing better results on the following DC's as well:
I'm seeing worse :-P
The one bright spot, Yahoo and MSN are sending more my way (not just percentage wise, but actual visitors). It's weird how over the past week Google has been steadily dropping pages while Yahoo and MSN are both adding them, but who cares, traffic is traffic.
| 8:38 pm on May 26, 2006 (gmt 0)|
Hmm, some of my cache dates have updated to May 24th, and other datacentres are still stuck at May 11th.
A new page linked only from that page now shows up in all datacentres, so the new content (the link) added on May 21st has been indexed and followed even if the cache copy hasn't been updated to show that newer version of the page.
| This 133 message thread spans 5 pages: < < 133 ( 1  3 4 5 ) > > |