HTTP Redirect Checker Guide

An HTTP redirect checker traces what happens between the URL a visitor requests and the page they actually land on. It reveals every hop in the chain, the exact status code at each step, and whether the final destination is the one you intended. This guide explains what a redirect checker reports, how to read the status codes, and how to fix the redirect problems that leak ranking signals and slow your site down.

What an HTTP redirect checker does

When your browser requests a URL, the server can answer with a redirect: a 3xx status code plus a Location header pointing somewhere else. The browser then requests that new location, and the process repeats until it receives a final response, usually a 200 (OK) or an error such as 404. A redirect checker automates that journey and shows you the whole path.

A typical report lists, for each hop, the requested URL, the HTTP status code, and the target URL. Reading it top to bottom tells you three things: whether redirects fire at all, whether each is the correct type, and how many hops it takes to reach the destination. That is exactly what you need to diagnose a migration, an http to https switch, or a stubborn ranking drop after a URL change.

The redirect status codes you will see

The 3xx family covers redirection. According to MDN, the ones that matter for SEO are:

• 301 Moved Permanently: the resource has permanently moved. Search engines pass ranking signals to the new URL and treat it as canonical.
• 302 Found: a temporary move. The original URL stays canonical, so signals are not consolidated to the target.
• 307 Temporary Redirect: like 302 but guarantees the HTTP method is preserved.
• 308 Permanent Redirect: like 301 but preserves the HTTP method, which matters for form submissions and APIs.

One subtle trap: when a user agent receives a 301 in response to a POST request, it may switch to GET for the follow-up request. MDN recommends using 308 instead when you need to preserve the method. For ordinary page moves, 301 remains the standard choice.

301 versus 302: the most important distinction

Google's guidance is explicit. As its documentation on redirects explains, Googlebot follows a permanent redirect and the indexing pipeline uses it as a signal that the target should be canonical. With a temporary redirect, Googlebot follows it but does not treat the target as canonical, so the original URL can stay indexed.

The practical rule is simple. If a page has moved for good, use 301 or 308 so the new URL inherits the old one's ranking strength. If you are running a short experiment, a seasonal page, or maintenance, use 302 or 307 so you do not permanently reassign signals. Using a 302 for a permanent move is one of the most common and costly redirect mistakes, because your new URL never fully inherits the authority of the old one.

How to read a redirect checker's output

When you run a check, work through the report with these questions:

1. How many hops are there? One is ideal. Two or more means a chain you should collapse.
2. Is each status code correct? Permanent moves should be 301 or 308, not 302.
3. Does the final URL match your canonical? The last stop should be the exact URL you want indexed, including the right protocol, host, and trailing slash.
4. Is the final status a 200? A chain that ends in a 404 or 500 is a broken redirect sending users and crawlers to a dead end.

Common problems and how to fix them

• Redirect chains. A redirects to B redirects to C. Update the first rule to point straight at C so there is a single hop. Chains waste crawl budget and add latency on every request.
• Redirect loops. A points to B and B points back to A, so the page never loads. Fix the conflicting rules, often a clash between your CMS, a plugin, and a server config.
• Wrong redirect type. Swap any 302 that should be a 301 for a permanent move so signals consolidate.
• Mixed protocol or host. Make sure every URL resolves to a single canonical version, for example forcing https and one preferred host, in one hop.
• Redirects that end in an error. Point the rule at a live, relevant page instead of a missing one.

After a bulk migration, recheck a sample of your most important URLs. A redirect that works for the homepage can still be broken for deep pages, which is how a broken link problem creeps in unnoticed.

Free tools that check redirects

You do not need to buy anything to trace a redirect. Reliable free options include:

• Your browser's DevTools Network tab, which records every request including each redirect and its status code as you load a page.
• Free web-based redirect tracers that let you paste a URL and see the full hop chain in your browser.
• The command line, where curl -I or curl -IL shows response headers and follows redirects so you can read each status code.
• Google Search Console, whose page indexing report flags redirect issues that are affecting how Google indexes your URLs.

For a marketer-friendly walkthrough of destination checking and link safety, see our companion guide on how to check URL redirection. To audit redirects across a whole site at once, a crawler like the one covered in our Screaming Frog review lists every hop for every URL. Redirect hygiene is a core part of ongoing technical SEO, and a general URL checker helps you confirm a single address resolves cleanly.

Frequently asked questions

What is an HTTP redirect checker?

It is a tool that requests a URL and follows each 3xx redirect response until it reaches a final status code, then lists every hop along the way. It shows you the status code and target at each step so you can confirm redirects fire correctly and land on the intended page.

What is the difference between a 301 and a 302 redirect?

A 301 is a permanent redirect: search engines pass ranking signals to the new URL and treat it as canonical. A 302 is temporary: the original URL stays canonical and signals are not consolidated. Use 301 for permanent moves and reserve 302 for genuinely temporary changes.

Are redirect chains bad for SEO?

Yes. A chain of multiple redirects wastes crawl budget and adds latency for every visitor and crawler. It is best to redirect in a single hop straight to the final destination. If you find a chain, update the first rule to point directly at the final URL.

When should I use a 308 instead of a 301?

Use a 308 when you need to preserve the HTTP method, such as a POST request to a form or API endpoint. A 301 may cause some clients to switch a POST to a GET on the follow-up request, whereas a 308 keeps the original method. For ordinary page moves, a 301 is fine.

Can I check redirects for free?

Yes. Your browser's DevTools Network tab records every redirect and status code, free web-based tracers show the full hop chain, and the command-line tool curl with the -I or -IL options prints response headers and follows redirects. Google Search Console also flags redirect issues affecting indexing.

What redirect type does Google recommend?

Google recommends a permanent server-side redirect whenever possible for URLs that have changed for good, because it is the clearest signal to consolidate to the new URL. Meta refresh and JavaScript redirects are supported but weaker fallbacks, so use a server-side rule first.