A Two-Hop Redirect Chain Was Leaking 15% of Every Backlink

A B2B SaaS site came in for a backlink audit after rankings on competitive head terms had stalled. Their domain authority looked healthy on paper. The links were there. The pages they pointed at were strong. Something between the link and the page was bleeding equity.

Every external backlink was going through a two-hop redirect chain. The nginx layer redirected from www to non-www (hop one). Then the WordPress canonical handler added a second hop to enforce the trailing slash (hop two). Conservatively, that two-hop chain was leaking around 15% of the link equity from every inbound link. Google docs treat each redirect as a small dilution. Two hops compound.

Step one was a redirect trace. We pulled a sample of 20 high-authority backlinks and ran each one through a redirect tracer (curl -IL is enough). Every single one showed the same pattern.

GET https://www.example.com/page -> 301 https://example.com/page -> 301 https://example.com/page/ -> 200

Two redirects. Same root cause repeated across the entire link profile.

Step two was finding the source of each hop. The first redirect lived in the nginx server block (a www-to-apex rule that had been in place since launch). The second lived inside WordPress, where the canonical handler enforces trailing slashes on permalinks.

Step three was consolidating both decisions into the nginx layer. One rewrite rule went from www-without-slash directly to apex-with-slash, in a single 301.

Every external backlink now resolves in one hop instead of two. The conservative estimate of recovered link equity is around 15% per inbound link. On a site with hundreds of referring domains, that is a meaningful share of the link profile no longer being thrown away.

The fix took one nginx config change and a reload. No content moved, no URLs changed for users.

The Setup

A B2B SaaS company came in for a backlink audit. Their rankings on competitive head terms had stalled. Domain authority looked healthy on paper. The links were there. The pages those links pointed at were strong. Something between the inbound link and the live page was leaking value.

What We Found

Every external backlink to the site was going through a two-hop redirect chain.

GET https://www.example.com/page
  -> 301 https://example.com/page
  -> 301 https://example.com/page/
  -> 200 OK

Two hops, same root cause repeated across hundreds of referring domains. Google’s documentation treats each redirect as a small equity loss. Two redirects compound. Conservatively, that was around 15% of link equity bleeding off every single inbound link.

The Diagnostic

Three steps.

1. Redirect trace on a sample of high-authority backlinks. A simple curl -IL against twenty referring URLs. All twenty showed the same two-hop pattern.
2. Find the source of each hop. The first hop lived in the nginx server block as a long-standing www-to-apex rule. The second hop lived inside WordPress, where the canonical handler enforces the trailing slash on permalinks.
3. Decide where to consolidate. Doing the consolidation in nginx is faster, more reliable, and removes the WordPress hop entirely. One rewrite rule, evaluated before WordPress is even loaded.

The Fix

A single nginx rewrite that took both decisions in one hop. Configuration changed, nginx reloaded, every backlink in the profile now resolves in one redirect instead of two.

Outcome

Every external backlink now lands in a single hop. On a site with hundreds of referring domains, recovering an estimated 15% of equity per link is a meaningful chunk of the link profile no longer being discarded.

No URLs changed for users. No content moved. The fix lives entirely in server config.

Lessons

• Two redirects is one too many. Single-hop redirects pass nearly all the equity. Each additional hop is a small tax. The compounding adds up across an entire link profile.
• Backlink audits do not stop at the link. A clean backlink list is not a clean link profile. The path from the link to the live page is part of the audit.
• Decide redirect logic in one layer. When nginx and the application both apply canonical rules, you get chains. Pick one layer (almost always the web server) and let everything below it serve the canonical path directly.
• curl -IL is the cheapest tool in technical SEO. Twenty seconds against a referring URL surfaces problems no third-party crawler will catch in a default scan.

Brent’s Take

Long-standing infrastructure rules are the easiest place for equity leaks to hide. Nobody touches them because they have been there since launch. That is exactly why an outside audit catches them.