# How to fix redirect chains

> Each redirect adds a round trip before the page can load and leaks ranking signals along the way. Link straight to the final URL.

Technical SEO · HTML version: https://getreport.app/learn/redirects

## Redirects before the page

Passing looks like: No redirects before the page.

**Why it matters.** Every redirect is a full round trip before the browser can even ask for the page. http → https → www → trailing slash can easily add a second on mobile.

**How to fix it.**

1. Link straight to the final URL everywhere (menus, ads, social profiles).
2. Collapse chains: redirect http and non-www directly to the final https URL in one hop.

## Redirect chains

Passing looks like: The URL loads without a redirect chain.

**Why it matters.** Each redirect is a full round trip before the browser can start loading, often 100–300 ms on mobile. Search engines pass less value with every hop and stop following after a few.

**How to fix it.**

1. Point every old URL straight at the final one (a single 301), and update internal links to use the final URL directly.
2. Look for rules that stack, for example http → https, then non-www → www, then trailing slash; combine them into one rule.

## Links through redirects

Passing looks like: No link on the page goes through a redirect.

**Why it matters.** Every redirected link costs visitors an extra round trip and passes slightly less ranking signal. Linking to the final URL is free.

**How to fix it.**

1. Update each link listed in the technical detail to its final URL.
2. Search your templates and content for the old URLs after a domain, https or trailing-slash change.

Check your own page: https://getreport.app/