Search Engine Land: Google publishes SEO guide to HTTP status codes, network issues and DNS errors. “Ever wonder how your various HTTP status codes or how your network or DNS responds to GoogleBot may impact how well your site performs on Google Search? Well, Google has published a new guide and help document detailing how HTTP status codes and network or DNS errors impact your Google Search performance.”
The Register: Google Chrome to block file downloads – from .exe to .txt – over HTTP by default this year. And we’re OK with this
The Register: Google Chrome to block file downloads – from .exe to .txt – over HTTP by default this year. And we’re OK with this. “Continuing to drop flame retardant on the dumpster fire that is web security, Google on Thursday said it will soon prevent Chrome users from downloading files over insecure, plain old, unencrypted HTTP.”
CNET: Chrome’s HTTP warning seeks to cut web surveillance, tampering. “The Hypertext Transfer Protocol lets your web browser fetch a web page from the server that hosts it. HTTP has had a good run, but it has a problem: It doesn’t protect communications with encryption that blocks eavesdropping and tampering. That’s why Google, Mozilla and other tech industry allies have been pushing websites everywhere to switch to the secure version, called HTTPS. And it’s why, starting with the release of Chrome 68 on Tuesday, Google’s browser will warn you whenever it loads an unencrypted HTTP website.”
Search Engine Journal: Migrating a WordPress Website from HTTP to HTTPS: A Complete Guide. “In this post, I will share the experience I had from migrating the SEJ website to HTTPS and many other WordPress-based websites I’ve worked on. I’ll be assuming you have basic WordPress coding skills and have already installed an SSL certificate on your website, since most hosting providers offer that feature with one click.” This is VERY thorough with LOTS of screenshots.
Google Online Security Blog: A secure web is here to stay. “For the past several years, we’ve moved toward a more secure web by strongly advocating that sites adopt HTTPS encryption. And within the last year, we’ve also helped users understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages as ‘not secure’. Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as ‘not secure’.”
Smashing Magazine: A Complete Guide To Switching From HTTP To HTTPS. “Setting up HTTPS can be a bit intimidating for the inexperienced user — it takes many steps with different parties, it requires specific knowledge of encryption and server configuration, and it sounds complicated in general. In this guide, I will explain the individual components and steps and will clearly cover the individual stages of the setup. Your experience should be easy, especially if your hosting provider also supplies HTTPS certificates — chances are you will be able to perform everything from your control panel quickly and easily.” Very extensive.
Chrome will start marking http connections as unsecure. “To help users browse the web safely, Chrome indicates connection security with an icon in the address bar. Historically, Chrome has not explicitly labelled HTTP connections as non-secure. Beginning in January 2017 (Chrome 56), we’ll mark HTTP sites that transmit passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.”