Redirects and URL Normalization: One Address per Page
Collapse http, https, www and non-www into one address. How redirect chains and loops form, what they cost, and how to fix them at the edge.
Every site has 4 default front doors: http and https, with and without www. A visitor or a crawler can arrive at any of them. Normalization collapses those into the canonical address reached in a direct 301 hop, so link equity, analytics and cookies all land in the same place. Redirect problems compound rather than announce themselves. A chain forms when an old rule and a new rule both fire, turning a request into 3 hops. Each hop costs latency and dilutes the signal, and crawlers abandon long chains. A loop forms when 2 rules disagree about the canonical form, appending a trailing slash on the way in and stripping it on the way out, and the page becomes unreachable for everyone, including the crawler that would have reported it. Redirects also carry a security dimension. An http URL that stays on http leaves a plaintext hop where a response can be modified in transit, and it splits the site into 2 addresses in the eyes of search engines. The checks below follow every hop from the outside, the way a crawler does, and report the full path rather than only the destination. Fix the rules at the edge, in a central place, so a new redirect replaces the old ones instead of stacking on top of them.
HTTP to HTTPS redirect missing
Why it matters
When domain variants do not resolve cleanly, search systems can encounter separate crawl and canonicalization paths for the same destination.
How we check it
The redirect chain from HTTP to HTTPS was traced.
How to fix it
Configure your server or CDN to redirect all HTTP requests to HTTPS with a 301 status code.
Alternate host not normalized
How we check it
Domain variants (www vs non-www) were tested for clean resolution.
How to fix it
Pick a single canonical domain and redirect the alternate hostname to it with a 301.
Redirect chain detected
Why it matters
Redirect chains and loops slow visitors down and dilute the signals search engines pass between URLs.
How we check it
Redirect chains were traced through every hop.
How to fix it
Update redirects to point directly to the final destination URL instead of chaining. Why this matters: Each redirect hop wastes crawl budget, slows page load, and dilutes link equity—Google may stop following long chains before reaching your content.
Redirect loop detected
How we check it
URL paths were tested for circular redirect patterns.
How to fix it
Fix the circular redirect chain where URL A → B → A. Redirect to a final stable URL. Why this matters: Redirect loops make pages completely inaccessible to both users and crawlers, effectively removing them from search results until fixed.
Domain hands traffic to a different website
Why it matters
Every visitor and every ranking signal that reaches this entry point is handed to a different website — often an old copy of the site that competes with the real one in search results.
How we check it
The audited domain and its www/non-www sibling were followed through their redirects, and each destination host was compared against the audited domain.
How to fix it
Point the redirect at your real site with a 301 and decommission the old destination so it stops serving a copy of your content. If this is an intentional migration, audit the destination domain instead.
See How Your Site Ranks
Get a free AI-powered SEO report with actionable findings and priority fixes for your website.
No signup required.