A redirect automatically sends visitors from an existing web address to another one. This is useful when moving a website to a new domain or changing individual page addresses.
This guide explains how to create, test and remove redirects.
Who is this guide for?
This guide applies exclusively to customers whose hosting is managed on the new Webland platform (WHMCS) and whose hosting plan includes cPanel.
Essential Hosting without cPanel: This guide does not apply to your hosting.
Previous platform using System Configurator or Domain Manager: Sign in at classic.webland.ch. The steps below do not apply to that platform.
Important information
The original domain must continue pointing to the hosting where the redirect is configured.
If visitors access the original address over HTTPS, that address also needs a valid SSL certificate.
Existing redirects cannot be edited directly in this cPanel feature. Delete the relevant rule and create it again.
To redirect HTTP to HTTPS only, use “Force HTTPS Redirect” under “Domains”, provided the feature is available and a valid certificate is configured.
Browsers may cache redirects, which can affect testing after changes.
Requirements
Before you begin, make sure you:
Have access to your cPanel hosting service.
Have the original domain configured in this hosting account.
Know the original address and complete destination address.
Have checked that the destination page is accessible.
Step 1: Sign in to cPanel
Find your hosting service in the active services overview in the client area.
Click “Log in to cPanel”.
You will be signed in to cPanel automatically.
Step 2: Open Redirects
Open the “Domains” section in cPanel and click “Redirects”.
Step 3: Select the redirect type
Under “Type”, choose the appropriate option:
Type | Use |
Permanent (301) | The page or website has moved permanently. |
Temporary (302) | The redirect is temporary and will be removed later. |
A 301 redirect signals a permanent address change to search engines. A 302 redirect indicates a temporary move. Neither guarantees unchanged search rankings.
Step 4: Set the original address and destination
Select the domain you want to redirect from.
Enter the relevant page or directory path in the field after the domain. For
example.com/blog/article.html, enterblog/article.html.Leave the path field empty if the rule should apply to the domain without restricting it to a particular path.
Under “Redirects to”, enter the complete destination address, such as
https://example.org/new-page.
Important: The destination must include the protocol, such as https://.
The system creates the redirect and adds it to the list of current redirects:
Step 7: Test the redirect
The rule appears under “Current Redirects”.
Open the original address in a private browser window.
Check that you reach the correct destination.
Test both www variants where applicable.
For a wildcard redirect, also test several subpages.
Change or delete a redirect
Find the rule under “Current Redirects”.
Click “Delete” under “Actions”.
Confirm deletion.
If needed, create a new rule with the required settings.
Troubleshooting
The redirect does not work
Check the domain, original path, destination and DNS configuration. Also check that the selected www option matches the address you are testing.
The browser still uses an old redirect
Clear your browser cache or test with another browser or a new private window.
The browser reports “Too many redirects”
Check for conflicting rules or a destination that redirects back to the original address. Include CMS redirects and HTTPS settings in your checks.
WordPress or another CMS ignores the rule
CMS or .htaccess rules may take priority. Ask your website developer to review the rule order or configure the redirect through the appropriate CMS feature.