Marval - 10:49 pm on Mar 11, 2005 (gmt 0)

Yidaki - this has actually been going on since July of last year - its just starting to show its effects recently - there is some problem which I still cant pin down in how they are handling not only 301s, but stacked domains (you buy the .net and .org for protection, no zone file entries, all pointing at the same IP) and those are being split out as well by Google where very large sites are being split into many vanity domains.

As far as whether 301s worked before and now dont - I can say that its a good statement.

theBear - that is correct for directories however it is not the correct way to redirect an entire domain I dont believe

bhartzer - I believe that is 302's that they have been working on to prevent what you are describing - although it may be leading to this problem but the 301 problem first appeared in July and surfaced with the SERPs update on Aug 14th last year

Emmett - I believe the filter=0 is entirely related to this as a downline effect from the change in the algorithm, or very possibly in the coding of the new Googlebot although you would think that they would have tested that end of things