Home >Blog

How to Check a Redirect Chain in Chrome DevTools (Step by Step)

Published Updated

A redirect chain is easiest to check in Chrome DevTools when you can see the individual document requests, not just the final address in the browser bar. The goal is to answer four concrete questions: how many hops occurred, which status code each hop returned, where each Location header pointed, and whether the final response is the page you intended.

This browser workflow is useful after a domain move, HTTPS change, host canonicalization update, or CMS migration. It complements a dedicated redirect chain checker when you need to inspect one URL in the context of the browser request.

What you should see

  • A first document request for the URL you entered.
  • One or more 3xx responses with a Location header.
  • A final 200, 4xx, or 5xx response that explains where the chain ended.
  • The exact host, scheme, path, and query string at every hop.
  1. Open DevTools. Press F12 or choose More tools → Developer tools, then select the Network panel.
  2. Keep the request log clean. Click the clear icon, enable Preserve log only when you need navigation context, and tick Disable cache while DevTools is open.
  3. Start the navigation. Paste the URL into the address bar and press Enter, or use a hard reload while the Network panel is recording.
  4. Filter the document request. Use the Doc filter and select the first request for the page. A redirect chain can include several document rows, so do not stop at the last one.
  5. Read the response. In Headers, check the status code and the Location response header. Copy the target URL exactly, including scheme, host, path, and query string.
  6. Inspect the last hop. Select the final document request and confirm the status, response URL, content type, and page title. A successful final page does not erase a bad earlier hop.
Chrome DevTools style view showing connected HTTP redirect requests

How to read the chain

A normal migration often has one clear reason for the redirect: HTTP to HTTPS, an old host to a new host, or an obsolete path to its replacement. A long chain usually means those rules were layered over time. For example, an old URL may first move to a new host, then from HTTP to HTTPS, then from a legacy path to a current slug. Each hop can work alone while the combined path remains wasteful.

Pay attention to method-sensitive redirects when you are testing forms or API requests. Browser page navigation usually uses GET, so a chain that looks harmless in DevTools may not behave the same way for POST traffic. For page SEO checks, also watch for loops, alternating hostnames, and a final URL that differs from the canonical page.

A quick command-line cross-check

DevTools shows the browser view. A header-only request helps you confirm the server response directly:

curl -I https://example.com/old-page

Do not add -L when you want to inspect the first hop. Following redirects is useful for the final result, but it hides the intermediate response unless you ask for verbose output or inspect each target separately.

Questions people usually ask

Can DevTools show every redirect?
Select each document request and read its status and Location header before judging the chain.

What status codes usually appear in a chain?
Select each document request and read its status and Location header before judging the chain.

Is one redirect always a problem?
Select each document request and read its status and Location header before judging the chain.

How do I check the final response?
Select each document request and read its status and Location header before judging the chain.

Can a redirect chain slow a page down?
Select each document request and read its status and Location header before judging the chain.

Fix the rule at the earliest point you control, then repeat the same DevTools check with cache disabled. The cleanest result is usually one intentional hop followed by the final document.

FAQ

Can DevTools show every redirect?
It can show each request when the Network panel is open before the navigation starts. Cached responses can hide a request, so disable cache while DevTools is open when the result looks incomplete.
What status codes usually appear in a chain?
301 and 308 are permanent redirects; 302, 303, and 307 are temporary variants with different method behavior. Read the actual response instead of guessing from the final URL.
Is one redirect always a problem?
No. A single deliberate redirect is often fine. The debugging concern is an unnecessary sequence, a loop, or a hop that sends users through the wrong host or protocol.
How do I check the final response?
Select the last document request and confirm its status, URL, content type, and page title. The final page should be the one you meant to serve.
Can a redirect chain slow a page down?
Each extra hop adds another request before the browser can fetch the final document. The impact depends on network conditions, caching, and how many hops are involved.

Table of Contents

Information

  • Hits26
  • Published date2026/10/07

More Posts

Explore more articles from this section