Redirects and HTTPS: avoid loops when moving a page or domain

A redirect sends a browser to a different URL. It does not move files, transfer domain registration or fix incorrect DNS. The source hostname still needs to reach a server capable of issuing the redirect.

Plan the destination

1. Decide the final HTTPS hostname and path, including whether www is canonical.
2. Confirm the destination works and has a valid certificate.
3. Review redirects already configured in the application, cPanel, .htaccess and any CDN.
4. Add the narrowest required rule and choose permanent status only when the move is genuinely permanent.
5. Test the source and destination with and without www, HTTP and HTTPS, and important paths.

Diagnose loops

Conflicting layers can redirect to each other. A reverse proxy may also report the original scheme incorrectly if trusted-proxy configuration is wrong. Do not fix this by trusting arbitrary forwarded headers from every visitor.

Retain a copy of old rules and change one layer at a time. Preserve query strings only where the migration requires them; avoid carrying credentials in URLs. Do not redirect certificate-validation paths or admin interfaces blindly. After a move, update internal links so normal navigation reaches the final URL directly.