Domain redirection automatically sends visitors from one domain to another, useful for rebranding, multiple domains, or temporary changes.
Types of redirects
301 Redirect (Permanent)
- SEO-friendly: Passes ranking power to new domain
- Browser caching: Browsers remember the redirect
- Best for: Permanent moves, rebranding, domain consolidation
- HTTP status: 301 Moved Permanently
302 Redirect (Temporary)
- Temporary solution: Indicates change is not permanent
- No SEO transfer: Search engines don't transfer ranking
- Best for: Maintenance, testing, short-term changes
- HTTP status: 302 Found
Setting up redirects in cPanel
Step 1: Access Redirects
- Log in to your cPanel
- Navigate to the Domains section
- Click on Redirects
Step 2: Configure redirect
- Select redirect type:
- Permanent (301) - for permanent moves
- Temporary (302) - for temporary changes
- Choose the domain to redirect from the dropdown
- Leave the path field empty for full domain redirect
- Enter the destination URL in the "Redirects to" field
Step 3: Additional options
- Wild Card Redirect: Check to redirect all subdirectories
- www redirection: Check to redirect www version too
Step 4: Apply redirect
- Click Add to create the redirect
- Test the redirect by visiting your domain
- Verify the redirect works with different browsers
Common redirect scenarios
Full domain redirect
Redirect entire domain to another domain:
- From: olddomain.com
- To: https://newdomain.com
- Type: Permanent (301)
- Wild Card: Enabled
Subdomain redirect
Redirect subdomain to main domain:
- From: blog.example.com
- To: https://example.com/blog
- Type: Permanent (301)
HTTPS redirect
Force HTTPS for security:
- From: http://example.com
- To: https://example.com
- Type: Permanent (301)
- Wild Card: Enabled
Using .htaccess for redirects
Full domain redirect
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?olddomain\.com$ [NC]
RewriteRule ^(.*)$ https://newdomain.com/$1 [R=301,L]
HTTPS redirect
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Specific page redirect
Redirect 301 /old-page.html https://example.com/new-page.html
DNS-level redirects
Using CNAME records
- Access your DNS management panel
- Create a CNAME record pointing to destination domain
- Set TTL to appropriate value (300-3600 seconds)
- Save and wait for propagation
URL forwarding service
- Enable URL forwarding in domain settings
- Choose forwarding type (frame or redirect)
- Enter destination URL
- Apply settings and test
Testing your redirects
Browser testing
- Clear browser cache and cookies
- Visit the original domain
- Verify it redirects to the correct destination
- Test with different browsers
Online tools
- HTTP status checkers: Verify redirect code (301/302)
- Redirect trace tools: Follow redirect chain
- SEO tools: Check redirect impact
Best practices
SEO considerations
- Use 301 redirects: For permanent moves to preserve SEO
- Avoid redirect chains: Don't redirect to another redirect
- Update internal links: Point directly to new URLs
- Monitor traffic: Watch for any issues after redirect
Performance tips
- Minimize redirects: Each redirect adds load time
- Use server-level redirects: Faster than JavaScript redirects
- Set appropriate TTL: Balance caching with flexibility
Managing redirects
Viewing existing redirects
- Return to cPanel Redirects section
- View list of current redirects
- Note redirect type and destination
Modifying redirects
- Click Edit next to the redirect
- Update destination URL or redirect type
- Save changes and test
Removing redirects
- Click Delete next to the redirect
- Confirm deletion
- Test that redirect no longer works
Important: Test redirects thoroughly before making them live to avoid broken links or SEO issues.
Tip: Use 301 redirects for permanent moves to maintain search engine rankings and avoid duplicate content issues.