Popular channels


Regardless of the size of your website is, there are a few key things to consider when migrating to HTTPS:
Ensure that you do a 301 redirect from the HTTP version to the HTTPS version.
Ensure that any canonical tags point to the HTTPS version.
Internal links should also all point to the HTTPS. Even though they’re all going to redirect over, you want to eliminate that need to redirect. When Google is crawling and indexing a website, it doesn’t handle redirects very well, particularly if there’s a redirect chain that goes through more than one step at a time before you reach the final destination.
Make sure that all images, JavaScript, and resources on the page are also being loaded through HTTPS.
It is key to set up Google search console for the new HTTPS version of your site; because Google splits the data, they won’t treat it the same as the non-HTTPS version. So, before you start, make sure you set it up so that you can see the data as it starts populating.
Once you have hardcoded a website, you will need to go back through and update the site to point to the HTTPS version, or use what’s called a protocol agnostic version. This is where you leave out the HTTP. By simply typing // followed by the domain, it retains the same protocol – so HTTP will stay HTTP and HTTPS will link to HTTPS.
Remember that if you’re loading JavaScript from, for example, an HTTP source, modern browsers are going to consider that as insecure content, and, more often than not, will block it from loading. This means that if you have a booking form or some type of functionality that requires the HTTP JavaScript, it’s not actually going to load it because it’s being loaded from an insecure source, which means you could potentially break your website.