| 5:28 pm on Jan 17, 2006 (gmt 0)|
>> And while you are waiting for that miracle to happen, I suggest you and I travel to USA and join BillyS in watching the american green grass grow :-)
Two new blades of grass on the front lawn this morning, 50 pages fewer in BigDaddy today.
| 5:35 pm on Jan 17, 2006 (gmt 0)|
Something I've noticed today - G has not updated all the internal backlinks for my site - for the pages where it has updated them, we are ranking well, for the ones with outdated internal links, we are a long way down the index or not in it at all.
| 5:37 pm on Jan 17, 2006 (gmt 0)|
More snow here :-)
I'm going crazy over getting three different sets of SERPs using three different browsers on the same system.
I'll just stick to shoveling snow I think. Or doing some real work.
| 6:18 pm on Jan 17, 2006 (gmt 0)|
For what it's worth. My site that had it's downfall on Feb 2nd of last year is now seeing updated caches (all in the year 2006) on 184.108.40.206.
A few weeks ago big daddy had all the main pages and about 1/3 of the site listed with correct url's and descriptions but a lot of the caches were old, some from Jan 2005. The only pages with current caches were the few that regular google had listed.
Now all those pages are still there that were on big daddy a few weeks ago but with updated caches. Some of these pages haven't been on any datacenter except big daddy for almost a year.
Still no supplementals or url only pages on big daddy. I have even found several good keywords where we actually are ranking in the top 50 at least. I haven't analyzed that part much, I am just thrilled to be found in the serps at all. It has been so long since I saw our pages show up for any terms that I will call this progress (for my site anyway on big daddy).
Not that this means anything anymore but I was on the site a few days ago and noticed that my pages were showing pagerank on the google toolbar. It was only up there for a little bit that I saw though. Some of the pages I looked at had the old pagerank on them but others were different than what they were the last time I could see that little green bar. (Some up and some down).
| 7:08 pm on Jan 17, 2006 (gmt 0)|
I am seeing the odd good thing too - but I try to be pessimistic until something concrete is definetly happening.
It sounds like some of your pages went PR0 - did your homepage also go PR0?
| 7:22 pm on Jan 17, 2006 (gmt 0)|
Most of our site went PR 0, including our home page.
Very little of the site shows pr on the toolbar currently and the home page is still 0.
It took quite awhile for the toolbar to show that the PR was 0 on the homepage, but we could tell by our crawls that it had happened long before the toolbar told us. Plus all our pages just slowly disappeared and went url only and supplemental.
Still the only thing that we can figure that caused it is canonical, 302, and 301 problems.
I don't know if you have seen this but when I watch mozillabot crawl our site. It often hits a page as a 200 and then comes back a couple more times without the www's and hits it as a 301.
In the past mozilla bot would hit the pages as a 301 (no www) and then turn around and hit it again with the www's as a 200.
Regular googlebot will hit the page without the www's and get the 301 and then about 1/2 the time come back and get the 200. When it hits our robots without the www it always immediately comes back with the 200.
Not sure if that tells us anything but it is a changing trend I have been seeing in mozillabot. I don't even know if that is good or bad!
| 9:33 pm on Jan 17, 2006 (gmt 0)|
Good evening Folks
I'm happy to announce that the folks at the plex have removed BigDaddy from my two favorite DCs. Maybe because I wrote Matt that I will spam his blog if he isn't going to leave my DC in peace :-)
Thanks to Matt & Co ;-)
| 9:52 pm on Jan 17, 2006 (gmt 0)|
I have a dumb question
Which DC is currently showing big daddy or are none of them
| 9:56 pm on Jan 17, 2006 (gmt 0)|
[220.127.116.11...] is showing BigDaddy
| 11:33 pm on Jan 17, 2006 (gmt 0)|
Don't do that, 18.104.22.168 is (was) the big daddy DC that I was seeing all my cache's updated on. Now they are gone : (
| 12:03 am on Jan 18, 2006 (gmt 0)|
I just checked and I am seeing mozillabot crawl pages that haven't been crawled in quite some time. Right now it is crawling my site really hard.
| 3:18 am on Jan 18, 2006 (gmt 0)|
"http://22.214.171.124 is showing BigDaddy"
I think it's not BigDaddy DC, bcuz the results are showing at my default google.com - [126.96.36.199...]
Thanks in advance.
| 3:27 am on Jan 18, 2006 (gmt 0)|
the sf giants works everytime if you want to check for BigDaddy. If you get mlb dot com then it's BigDaddy.
| 6:15 am on Jan 18, 2006 (gmt 0)|
Anyone can give a thread? how do you know which DC is testing, and which DC will be the final result?
I track one of my sites indexed pages, see the below report.
DC Dec 31,2005 Jan 10,2006 Jan 18,06
188.8.131.52 37,100 33,200 198,000
184.108.40.206 4,090 33,200 198,000
220.127.116.11 37,100 33,200 14,700
18.104.22.168 1,380 33,600 1,620
www.google.com 37,100 33,200 18,000
google.com.cn 4,090 3,660 1,980
22.214.171.124 33,000 33,200 14,700
What do you think? Our site is chinese, and host is in Sg, it's a new domain name, but the old site rewrite to this new site. new domain name was launched on Dec 12,2005.
Pls give some advise, thanks.
| 6:25 am on Jan 18, 2006 (gmt 0)|
DC ¦ Dec 31,2005 ¦ Jan 10,2006 ¦ Jan 18,06
126.96.36.199 ¦ 37,100 ¦ 33,200 ¦ 198,000
188.8.131.52 ¦ 4,090 ¦ 33,200 ¦ 198,000
184.108.40.206 ¦ 37,100 ¦ 33,200 ¦ 14,700
220.127.116.11 ¦ 1,380 ¦ 33,600 ¦ 1,620
www.google.com ¦ 37,100 ¦ 33,200 ¦ 18,000
google.com.cn ¦ 4,090 ¦ 3,660 ¦ 1,980
18.104.22.168 ¦ 33,000 ¦ 33,200 ¦ 14,700
| 7:00 am on Jan 18, 2006 (gmt 0)|
Has the Plex lost interest in spam reporting?
Good morning folks
Ok. I'm giving up. It seems the folks at the plex think that hijacking my two babies DCs is more fun and therefore they put again that BigDaddy thing on them again. Maybe its a way to press for BigDaddy feedback, and I assure you they are gonna get what they have asked for :-)
Here is an honest reseller BigDaddy feedback.
Spam - I still see for example a site on top of BigDaddy serps (for a sector I watch) using gateway pages and another using keyword stuffing. And yes, I have reported the two sites to Google, but it seems that WebSpam Team isn't interested in spam reports anymore. Even Inigo has stopped mentioning spam reporting.
Search Relevancy - Poor..very poor. I see irrelevant sites on top of the serps just because they have mentioned one of my test keywords on their pages.
Canonicals - Not much improvements. Better to keep watching BillyS grass grow :-)
Supplementals - Ask my kind fellow member steveb and he shall tell you that not much improvements have taken place on that part either.
Have I forgotten anything in my feedback ;-)
Its therefore I keep asking fellow members not to waste time on BigDaddy. Better to watch the other DCs which is more inspiring, IMO.
Wish you all a great day.
God Bless WebmasterWorld community.
| 7:43 am on Jan 18, 2006 (gmt 0)|
As I checked site index of you site I found that you have two result:
On BD DC you have > 546,000 page indexes
On non BD DC you have > 601,000 page indexes
Try to check again and let us know what's the result you got...
| 8:20 am on Jan 18, 2006 (gmt 0)|
looks very bad for Google, results getting worse on each update, Fooling all webmasters.
I see more spam, and sites inter-connected on the first 5 pages of results.
many old sites , non relevant sites. As far as real estate goes it has died on Google, they just want realtors to pay for ad words.
Yahoo and Msn is much better for real estate sites, google is dropping many realtors in favor of worthless directories,because of this many realtors are creating there own directories. When will they learn the more they try to beat the webmasters the worse there results get. I know many people on here think google is the greatest, but they are just fooling themselves. Compare the 3 SE
and google can never stand up to MSN and Yahoo page for page.
| 9:21 am on Jan 18, 2006 (gmt 0)|
That pretty much mirrors what has happened to my main site - although I have not watched Mozilla Googlebot that closely so dont know if it is getting 200s followed by 301s.....
Last time I looked it hit the 301 and then went to the url which was redirected to and got the 200.
For me I have had lots of pages crawled by Mozilla Googlebot which have not made any dcs yet.
BD results are back on [22.214.171.124...] and 104 - to me these look like a more advanced stage than the other dc.
Although I am getting the odd page come back - it is like for a total title match and it returns in the 50s to 60s - while some pages dont rank at all still - I am still hoping that an internal PR update will mix things up a bit.
| 9:26 am on Jan 18, 2006 (gmt 0)|
I noticed that there are two different Bigdaddies: The big
BD and the small BD.
Big BD has more pages. A "www" yields more than 25B pages. For example, currently live at: [126.96.36.199...]
Small BD has relatively less pages. A "www" yields 15.4M pages. For example, currently live at: [188.8.131.52...]
| 9:46 am on Jan 18, 2006 (gmt 0)|
That's interesting about the 25B pages, considering last I heard their index was only around 8B (thinking back to around March 2004 or so?).
Perhaps, amongst other things, BigDaddy will sport an increased index capacity?
I thought the next logical progression would be to 16B, but perhaps they are jumping to 32B?
Or its just another of those 'Google counts approx X10 when over 1000 actual results' phenomenon's?
Just did a search and apparently they claimed they increased it again last September, but they have not specifically announced the size...
| 11:00 am on Jan 18, 2006 (gmt 0)|
Why are you talking about the same thing on SO many pages, we know that google has a test DC, they are triying to fix the non www issue, 301,302 links, we can also see less supplemental results on that test DC and it shifts between google.com and test DC, but thats it, it has done that for weeks and nothing new had happen.
I could understand this thread went nuts when we got new PR, rankings or it stayed on google.com, but that is not the case, I also understand that it is a horror to be in this situation, I got hit with a site nov3 2004 with a site that got 35.000 unique visits a day.
Im also watching this posting and hoping for news, but its always the same posting.
| 11:07 am on Jan 18, 2006 (gmt 0)|
Come on Google we must be getting close to the next stage of Big Daddy of an interal PR update and a good crawl based on the new infastructure?
They cant be totally happy with the identification of the canonicals and 301/302 following I guess.
| 11:13 am on Jan 18, 2006 (gmt 0)|
>>They cant be totally happy with the identification of the canonicals and 301/302 following I guess<<
And that might explain why Matt isn't talking anymore about BigDaddy ;-)
| 12:49 pm on Jan 18, 2006 (gmt 0)|
Maybe just maybe ,the canonical issue is not a problem with google or any data center including BD.Probably Penalised pages will have the canonical problem as long as the penalty is there.And probably wrong canonical indexing is a new way of Google to apply penalties.So as Zeus said this thread goes to dead end as long as we with penalties have to stay in Prison ,just like in Monopoly game.
As a proof to the above :why unpenalised pages have not any problem with canonical issues? why they are survive any update.All of us that suffer we will suffer as long Google exists.Some mistaces we did in the past will never be forgiven by the google religion of "Do no Evil" (hmmm someone else from the USA ("land of freedom") made the word EVIL famous and use it to exterminate K's of EVIL ones in several countries.
As about Googlers zeelots,I hope when a new comet aproaches the earth they will do the same like they did some multimilionaire freeks a few years ago (does anyone remembers the story?)
| 1:17 pm on Jan 18, 2006 (gmt 0)|
bluewidgets - Its not a penalty, most of us got hit by the googlebug 302, that means 302 redirects are shown in the google serps as a unique page and that way many got filtered out of the index because of dublicated content, those pages has been in the index until now, but on the test DC I dont see any caches of those redirects or hijackers and as a bonus they have also fixed the non www issue.
| 2:08 pm on Jan 18, 2006 (gmt 0)|
The pages that finally got an updated cache on big daddy yesterday were crawled on Jan 6th if that helps you. I will let you know when and if the pages crawled yesterday show up on bigdaddy.
| 2:13 pm on Jan 18, 2006 (gmt 0)|
Are you seeing pretty much all pages that Mozilla Googlebot crawls making the test index then?
Large site - or just a small one?
I also had a heavy Mozilla Googlebot crawl overnight.
| 4:13 pm on Jan 18, 2006 (gmt 0)|
Our site is about 2000 pages built over the last 5 or so years.
We only saw stuff happening on big daddy after this particular mozilla bot started crawling 184.108.40.206, It heavily crawled old old pages that were long ago 410'd or 404'd. (we did change all our 410's to 404's in november/December - not sure if that made a difference).
This is the mozillabot that yesterday hit pages that have not been indexed on google anywhere for a long time. I will keep watching to see if they get added to any index. It took from Jan 6th crawl to yesterday for updated cache dates (or even a cache at all in some cases) to show up on big daddy for us so it seems to take awhile.
I have noticed that when regular googlebot hits a page that is in all the datacenters it gets an updated cache on bigdaddy as well. It is pages that are only on big daddy that seem to take awhile to get a cache or a new cache date.
I am not sure if this helps you, but I think this mozillabot is different than other ones that have been on our site in the past. I haven't seen much from any other mozillabots lately to do a comparison though.
| 4:31 pm on Jan 18, 2006 (gmt 0)|
Hmmmz - I guess we will just have to be patient a bit longer.
I have had pages added to the index from Mozilla Googlebot from a different IP addy to the one you have said - so I dont know if there is any significance in which IP address Mozilla Googlebot comes from.
Although the index at [220.127.116.11...] only showed updated cache over the last few days I am pretty sure that this updated cache is being used for the results on [18.104.22.168...] and has been for a while. True that when you query the cache it does not show the updated details - but the serps snippets do indicate the more recent crawl - and it did not take so long for that data to appear on that dc.
| 5:11 pm on Jan 18, 2006 (gmt 0)|
I predict a major change within two weeks. Traditionally google has done relatively major algo changes on February, and it's been a while since jagger.
| This 209 message thread spans 7 pages: < < 209 ( 1  3 4 5 6 7 ) > > |