Removing a cPanel redirect and checking for cached rules

Record the old source, destination and type before deleting it. Confirm what should serve the source URL afterward. If you are replacing a redirect, prepare the new destination and avoid leaving a loop or a period where visitors reach unintended content.

1. Open Redirects and inspect Current Redirects. Find the row whose source domain and path match the rule you want to remove.
2. Choose Delete or Remove for that row and confirm the specific rule. Do not delete unrelated redirects as a troubleshooting shortcut.
3. Test the source with a private browser window or a fresh HTTP client. Compare its response with the expected local page or replacement rule.
4. If redirection remains, check the application’s site URL settings, other .htaccess rules and any CDN or reverse-proxy redirect configuration.
5. Update links that pointed through the retired redirect if you control those links.

Confirm both the original URL and the former destination behave independently as intended. Test a nearby path to make sure removing the rule did not expose a broken application route.

A cached 301 response can outlast a server-side change, so do not repeatedly alter working configuration based on one browser. If the old rule is needed again, recreate it from the saved details. Restore .htaccess only after comparing newer changes that must be kept.

• Creating a page or domain redirect in cPanel
• Finding and editing .htaccess in cPanel
• Redirecting a cPanel subdomain to an external URL
• Enabling the cPanel HTTPS redirect without a redirect loop

• cPanel documentation