Implement HTTPS redirects at server level and update all internal links.
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Proper HTTPS migration requires server-level 301 redirects and updating internal links for efficiency and link equity preservation.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- Configure server (nginx/Apache) to serve 301 redirects from HTTP to HTTPS.
- Audit all internal site links and update them to use HTTPS URLs only.
- Update canonical tags on all pages to point to HTTPS versions.
- Revise XML sitemap URLs to HTTPS and submit updated sitemap to search engines.
- Test multiple pages to verify redirects and link updates are functioning as intended.
Watch for
Using CMS-level redirects or leaving internal HTTP links causes inefficiency and possible ranking issues.
Definition of done
All old HTTP URLs return 301 redirect to HTTPS and internal site links reference HTTPS URLs directly.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.