Redirects in cPanel vs .htaccess

cPanel redirects and .htaccess both control the same Apache rewrite layer on shared hosting. The Redirects tool in cPanel writes rules into .htaccess for you, so you should manage permanent and temporary moves in one place only. Adding the same hop in WordPress, a CDN, and the panel at once usually creates a loop.

How cPanel redirects work

On shared hosting you get cPanel with LiteSpeed and CloudLinux LVE, and you do not have root. Open cPanel, find Redirects, and choose a temporary 302 while you test or a permanent 301 when the move is final. Point the old path or domain at the new URL, keep www versus apex consistent, and send HTTP traffic to HTTPS in that same rule set. AutoSSL and Let’s Encrypt can handle certificates on the account, but they do not replace a clean redirect.

Browsers cache 301 responses, so start with 302 until you confirm the hop. After you are sure, change the type to 301. Same price at renewal applies to the hosting plan itself; redirects are just configuration on that account.

When .htaccess is the better edit

Advanced patterns sometimes need a direct .htaccess change in File Manager or over FTP. That file is still the same layer cPanel uses, so do not stack a panel redirect on top of hand-written rules for the same URL. Keep regex simple. A rule you do not fully understand can block /wp-admin or other paths you still need.

If the site runs WordPress, WP Toolkit can help with common account tasks, but site URL settings inside WordPress must match the final HTTPS address. A perfect server rewrite will not fix http:// links that still print in the HTML.

Prove one hop, then stop

Check the response headers before you call the job done. You want a single Location header and a clear 301 or 302, then a stop. Five hops from HTTP www through a plugin and a CDN to HTTPS apex is the bug, not a feature.

curl -sI http://example.com | head -n 20

Replace example.com with your hostname. Read the status line and the Location value. One hop is enough for users and for search engines. More 301s in a chain do not improve SEO; they only slow the first visit and hide mistakes.

1. Use a temporary 302 while you test, because browsers remember 301s.
2. Confirm the hop with curl and expect one hop, or two at most.
3. Switch the rule to 301 only when the destination is final.
4. Fix the WordPress site URL if pages still emit http:// links in the HTML.

Primary domain changes are a separate step

Changing the primary domain on the account is not a redirect strategy by itself. If you rebranded, an alias plus a single 301 is usually enough for visitors. Get the hop working first, then discuss renaming the account if you still need that later. Nameservers stay ns1.logicweb.com and ns2.logicweb.com unless you were told otherwise for DNS.

Pick the layer closest to the edge you control, keep www and HTTPS decisions in that one place, and leave the other tools alone. That is how cPanel redirects stay predictable next to .htaccess.