YettyOpen Beta
Free tool

Redirect chain
visualizer

Trace a real URL and watch every redirect hop happen - status codes, 301 vs 302, loops - or paste your redirect rules and see every chain drawn hop by hop, with a copy-ready fix list that collapses each chain to one direct hop. We fetch your URL securely - nothing else leaves your browser.

Free, no signup We fetch your URL securely - nothing else leaves your browser Finds chains, loops and forks
Map your redirects

Trace a URL. See every hop.

Or paste redirect rules manually

Both formats work, one rule per line: /old -> /new   or   301 /old /new. Lines starting with # are ignored.

100% private - your rules never leave your browser.

Every chain, hop by hop

Want redirects handled for you?

When you move or rename a page on Yetty, the old address is redirected for you - one clean hop, never a chain.

What it catches

Four ways redirects
quietly go wrong

Multi-hop chains

A to B to C. Each extra hop adds latency and leaks a little link equity. Point A straight at C.

Loops

A chain that circles back to itself. Browsers give up, the page dies. We show you the exact cycle.

Forks

The same source redirected twice to different places. Only one rule wins - usually not the one you meant.

Mid-chain targets

A redirect target that is itself redirected - the telltale sign a chain is forming under your feet.

Speed cost

Every hop is a full round trip before the page even starts loading. Chains are invisible slowness.

The fix list

Every chain rewritten as one direct rule, ready to paste back into your config.

Good to know

Redirect questions,
answered simply

How many redirect hops are too many?

One hop is fine - that is what a redirect is for. Two or more hops in a row start to hurt: each extra hop adds latency, and search engines pass slightly less link equity through long chains. Google says it follows up to 10 hops, but best practice is to point every old URL straight at its final destination in a single hop.

Do redirect chains hurt SEO?

Yes, in two ways. Long chains slow the page down for visitors and crawlers, and every hop can leak a little ranking signal. A redirect loop is worse - the page becomes unreachable and eventually drops out of the index. Collapsing chains to one direct 301 is one of the cheapest technical SEO wins there is.

What is a redirect loop and how do I fix one?

A loop is when a chain of redirects eventually points back to a URL already in the chain - A to B to A. Browsers give up with a "too many redirects" error and the page is dead. Fix it by deciding which URL is the real destination, pointing every other rule straight at it, and deleting the rule that closes the circle.

More free tools: the full toolbox · internal link graph · meta robots decoder · how Yetty handles SEO for you

Sua vez

Traga o site que você já tem.

Or never write a redirect again.

On Yetty, moved and renamed pages get one clean redirect automatically - chains never get a chance to form.