How to Fix a Double Redirect

Reduce every chain to one direct redirect to the established primary website version.

Order
the fix

Do it
yourself

Check
manually

Safe chain reduction

Find every redirect layer and leave one responsible rule

The easiest route is to send the exact chain and preferred URL to hosting support. An unnecessary hop can often be removed in the panel or by support without editing the server yourself.

CDN, server and CMS rules are consolidated into one direct redirect with backup and testing — Review CDN, panel, web server and CMS together because a second rule often runs after the first.

Message for support

Hello,
The preferred URL is https://example.com/
This chain was found:
http://www.example.com/ →
https://www.example.com/ → https://example.com/
Please configure one direct permanent 301
from every variant to the preferred address.

Technical sequence

Inspect CDN, hosting panel, Nginx, Apache/.htaccess, CMS and plugins.
Identify which rules change HTTP/HTTPS, WWW and old paths.
Use temporary 302 responses while the outcome is unconfirmed.
Point every source directly to its final URL while preserving paths and parameters.
Run the server's configuration test and reload.
After full testing, replace temporary responses with 301 or 308.

What to retest

Checks after the change
URL	Expected	Problem
Preferred hostname	200 without redirect	Any unnecessary 3xx
Alternative variant	One 301/308	Two or more 3xx responses
Old internal page	Corresponding new page	Unnecessary home-page redirect
Query parameters	Preserved where required	Lost parameters

Do not copy a rule without adapting it

Nginx often uses a dedicated server block, while Apache uses RewriteRule. Review the complete configuration and exclude loops.

Finish with a manual chain check.

An Automatic check is available at the top of this page. You can independently confirm its result using the manual verification instructions, then fix the issue yourself or order a professional fix.