Use a redirect when visitors to an additional domain should be sent to another URL. A redirect changes the browser’s destination; sharing a document root or changing a DNS record does not perform the same task.
IN THIS ARTICLE
What you need before you begin
Confirm you control the source domain and that it reaches this hosting account. HTTPS visitors need a working certificate on the source before its redirect can be read. Decide whether paths should be preserved and whether the move is temporary or permanent.
01 Redirect an additional cPanel domain to another website
- Open Redirects in cPanel and select the specific additional domain as the source. Avoid choosing every domain unless that broad scope is intentional.
- Choose a temporary redirect while testing, or a permanent redirect for a settled move. Enter the complete destination URL, including
https://. - Review the www options and any wildcard/path-preservation setting. A path-preserving redirect needs matching paths on the destination site.
- Add the rule and test the bare domain, www variant and a representative internal URL. Check the final address and whether the page exists there.
Confirm the expected result
Use a private browser window or a fresh HTTP request to avoid a cached permanent redirect masking the current rule. Confirm there is no loop between the old and new sites.
Why does the domain redirect fail or persist after removal?
If the redirect fails, check source DNS, SSL and any application or CDN redirects that run earlier. Keep a copy of .htaccess before editing rules manually. To reverse the change, remove the specific redirect and allow for browser caching rather than deleting the domain’s website files.