Redirect recipes you can trust
- Covers canonical host moves, protocol upgrades, single URL hops, and slash policies.
- Toggle 301 vs 302 to match permanent migrations or short-lived campaigns.
- Plain-language explanations accompany every generated snippet.
- Copy or download the text file for version control friendly hand-offs.
How to deploy safely
- Choose the scenario that matches your hosting panel (cPanel, Plesk, bare Apache).
- Enter canonical domains or paths — avoid mixing trailing slash styles.
- Generate, read the explanation, then paste near the top of .htaccess above fragile rules.
- Test with curl -I or browser devtools, watching for loops or double redirects.
Common scenarios
HTTPS cutovers, blog subdomain consolidations, and post-acquisition domain merges all need disciplined redirects. After deployment, confirm TLS with the SSL checker and validate propagation via the DNS checker.
Keep bots aligned after URL changes
Pair redirects with refreshed canonical meta tags so search engines consolidate signals to the final URLs quickly.