cPanel Redirects: 7 Easy Steps to Redirect a URL
cPanel redirects send visitors from an existing web address to another page or domain. They are useful when you rename a page, move a website or replace outdated content with a relevant alternative.
For example, you could redirect:
https://example.com/old-guide/
to:
https://example.com/new-guide/
The visitor’s browser follows the redirect and displays the destination URL.
On This Page
- Choose between a 301 and 302 redirect
- Open cPanel Redirects
- Select the source address
- Enter the destination
- Choose the www behaviour
- Check whether you need a wildcard
- Save and test the redirect
1. Choose the Right Redirect Type
Before creating a redirect, decide whether the change is permanent or temporary.
| Type | Use it when | Search-engine signal |
|---|---|---|
| Permanent — 301 | A page or website has permanently moved | Signals that the destination should replace the old URL |
| Temporary — 302 | Visitors need a different destination for a limited time | Signals that the original URL should generally remain preferred |
Use a 301 redirect for a permanent page rename or domain migration. Choose 302 when you expect to restore the original address.
A redirect does not reliably rewrite visitors’ saved bookmarks. Its purpose is to handle requests for the old address and send them to the correct destination.
For more detail, see Google’s guidance on redirects.
2. Open cPanel Redirects
Sign in to cPanel and open:
Domains → Redirects
Select Permanent (301) or Temporary (302) from the Type menu.
If the Redirects tool is unavailable, ask your hosting provider whether it is enabled for your account.
3. Select the Source Domain and Path
Choose the domain receiving requests for the old address.
For a single page, enter its path in the adjacent field. For example:
Source domain: example.com
Source path: old-guide/
Choose the specific domain you intend to change. Avoid selecting All Public Domains unless the rule should apply to every public domain on the account.
For a whole-domain redirect, leave the path field empty and review the wildcard setting in step 6.
4. Enter the Full Destination URL
In Redirects to, enter the complete destination address, including the protocol:
https://example.com/new-guide/
Open this address before saving the redirect. Confirm that it loads correctly and is the page you want visitors to reach.
Use HTTPS where the destination supports it. Avoid sending visitors through an unnecessary intermediate address.
5. Choose the www Redirection Behaviour
Select the option that matches the addresses you want the rule to handle:
| Option | Behaviour |
|---|---|
| Only redirect with www. | Matches requests using the www hostname |
| Redirect with or without www. | Handles both hostname versions |
| Do Not Redirect www. | Excludes requests using www |
For a page move that should work from either hostname, Redirect with or without www. is usually the appropriate choice.
Test both versions afterwards. DNS, hosting configuration and existing rules can affect whether each hostname reaches the redirect.
6. Decide Whether to Enable Wild Card Redirect
A Wild Card Redirect preserves the matching path when sending visitors to another location.
For example, when moving a whole website:
Old address:
https://old.example.com/about.html
Destination:
https://new.example.com/about.html
Enable this only when the destination has a matching page structure.
If the new website uses different paths, create individual mappings instead:
/old-services.html → /services/
/contact-us.html → /contact/
A wildcard cannot work out which new page is the best replacement for each old page. Test representative pages and nested paths rather than checking only the homepage.
7. Save and Test Your cPanel Redirects
Click Add, then test the original address.
Check that:
- The redirect reaches the intended destination.
- The response uses the expected 301 or 302 status.
- Both required hostname versions work.
- The destination loads successfully.
- There is no redirect loop or unnecessary chain.
Use your browser’s developer tools to inspect the first document request in the Network panel.
If you have a terminal, this command displays the response headers for a normal GET request:
curl -sS -D - -o /dev/null https://example.com/old-guide/
Look for the status code and the Location header. Replace the example URL with your actual source address.
To inspect the sequence through to the destination:
curl -sS -L -D - -o /dev/null https://example.com/old-guide/
Test the exact addresses visitors use, including trailing slashes and query parameters where relevant.
Common Redirect Problems
The Old Page Still Loads
Try a fresh browser session and inspect the response headers.
Also check whether WordPress, another application or a CDN handles the request before the cPanel rule takes effect. Adding duplicate rules can make the behaviour harder to diagnose.
The Browser Reports Too Many Redirects
Two rules may be sending requests back to each other.
For example:
Page A → Page B
Page B → Page A
Conflicting HTTP/HTTPS or www/non-www rules can cause similar loops. Review all systems that manage redirects and remove the conflict.
The Destination Returns a 404 Error
Open the destination directly and check its spelling and path.
For wildcard rules, confirm that the same path exists on the destination website. If it does not, use a specific page-to-page redirect.
HTTPS Fails Before the Redirect Runs
The original HTTPS hostname needs a valid TLS setup so the browser can connect before receiving the redirect.
Redirecting to a secure destination does not fix a certificate error on the source hostname.
A WordPress Redirect Conflicts with cPanel
Decide which layer should manage the rule: WordPress, the web server or your CDN.
Check existing rules before adding another. For server-level configuration help, see How to Edit .htaccess File.
Redirects and SEO: Practical Checks
A useful redirect takes visitors to the closest relevant replacement.
- Map old pages to matching new pages. Avoid sending every removed URL to an unrelated homepage.
- Keep the route direct. Prefer old URL → final destination over several intermediate redirects.
- Update internal links. Link directly to the new address once the move is complete.
- Update your sitemap and canonical references where the permanent URL has changed.
- Monitor important old URLs. Check that they continue reaching the correct destination after future website changes.
If a deleted page has no suitable replacement, a helpful 404 page may be more appropriate. See Custom Error Pages in cPanel.
How to Change or Remove a cPanel Redirect
Find the rule in the Current Redirects table.
To change a redirect through this interface, record its settings, delete it and create the replacement. Test the source address again afterwards.
Removing a rule does not immediately clear a redirect already cached by a browser or another system.
The official cPanel Redirects documentation explains the available options.
Frequently Asked Questions
Can DNS Records Redirect a URL?
Standard A and CNAME records do not perform an HTTP page redirect. They help resolve a hostname to its destination.
A redirect requires a web server, application or forwarding service to respond to the request. For related guidance, see How to Change DNS Zones.
Should I Use cPanel Redirects to Force HTTPS?
For a straightforward HTTP-to-HTTPS change, cPanel provides Force HTTPS Redirect in its Domains interface.
Check that HTTPS works correctly before enabling it, and avoid conflicting rules elsewhere.
Should a Redirect Keep the Original URL Visible?
A normal HTTP redirect changes the address shown in the browser. Keeping the original address visible is a different requirement and should not be confused with a standard redirect.
Does a 301 Redirect Guarantee Better Rankings?
No. A permanent redirect helps search engines understand a move, but it does not guarantee rankings or an immediate search-result update.
Need Help Setting Up a Redirect?
Contact DigitalBerg support with the original URL, destination URL and whether the change is permanent or temporary.
Include any unexpected behaviour, such as a loop, certificate error or incorrect destination.






