| 5:10 pm on Dec 27, 2005 (gmt 0)|
In my case I'm pretty sure that my site had suffered from a dupe content penalty. I made a mistake in my robots.txt last summer that allowed Google to crawl dupe pages (print and mail versions).
During that penalty my site's homepage never showed up first for site:www.mysite.xy. Now I see my site rushing back and the homepage is appearing first.
I think the penalty was site wide since my homepage was not duplicate.
| 5:16 pm on Dec 27, 2005 (gmt 0)|
i think i also triggered the dupe content flag :(
do you have now a lot of only url results on site:domain.com? i have several sections 100% only-ulr and i am going to ban it for crawlers
i wish you all a 2006 free of dupe contents :)
| 5:28 pm on Dec 27, 2005 (gmt 0)|
spainly: no url only results.
A penalty free 2006 to everyone - I suffered twice from dupe content penalty this year. That should be enough...
| 5:38 pm on Dec 27, 2005 (gmt 0)|
Dayo, the good site: results are on my current google.com (22.214.171.124) as well as on the test DC. Haven't checked any DCs beyond those two, but the volume of traffic coming in would suggest that the change affecting our site is widespread.
BTW, the last time I checked the test DC before Chritmas, the site: results were still scrambled, as with other DCs. Now they're substantially the same, although the test DC reports a 50% smaller number of pages from our site indexed.
| 5:56 pm on Dec 27, 2005 (gmt 0)|
There are several camps on updates. Most recently it seems to have been the duplicate content and the canonical (Fire!) issues with Jagger with a passing mention on links.
I think I was just hit by both, canonical and duplicate, pretty much at the same time.
A 301 is not a problem, I can do it and since it is a technical problem, Google will sort it out eventually.
The other problem is duplicate content. This is a very serious issue for content writers. We all spend hours reading our work over and over again, only for some thief to come along, highlight it, press ctrl + c and then ctrl + v in their HTMl editor.
Content theft has reached ridiculous proportions and honest writers are being nailed left, right and center on this.
I am constantly fighting fires with sites stealing my stuff and I am starting to have it up to here with it! I've duelled with people in Hong Kong, Canada, Germany and now, just quickly, I have found another 3.
Once back from holidays, I will write a nice long how to etc etc... about content theft, finding it, steps to take and all that jazz to fight this plague.
We all need to start enforcing our ownership of our content. It's the only way because Google, as much as they say they are working on it, i think it is far too "untechnical" a problem for a computer to figure out. Copyright laws - whatever - kind of like a law against J-walking, it's rarely enforced and people laugh when it is.
Anyway, I'm upset, tired of theft and want to do something about it so that other sites don't go from page 1 to page 10 because of thieves.
| 6:15 pm on Dec 27, 2005 (gmt 0)|
My site dropped before Jagger really rolled out. That was some time in late September. I remember reading something MC said about the adjustment before Jagger hit - he said something like "that adjustment was targeting something else." I took that to mean penalizing sites.
I almost give up when in comes to Google. My site's so clean it squeaks. What I came to realize is that Search Engines are really pretty stupid. I gave them too much credit for being able to figure out things. They can't and really need to be spoon fed information.
The ironic part here is the more they do to combat spam, the deeper the hole they dig themselves.
| 9:18 pm on Dec 27, 2005 (gmt 0)|
I see some of the remaining problems from September 22 being fixed, although a few pages still hold out in having a problem. Perhaps they too will recover in a day or two.
Some progress made... <gasp>
| 10:17 pm on Dec 27, 2005 (gmt 0)|
Hmm my site dropped 300+ places on (126.96.36.199), wonder what's cooking there?.
| 10:32 pm on Dec 27, 2005 (gmt 0)|
My 2 bits:
Looks like the typical post update re-adjustment. 2 of my sites that were wiped out by Jagger (for mysterious reasons I couldn't really track down), are back to roughly where they were before Jagger.
I saw similar behaviour the previous two years. Big mongo update in November. Mass panic and confusion. Then December/January, things started to settle back down, and a lot of "penalized" sites re-appeared.
I just wish they'd move the big update to January, after the Christmas sales rush, so that the minor flaws that seem to creep up with every major update wouldn't have such a detrimental affect on e-tailers.
| 11:45 pm on Dec 27, 2005 (gmt 0)|
|I just wish they'd move the big update to January, after the Christmas sales rush, so that the minor flaws that seem to creep up with every major update wouldn't have such a detrimental affect on e-tailers. |
Possibly, but in some sectors (such as mine), traffic and commercial activity are much greater after the first of the year than during the Christmas season, so one man's meat is another man's poison. Also, if search traffic in general is lower in December than it is in January (a reasonable assumption), it may make sense for Google to do its housekeeping during the eggnog-and-office-party season.
(For what it's worth, I lost 70-90% of my Google referrals between late March and late May of 2005, which was probably the worst time of year to have that happen. If Google whacks me again, I hope it's in November and December!)
| 2:06 am on Dec 28, 2005 (gmt 0)|
seems toolbar PR is bouncing a bit on this DC and a couple others. my PR5 site shows as a 4 on:
It was a 4 until the last PR update so maybe some back n forth type stuff going on?
| 2:14 am on Dec 28, 2005 (gmt 0)|
Wow, these two dc's have completely dropped my site:
However, I'm not that concerned.
These two have moved my site to #2 position.
Yet, I'm not that happy.
And all the others have me at either 5 or 28 on my main keyword (which is my barometer for these updates).
This is following an eerily similar patter to Jagger 1 for me. Obviously these results didn't stick for J1, but there is some sort of similar pattern.
My guess is this is the beginning of another set of updates. Check back in two weeks after the dust settles...
| 4:09 am on Dec 28, 2005 (gmt 0)|
I think they are still updating the Test DC .. results seem to be changing the last couple of days..
| 7:25 am on Dec 28, 2005 (gmt 0)|
The set of results that I see for my site are live. I'm now back to pre-Jagger which is a very good thing, and again, speaking only for my site all the Dc's are identical. I made one major change right as this "update" began, and it seemed to be the right one. My traffic dropped nearly 2/3rd's after Jagger, but just today traffic is back to normal, so it would appear to me I'm not the only one seeing new results. It is an update in my non-commercial sector, but as we all know it could change when I check again tomorrow.
| 8:08 am on Dec 28, 2005 (gmt 0)|
My main site has been hit hard :\ Was getting 1500-2000 visitors for a month and now I'm down to about 100-200. Used to rank top 10 for almost all my keywords and now my site can only be found around 200's. Its an affiliate site with a bunch of product pages so I guess thats why it got hit.
| 8:46 am on Dec 28, 2005 (gmt 0)|
Good morning folks
Hopefiully you are enjoying the present vigorous reshuffling on the DCs. Something for sure has happened during the last 9 hours or so!
It could lead to anything ;-)
Ladies and Gentlemen.. please fasten your seat belts!
| 9:14 am on Dec 28, 2005 (gmt 0)|
What type of problems being fixed are you seeing - Canonical? - or ranking? or other?
I am seeing some Canonical problems being fixed but they are not ranking.
Hopefully rank will follow..... I guess that make sense - but would be intrested to know if you are seeing rank return for the problems you have identified.
I have not seen much progress over the last few days although cache on the 22nd for a few homepages have been entered so the homepages at least have relatively new cache - shame about the rest of the site :/
| 9:33 am on Dec 28, 2005 (gmt 0)|
Think I reported this to the wrong thread, so apologies for repeating myself but our site completely re-emerged from the depths of jagger yesterday across all dcs (on mcdar). Notably, our home page is now top when I do site:domain.com or site:www.domain.com with only www pages being returned. Also when searching on title of our home page we appear first (previously > 300). We did make a number of changes to titles (making unique), content and keyword frequency, but with 1500 html pages, we only got round to changing a few so this can't have made a difference. Either we were penalized (can't see a reason for this) or Jagger introduced a bug. IMO the fact that our home page now appears top for site:www.domain.com suggests that page rank is cascading in one direction rather than evaporating from across our whole site.
| 9:51 am on Dec 28, 2005 (gmt 0)|
Please take a look at these two DCs. The serps of these two DCs look different than the rest, in the sectors I'm watching.
Do you see anything of interest ;-)
| 9:58 am on Dec 28, 2005 (gmt 0)|
I like those but why wouldn't I? I am #1 on both for my word. I made a change to my site a few weeks ago and Google caught it and lifted me up.
Why did you choose those 2 DCs?
| 10:01 am on Dec 28, 2005 (gmt 0)|
For me those DCs are the same as the half a dozen or so, including 188.8.131.52, that have been showing different results since Jagger3 started.
They have not spread to other dcs at all in that time though.
| 10:06 am on Dec 28, 2005 (gmt 0)|
These unchanging 6 that have not propogated, do you know what part of the world they serve?
| 10:09 am on Dec 28, 2005 (gmt 0)|
>>Why did you choose those 2 DCs? <<
Because I have noticed they have different serps than the rest in the sectors I watch. Also fresh cache.
If an update is underway, those two DCs are going to lead, IMO.
I guess we shouldn't let the test DC 184.108.40.206 blind our vision of whats going on on the rest of DCs.
So, until further.. I suggest you keep an open eye on the two DCs ;-)
| 10:10 am on Dec 28, 2005 (gmt 0)|
From the UK I virtually always hit 220.127.116.11.
But it could be my ISP or something. I guess they are in rotation in most areas.
Reseller - I think the test dc is more significant - we know and can see that new infastructure is being built there.
| 10:22 am on Dec 28, 2005 (gmt 0)|
For me those DCs are the same as the half a dozen or so, including 18.104.22.168, that have been showing different results since Jagger3 started.<<
Not at all. Sorry my friend ;-)
22.214.171.124 is showing at the moment entirely different serps than the two DCs I mentioned, as far as the sectors I'm watching are concerned.
| 10:26 am on Dec 28, 2005 (gmt 0)|
Dayo, the fix seems to relate to pages lost September 22 (three weeks before Jagger). They did a fix during Jagger that partially helped, then now it seems to have helped a lot more, though I still see some pages with concrete overshoes on them.
These are not canonical issues. I don't think there was ever any clear understanding of what happened September 22nd. I have to laugh because some changes are so huge, even though lots of folks might not notice anything. One search I track got back its previous #1 and #2 pages (tho #2 is at #3 now). Pages seem to not have fully regained rank but are close.
| 10:31 am on Dec 28, 2005 (gmt 0)|
My site that was hit Sept 22 but got partially back in Jagger 3 has been filtered back to nowhere on all datacenters.
I picked up my mail for today and Google just sent me a happy new year card. How ironic.
| 10:32 am on Dec 28, 2005 (gmt 0)|
Ok - thanks Steve
I did not have any sites hit then so cant really comment on that issue.
All my sites date back to problems starting in Algera (or slighly before) due to Canonical/302 probs etc - I am hoping the new groundwork that Google has in place will lead to at least these sites getting correctly crawled. But I guess that will take time - at least the homepage(s) are being crawled again :)
Anyone seeing improvements in sites effected/hit back then by the Canonical/302 Bug?
| 11:17 am on Dec 28, 2005 (gmt 0)|
Dayo_UK - still seeing a friends site having canonical problems with that new dataset - an example where a site: command brings back two copies of the same page - one with the www and the next entry is the same page without the www.
Noted that the version with the www cache date is the 19th of Dec and the version without the www cache date is the 20th of Dec.
Looks like they got rid of the weird variants though where he had wwww and ww2 etc listed as well - those are gone.
Looking at rankings he hasnt regained anything although he has been an authority in that area since 1996 and has normally been top 10 with no problems over the years for hundreds of phrases and single word searches
| 11:20 am on Dec 28, 2005 (gmt 0)|
ONE THING I HAVE TO SAY
THANK YOU GOOGLE FOR MY BEST EVER XMAS PRESENT.
I WILL NEVER FORGET THE 27/12 2005.
| 12:04 pm on Dec 28, 2005 (gmt 0)|
Anyone ever noticed
Your input is much appriciated.
| This 251 message thread spans 9 pages: < < 251 ( 1 2 3  5 6 7 8 9 ) > > |