| 9:57 pm on Jul 15, 2006 (gmt 0)|
| 1:24 pm on Jul 15, 2006 (gmt 0)|
System: The following 4 messages were spliced on to this thread from: http://www.webmasterworld.com/google/3009357.htm [webmasterworld.com] by tedster - 5:57 pm on July 15, 2006 (EDT -4)
Just saw that after the last backlink update the related: command brings zero result to my site as well as many others. Anybody knows something about it?
| 4:11 pm on Jul 15, 2006 (gmt 0)|
I have been affected by it also. I use to get 28 results, now none.... oh well, just gonna keep on building content
| 5:03 pm on Jul 15, 2006 (gmt 0)|
Weird, related: command for me is also down to just a handful of sites from nearly one and a half pages of them.
| 5:11 pm on Jul 15, 2006 (gmt 0)|
Looks like backlinks have been calibrated down as well.
| 2:17 pm on Jul 17, 2006 (gmt 0)|
I've always looked at related results as some interesting stuff turns up, no results for an established site is rarely good news and often indicates some sort of a linkage problem, IMO.....
| 9:18 pm on Jul 17, 2006 (gmt 0)|
From the sites that I checked out the reduction was to improve quality (at least that's the idea, I'm sure). Some of the "related" pages before the update really weren't related at all, but now they seem to have taken a step forward in actual relational analysis. Still, as with any automated process, I'm sure there are holes that will soon be exploited.
I expect that the relational update is part of the larger battle against link spam. If they can devalue unrelated links they can weed out some of the spammers. I wonder how they're viewing relationship, though. Some ideas aren't in the same industry, but still have good reason to link to each other.
| 8:40 pm on Jul 19, 2006 (gmt 0)|
I see a bit better quality in search and less repeatative links
| 11:41 pm on Jul 19, 2006 (gmt 0)|
I know this particular thread is not getting much attention, but I believe it's no coincidence that the related: command doesn't work.
I posted about the related command back in March:
To me it seemed "broken," but I suspect the problem might have run deeper than this simple command and might somehow be related to BigDaddy.