A redirect tells browsers and other HTTP clients where a page has moved. Choose the source scope carefully: a rule for one retired page is different from a rule that sends every URL on the domain elsewhere.
IN THIS ARTICLE
Check access and requirements
Write down the old URL, the intended destination and whether the move is temporary or permanent. Back up .htaccess if the site uses it. Check for existing application, web-server and CDN redirects so you do not create a conflicting chain.
01 Create a page or domain redirect in cPanel
- Open Redirects and select the source domain. Enter a specific source path if only one page or directory should move.
- Choose the appropriate redirect type, commonly temporary
302for a temporary change or permanent301for a settled move. Permanent responses can be cached by browsers and other systems. - Enter the full destination URL including its scheme. Choose the www behaviour and wildcard option according to whether incoming paths should be preserved.
- Save the rule and test the exact source URL. Also test an unrelated page to confirm the rule is not broader than intended.
- Check the destination’s own redirects and content before treating the migration as complete.
02 Example: move one page without redirecting the whole website
Suppose https://example.com/old-contact should move to https://example.com/contact. Select example.com as the source and enter only the intended old-page path in the source-path field. Use the complete new URL as the destination.
Test the old contact URL and confirm its final destination. Then open an unrelated URL such as https://example.com/about and confirm it still serves its own page. This second check catches a rule whose scope is broader than the page you intended to move.
Confirm the expected result
Inspect the response status and final URL with browser developer tools or an authorised HTTP client. Verify that query parameters and paths behave as the application requires.
How do I fix a redirect loop after adding a cPanel redirect?
A loop usually means two layers disagree about the canonical URL or HTTPS mode. Remove the newest rule, restore the previous configuration and test one layer at a time. If a deleted redirect appears to persist, use a fresh client to distinguish browser cache from an active server rule.