Announcements about Solo Build it!, SBI! for WP, WordPress, and other related news and announcements are posted here. You can either follow the news here, in Site Central, via the SBIX newsletter or in your WordPress dashboard (if using SBI! for WordPress).

Moderator: Debs from SiteSell

Read Only
#1377028 by Help Elf from SiteSell
Tue Jul 18, 2017 4:21 pm
Katia, inserting pins/markers should have no issue, since they're part of the code. Use the same process. Convert a map to https. If the pins still show, you'll good to go. If they don't, let me know here and I'll investigate further for you.

Debra, if you're building a new site with nothing but the payment services provider, you'll probably not need to do anything. Most providers are already using SSL. If, however, you add anything else to your site, you'll have to check any URLs it references.

Alastair, no, there's no timeline. Although I think I can get away with saying it will be this year. :-D Probably sooner though. Maybe. ;-)
#1377042 by Katia, Anastasi, Apostoli from We Love Crete
Wed Jul 19, 2017 12:50 am
Thanks Help Elf,

Sorry I am confused about the Google map. :oops:

The pins/markers are fine, yes they are part of the code, but I have a URL to my site within each marker. This URL is http and not https. Does this mean that each URL will not work after conversion?

Do I need to go and change each URL to https? Or is that the same for any pre-existing incoming link - it will be 'forwarded'?

Example here:


Kind regards

#1377183 by Shambhunath from Waukegan
Thu Jul 20, 2017 7:41 pm

I'm still planning to use MoveIt! to change my domain. I'm wondering if changing to https will also be considered a site move by Google? Would it be better or worse to make one move to to

rather than two moves: to to

Or is it all the same?
#1377243 by Debs from SiteSell
Fri Jul 21, 2017 2:25 pm
The https is not seen a site move by Google. It is just the secure layer associated with (which is your true actual domain name ... http/https is non-secure/secure on the same domain ... www. or not, same domain, just a different URL)..

If you change to https right now, you have to redirect the old page http over to the new page https. I believe this will be handled automatically by the new HTTPS option SiteSell is working on.

All my best,

#1377439 by Ruth from Kampong Bahru
Mon Jul 24, 2017 2:20 am

It is rather obvious to me that Google search engine is now favoring https websites. Many of my key pages (and I believe also other SBI websites) have been very much affected by how Google has ranked https web pages. Many of the the featured website listed first, topmost on the search result page are https. And this featured website (appears for many key words) is dominating the entire page on the laptop screen! You may want to do a search for your own website keywords - the first web page from the search result occupies the top page, followed by a big section on "People also ask". This means the from the 2nd web page on wards, the chance of being clicked is extremely low.
Are Ken and his team looking into this issue? I see it as a huge problem for SEO if https is happening too slowly. In 2015, many internet marketers had already noticed that Google had started with a minor shift to favor https websites. Now it is already mid 2017. Can I appeal that SBI expedite the release of SSL? (I am almost done with all the steps listed as pre-tasks to move into https). Can Ken's team address my concern in this post?

Thanks very much!
[Domain Private]


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).

We'll deal with as many of the common ones as possible before the release, but there are hundreds, if not thousands, of JavaScript and other tools, not to mention third-party fonts, etc., that are called from another site. And if any of those called URLs use http, they need to be updated or changed, if you want your pages to be secure.

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.

If you're using newer code for Google tools or properties, the code may already have http: removed. But if you're using older code, check for http: in the JavaScript URL. And be safe -- check all the Google code your site uses.

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="//"></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.)

3. If you see http: in the JavaScript URL, remove it. The script tag should then look exactly like the one above.

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 Fonts

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.

Google Maps

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.
#1377472 by Debs from SiteSell
Mon Jul 24, 2017 2:36 pm
It has been expedited and the programmers are working on it, or will be once BI4 is out. Ken already noted this, that is why H.E. is posting tips for everyone to get ready. You can't just turn it on; you do need to prepare for it.

#1377483 by Susan from Ash Flat
Mon Jul 24, 2017 4:33 pm

So many things that to look at for this, makes me very nervous :shock: I've sorted the Adsense for all my sites but I'm a little confused about the analytics code.

I can't even remember how I got the codes for that in the first place! If anyone can refresh my memory that would be wonderful.

Meantime, this is the GA code on one of my sites, it does have https:// prefixes but also one with http:// does this mean it needs to be changed.. or not..?

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "' type='text/javascript'%3E%3C/script%3E"));
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-1841842-3");
} catch(err) {}</script>

Also, one last question. Had there been updates or other threads telling us what to work on after Google? I seem to have missed them if so :roll: Thank you!
#1377490 by Mary from Mico
Mon Jul 24, 2017 5:43 pm
Ruth and Debs - Thank you for your notes. Ruth thank you for reposting those directions.

Which brings me to Sue's comment.

Sue - I agree. I feel as if I've missed something because I feel I have not done much to prepare, but I tried to do all that's been mentioned above and through this thread.

Debs - I really appreciate seeing your comment here. I know what it's like to prepare for a move or a sitewide change and know that matters might seem to move slowly when actually things are flying as fast as possible. Thanks to Ken and all for expediting all of this.

Who expects to use the https bit soon after its release.
#1377757 by Katherine T from Swindon UK
Fri Jul 28, 2017 11:34 am
The google search box code is http:
In adsense I added a new one but the code is still http.
Do we just delete search for now?
Someone retweeted the following link from my website on twitter
[Domain Private]/what-is-prayer.html
and the link was labelled as from a site that contains 'not secure' content.
I don't know why and wonder if it just being http.
Any help wd be appreciated.
With thanks
#1377799 by Jeff from
Fri Jul 28, 2017 8:01 pm

Hi Katherine. That's correct. Your site is not secure. That's what HTTPS will take care of. But if you have content on a page that is not secure (such as the Google search box) the browser will tell people that the page is not secure.

The only way to fix that issue is to convert all the http URLs to https URLs, or use a new HTTPS URL provided by the business whose code you're using.


Katherine T from Swindon UK wrote:The google search box code is http:
In adsense I added a new one but the code is still http.
Do we just delete search for now?
Someone retweeted the following link from my website on twitter
[Domain Private]/what-is-prayer.html
and the link was labelled as from a site that contains 'not secure' content.
I don't know why and wonder if it just being http.
Any help wd be appreciated.
With thanks
Similar Topics Statistics Last post
TASK 2: FB PREP 👉 HTTPS Tasks to Take Care of Before the Release
1, 2, 3 by ken-admin Thu Jun 15, 2017 7:16 pm
31 Replies
by Debs from SiteSell
Tue Oct 17, 2017 6:16 pm
HTTPS Post-Conversion Tasks Article
1, 2 by ken-admin Mon Oct 16, 2017 12:37 pm
24 Replies
by Debs from SiteSell
Sat Oct 21, 2017 5:46 pm
Release: June 8, 2017: Action Guide Tasks (Interactive, Too!)
by ken-admin Thu Jun 08, 2017 5:37 pm
4 Replies
by Moorea S. from USA
Wed Jun 14, 2017 3:49 pm
1, 2 by ken-admin Wed Aug 30, 2017 11:58 pm
19 Replies
by Debs from SiteSell
Tue Oct 17, 2017 6:18 pm
HTTPS: Are You 100% Sure Your Conversion Is Complete?
1, 2, 3, 4 by Cath, SiteSell Content Team Thu Dec 21, 2017 3:17 pm
48 Replies
by Mary from Mico
Fri Feb 02, 2018 5:40 pm

Users browsing this forum: Holly from Rainbow Flat and 2 guests