SEO Tools·4 min read

Redirect Chains and SEO: Trace Every Hop of a URL

The link between redirect chains and SEO is simple to state and tedious to police: every extra hop between a link and its destination wastes crawl budget, adds delay, and gives signals another junction to leak at. Chains grow silently. A URL redirected during an HTTPS switch gets redirected again in a later restructure, and suddenly old backlinks travel three hops to arrive. Nobody decided that; it accumulated. This guide covers tracing a chain hop by hop, how much is too much, the redirects a trace can't see, and how to flatten what you find.

Open the free Redirect Checker All insights

How a redirect chain builds itself

Each hop made sense at the time.

Year one: the blog moves from http to https, so http://example.com/blog/seo-guide gains a 301 to its https twin. Year two: a restructure moves posts under /resources/, adding a second redirect. Year three: the guide is merged into a newer article, and a third one appears. Every individual decision was correct. The result is that a backlink earned in year one now passes three junctions before content loads.

Multiply by every URL that has ever moved and you get the usual state of a mature site: hundreds of quiet chains, none of them on any dashboard, all of them shaving a little off crawl efficiency and page speed. The only way to see them is to trace URLs and count.

Tracing redirect chains for SEO with the Redirect Checker

The whole path, laid flat.

Paste a URL into the Redirect Checker and click Trace redirects. If you leave off the scheme, it starts from http:// so you can see how your site upgrades plain requests. Our server requests the URL, reads each Location header and follows it for up to 10 hops. You get the final destination at the top, a list of verdicts marked pass, warning or problem, and the numbered chain below, each hop with its status code and a copy button for its URL.

The verdicts do the first read for you. A single redirect is marked as the ideal. Two or more in a row get a warning to point the first URL straight at the final one. Temporary 302 and 307 hops are flagged, as is a hop that only upgrades to HTTPS or only adds or removes www before another redirect. A URL appearing twice is a loop, and a chain that ends on 404 or 5xx is marked as a problem.

A worked trace: 301, then 302, then 200

Three hops, three findings.

Trace http://example.com/blog/seo-guide and the chain comes back as three rows. Hop 1: http://example.com/blog/seo-guide returns 301, forwarding to https. Hop 2: https://example.com/blog/seo-guide returns 302, forwarding to /resources/seo-guide/. Hop 3: https://example.com/resources/seo-guide/ returns 200.

The verdicts list the findings. Two redirects in a row, which should be one. One temporary redirect: the 302 at hop 2 is a permanent restructure with a temporary label, so search engines may hold onto the old URL. And HTTP to HTTPS takes its own hop before another redirect. The fix is one edit: point the original rule at the final https /resources/ address as a 301, then trace again to confirm the chain collapsed to a single 301 into a 200.

How many hops is too many

Budgets, not bans.

Google says Googlebot follows up to 10 redirect hops before reporting an error, so nothing breaks outright at three or four. The practical ceiling is far lower. Each hop is a full round trip before the page starts loading, and visitors on slow mobile connections feel every one of them.

There's also attrition: each junction is a place where a rule can later be edited, removed or pointed somewhere stale. The working standard is one hop from any retired URL to its final destination, two tolerated briefly mid-migration, and anything longer queued for flattening. If a chain reaches 10 hops without finishing, the checker stops and says so, because browsers and crawlers give up too.

Meta refresh and JavaScript redirects: the hops most traces miss

Same destination, worse mechanics.

Most checkers follow HTTP redirects only, the kind sent in a Location header. A meta refresh is an instruction inside the HTML, so the page returns 200 and the browser moves on afterwards. With its detection option ticked, the Redirect Checker reads that final page, finds a meta refresh or a simple window.location script, and follows it as an extra hop labeled as such. Scripts that build the address at run time still slip through, so a chain that stops at a 200 you know forwards people is the cue to read the page source.

Google treats an instant meta refresh roughly like a permanent redirect, but it's slower for users, invisible to plain HTTP tools, and flagged by accessibility guidelines. JavaScript redirects look the same from a trace's point of view. Whenever you control the server, a real 301 is the better choice.

Chain cleanup mistakes that make redirects worse

Good intentions, new hops.

Flattening chains is straightforward; these are the ways it goes wrong:

Fixing the final hop instead of the first: the deepest rule gets edited while the entry URL everyone links to still travels the whole chain.
Deleting an intermediate redirect outright, which gives every external link pointing at that middle URL a fresh 404.
Leaving a 302 in place for a move that's permanent, holding signals on a URL that will never come back.
Never tracing again after the edit, so a chain that still has two hops ships as finished.
Redirecting everything to the homepage during cleanup, which Google tends to treat as a soft 404 rather than a move.

Where the Redirect Checker stops and other tools start

Trace, fix, verify, in that order.

The Redirect Checker diagnoses paths; it doesn't repair them. On Apache, the repairs happen in rewrite rules, and the Htaccess Redirect Generator writes them with page redirects pointing straight at full URLs. Its Bulk tab traces up to 50 old URLs against their expected targets, and the HTTP Status Code Checker takes up to 100 at a time with CSV or Excel export. For expanding a short link from someone you don't trust, the URL Expander runs the same trace from our server with a simpler layout. And when the problem is two live URLs sharing content rather than a moved one, no redirect belongs there; the Canonical Tag Generator handles that case without taking either page offline.

Try it now

Open Redirect Checker

The tool is one click away. No sign up, no upload, no payment.

Open Redirect Checker

Write a review