Update Saga. Part 5

[Brett_Tabke]

What say you?

Over and done with?

All done all through?

[Dayo_UK]

>>> but some of the folk were sad to hear it, so I kept quite ;-)

Probably sick and tired of this update :(

Just noticed something about a site that I 301'd the non-www to www ages ago - the 301 was picked up by Google about July time.

However, the non-www is showing different PR and BL to the WWW again. :(

Sooooo - even though it appears that Google picks up and recognizes the 301 - it still seems to be able to come back and split them again :(

It seems to be a very deep rooted problem - however, MC did say that new 301 stuff is coming in soon (Hmmmz - cant remember now - might be after Xmas even) - maybe that will help.

I have given my business until Xmas - if no improvements Dayo is going back to P/T Webmaster I guess.

[reseller]

Dayo_UK

There is all indications that the folks at the plex are still busy in tweaking and who knows with what else.
The "cache" case, the current flux are some of these indications.

Its my FEELING, no more no less.. that the folks at the plex still working to improve the final results of Jagger3. Don't expect GG or Matt to talk about it... Fair enough!

[reseller]

WW_Watcher

>>"EverFlux"<<

No its a FLUX.

And you better go "Back to watching" the Flux :-)

[Dayo_UK]

Found the bit on MC blog regarding the 301s.

[mattcutts.com...]

I have heard some reports of people having issues with doing a 301 from olddomain.com to newdomain.com. I’m happy to hear those reports in the comments and I can pass them on to the crawl/indexing team, but we may be due to replace the code that handles that in the next couple months or so.

I wonder if a 301 from non-www to www actually counts as two different domains - hmmmz

Intresting comments in that thread also - eg about Google not recognizing 301s (esp supplementals) I suppose this is what has/is happen(ed)ing to some of my old non-www.

[Kangol]

"Jagger3 was visible starting at 66.102.9.104 around 11/4/2005. Jagger3 is not widely visible yet (it might also be at 216.239.51.104), but I expect it migrate to other data centers over time." Matt Cutts - November 10.

I get different results (better) on 216.239.51.104 so J3 is just on 66.102.9.104. Do you see 9 migrate to other data centers?

[Ankhenaton]

still going down although all pages on all DC's main keyword still n#1 on all dc's ... detected fallback of new content from p1 -> p3 and later ... Dickipedia rules as usual ..

[lee_sufc]

Kangol, I also see better results at 216.239.51.104

[Kangol]

lee_sufc i think that we may have the same problem.
I rank better on every DC except 9. I think that I had a www/non www problem.

[lee_sufc]

yeah, dayo uk looked at my site the other day and said it looks like that too (I don't know too much when it comes to that so PM if you wanna take a look at my site)

[joeduck]

Dayo - were ANY of your site's problems resolved? Are you still confident it's only canonical confusion?