Redirect Chain Checker: How to Trace 301/302 Redirects

A redirect chain checker traces every 301/302 hop a URL passes through before reaching its real destination. It tells you exactly how many hops there are, the status code at each step, and whether you're stuck in a loop. It's most useful right after a domain change, an HTTP-to-HTTPS migration, or a URL structure redesign — the moments when long redirect chains tend to sneak in unnoticed.

Why a URL ends up taking the scenic route

This usually isn't intentional. Say you move from shopabc.com to shop-abc.io, then a few months later restructure URLs from /products/item-name to /shop/item-name. If the old redirects never get cleaned up, an old link now has to hop through three stages: old domain → new domain → new URL structure. Three steps for one click, when a single hop would do.

301 vs 302 — picking the wrong one causes real headaches

301 means "permanent" and tells Google to transfer all the SEO value (backlinks, rankings) to the new page and drop the old one from the index. 302 means "temporary" — Google keeps the old page indexed because it assumes you'll switch back. A lot of sites default to 302, thanks to a plugin or CMS setting, for what is actually a permanent move — so Google ends up indexing both URLs and your rankings get diluted.

Every hop costs something

Each redirect adds a full HTTP round trip — anywhere from 100 to 300ms depending on server distance. That's not much for a human visitor, but for Googlebot crawling thousands of URLs against a limited crawl budget, every unnecessary redirect is time spent not discovering new content. Google has previously advised keeping redirect chains to no more than 2–3 hops.

Signs you should check right now

• Traffic dropped suddenly after a site migration or domain change.
• Search Console flags "Page with redirect" under Coverage.
• Pages load slowly for no obvious reason.
• You just installed a new redirect plugin (WordPress) or added an .htaccess rule.

Trace your chain in seconds

Paste a URL into the free Redirect Chain Checker — it shows every hop with its status code, flags loops, and checks whether the final destination matches its own canonical. Nothing to install.

Cleaning up a redirect chain

The simplest rule: every old URL should redirect directly to its final destination in one hop, never through another redirect. On WordPress, go into your redirect plugin and repoint every old rule straight at the latest URL instead of letting them stack over time. On a custom-coded site, fix it directly in your Nginx or .htaccess config.