Knowledge base article

Search the support library or follow the guide below.

Step-by-step guidance

How to Redirect an Addon Domain in cPanel

Redirect an addon domain in cPanel when visitors should move to a different website or address. Keep the domain's hosting entry and DNS working so requests can reach the redirect. A redirect changes the visitor's address; it does not move website files.

Older Addon Domains screens may offer Manage Redirection. In current cPanel versions, use Redirects to create and review these rules.

Before you start

  • Open the intended destination and confirm it works. Record the source domain and whether existing page paths should be preserved.
  • Check for existing redirects in cPanel, the website application, and any CDN. Conflicting rules can send visitors back and forth between addresses.

Instructions

  1. Choose the redirect type

    Open Redirects in cPanel. Select a permanent 301 only for a lasting move, or a temporary 302 when the change should remain temporary.

  2. Select the addon domain

    Choose the exact source domain from the domain menu. Leave the source path empty for its root. Avoid selecting all domains unless every hosted domain should be affected.

  3. Set the destination

    Enter the complete destination URL, including https:// and any required page path. Choose the www handling that matches the source addresses visitors use.

  4. Decide how paths behave

    Enable Wild Card Redirect only when source paths should carry over, such as /contact going to /contact on the destination. Leave it off for a single landing-page destination.

  5. Save and test

    Add the redirect and locate it in Current Redirects. Test the source root and a representative page in a fresh browser session.

Check the result

  • The browser reaches the intended destination without repeated redirects or missing-page errors.
  • Both www and non-www source addresses behave as intended; unrelated domains still work.

Troubleshooting

A certificate warning appears before the redirect.
An HTTPS source needs a valid certificate before it can deliver a redirect. Check source-domain SSL coverage.
The redirect keeps returning to the source.
Review destination-side and application rules. Remove the conflicting rule rather than adding another redirect.

Watch the video

The video may show an older interface. Use the written instructions above when screen names differ.

Continue with a related task

Official documentation