Next steps toward more connection security

Chromium Blog

News and developments from the open source browser project

Thursday, April 27, 2017

In January, we began our quest to improve how Chrome communicates the connection security of HTTP pages. Chrome now marks HTTP pages as “Not secure” if they have password or credit card fields. Beginning in October 2017, Chrome will show the “Not secure” warning in two additional situations: when users enter data on an HTTP page, and on all HTTP pages visited in Incognito mode.

http not secure

Treatment of HTTP pages in Chrome 62

Our plan to label HTTP sites as non-secure is taking place in gradual steps, based on increasingly broad criteria. Since the change in Chrome 56, there has been a 23% reduction in the fraction of navigations to HTTP pages with password or credit card forms on desktop, and we’re ready to take the next steps.

Passwords and credit cards are not the only types of data that should be private. Any type of data that users type into websites should not be accessible to others on the network, so starting in version 62 Chrome will show the “Not secure” warning when users type data into HTTP sites.

 

non secure in incognito mode

Treatment of HTTP pages with user-entered data in Chrome 62

When users browse Chrome with Incognito mode, they likely have increased expectations of privacy. However, HTTP browsing is not private to others on the network, so in version 62 Chrome will also warn users when visiting an HTTP page in Incognito mode.

Eventually, we plan to show the “Not secure” warning for all HTTP pages, even outside Incognito mode. We will publish updates as we approach future releases, but don’t wait to get started moving to HTTPS! HTTPS is easier and cheaper than ever before, and it enables both the best performance the web offers and powerful new features that are too sensitive for HTTP. Check out our set-up guides to get started.

Posted by Emily Schechter, Chrome Security Team

Spearhead Multimedia gas very inexpensive solutions to make your site secure.  Find out here…

Google Gives A Ranking Boost To Secure HTTPS/SSL Sites

google-ssl-https-secure

Google Gives Secure Sites A Ranking Boost

Google has announced that going HTTPS — adding a SSL 2048-bit key certificate on your site — will give you a minor ranking boost.

Google says this gives websites a small ranking benefit, only counting as a “very lightweight signal” within the overall ranking algorithm. In fact, Google said this carries “less weight than other signals such as high-quality content.” Based on their tests, Google says it has an impact on “fewer than 1% of global queries” but said they “may decide to strengthen” the signal because they want to “encourage all website owners to switch from HTTP to HTTPS to keep everyone safe on the web.”

Google also said based on their tests for the past few months, the HTTPS signal showed “positive results” in terms of relevancy and ranking in Google’s search results.

As you may remember, at SMX West, Matt Cutts, Google’s head of search spam, said he’d love to make SSL a ranking factor in Google’s algorithm. Well, less than five months after that announcement, and while he is on an extended leave, Google is making it a reality.

SEO Concerns With Going HTTPS

Should you be concerned when switching from your HTTP to HTTPS site for SEO purposes? Not so much. Google has been telling webmasters it is safe to do so for years. But you need to take the proper steps to ensure your traffic doesn’t suffer. That means make sure to communicate to Google that you moved your site from HTTP to HTTPS. Google promises to release more documentation in the future, but for now has provided the following tips:

  • Decide the kind of certificate you need: single, multi-domain, or wildcard certificate
  • Use 2048-bit key certificates
  • Use relative URLs for resources that reside on the same secure domain
  • Use protocol relative URLs for all other domains
  • Check out our site move article for more guidelines on how to change your website’s address
  • Don’t block your HTTPS site from crawling using robots.txt
  • Allow indexing of your pages by search engines where possible. Avoid the noindex robots meta tag.

Google has also updated Google Webmaster Tools to better handle HTTPS sites and the reporting on them.

One last thing: You will want to make sure to track your HTTP to HTTPS migration carefully in your analytics software and within Google Webmaster Tools.

Postscript: Google webmaster trends analyst John Mueller is also answering some questions about the change here on Google+.

Spearhead Multimedia offers multiple choices for SSL Certificates.  Get yours here today.

From http://searchengineland.com 

Positive SSL