Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Technical and performance
  3. Redirect Checker

Redirect Checker

Follow an address’s real journey, hop by hop, to its final destination.

Real redirect following, hop by hop, recording the HTTP code and the delay of every step. No usage limit.

What this tool is for

Between the address typed and the page displayed, more usually happens than people think. One address can cross four redirects before arriving: the move to HTTPS, the addition of www, normalisation of the trailing slash, then a migration rule.

None of that shows. The visitor lands on the right page, the browser displays the final address, and nobody suspects the three extra round trips — each costing its network latency, which is especially noticeable on mobile.

This tool unrolls the whole journey. It reveals the chains accumulated over the years, the 302s left where a 301 was called for, and the loops that make a page simply unreachable.

When it matters most: a migration. Checking every important old address before and after the switch is the only way to be sure the redirect plan does what it claims.

How to read the results

The number of hops is the first figure to look at. One hop is normal. Two are sometimes justified. Beyond that, there is nearly always a way to connect the origin straight to the destination.

The code of each step determines what is passed on. A 301 transfers the signal; a 302 transfers nothing and keeps the old address in the index. A 302 on a permanent migration should be fixed first.

The delay per hop measures the real cost. Every step adds a network round trip, easily a hundred milliseconds on mobile. Four hops is close to half a second lost before the page even starts loading.

The move from HTTP to HTTPS appears as a separate hop. It is normal, but it becomes pointless if your internal links already point at HTTPS: better to remove the step at source.

The final destination should always be checked. A chain ending at the home page instead of the expected page signals a rule that is too broad and is absorbing addresses it should not.

Common mistakes

Stacking rules without ever rereading them. Every migration adds its layer. After three rebuilds, some addresses cross five hops. A periodic review of the configuration file prevents that sedimentation.

Using a 302 out of caution. “We will see later whether it is permanent” is a common line of reasoning, and it is expensive: Google keeps the old address and passes nothing on. If the move is permanent, say so.

Redirecting en masse to the home page. Treated as a disguised error by Google, and disorienting for a visitor who was looking for a specific page. A plain 404 is better than a misleading redirect.

Forgetting to update the internal links. Redirecting is a dressing; fixing the link at source removes the hop. On well-used links, fix them at source.

Testing only the home page after a migration. It is the best-redirected page, almost always. Test a sample of deep pages: that is where the rules fail.

Going further

Frequently asked questions

What is the difference between 301 and 302?

A 301 announces a permanent move: Google transfers the signal from the old address to the new one and eventually deindexes the old. A 302 announces a temporary move: Google keeps the old address in its index and transfers nothing. Using a 302 for a permanent migration is the most expensive mistake in search.

How many chained redirects are acceptable?

One, ideally. Google follows up to about five hops, but every step costs load time and dilutes the signal. A chain of three redirects on a well-used link is pure waste: connect the origin straight to the final destination.

How do redirect chains form?

By accumulation. Moving to HTTPS adds a hop, the choice between www and non-www another, normalising the trailing slash a third, then a migration adds one more rule. Each decision is reasonable on its own; stacked, they produce four hops before the page is reached.

Does a redirect lose search equity?

Google has confirmed that a 301 redirect transfers the full signal, with no loss. What does cost is something else: the time added by each hop, and the risk of a chain breaking at an intermediate step. Do not fear the redirect, fear the stack.

What should I do about a redirect loop?

Fix it without delay: the page is entirely unreachable, to visitors and crawlers alike. The usual cause is a rule that fires on its own destination — typically an HTTPS rule and a www rule bouncing off each other. Check the order of the rules in your configuration.

Should deleted pages redirect to the home page?

No. Google treats those mass redirects as disguised errors and ignores them, while confusing your visitors. A deleted page with no equivalent should return a 404, or a 410 if the deletion is permanent. Redirect only to genuinely equivalent content.