The simplest option is to send the detected chain and the exact preferred address to hosting support. An unnecessary step can often be removed in the hosting panel or by support at no additional cost.

Message for support

Hello,
The preferred website address is https://example.com/
The following unnecessary chain is present:
http://www.example.com/ → https://www.example.com/ → https://example.com/
Please configure one direct permanent 301 redirect from every additional
variant to the preferred address, without cycles or intermediate pages.

Technical notes

  1. Back up the configuration.
  2. Confirm the exact preferred address, including HTTPS and the correct WWW variant.
  3. Identify every layer that can add redirects: CDN, hosting panel, Nginx, Apache/.htaccess, CMS and plugins.
  4. Leave one responsible rule. Every additional variant should return the final preferred URL immediately.
  5. Use the server's configuration test before reloading it.
  6. Retest all four variants and representative old internal URLs.

Do not copy a rule without adapting it to the installed server. Nginx normally uses a dedicated server block, while Apache commonly uses a RewriteRule with R=301. Review the complete configuration so a second rule does not run after the first.

Use a temporary 302 while testing if the outcome is uncertain. Change it to a permanent 301 only after the entire route is verified.