There are a few steps to making your site secure.
The first is to run
the HTTPS Resources Check. You'll find the link to it in the SiteBuilder
section, in the left column. See the screenshot below.
It's bring you to a page that will prompt you if you want to start the HTTPS migration, and if you're ready, click "Yes, start the migration" but before that, here are some notes/precautions/preparations that you should read first BEFORE you migrate to HTTPS:
Converting to HTTPS, and
Google Chrome's v62 is upon us, which means it's time to convert your
site to HTTPS (or have Chrome warn visitors that forms and other content
on your pages is not secure).
Having a secure site is also essential for being compliant with the European Union's GDPR
(General Data Protection Regulation). If you're reading this after May
25, 2018, and your site is still not secure, it's essential that you get
this done as soon as possible.
Now that the HTTPS conversion tool is available, you probably want to
get it done. That's assuming that you've changed everything on your site
that needs changing.
Important Note: If you have a Google Custom Search
Engine (CSE) on your site, you may need to change the URL to HTTPS if it
isn't already. There are multiple versions of the CSE URL, and the
system cannot change one of them due to the negative effect it has on
After the conversion, check that yours is still http. If it is, edit
the URL. If it's in a Reusable Block or Sitewide Dot, edit the block or
dot content and rebuild the page you edited.
If you have more than one site, select one, run the checker and fix any
non-secure content it reports. Then move to the second and repeat, until
you've checked all of your sites and fixed all the non-secure content.
Before you convert your site to HTTPS, there are some things to be aware
In particular, risks to your traffic, and tasks that you'll need to
perform as soon as the conversion is complete (which will be an hour or
two), along with a few that will take some time.
If you registered your domain name after October 16, 2017, your site
already uses HTTPS. You can safely ignore everything in this article.
Better yet, stop reading now and publish more content on your site!
Your site may experience some traffic drops over a few weeks after you convert, perhaps even for a few months.
The SiteSell Dev team has worked hard to minimize the amount of
traffic your site might lose in the short-term, including setting up
automatic 301 redirects from the http version of each page to the HTTPS
version of the page.
Take your time now to think through all the possible scenarios
regarding traffic and income. Then base your conversion "go or no go" on
what you determine is the best course of action right now.
decide to wait until a particular time, take a moment now to schedule a
review in your calendar.
If your site is seasonal, and your big season is in the next 2-3
months, you may want to hold off on converting to HTTPS until that
On the flip side, if you don't convert, and there are order
forms on your pages, those forms will be flagged as not being secure.
So some of your visitors may be scared away from ordering from you.
If you send visitors to affiliate sites using banner or product
images, and those image URLs use http, Chrome will also report those
images as non-secure.
Even if you decide to hold off on converting, fix
as many of these affiliate image issues as you can. This will reduce the
number of warnings your visitors see when they visit the pages where
you promote affiliate products.
When you're ready to proceed, take note of your social share numbers
(Facebook page and site likes, Twitter followers, Pinterest saves
(pins), etc.). You'll want those to compare with the numbers you see
Also update your Search Engine HQ Keyword Ranking Report, then take a
screenshot of the updated numbers, to compare with the post-conversion
numbers after 3-4 weeks.
Conversion is a one-way process. If you convert your site, you can't
"unconvert" it back to http if you don't like some aspects of it
(traffic goes down, social shares are lost, etc.).
So be absolutely certain that you want to convert your site to HTTPS.
If you decide to delay converting, you don't need to continue