Welcome to WebmasterWorld Guest from 54.198.69.193

Message Too Old, No Replies

New Serps on Google since 1st January 2006

Observations and comments

     
6:03 pm on Jan 1, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi Folks

It seems that what we thought to be testing serps on the test DC [64.233.179.104...] have suddenly today started showing on "defaults" googles, as google.de, google.co.uk and google.com etc...
While the test DC isn't showing anymore the new serps.

I'm starting this thread to post our remarks concerning the new serps.

Thanks!

6:11 pm on Jan 1, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



My GG default is 74.14.203.104

While this DC seems to show a combo of the new SERPs and the old SERPs, I would be happy with a complete switch over to the “new" SERPs that look to be propagating.

6:47 pm on Jan 1, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



It seems that what we thought to be testing serps on the test DC [64.233.179.104...] have suddenly today started showing on "defaults" googles, as google.de, google.co.uk and google.com etc...

No, they're not the same. A wrong assumption.

6:49 pm on Jan 1, 2006 (gmt 0)

10+ Year Member



Test results are here at the moment - [66.249.93.104...] and not on the test DC.

The 66.249.93.104 has been serving results on Google.com for me.

6:59 pm on Jan 1, 2006 (gmt 0)

5+ Year Member



That's right indeed I see, but www.google.com shows these results with "&e= tag" and the serps keep switching with other test results on www.google.com (2 different test results?, how long would this stay.
7:05 pm on Jan 1, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



66.249.93.104 is very close to the test DC (which I saw two days ago) with less pages and new caches. My default google.com and google.ca show different and haven't changed for the last three days. Tried google.de and google.co.uk and saw the same results.
7:34 pm on Jan 1, 2006 (gmt 0)

WebmasterWorld Senior Member steveb is a WebmasterWorld Top Contributor of All Time 10+ Year Member



The test data has moved to other dcs but not on where it was. Not much newsworthy in that.
8:07 pm on Jan 1, 2006 (gmt 0)

10+ Year Member



I think my new years resolution will be not to read anything which includes the words "test DC", "SERPS" or other related words it gives me headaches.

Am I alone in this? Even 4 ibuprofen doesn't help.

I'm afraid this resolution won't last very long. :-(

8:29 pm on Jan 1, 2006 (gmt 0)

WebmasterWorld Senior Member g1smd is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month



>> 74.14.203.104 <<

No such IP.

Did you mean 64.14.203.104 instead?

Nope. That doesn't work either...

10:49 pm on Jan 1, 2006 (gmt 0)

5+ Year Member



I got results from [66.249.93.99...] on Google.de the whole day and for one of my domains they are pretty cool. Today this domain got so far additional 1000 visitors from Google.de.
11:53 pm on Jan 1, 2006 (gmt 0)

10+ Year Member



64.233.179.104 have now the Test Results again!
2:44 am on Jan 2, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



>> 74.14.203.104 <<

Sorry 72.14.203.104 is the default DC I get.

3:15 am on Jan 2, 2006 (gmt 0)

5+ Year Member



Reseller. I think you are right. I have been watching the 2 test data centers closely. The other DC mentioned earlier is new however I use Mcdars tool and as of the last 45 minutes the test results have spread to 5 data centers. This is the first time this has happened. The results have never left those 2 data centers.. I think it is time.. Bring on Big Daddy.
5:57 am on Jan 2, 2006 (gmt 0)

10+ Year Member



So is 64.233.179.99 considered a test datacenter? I show way different results on this one than on regular google.
6:17 am on Jan 2, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Good morning Folks

Great first working day of 2006 and the first cup of Cappuccino has already been consumed :-)

I still see the new serps on my default google.com IP 64.233.183.104 . I see also fresh cache as to my sites.

I wish to hear from fellow members who have canonical and supplemental issues which have been affecting their sites. Do you see folks any signs of improvements on the new serps?

Wish you all a great day.

7:13 am on Jan 2, 2006 (gmt 0)



Good Day Reseller & Happy New Year,

It would seem that my ban was caused by duplicate content caused by the www. non www. problems.

Now if I search for mysite.co.uk, I get www.mysite.co.uk, and no other options. I still have some out of date supplimental pages, but given that I was not listed at all 3 days ago ... I'm quite happy.

I gutted & rebuilt my main site during the Jagger aftermath, but my PR seems to be same as before.

The only concern is that the last time this happened my site got whacked again when my incoming links were recalcuted (Aprox 10 days after reinclusion in September). But the plus seems to be that there is no solid rule for how long you spend being banned. I think that webmasters tend to blame their pages for getting banned, when in actuality it's just another update and it could hit anyone.

All the best & keep drinking the coffee :-)

Col

7:35 am on Jan 2, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



colin_h

>>Good Day Reseller & Happy New Year,

It would seem that my ban was caused by duplicate content caused by the www. non www. problems.

Now if I search for mysite.co.uk, I get www.mysite.co.uk, and no other options. I still have some out of date supplimental pages, but given that I was not listed at all 3 days ago ... I'm quite happy.<<

Happy New Year to you too my friend :-)

Thats very encouraging news you bring us. Lets hope the folks at the plex continue on resolving such issues.

7:40 am on Jan 2, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi Colin and co. Happy New Years guys

Colin, if you do a search for site:mysite.co.uk -www does this show supplemental results for the non www url?

If so, it's likely you are not out of the storm yet.

However, being in the index has gotta make you happy at this point.

For all of my sites the index search for non www was remedied a while back after imlementing the infamous 301 r, however in all sites there are tons of lingering non ww results that are supplementals.

