Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Redirect a Specific Page or Directory with cPanel

Published

cPanel

Use cPanel Redirects to send an old hosted URL to an intended destination. Choose a narrow source and verify the actual response; do not redirect every domain on the account when only one page moved.

Add the intended rule

  1. Enter verified HTTPS cPanel and Domains > Redirects.
  2. Choose Permanent (301) for an actual permanent move or Temporary (302) for a temporary destination.
  3. Select the exact source domain and source path. Avoid All Public Domains unless that broad scope is specifically intended.
  4. Enter the complete destination URL, including scheme, and review the www matching option.
  5. Leave wildcard behavior off for an exact-page task. Enable it only when the intended corresponding-path mapping has been reviewed.
  6. Add the rule, inspect the saved entry and test before declaring success.

Understand www and wildcard scope

The options distinguish www-only, both www/non-www and non-www-only matching. They do not establish certificate coverage or automatically choose your application’s canonical host.

A wildcard redirect can map additional paths to corresponding destination paths. It is not proof that every intended page exists at the destination. Test representative nested paths and a nonmatching sibling; do not accidentally send unrelated missing pages to an irrelevant destination.

Verify HTTP and application behavior

Inspect status and Location, query handling, loops and existing application/CDN/HTTPS rules. HTTP and HTTPS source requests can behave differently; an HTTPS source needs a valid certificate before a redirect can be followed. Test logins, forms and APIs separately rather than assuming a GET check preserves every method/body.

301/302 communicate move intent but do not force a particular Google indexing or ranking outcome. A temporary redirect does not guarantee the destination cannot be indexed. During validation consider caching and retain rollback. Remove only the exact saved rule and verify the server response again; previously cached permanent redirects can persist.

References: cPanel Redirects and Google redirects and search.

Reviewed October 16, 2026. No customer redirect or application route was changed or tested.

Related guides

Account services are unavailable until the production backend is configured.