Welcome to WebmasterWorld Guest from 18.104.22.168
Google has announced... that going HTTPS -- adding a SSL 2048-bit key certificate on your site -- will give you a minor ranking boost.
Google says this gives websites a small ranking benefit, only counting as a "very lightweight signal" within the overall ranking algorithm.... Google says it has an impact on "fewer than 1% of global queries" but said they "may decide to strengthen" the signal because they want to "encourage all website owners to switch from HTTP to HTTPS to keep everyone safe on the web."
- Use relative URLs for resources that reside on the same secure domain
- Use protocol relative URLs for all other domains
Kind of scary for a site that already ranks well. Should this be done incrementally?
The goal is to rank and make money, not argue with Google.
Kind of scary for a site that already ranks well.
Question though, is there anything against doing it incrementally? If so, what is the downside to doing it incrementally / upside to doing it all at once?
Move incrementally, page at a time, and I guarantee you will 'f' that up.
Well I guess I understand how that happens. Next step will probably be for AdWords to start pushing the advertisers into SSL, then.
...except moving everything to SSL is, as noted above, about three lines of code. Move incrementally, page at a time, and I guarantee you will 'f' that up. Way too error prone IMO, and I still fail to see the benefit to doing it incrementally, or the drawback to doing it all at once.
First off it's not three lines of code but that's not the real problem.
If I change ten URLs to SSL as a test and it doesn't work as expected then I can revert back and think again, no real damage done. And I can let the change "settle down" without major financial impact to really test the effect of the change. If it does work I might be tempted to revert back those ten URLs and then make a site wide change.
It would be better to add maybe a small padlock or something so that the https:// part is removed and doesn't confuse visitors (it's enough that some of them are confused with the 'www.' part already). Now user has to read the extra 'https://' to read your brand name (ie. domain name).
please be aware that because we remove non-SSL compliant ads from the auction, thereby reducing auction pressure, ads on your HTTPS pages might earn less than those on your HTTP pages.
There may be a few php/js files which use full urls but that is simply a replace all of http/https.
In other words, for this type of site, wouldn't you be better off not to make the switch, especially since there's no other reason to do so anyway.