Google recognized ‘HTTPS’ as an important ranking signal on August 6, 2014. Since then, many webmasters are shifting from HTTP to HTTPS version of their website; and this exodus seems to be heading in the right direction with Ecommerce websites leading from the front. As e-retailers cannot do without a secured encryption, HTTPS versions become the obvious option.
After you have decided to make the switch; do read this checklist that enables you to proceed with the HTTPS upgrade cautiously. In this article, we have compiled a list of pointers that you can keep in mind while upgrading your website to the HTTPS version.
Please note: Not all the points mentioned below are applicable to non-eCommerce websites but all points on HTTP to HTTPS update are relevant for Magento based eCommerce stores.
Want a PDF of this infographic? Download it from here
Firstly, you need to verify the website’s Https version in Google and Bing Webmaster tools. Verify and confirm whether the version to be updated is www or non-www. The www version is, of course, the preferred one and the update will be made to this.
Implement the SEO friendly “301 Redirect”. Always use permanent redirect on the non-preferred version and direct it to the verified HTTPS version. It is recommended that before the 301 redirects are applied, you have a list of all the areas where redirects are to be made and organize all the data which will have 301 redirects implemented. These may include a total number of links, index stats and sitemap stats, sitelinks and PPC landing pages.
Update Links to HTTPS:
Once the website is upgraded to the HTTPS version, you need to update all the main internal such as home page, CMS pages, PDFs, URLs in Videos and also links on all external online properties. Do not forget to update the URLs/ internal links in your newsletters. This will ensure that we are sending unique SEO page signals to search engines.
Update Links on Social Media:
The external links on social profiles, at least the main and popular ones, should have the HTTPS version of URLs.
Configure a new sitemap with the HTTPS URLs of the website and submit it in both Google and Bing webmasters.
Update the existing Robots.txt file of the website and update the new sitemap, configured for the HTTPS version of the website.
Once the Robots.txt file is updated, you should double check it to ensure that it should not block any pages like CMS, Product page or any other. This needs to be done, especially, if you have introduced new pages or sections while upgrading from HTTP to the HTTPS version.
Configure Canonical Tags:
Configure canonical tags and make them point to the HTTPS version. The canonical tag should be implemented on the same pages but this time they should point to the HTTPS versions. Please note that Magento may do this on its own but webmasters will still need to ensure that the implementation was correctly executed.
Update PPC / CSE landing pages with the HTTPS version URLs so that they should not affect the landing page score.
Take a backup of Google Webmaster HTTPS versions (snapshot and details).
Re-Submit the Links:
Re-submit the Links Disavow file in both the Webmaster tools. This ensures that spammy links will not affect the new verified version of the website. You need to update the Robots.txt file on both Google and Bing webmaster tools.
Manage URL Parameters:
Make sure that you manage URL parameters for the HTTPS version in both Google and Bing webmaster tools. For this, you can simply copy the URL parameters settings from the HTTP version and reflect them in the HTTPS version.
Update Google Analytics:
Update Google Analytics Admin settings. Please select “HTTPS ” version and save the settings. This ensures that all the reported data procured in Google Analytics will now be for the HTTPS (new version).
Update URL in Email Signatures:
Update your email signatures with the new URL i.e. https://www.example.com
Ensure that the existing CDN on the website does not cause any issue once the website is shifted from HTTP to HTTPS version. Coordinate with the CDN team and make the necessary changes. Make sure that your CDN can handle SSL. Also, ask your CDN company to share their concerns regarding the upgrade beforehand, so that the switch does not become counterproductive.
Re-design the Newsletter:
Re-design the newsletter templates – Auto-responder emails, Triggers, on site pop-ups and update all the links with HTTPS URLs. Also, update the internal links of Newsletter Welcome series emails that maybe be configured on Magento or any Newsletter Marketing software.
Plan Your Newsletters:
Do not send any newsletter or offers for at least 4-5 days before the planned upgrade is due.
Code Check Up:
Consider upgrading the website at a time when the traffic on the website is at its lowest for that season. This is really crucial for eCommerce stores.
Optimize Google Webmaster:
Optimize Google Webmaster crawl time using ‘Crawl settings’. Please minimize the requests sent per second before the upgrade is due. This setting will take 48 hours to be effective, so make this change at least 2-3 days before the planned upgrade.
Update all the implemented 301 redirects to the HTTPS version. This can be done at the server level by your Server team. Basically, all the 301 redirects implemented on 404 pages should be updated to the HTTPS version.
3rd Party Tracking Codes:
Keep a backup of the 3rd party tracking codes (Adwords, Bing, Conversion codes, Remarketing codes, and Analytics codes) and update them to the HTTPS version.
Check hosted Blog extension settings, plugins, etc. For example, WordPress Blog should work on HTTPS and so should the installed plugins like Yoast extension, social sharing and security plugins.
Evaluate the Mobile Version:
Evaluate the mobile version of the website and ensure that the HTTPS URLs are responsive or non-responsive. If not, configure the settings accordingly for a mobile-friendly HTTPS version of the website.
Re-submit the Removal Request:
Re-submit the removal request of URLs in Google and Bing webmaster tools. For example, The old HTML sitemap or any other page on the website that was submitted for removal needs to be re-submitted for the HTTPS version also.
Update the Dev Version:
The Dev version of the website should also be updated to HTTPS. This way potential changes which may be required on the live HTTPS site can be tested on the Dev site with the HTTPS encryption. So you can have something like https:www.dev.websitename.com
Check 3rd Party Extensions:
Check to ensure that the 3rd party extension like Website search is working fine in the upgraded version.
Https Version Validation:
Get the new HTTPS version validated by an online tool such as W3c. This will help you make your website cleaner after the switch. As Google grants more leverage to cleanly coded and glitch-free websites, getting your version checked and reported for errors or warnings is highly recommended.
Compare Page Speed:
Compare the website page speed for both the HTTP and HTTPS versions using the Google tool and implement the necessary changes.
Check Social Sharing Extension:
All the social sharing extensions (buttons on product page or blog) should work on the updated version.
Configure Data Highlighter:
Configure Data Highlighter in Google Webmaster tools and set it for HTTPS version. This enables the HTTPS URL to get picked up in the rich snippet results.
Absolute and Relative URLs:
If a website is using both ‘Absolute and Relative URLs’, on the website, then the Relative URLs will update to HTTPS automatically. Absolute URLs have to be updated manually. Please ensure that both URL types are duly updated.
Update URLs on External Links:
Update “301 redirects” on the external domains owned by you. For example, there can be a number of websites or blogs that might be 301 redirecting to the HTTP version. This needs to be updated so that the external links can redirect to the HTTPS version after the upgrade is pushed live.
Update Blog Links:
The internal links on the website’s images linked from the blog posts also need to be updated to their HTTPS URLs. Do update these in WordPress. This can be done under the “General Settings” section where you can mention the ‘WordPress Address (URL)’ as HTTPS.
Check if RSS subscription feed of the Blog or the website is working for the upgraded version.
Get URLs Updated on 3rd Party:
Contact the website owners/affiliates and ask them to update the website URL and use the new HTTPS.
Use Updated URLs for Link Building:
If you employ a link building strategy that involves leaving links in different forums and threads, then, continue with your link building efforts but now use the updated URLs of the website.
Ensure that the content on HTTP and HTTPS website is similar.
Upgrade Your SSL Certificate:
Upgrade your website SSL certificate to SHA2 to support website pages like Checkout, Category pages, and Product pages. Otherwise, it can trigger Server errors in the Webmaster tools. Moreover, Google prefers the SHA2 certification and considers it as a ranking parameter.
Upgrade 3rd Party SEO Tools:
If you are using any 3rd party SEO tool like Moz.com, please submit the HTTPS version to them to make sure it shows the SEO score of HTTPS version.
- Check Social media counters
When you migrate to HTTPS the social counters often stop working and reflect the old numbers, or get reset to zero. Updating the plugins (on WordPress) often solves the problem.
- Support and Enable HSTS
The HSTS (HTTP Strict Transport Security) helps protect websites against protocol downgrade attacks and cookie hijacking. Google says HSTS tells the browser to request HTTPS pages automatically, even if the user enters HTTP in the browser address bar. It also tells Google to serve secure URLs in the search results.
- Enable OCSP stapling
The process of OCSP (Online Certificate Status Protocol) checking slows down browsing as it requires real time checking of security certificate each time a URL is requested. OCSP Stapling allows rectifying this by issuing a signed time-stamped response. This reduces the need to cross-reference with a Certificate Authority (CA) thereby increasing speed.
- Update Local Citations
Do not forget to update your site’s address across all Local Citation sites.
- Check Your Website For Mixed Content Warnings
Mixed content warnings appear when you serve unnoticedly serve both HTTP and HTTPS assets/content. Serve all assets through HTTPS to avoid such warnings.
- Check RSS Feed
Make sure all the URLs served in RSS feed are HTTPS.
The HTTPS upgrade, if not done properly, can result in reduced visibility in the search results; a fallout of lowered rankings. Also, there may be other severe long-term effects of not making the switch. These can include insecure connections, compromised referral data and now, a bad rap with Google.
These 40 points must be implemented so that the transition from HTTP to HTTPS is event-less. We’d also like to hear about the cautions that you take or have heard of and can add to this list shared here.
If you’d like to discuss migrating your site to HTTPS, get in touch with us.
Wishing you a happy and a smooth switch!