Firefox switching to HTTPS Google search by default
Nuttakorn
7:55 pm on Mar 21, 2012 (gmt 0)
Can't imagine how much significant increase of (not provided) - even now it is very high - some of my client reached 17% of not provided keywords. It keeps continue increasing!
That's just.. lame, FireFox getting canibalized by Chrome in 2 years, my pessimistic prediction.
dstiles
10:44 pm on Mar 21, 2012 (gmt 0)
Some time ago I removed G completely from FF. That's how it's going to stay.
Sgt_Kickaxe
6:28 am on Mar 22, 2012 (gmt 0)
What happened to user choice?
The irony - FF moves one step closer to being like G and we lose more options in the process.
martaay
11:24 am on Mar 22, 2012 (gmt 0)
does anyone consider for example if FF goes through with this and IE, chrome follow suit, that us webmasters will in effect be forced to change our websites to use https in order to get this keyword data back?
Nuttakorn
2:06 pm on Mar 22, 2012 (gmt 0)
Anyone plan to switch your site over to https?
dstiles
10:05 pm on Mar 22, 2012 (gmt 0)
A while ago FF dropped G completely. It seems G then offered money...
The problem with https is that it puts a lot more strain on the server. Everything has to be encrypted before being sent, even the images (unless you want browsers telling their users that the page contains non-SSL content, which could frighten people away.
A lot of DIY web site owners now run straight-from-camera images onto their sites, relying on browsers re-sizing the image on receipt. Very bad all round, but the perpetrators are generally ignorant of the logic behind image control and I suspect some CMS systems don't mention it anywhere obvious. But imagine the server load if those people went SSL - and YOUR computer load as your browser decrypts the images! I've seen whole ecommerce home pages littered with dozens of such images; most (all?), so far, non-SSL.
Aside from that is the cost of SSL certs. If you want a good one it costs. If you settle for cheap ones then the root cert may be compromised by site hijackers and used for exploits: the root cert then gets revoked from the browser's store and there is the hassle of a) moving to another cert supplier or b) relying on all browsers getting a new root cert PDQ. As has recently happened.
Sadly, we seem to be gradually forced down the SSL route.
And also sadly, SSL is not unbreakable. Exploiters are already working on this, with some success as far as I understand.
