How to Redirect an Add-on Domain?

Use cPanel. Go to Home > Domains > Redirects, choose Permanent (301) or Temporary (302), pick your add‑on domain, enter the destination URL including https://, then add the redirect. Do this instead of the old Addon Domains screen.

Before you start

• You can log in to cPanel for the hosting account.
• The domain is present in cPanel > Domains. If it is missing, add it there first. The old “Addon Domains” icon was removed in Jupiter.
• You know the full destination URL and whether this move is permanent (301) or temporary (302).

Step 1: Create the redirect in cPanel

1. Log in to cPanel, then open Home > Domains > Redirects.
2. Set Type to Permanent (301) for a domain move you intend to keep, or Temporary (302) if you plan to revert.
3. In the domain list, select your add‑on domain. Do not choose “All Public Domains” unless you want every domain in this cPanel account redirected.
4. Leave the path box empty to redirect the whole domain. Fill it only if you are redirecting a specific folder.
5. In “Redirects to”, enter the destination including the protocol, for example https://newexample.com.
6. Set the “www” option as required. “Redirect with or without www” is fine for most cases.
7. Tick Wild Card Redirect only if you want paths to map one‑for‑one, for example oldsite.com/page to newsite.com/page.
8. Save the redirect. cPanel shows it in the list and provides a link to test it.

Step 2: Test and allow for caching

1. Use the test link cPanel shows, or visit your old domain in a private window. 301s are cached by browsers, so a normal refresh can mislead.
2. Know that cPanel appends rules to the bottom of the site’s .htaccess. If your CMS has rewrite rules higher up, they can take precedence. See “If it does not work”.

Step 3: Undo or change the redirect

1. Return to cPanel > Redirects, find the rule and delete it. You cannot edit an existing redirect.
2. Recreate it with the new settings. If you changed a 301, clear your browser cache or use a different browser to test.

If it does not work

• Another rule is taking priority. The Redirects tool writes at the end of .htaccess, so WordPress or other rewrites above it can block your redirect. Fix by editing .htaccess in File Manager, then moving or adding your rule above the CMS section. For example:

  Redirect 301 / https://newexample.com/

  Place your change above any “# BEGIN WordPress” block, then retest.
• Loop detected, for example ERR_TOO_MANY_REDIRECTS. This indicates circular rules, often from mixing Force HTTPS with a domain‑to‑domain rule or a plugin doing its own redirect. Temporarily disable Force HTTPS for the source domain in cPanel > Domains > Domains, remove one of the conflicting rules, then reintroduce redirects in a single place.
• Wrong scope selected. If other sites in your account started redirecting or every path moved unexpectedly, you likely chose “All Public Domains” or ticked Wild Card Redirect by mistake. Delete the rule, recreate it for the single domain, and leave Wild Card unticked unless you intend path mapping.

If you want us to check the .htaccess order or diagnose a loop, open a support ticket and tell us the domains involved.

What next

If this is part of a migration and you run your own server, see our VPS guides for server‑level notes. Planning a new UK environment to test redirects before switching live traffic? See our Linux VPS. If you need hands‑on help, open a support ticket.