Starting in July many of the Google products will be marking any websites that have not been converted from http to https as “not secure.” You may want to share this with your webmaster so that he/she can take the necessary steps to ensure that the website is available on Google Chrome, Adwords, YouTube, etc. once this change happens. Order your SSL Certificate here if you are a GMI client.!
Here is some information provided by Google:
The importance of HTTPS
User privacy is a matter of the highest importance for Google and for anyone doing business online. HTTPS is a secure protocol that helps protect your customers’ information by encrypting data traveling between a web browser and a web server. AdWords recommends (and in some cases, requires) that all URLs use the HTTPS protocol instead of HTTP to protect customers’ personal and financial information.
Trust and safety
Customer privacy is a primary concern for your business and for AdWords. This is why Chrome will mark all HTTP pages as “not secure,” starting in July 2018.
HTTPS enables technologies that speed up the user experience. New performance-enhancing web protocols like HTTP/2 require HTTPS, which is one of the reasons that 81 of the top 100 sites on the web use HTTPS by default. Also, AdWords’ speed-enhancing parallel tracking feature requires that all click-measuring URLs (URLs contained in the “Tracking URL” field) use HTTPS. Starting October 30, 2018, parallel tracking will become the only method for click measurement. Because of this, all Tracking URLs will need to use HTTPS.
Because of the security and performance benefits associated with its use, HTTPS has become the standard protocol used on the web.
How to check if your site supports HTTPS
Open your website in a Chrome browser and see which of the following situations apply to you:
- If you see a green lock icon to the left of the URL, then your site supports HTTPS.
- If the lock does not appear, try re-entering your website URL with “https://” instead of “http://”.
- If the page doesn’t load, then your site does not support HTTPS.
If your site supports HTTPS
Change your AdWords final URLs and mobile final URLs to use HTTPS. There are three ways to bulk edit ads and keywords:
The bulk uploads feature within AdWords (best for smaller accounts)
For this option, download your ads and (if necessary) keywords from AdWords, update your URLs, and then upload your edited ads back into your AdWords account. Learn more about making changes with bulk uploads.
The desktop tool AdWords Editor
If your site does not support HTTPS
Speak with your webmaster or the administrator of your CMS platform. If you manage your own website, you can learn more at the following websites:
When you enable HTTPS on your website, it is a recommended best practice to redirect instances of HTTP to HTTPS to make sure old links keep working and visitors to your website are redirected to secure content.
We strongly recommend that you explicitly change your final URLs and mobile final URLs from HTTP to HTTPS in AdWords. Reliance on redirects does not provide the full security protections of the HTTPS protocol. Users’ requests are not encrypted. Also, redirects slow down page load times, which affect the landing page experience, and can potentially impact your conversion rate and return on ad spend (ROAS).
AdWords automatic redirecting to HTTPS
The best practice is to replace your HTTP URLs with HTTPS URLs. But, in some cases, if you have HTTP URLs in AdWords and your website is detected as supporting HTTPS, AdWords will automatically forward your clicks directly to the HTTPS version of the URL.
Starting the week of June 11, 2018, AdWords will begin forwarding some, or all, of your HTTP clicks to HTTPS in the following situations:
If your website has implemented HTTPS Strict Transport Security (HSTS), all clicks will be forwarded to HTTPS.
If a URL is forwarded to an equivalent HTTPS URL via a 301 redirect, all clicks on that URL will be forwarded to HTTPS.
What Is The Most Secure & Private Web Browser For 2018?
Click here for a very informative article by PixelPrivacy.com