Warning

Visitors pass through several redirects

The short version

Redirect straight to the final address in one hop.

What it means

At least one entry point passes through more than two redirects before it reaches a page, for example http://example.com/ to https://example.com/ to https://www.example.com/ to https://www.example.com/en/. The detail names the entry points with long chains.

Why it matters

Every redirect is another round trip, often a new connection and a new TLS handshake, so a long chain adds noticeable delay on mobile networks before anything appears. Search engines follow a limited number of hops, and each hop is another place for a mistake such as a downgrade or a loop.

How to fix it

  1. Write down your final address, including any language path.
  2. Change each redirect to point straight at it instead of at the next step.
  3. Combine rules: one rule can switch scheme and host at once, for example return 301 https://www.example.com$request_uri; in the plain HTTP server block of Nginx.
  4. Make sure the application doesn't add its own redirect on top, such as a trailing slash.

Check it worked

Run the HTTP and security headers check again. Each entry point should reach the page in at most two redirects, and the finding should be gone.