A domain redirect is a simple change with a big effect: it tells every visitor, browser, and search engine where your site has moved. Whether you are switching domains, sending an old product page to a new one, or forwarding a parked domain to your main website, learning how to redirect a domain in cPanel step by step helps prevent visitors from landing on dead pages.

The process is usually completed in a few minutes. The key is choosing the correct redirect type and checking that the destination page works before you rely on it.

Before You Create a Domain Redirect in cPanel

Have the full destination address ready, including https://. For example, use https://www.example.com/new-page/ rather than only www.example.com. A complete URL helps cPanel send visitors to the right secure version of the page.

Also confirm that the domain you want to redirect is connected to the cPanel account. If you recently registered the domain or changed its nameservers, DNS updates may still be in progress. A redirect rule can be correctly configured in cPanel, but it will not work for the public until the domain points to the hosting account.

If the destination is another website, make sure that site is live and has a valid SSL certificate. Sending visitors from a secure HTTPS address to an unsecured HTTP page can trigger browser warnings and reduce trust.

How to Redirect a Domain in cPanel Step by Step

1. Sign in to cPanel

Log in to your hosting account and open cPanel. Most hosting dashboards include a direct cPanel login button. Once inside, look for the Domains section.

Depending on your cPanel theme and version, the redirect tool may appear as Redirects or be available from the main Domains area. The name may vary slightly, but the settings work the same way.

2. Open the Redirects Tool

Select Redirects. You should see a form where you can choose a redirect type, select a domain, add an optional path, and enter the destination URL.

This is also where you can review redirects that already exist. Check this list before adding a new rule, especially if the domain was previously used for another website. Two redirects that conflict with each other can cause unexpected results.

3. Choose a Permanent or Temporary Redirect

At the top of the form, choose one of two redirect types: Permanent (301) or Temporary (302).

Use a 301 redirect when the move is intended to last. This is the right choice when an old domain has been replaced, a page has a new permanent address, or you want search engines to treat the new URL as the primary location. A 301 redirect also gives returning visitors a consistent path to the new site.

Use a 302 redirect when the change is short-term. For example, you might temporarily send visitors to a maintenance page, a seasonal promotion, or a testing version of a website. Search engines generally continue to associate the original URL with the content when a 302 is in place.

For most domain changes, a permanent 301 redirect is the practical choice. It avoids confusion for visitors and gives search engines a clearer signal about your new address.

4. Select the Domain You Want to Forward

Choose the source domain from the drop-down menu. This is the address visitors will type or click before being sent elsewhere.

If you want to redirect the entire domain, leave the path field blank. For example, selecting oldbusiness.com with no path means the rule applies to visitors arriving at the main domain.

If you only want to redirect one page or folder, enter that path in the available field. A path such as services can send visitors from oldbusiness.com/services to a different destination while leaving the rest of the site unchanged. This is useful when reorganizing a website without moving every page.

5. Enter the Destination URL

In the redirects-to field, enter the full destination URL. Include the protocol, such as https://, and check the spelling carefully.

For a full-domain redirect, the destination may look like this:

https://www.newbusiness.com/

For a page-level redirect, it may look like this:

https://www.newbusiness.com/contact/

Do not set a domain to redirect to itself. For example, redirecting www.example.com to https://www.example.com/ can create a redirect loop if the rule is not configured precisely. Browsers display these loops as an error, and visitors will not be able to reach the site.

6. Set the www Option

cPanel commonly provides options for how the redirect handles the www version of a domain. In most cases, choose the setting that redirects visitors whether they enter the domain with or without www.

That means both example.com and www.example.com will reach the same destination. It is the simplest option for small business websites because visitors do not have to remember which version of the address you use.

Use the more specific www options only when you have a reason to treat the two versions differently. Most website owners do not need separate behavior for them.

7. Decide Whether to Use Wild Card Redirects

A wild card redirect carries the rest of the original URL to the destination domain. This is especially helpful when you are moving a complete website and want individual pages to keep their paths.

For example, with a wild card redirect enabled, a visitor going to:

oldbusiness.com/blog/summer-offer

could be sent to:

newbusiness.com/blog/summer-offer

Without a wild card redirect, that same visitor may land only on the homepage of the new domain. That can be frustrating if the page they expected still exists at the new site.

Wild card redirects are not always the right option. Leave them off if every old page should go to one specific landing page, or if the page structure on the new site is different. Otherwise, visitors may reach pages that no longer exist and see a 404 error.

8. Create the Redirect and Test It

Click Add or Create to save the rule. cPanel should confirm that the redirect was added successfully.

Test the result in a private or incognito browser window. Check the domain with and without www, and test a few internal page URLs if you enabled wild cards. Private browsing helps you avoid misleading results caused by cached browser redirects.

Also test on a phone. A redirect should work consistently across desktop and mobile browsers, particularly if the destination uses HTTPS.

Common Redirect Problems and How to Fix Them

If the redirect does not work right away, start with the basics. DNS changes can take time to update across networks, particularly after a domain transfer or nameserver change. If the domain is new to the account, verify that it has been added correctly in cPanel.

A redirect loop usually means the source and destination overlap. This can happen when both the old and new domain point to the same site files or when another rule in .htaccess is already forcing a different URL. Remove duplicate rules and make sure the redirect points away from the source domain.

If visitors are sent to the homepage instead of the page they requested, review the wild card setting. Enable it only when the page paths should carry over to the new domain.

If the browser shows a security warning, verify that both the source and destination domains have active SSL certificates. A redirect does not replace the need for HTTPS. Visitors must be able to connect safely to the original domain before the browser can follow its redirect instruction.

When a cPanel Redirect Is Not the Best Choice

The cPanel Redirects tool is ideal for straightforward forwarding. However, it may not be enough when you need many page-by-page redirects, advanced conditional rules, or a website migration with a completely different URL structure.

For example, moving from an old ecommerce platform to a new one may require individual redirects for products, categories, and blog posts. In that case, a carefully managed .htaccess file, a website migration tool, or help from hosting support may be the better option. The goal is not simply to forward traffic, but to send each visitor to the closest relevant page.

A correctly configured redirect protects the work you have already put into your domain, content, and brand. Set it up carefully, test it from a visitor’s perspective, and keep the old domain active as long as people or search engines may still use it.