Update Saga. Part 5

[Brett_Tabke]

What say you?

Over and done with?

All done all through?

[Dayo_UK]

Yes, PR is different on :-

216.239.57.*
216.239.53.*

Just a temp roll back? Or new?

Looks just like a temp roll back - probably insignificant then.

[tigger]

no movement across my sites so at least thats one plus point

[jaffstar]

Can someone help , I am trying to redirect domain.com to www.domain.com on a hsphere cp.

Tried the following, but did not work in .htaccess.

RewriteEngine on
RewriteRule ^/$ /e/www/ [R]

[sit2510]

>>> Sure do, using the SEOchat future pagerank tool I can see a few DCs showing new PR.

Nick0r, Thanks!

>>> 216.239.57.*
>>> 216.239.53.*
>>> Just a temp roll back? Or new?

Just a little bit dispointed that they are not from 66.102.9.104 or 216.239.51.104

Not sure whether just a temp roll back or new as most sites seem to get back to the Pre-Jagger ones for the above two sets, BUT there is one website of mine which is PR4 before Jagger; it falls to PR3 because most of the pages are knocked off from the index due to canonical problem and those two sets are now showing PR5 for this particular website. Very strange :)

[The Contractor]

You cannot perform this through Hsphere control panel. If you do not have an .htaccess file open a text editor and paste in the following:

<Files .htaccess>
deny from all
</Files>
RewriteEngine On
RewriteCond %{HTTP_HOST}!^www\.yoursite\.com [NC]
RewriteRule ^(.*)$ [yoursite.com...] [R=301,L]

Save this as .htaccess (with no extension etc.)

Login via FTP and make sure you can view hidden files. Upload to the root of your domain (yoursite.com) where your index/homepage is located. If this does not work then your host does not allow .htaccess to be used. This would be a 1st for me as hosting companies using HSphere are probably some of the best available generally (9 out of 10 cluster their servers).

[edited] This is assuming your site is using Linux/Unix and not a Windows box. Also, give it 5-10 minutes before you come to the conclusion that it doesn't work.

[edited by: The_Contractor at 1:42 pm (utc) on Nov. 14, 2005]

[reseller]

Dayo_UK

>>Yes, PR is different on :-

216.239.57.*
216.239.53.*

Just a temp roll back? Or new? <<

Very old ones. As old as a yesterday's paper telling yesterday's news :-)

"Have you seen the old man,
In the closed down market,
Picking up the papers,
With his worn out shoes,
In his eyes you see no pride,
And hanging loosely at his side,
Yesterdays paper,
Telling yesterdays news,
So how can you tell me you’re lonely,
And say for you that the sun don’t shine,
Well let me take you by the hand,
And lead you through the streets of London,
I’ll show you something to make you change your mind."

la...la...la... :-)

[Leosghost]

Irrational use of CSS

Using CSS techniques that are so bleeding edge that most incoming browsers in use on the net are gonna break when they get to the page ..and using CSS for things that it wasnt meant for just because it can do it ..

BTW ..who beleives that the list of things there ( pandia )came from google ..;) they are just speculating about their own observations ..they ain't the "plex"

@clean up ..leave them like they are ..one might get shot down next algo round ..merger them and they can get you with just the one bullet

It would be nice if all the people calling out what they see moving at particular DC's would try to read WW Watchers post about how it works in essence and then stop talking about fluctuation from any particular DC ..if you can't get the guys explanation what the **ll are you doing posting in "professional webmaster fora" ..even my 12 year old son can't see how you can't get this ..

And from where I post jagger 3 finished nearly 2 weeks ago ..I said so at the time ( tiny shifts up or down for us on page one positions ..like from #4 to #3 and back to #4 etc and a few thousand more or less on the "results found" numbers ..) ..maybe they let the smaller data pools have the stuff sooner ..

( smaller user language base in France ..les International DC's to update ..less boxes per DC ..less load etc )

You know the "bit push" or what ever "googlygeek" "techie phrase" it was tha t GG used ..( ROTFALOL )..

It's over the fat lady has sung ..and waiting around till GG tells you so is just laughable ..and pavlovian ..
When the update started it was denied ..during it's phases you were all given missdirection from GG and the cutts blog ( actually look at what was posted and what was actually done ..or not done and the dates and time frames given ..) ..

Get "unhypnotized" and move on ..reminds me of rabbits in headlights ..

The analysis here is almost zero ..and anyone ( as many did ) who made changes in the last 30 days or so ..why introduce variables into an unknown system in declared (eventually ) flux ( not "ever" ..but the real meaning of the word )..

Crawling has been restarted since the beginning of november ..heavy ..and the dates showing are now yesterdays or the day befores in almost the entire world ..except maybe Denmark and the USA apparently..

These threads just look like delayed chat between 20 or so posters ..problem is some newcomers actually seem to beleive that cos you're are all talking and posting so much on the subject of this update that you actually know what you are talikng about and can advise them ..

That would be tragic ~:o

The exception is maybe the canonicals problem ..but why not just accept that inspite of the PR and the statements from GG and the Cutts blog that they would fix it ..they didnt ..cos it is not a priority for them.

It's not on their list of "things we must do for the bottom line"..

Adwords and adsense are the priorities at the moment ..as they should be for they are what brings the money to google ..

[WW_Watcher]

On the topic of Possible PR update

I used that popular tool for checking pr across datacenters, and checked both www and non-www, for my site, because I recently added the redirect to my .htaccess file, expecting as one of the benifits to consolidate the PR that was split between them.

On the tool, for the www pr query it is consistant thru all IP addresses, for the non-www query, it shows about half of them displaying no pr.

So, is G in process of updating PR, and has it already found my redirect of non-www to www, and making the change, adding the PR from the non-www, to the www?

Any thoughts

Back to watching,
WW_Watcher

Edited to add, there is no difference in Back links displayed on any IP, for either non-www, or www.

[edited by: WW_Watcher at 2:28 pm (utc) on Nov. 14, 2005]

[Pico_Train]

Yes Leo, your website experience must be the only one around and everybody is experiencing the same as you and yes, you are right, most definitely.

In fact, can I have your autograph, you're my hero.

Relax, let people do what they're gonna do, no point getting frustrated at them.

Cheers.

[Dayo_UK]

WW_Watcher

This is not new PR - 99% sure it is old. EG take Matts Blog - it is showing a PR0 on the datacenter with the different PR.

Sooo - it is more likely showing that it did not have the problem a month or so ago (eg PR was the same on www and non-www) - so in other words Google have only recently split your PR.

Only suffered recently from ranking loss?

It does look like Leosghost is correct, Google are not bothered about fixing the issue anyway.

However, just as there are fresh dates about does not indicate a deep crawl - yes I am seeing fresh dates from a day or two ago.

Cant see any evidence that Googlebot activity is heavy - but Pico_Train that is only looking at my own sites ;)