This guide is for websites running on UtCloud with OpenLiteSpeed. It covers safe checks for redirects in your site's .htaccess file, not changes to managed server configuration. Instructions for Apache or cPanel may not apply unchanged.
1. Back up the file first
Save a copy of the current .htaccess file before editing it. Work in the correct website's document root and, where possible, test on a staging copy. Incorrect rules can break your website or cause a redirect loop. Do not replace the whole file or remove unrelated security or application rules.
2. Check the redirect syntax and rewrite engine
If your old instructions use Apache Redirect 301 directives, do not assume they will work unchanged on OpenLiteSpeed. Rewrite-based redirects use RewriteRule. Ensure the rewrite block includes RewriteEngine On.
For example, this redirects one old path to another on the same site. Replace the example paths with your own; do not paste it unchanged:
RewriteEngine On
RewriteRule ^old-page/?$ /new-page/ [R=301,L]
Check that the destination exists and does not redirect back to the old address.
3. Put redirects before the application catch-all
Rule order matters. A WordPress or other application block may end with a catch-all such as RewriteRule . /index.php [L]. If your redirect block sits below it, requests can be sent to the application before they reach your redirects.
Place custom redirects before that catch-all/application block. Keep custom rules outside automatically generated WordPress sections so the application does not overwrite them. Review their order alongside existing HTTPS and www rules to avoid loops.
4. Test without an old cached redirect
Browsers can remember permanent (301) redirects. Test in a fresh private browser window. If you are comfortable using a terminal on your own computer, you can also inspect the response headers:
curl -I https://www.example.com/old-page/
Replace the example domain and path. Look for a 301 response and the expected Location destination, then open the destination and check it works. This test does not require logging in to the server.
Still not working on a managed service?
Open a helpdesk ticket with your domain, the source and destination URLs, the relevant rules and their position in the file, what you changed and the response you see. Do not include passwords.
If a managed server setting needs checking or the configuration needs to be applied server-side, our technical team will review that through the ticket. Do not attempt root commands, server restarts or WebAdmin changes based on generic instructions. Custom website rule development or content edits are not included as free changes; ask for a quote if you need that work.