Forum Moderators: Robert Charlton & goodroi
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!
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.
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.
The 66.249.93.104 has been serving results on Google.com for me.
I'm afraid this resolution won't last very long. :-(
No such IP.
Did you mean 64.14.203.104 instead?
Nope. That doesn't work either...
Sorry 72.14.203.104 is the default DC I get.
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.
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
>>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.
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.
Happy New Year.
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.
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.
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.
"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...
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.
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.)
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 :-)
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.
At least for queries with hl=de.
