Redirect Checker

Traffsite's redirect checker asks for a URL without following the redirect automatically. It reads the reply, then repeats the request at each new location until it reaches a final page. The result is a list of hops, and each hop shows the URL and its status code.

Redirects can be set at the server, in a CDN rule, with a meta refresh tag or through JavaScript. Server-side redirects are the most reliable because they arrive before the page starts to load.

Common redirect codes and what they mean

• 301 Moved Permanently. The page has a new home, and the move is meant to last.
• 302 Found. The move is temporary, and it often shows up in campaigns or short-term changes.
• 303 See Other. The reply points to a different page, usually after a form is sent.
• 307 Temporary Redirect. This is a temporary move that keeps the original request method.
• 308 Permanent Redirect. This is a permanent move that also keeps the request method.

Redirects hide in more places than most site owners expect. Traffsite's URL redirect checker is handy in all of these situations.

• Moving to a new domain. Every old address needs to point at the matching new page, and the tool shows which ones do.
• Switching from HTTP to HTTPS. You want one clean hop, not a chain of three.
• Choosing www or non-www. The version you do not use should always redirect to the one you do.
• Changing a page slug. The old URL should land on the new one without any detours.
• Retiring a product. A close replacement beats a 404 for visitors and for search engines.
• Reviewing campaign, affiliate and partner links. You can see where traffic goes before you send it.
• Auditing a site after a platform move. Old rules often point at the wrong place, and a scan makes them easy to spot.

Every case shares one goal. Visitors and crawlers should reach a live page in as few steps as possible.

Google follows redirects when it crawls, but it does not treat them all the same way. A 301 or 308 is a strong sign that the destination should be the canonical page. A 302, 303 or 307 is a weak sign. Google ignores the content at the redirecting URL and processes the final target instead.

That has real effects.

• Permanent redirects help move signals from an old URL onto its replacement.
• Temporary redirects keep the original URL in play, so use them only when the change really is temporary.
• Chains add delay. Google follows up to 10 hops by default, and a longer chain can end in an error.
• Loops never reach a page, so visitors and crawlers both hit a dead end.
• A redirect to an unrelated page, such as the home page, gives visitors a weak answer and gives search engines little reason to treat it as a replacement.

Redirect chains and loops explained

A chain happens when one URL sends visitors to a second URL, which sends them on to a third. An old HTTP address might jump to HTTPS, then to the non-www version, then to a new slug. Each step works on its own, so the page still loads in a browser. That is why chains stay hidden until you trace them. Point the first URL straight at the final page in one move.

The path sends a visitor back to a URL they already saw, so no page ever loads. Loops usually come from two rules that undo each other, and the trace shows exactly where the circle starts.

The aim is a clean path from every old address to the right new one. In practice, that means one hop, the correct status code and a final page that returns 200. A consistent host and protocol setup gives every page one preferred address. Rerun the check after the fix to confirm the chain is gone.

The tool does not decide your strategy. It shows what your server does right now, which is the first step toward matching the plan.

• It makes hidden rules visible. You see the status code and destination at every step.
• It catches what a browser hides. A page can load fine and still take four hops to get there.
• It gives developers a precise ticket. A failing hop and its status code are easier to fix than a vague report about a broken link.
• It backs up canonical decisions. A clean permanent redirect is a strong canonical signal, and the trace confirms it points at the right URL.
• It protects paid and earned traffic. An ad or partner link that passes through three redirects may still work, but the delay and the risk are easy to avoid.
• It speeds up diagnosis. When a ranking page starts to slip, you can rule redirects in or out fast.

Checking a 301 redirect, or any other kind, takes a minute.

1. Paste the URL you want to test, including the https part.
2. Start the check and let the tool follow the chain to the final page.
3. Read the hops in order, and note the status code at each step and the final URL.
4. Compare the result with the destination you planned. A permanent move should use 301 or 308 and land on a relevant page, while a temporary move should use 302, 303 or 307.
5. Fix the rule at the server, CDN or platform level. Remove extra hops, break any loops and point the original URL straight at the final target.
6. Run the redirect checker again to confirm the chain is one hop and the final page returns 200.

Anyone who changes URLs or inherits a site with a long history will find this Traffsite tool useful.

• SEO specialists use it during migrations, domain moves and canonical reviews.
• Developers use it to test server and CDN rules after a release.
• Site owners use it when an old link stops working or a campaign URL misbehaves.
• Marketers use it to confirm that paid and email links reach the right landing page.
• Agencies use it to audit a new client site before they touch anything.

You do not need server access to read the results. You only need it when it is time to apply the fix.