Google now using HTTPS as a ranking signal

Whilst this is awesome, it's going to piss off a hell of a lot of web hosts.

IPv4 addresses are already a commodity, and it's getting to the point where even big hosts are having trouble getting enough justification for larger IP pools. With dedicated SSL certificates, every domain's going to be needing it's own IP address.

The world needs to hurry up and adopt IPv6!

http://en.m.wikipedia.org/wiki/Server_Name_Indication

Wikipedia said:
This allows a server to present multiple certificates on the same IP address and port number and hence allows multiple secure (HTTPS) websites (or any other Service over TLS) to be served off the same IP address without requiring all those sites to use the same certificate.
 
I played with this a few weeks ago and after I made sure every URL is protocol agnostic in preparation for such a switch I constantly ran into outside content/scripts to break the SSL. We rely on adsense/DFP/Other networks banner ads for revenue. Lots of those campaigns and lots of ad agencies we deal with are not ready for SSL.

I aborted the switchover for that reason. Will wait a few more month and attempt again. But if my google ranking could get improved I may look at this sooner then later.

--
In addition SSL is the foundation for SPDY and SPDY does make sites faster. Safari will soon support it as the last major browser.

Same reason we haven't went full SSL yet. Hoping this push by Google gets more ad providers to support HTTPS soon. I have been wanting to make the switch for awhile.
 
You don't need to set any redirect changing from http to https... you simply force https and that is enough. http to https is actually not a domain change, as http is not considered part of your domain name structure. http / https / ftp / so forth, are web protocols.
You still need to redirect all request to https version.
And that is still 301 redirect as far as I understand.
 
You can actually feed Google both http and https, its called canonicalisation. Google will pick the best one, BUT, you then leave it to Google to choose. I would never recommend leaving it to Google, but Google do actually do it quite well without any issue. The same as they handle slashes under canonicalisation. Technically adding a slant is a different domain, thus they use canonicalisation to determine the optimal URL cached, identical to www or non-www.

It would depend on how you go about things... normally you just redirect the port, being the simplest way. Anything requesting port 80 gets redirected to port 443. Not really a 301, but it is a redirect of sorts. Again... the designator isn't actually part of a domain name, thus 301 is not really the right way to do it as a 301 uses the domain name, when http to https is a port redirect, not a URL redirect.
 
Couldn't care less.

Won't be switching my site to https any time soon.

Next it will be domains using google dns.

Then sites using google email addressees with G+ integraton enabled.

Then sites hosted completely by google using google proprietary forum software.

And so on.
I'm with you Brogan i could care less.
 
Looks like Cloudflare is looking into it. Looks like they may be even rolling it out for all customers for free!:eek:
Pretty smart IMHO... considering Google state it means little right now, giving everyone time to start thinking about change... then state, later it may weight more delivering secure websites to users over non-secure. That later thing sticks in my head.

Thinking about this, it could be the coincidence I was looking for in relation to just adding Adsense... in that my site is https and the new 200+ daily traffic is due to the minor factor being given, already using https???
 
I'm with you Brogan i could care less.
I think some advantages matter nowadays, considering the constant injection of new sites flooding every niche, all fighting for prominence.

People worrying about meta data and such nonsense... absolute waste of time. But when Google clearly gives you notice that they want to deliver their searchers secure websites over non-secure... it will give you an instant edge over everyone in your niche who isn't secure.
 
Last edited:
Okay, can someone clarify with authority that http -> https does not require 301 redirects? If it's 301 redirect, I'm going to let my site run on http. But if it's certainly NOT a 301 redirect, I'm all game for the https thingy.

Also, can someone quickly put up an article that shows how to migrate xenforo from http to https?

Update:

Just had a chat with the ssls.com representative and they said you will have to setup a 301 redirect to migrate your site from http to https. :(
 
Last edited:
Top Bottom