Fri Jun 09, 2017 4:00 pm
Edited: We have now put links to the tasks you need to complete before 1st October, plus other incidentals of use / importance, at the top of this first post. If you don't have time to read through the entire thread, these are the posts you need to be looking at - but please bear in mind that within the thread is a lot more specific information.
Prepare for Google Adsense - immediately under these links.
Prepare for Google Analytics, Google Tag Manager, Google Custom Search, Google Translate - immediately under Adsense.
Prepare for Google fonts and Google maps (if used) - immediately underneath the analytics section.
The links below (blue text) take you to posts with additional tasks to complete after you do the Google ones (below, in this post).
Tasks 1 - 4: specifics for uploaders.
Specific information about SBI!'s "tester" which will be released soon.
What to do if you have a WordPress site as a sub-domain via InfinIt.
Information about the SSL certificates.
Help Elf's most recent post covering what SS is doing, what you need to do and update on the tester.
FIRST TASK: PREPARE FOR GOOGLE ADSENSE
Help Elf here to let you know that the boss has decided to move forward with the HTTPS project. What's that? When it's released, all new sites created after that date will use https:// instead of http://. All sites that exist before that release date will have the option to switch over to https.
Why are we giving you the option rather than just switching your site over to a secure version? Because there may be tools or functionality that you added to your site a few years ago that still run on http. Anything that's not secure on a secure (https) page can make that page not secure, or provide a warning that part of the page is not secure.
If you added that functionality to every page of your site with a Sitewide Dot (for BB2 pages) or SBI! Include (for uploaded pages), then every page on your site will appear as not secure (or with a message that some part of it isn't).
Every week between now and the release, I'll be posting a tip on something to look for and switch so that you're ready soon after release day.
We'll start with the big one... Google.
Google deals with potential incompatibility by stripping out the part that could be incompatible. Which makes this a task that you can complete before the release, with no ill effects for your site.
Here's some AS code where http: (and https:) is already gone...
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
Note the lack of http or https.
Here's your task this week...
1. Open a page to edit it.
2. Open each Sitewide Dot that has AdSense Code in it. Also open every Reusable Block that has AS code in it. (One at a time, of course.)
Important Note: If you do see http:, that means you're using very old code, probably code that's not responsive, and not asynchronous (async code speeds up page loading). I urge you to update all your ad code to use the latest available from AdSense.
4. All the changes should have been saved, but to be safe, rebuild the page (do not update the RSS feed unless you made some content changes as well).
And that's it for AdSense.
Google Analytics, Google Tag Manager, Google Custom Search, Google Translate
If you use any of the above three, check the Sitewide Dot, Reusable Block, or Head section (the button at the top of the BlockBuilder page) for the code there. If you see http:, delete it. Even better, collect current code from Google. This is especially important for Analytics code if you've been using it for several years. You may not have made the switch to universal analytics (UA) code yet. It's imperative that you make that change, as Google has said that it will not be tracking traffic on sites using the older, GA code.
Important Note: Do you use Google Translate on your site? During the setup, Google asks for the URL of your site. You entered the http version of your site. I recommend that after the release, you go back and create a new version of the code for the https version of your site.
I will be covering post-release tasks in a TNT HQ article at the time of the release.
Google Font URLs use https:, so any that you're calling from your site should be good as is. However, I recommend that you double-check to be certain.
If you embed any maps from Google Maps, check the URLs in the iframe tags. If they have https, there's nothing for you to do. If they have http, I recommend that you get the embed code again.
Next week, I'll discuss social media. The good news is that we'll be doing most of the heavy lifting for the biggies of the bunch. But if you add a bunch of obscure/little known social media sharing/follow buttons to your site, you may have some work to do.
Links to helpful posts for the change to https:
Background & Wish List thread:
Help Elf (H. E.) posted to clarify & answer questions:
Jeff of DogQuotations.com posted tips:
Clayton, head of Programming posted re: Type of SSL certificates
Google Site Search:
Tracy asked: https://forums.sitesell.com/viewtopic.php?f=136&t=222843&start=30#p1374088
Jeff answered: https://forums.sitesell.com/viewtopic.php?f=136&t=222843&start=30#p1374093
Ken (H.E.) announces imminent release of HTTPS!