Common Redirect Mistakes to Avoid During SSL Installation from HTTP to HTTPS.
I would like to share one of my client's website's four types of redirect mistakes while they were redirecting after SSL installation from HTTP to HTTPS:
- Consolidated Redirect Mistake: Subpage URLs redirected from http://www.pothys.com/women-wear.html/ is redirecting to https://www.pothys.com instead of https://www.pothys.com/women-wear.html/.
- Partially Redirected to SSL: Not all website elements were properly redirected to the new HTTPS URLs, including image URLs, CSS, and JavaScript files, among others.
- Multiple Versions: The developer failed to set up 301 redirects for multiple URL versions, including HTTP to HTTPS, non-www to www, index.html, and index.aspx.
- 302 Redirect Mistake: Another mistake is a 302 redirect implemented on Pothys' site. Generally, it is not recommended for redirecting HTTP URLs to HTTPS URLs. A 302 redirect is a temporary redirect, and search engines may not update their index to reflect the new HTTPS URLs.
I identified these issues and successfully escalated them with the developer and rectified them. Proper redirect setup is crucial for a successful transition from HTTP to HTTPS. With the issues rectified, my client's website is now fully redirected to HTTPS, and the website traffic and search engine ranking have improved.
If you are planning to redirect your website to HTTPS, make sure you avoid these common mistakes. Properly redirecting your website will help ensure a smooth transition to HTTPS and maintain your website traffic and search engine ranking.
Comments
Post a Comment