TWIS Chrome HTTP Warnings

What’s this about?

This is an extract from TWIS SEO News & Updates w/e 18 August 2017.

Read the detail about Google’s upcoming Chrome HTTP Warnings and find out what you should be doing to migrate to HTTPS.

Click here to contact me to discuss migrating to HTTPS. I have a wealth of successful migration experience we can use to make sure traffic and rankings are preserved, or increased.

#SEO #HTTPS #GoogleSearchConsole #GoogleChrome #SiteMigrations


Google Warns of Upcoming Chrome HTTP Warnings 

Summary – Chrome HTTP Warnings:

  • The eagle eyed amongst you will have spotted the story I posted last week: Google Sending HTTP Security Warnings Now – you really should read it.
  • Google Search Console has been sending out warnings to the owners of properties in Google Search Console who do not have an https property also verified.
  • The warning advises that from October, Google Chrome will start to mark any page with  form element on it as Not Secure, if the URL is not on HTTPS.
  • The release date of this version of Chrome is October 17th, 2017. The email was generated two months prior to that release date, which unfortunately was  just just after midnight last Friday morning. Cue a number of people panicking over the weekend.

Google Search Console Chrome HTTP Warning

Actions to take – Chrome HTTPS Warnings:

  1. Read the actions in Google Sending HTTP Security Warnings Now.
  2. If you received a warning, but have an HTTPS variant of your website, include the HTTPS variant in Google Search Console. You should also 301 Redirect from HTTP to HTTPS.
  3. If you do not have an HTTPS variant, migrate your website to HTTPS, using 301 Redirects.
  4. Migrating is always not a super complex issue, but care does need to be taken to follow a sensible methodology from Point 1 to Point XX.
  5. Click here to contact me to discuss migrating to HTTPS. I have a wealth of successful migration experience we can use to make sure traffic and rankings are preserved, or increased.

Discussion:

Google has been getting more and more strident in its clear wish that all websites should be served on HTTPS. This is a good thing generally, as it is valuable to for user to know that their information is secured on it journey between their browser and your servers.

Much has been made of some recent posts regarding the “issue”  that HTTPS does not make your website secure. This isn’t an issue, because it is not the point of HTTPS. You can still have as many open backends, or databases as you want. HTTPS is all about securing the data as it is transferred between the user’s browser and your server. Nothing more, nothing less.

More info:

Return to Top


The State of SEO Mid-2017 Released

The State of SEO Mid 2017

We recently released the super-exciting The State of SEO in mid-2017. Read it now.

Return to Top


TL;DR

Thanks for reading. If you would like to discuss what these changes mean for your web property, or would like to know how to implement them, please feel free to contact me.

Return to Top