Update HTTP site to HTTPS

IMPORTANT: DO NOT BID on this project if you cannot provide references of site that you have migrated already. Experience required. SEE ATTACHED FILES for a complete task list. Below are only a few: Making the switch from HTTP to HTTPS Start with a test server. This is important because it lets you get everything right and test without screwing it up in real time. Even if you are doing the switch without a test server, there’s almost nothing you can do that you can’t recover from, but it’s still best practice to have a plan and have everything tested ahead of time. Crawl the current website so that you know the current state of the website and for comparison purposes. Read any documentation regarding your server or CDN for HTTPS. I run into lots of fun CDN issues, but it can also be straightforward. Get a security certificate and install on the server. This will vary depending on your hosting environment and server setup too much for me to go into details, but the process is usually well-documented. Update references in content. This can usually be done with a search-and-replace in the database. You’ll want to update all references to internal links to use HTTPS or relative paths. Update references in templates. Again, depending on how you deploy, this might be done with Git or simply Notepad++, but you’ll want to make sure references to scripts, images, links and so on are either using HTTPS or relative paths. Update canonical tags. Most CMS systems will take care of this for you when you make the switch, but double-check, because that’s not always the case. Update hreflang tags if your website uses them, or any other tags such as OG tags for that matter. Again, most CMS systems will take care of this, but it’s best to QA it just in case. Update any plugins/modules/add-ons to make sure nothing breaks and that nothing contains insecure content. I commonly see internal site search and forms missed. CMS-specific settings may need to be changed. For major CMS systems, these are usually well-documented in migration guides. Crawl the site to make sure you didn’t miss any links and nothing is broken. You can export any insecure content in one of the Screaming Frog reports if this is the crawler you are using. Make sure any external scripts that are called support HTTPS. Force HTTPS with redirects. This will depend on your server and configuration but is well-documented for Apache, Nginx and IIS. REMAINING STEPS INCLUDED IN ATTACHMENTS