9:27 am on Jan 2, 2006 (gmt 0)

10+ Year Member



66.249.93.104, 64.233.179.99 and 64.233.179.104 all give me massive pagecount crash for one of my sites, from 11,000+ pages to 800+ (probably about what it should be!). Not a supplemental in sight and only a handful of 301 URL-only pages. Results not quite as fresh as my regular Google.com (64.233.183.104), which has pages crawled only yesterday already showing, but which is still showing the (wrong) 11,000 pagecount.

Happy New Year.

10:05 am on Jan 2, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Before jagger I did a 301 on 3,000+ pages in order to shorten the url. After jagger, the first thing I saw was that I now had 6,000+ pages indexed, the new pages showed up but the 3,000+ 301 pages didn't go away. Out of those 6,000+ only 7 weren't supplemental.

Well my entire site was supplemental I went ahead and set up a sitemap and used the google url remover to axe the 301 pages and all other old pages. It still said I had 6,000+ results even though the 301's didn't show up in the serps anymore. Ninety percent of my pages were cached but the cache was from months ago.

I just checked the new results on [64.233.179.104...] and I now have 400+ pages, all freshly cached, no supplemental. I sure hope this sticks.

10:09 am on Jan 2, 2006 (gmt 0)

10+ Year Member



Surprising that this thread is not moving at a faster rate - could be that people are still on the Hols - or perhaps lots of people are not seeing much.

Even for the purpose of the test - which I assume is to correct canonicals and 301s then little excitment has been generated yet - I guess that is probably because although Google has sorted out some Canonical probs (esp Homepages) - the pages dont rank. (for sites that have had the problem for a while at any rate)

Hmmmz - seems a bit pointless correcting the canonical issue if the problems that were caused by the issue still remain - eg pages/sites got penalised.

I just hope the next PR update brings some for the long term effected sites - it seems the short term effected are coming back - but then they probably have not had the PR stripped totally from the site like the older problems sites have.

10:13 am on Jan 2, 2006 (gmt 0)

10+ Year Member



my main site is still under the hurricane of canonicals+pending301... site operator brings strange results ( missing homepage, etc) mozilla googlebot is eating my whole site yesterday and today as never google did before... i am sure it cannot get worse, so it can only get better :-). is this mozilla googlebot fast activity only for affected websites?
10:17 am on Jan 2, 2006 (gmt 0)

10+ Year Member



Happy New Year everyone,

as far as I can tell the change has been reverted again, after seeing the new results for 2 days online.
On McDar I now see the new results only on Test Dc's 64.233.179.99 & .104.

The google.com results for me are currently served from 216.239.59.147.

What it pity. But I'm hopeful results make it back soon.

10:19 am on Jan 2, 2006 (gmt 0)

5+ Year Member



Hey all...just joined the forum though i've read a bit before - great stuff. This update looks pretty good...a bit of reshuffling - seems to have taken out a few spam sites for my searches. How long does it usually take for these updates to be installed on the general servers?
10:22 am on Jan 2, 2006 (gmt 0)

5+ Year Member



Oh guess the answer to my question is already on another post:

"OK - folks remember also that MC said that this index will roll out in months and is in a test state so I guess no need for early panic stations and slagging of Google in this thread."

shame, I was excited...

10:30 am on Jan 2, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Dayo,
Wish you a great Y2K6 :-)

As you say, it is quite obvious that canonical/301 healing that has been implemented on 64.233.179.X is just ornamental. Nothing more than that.
This test DC returns the correct canonical for almost all domains I see and the other DCs which show test results (such as 66.249.93.X) still have canonical problems as always. Yet, results are almost the same. Can say that canonical issue addressing has had no impact on SERPs as yet on the Test DC.

10:33 am on Jan 2, 2006 (gmt 0)

10+ Year Member



Thanks McMahon - Happy New Year too :)

Yes, that is what may have happened - lets hope it is not just an ornamental change - Google have done this before - Hiding a problem rather than fixing it. (eg. Removing hijacks from a site search.)

10:54 am on Jan 2, 2006 (gmt 0)



Hi Cain,

Phew! No Supplimentals for the search -www. All I get is my front page listed with the www showing. When I search deeper into pages from this site there are some supplimentals for page now missing since my update, but they do not rate highly in searches anymore. My new pages do rate well and compete in some instances up to 20+ million.

I agree though, probably no time to celebrate yet. I'll just watch with interest as google is now a hobby rather than business, as was once the case.

All the best

Col :-)

11:17 am on Jan 2, 2006 (gmt 0)

5+ Year Member



All pages (including the homepage) of one of my sites went supplemental during last summer. There was no canonical problem (a 301 was in place long before). There was nothing that can be construed as gaming the Google, or dupe content, or anything triggering a penalty or ban. It is a small information site with some 15 pages in an uncompetitive niche.

And I did nothing, not changed/modified anything. Well until last week: I decided to ban google through robots.txt. My intention was to completely remove my site from Google index as webmasterworld did recently, and let it re-crawl the site afterwards.

Now, some of the pages (icluding the homepage) reappeared in some of the datacenters (eg. 66.249.93.104) as if out of a blue sky, with caches dating back 20th December, before implementing robots exclusion. So, Google seems correcting the so called "collateral damages" on its own, without any action on the part of the webmasters.

4:24 pm on Jan 2, 2006 (gmt 0)

10+ Year Member



The results returned from DC 64.233.179.104 now, are the same that were returned from www.google.de early this morning.

At least for queries with hl=de.

This 162 message thread spans 6 pages: 162
 

Featured Threads

Hot Threads This Week

Hot Threads This Month