Forum Moderators: Robert Charlton & goodroi
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.
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.
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.
Later!
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.
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.
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!)
66.102.9.99
66.102.11.99
However, I'm not that concerned.
These two have moved my site to #2 position.
64.233.179.99
64.233.179.104
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...
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 :/
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.
[64.233.183.99...]
[64.233.183.104...]
Dayo_UK
Do you see anything of interest ;-)
For me those DCs are the same as the half a dozen or so, including 66.102.9.104, that have been showing different results since Jagger3 started.
They have not spread to other dcs at all in that time though.
>>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 64.233.179.104 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 ;-)
[64.233.183.99...]
[64.233.183.104...]
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.
>>Reseller
For me those DCs are the same as the half a dozen or so, including 66.102.9.104, that have been showing different results since Jagger3 started.<<
Not at all. Sorry my friend ;-)
66.102.9.104 is showing at the moment entirely different serps than the two DCs I mentioned, as far as the sectors I'm watching are concerned.
[64.233.183.99...]
[64.233.183.104...]
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.
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?
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