Switching on a certificate is not the same as completing an HTTPS migration. Old links still need to work, embedded resources need to load securely, and customers must still be able to use the site.
1. Prepare the certificate and a rollback
Have the hosting provider configure a valid TLS certificate for the hostnames the site uses. Confirm certificate renewal and who owns it. Keep a recoverable copy of the existing configuration before changing redirects or canonical URLs.
2. Check the page resources
Load representative HTTPS pages and inspect images, scripts, styles, embeds and forms. Fix resources still requested over HTTP. Test the parts that matter commercially: navigation, product selection, checkout or enquiry submission.
3. Redirect each old URL to its equivalent
Use a server-side permanent redirect from an HTTP page to the corresponding HTTPS page. Do not switch off the old endpoint before it can redirect visitors. Do not send every page to the homepage.
The related 2016 article, “When HTTPS Goes Wrong”, described a site where the certificate was enabled but redirects were missed. The enduring lesson is the handoff: someone must own the URL mapping and verify it, not just install the certificate.
4. Align the search signals
Update internal links, canonical URLs and the sitemap to HTTPS. Confirm Search Console ownership and submit the current sitemap. Check that production pages intended for search are not carrying development-only noindex rules or crawl blocks.
Google’s Change of Address tool is for domain or subdomain moves, not a simple HTTP-to-HTTPS switch (guidance checked 10 September 2026).
5. Crawl, test and monitor
Test old URLs through to their final destinations. Check status codes, certificate errors, redirect chains and page resources. Monitor Search Console and analytics after launch, including important landing pages and the enquiry or purchase flow.
A migration can cause temporary search fluctuations. Passing these checks reduces avoidable mistakes; it does not guarantee unchanged rankings.
See when to use a 301 redirect or discuss the migration through our SEO service.
This checklist has been updated to reflect current HTTPS migration practice. See Google’s site-move guidance, checked 10 September 2026.