Thu Oct 05, 2017 11:08 pm
[Update: The converter is now live. See this announcement post... https://forums.sitesell.com/viewtopic.php?f=136&t=224028 I'm going to I'm going to lock this and most other HTTPS threads. -- Help Elf]
As of this past Wednesday (October 4), only about 665 sites had used the HTTPS Resources Check to see what work needs to be done on those sites before converting to HTTPS.
The converter is likely coming out next week, so if you haven't yet checked your site(s), get crackin'! Google's Chrome browser is set to start reporting unsecure forms and pages, etc., the week of October 17.
If you have not yet registered your domain name, I recommend that you wait a week or so, until after the converter is released. Your site will then automatically use HTTPS.
Here are a few things you need to know about switching to HTTPS...
1. URLs are translated to HTTPS "on the fly" -- that is, the system is handling it for you as a search engine or visitor requests the page. The pages may still appear as http when you edit them, but the system fixes them up when they're served to the browser.
2. Facebook likes and comments will be preserved.
3. Google +1 counts will be lost. (Even though Google talks in its Search Console help about making every effort to keep traffic losses to a minimum, this hasn't translated to +1 button counts.)
4. Pinterest Save counts will be preserved. The number of Saves listed on the Pinterest Button will increase; however, the link to your site will be http only (so a 301 redirect will take a Pinterest user to the HTTPS version of the page). This will be for existing pages. New pages will use the HTTPS version of the URL (all links will be direct, no 301 redirect needed).
5. And here's the one you'll really like... The conversion process takes all of about 5 minutes from the time you click the button. There will be tasks you need to do post-conversion. I will be covering those in an article I will be publishing to TNT HQ before the release (to give you time to plan your tasks).
SBI! Will Take Care of the Following
Here is a list of the services that SBI! will automatically switch for you. These were added to the list based on the following criteria...
* How many times did the domain name show up in the HTTPS Resources Check reports?
* How many SBI! sites were affected?
* Did the HTTPS version of the URL serve up the exact same content?
We've tested these the best we can, but no one knows your site like you do, so keep an eagle eye on everything, including post-conversion.
We highly recommend that you use the very latest code for third-party services before switching. Not only should they be HTTPS enabled, in many cases they also load faster.
Here's the list...
Your Site's URLs
* Any URLs on your site that reference your own domain name will be switched to HTTPS. This includes the RSS feed and XML sitemap.
* Google Custom Search
* Google Fonts
* Google Translate
* Google Maps
AdSense and Google Analytics already use compliant code. But you should check yours if you placed ads on your site or pasted in Analytics code several years ago. See my note at the end about Google Analytics.
* Video URLs
* jquery loaded from many popular third-party sites like Google API
Sitesell Affiliate Program
* graphics.sitesell.com image URLs
* youtube.sitesell.com video URLs
* http://www.sitesell.com/images image URLs
Amazon Associates Program
* 40 domain names used for the Amazon Associates program (including .co.uk, .ca, .de, .fr)
* If you haven't yet switched to One Link, now is the time to do it! You'll reduce your workload later, and you'll start earning from Amazon purchases made by people around the world.
Affiliate Programs / Advertising Networks
Subscriber / Mailing Lists
* Twitter Cards
* Add This
Unfortunately, Sharethis can't be translated, so you'll need to copy and paste new code from them into the applicable Sitewide Dot or SBI! Include.
RSS Feed Tools
* if you have used a FeedBlitz feed, you'll need to convert it to HTTPS. You may be able to simply add an "s" to the URL in RSS/Blog It!. If you do that, be sure to test thoroughly!
Unfortunately, Feedburner seems to have become Google's orphan. It does not accept HTTPS feed URLs, nor does it provide HTTPS versions of its feed URLs. So even if it accepted your site's URL after the conversion, it would give you back a non-secure URL, which Chrome will complain about.
So the only way to resolve this is to switch to FeedBlitz (which is not free), or switch back to using the RSS/Blog It! feed URL. If you plan to switch to either one, write a bloglet advising subscribers of the issue, and asking them to resubscribe in a couple of days when you've completed the switch to FeedBlitz or the Blog It! feed URL.
* Google Analytics code will be changed, but if it needs to be changed, you're using old code. It's best to get new code from Google Analytics. Simply check the Sitewide Dot (or the head) of one of your pages, and look at the code. If you see an http URL, change the entire code.
If you use Statcounter, you'll need to replace the existing code on your site with the new code that's HTTPS-enabled.
Until next time (which could be next week!).