Redirect checker
Follow a URL's full redirect chain and see every hop and status code (watch for chains and 302s that should be 301s).
Run a full graded audit for the whole site.
Follow a URL's full redirect chain and see every hop and status code (watch for chains and 302s that should be 301s).
A redirect checker traces a URL's complete path and displays every redirect hop, status code, and final destination. It instantly reveals where a link goes, whether redirects are broken or looping, and what HTTP status codes are returned at each step—essential for site migrations, link audits, and SEO health checks.
A redirect is an HTTP response that instructs a browser to navigate from one URL to another. When a user requests a URL, the server responds with a status code (like 301 or 302) and a Location header pointing to the new URL. The browser then makes a new request to that destination. This chain can continue through multiple hops if the destination URL also redirects.
Websites implement redirects for many reasons. A page might be moved to a new URL, requiring a redirect from the old path. A site might migrate to a new domain entirely, redirecting the old domain to the new one. HTTPS upgrades often use redirects to send HTTP traffic to HTTPS. URL structures change when sites reorganize content, and the old paths redirect to new locations. Sometimes two sites merge, and one domain redirects to the other.
Redirect chains—multiple redirects in sequence—form when redirects point to other redirects. For example, a URL might redirect to a second URL, which redirects to a third, before the browser reaches the final destination. Short URL services also create redirects: a tiny link expands to a medium URL, which redirects to the final page. Each hop adds a small delay and an HTTP request.
Checking redirects is essential in several situations. During a site migration, you must verify that old URLs redirect to their correct new locations without loops or breaks. If any redirect points to a non-existent page (404), visitors and search engines will never reach the final destination. A broken redirect chain stops the journey entirely.
Content audits often involve checking external links, affiliate links, and shortened URLs. An affiliate link might redirect through multiple services to reach the merchant, and a broken redirect costs you traffic and commission. Shortened URLs (tiny links) mask their final destination; checking them reveals where they actually lead.
Performance audits require checking for unnecessary redirect chains. Each redirect adds latency—users experience a perceptible delay, and Core Web Vitals metrics can suffer. SEO teams check redirects to ensure proper status codes (301 for permanent moves) are used, preserving link equity and ranking signals.
HTTP status codes in the 3xx range indicate a redirect. The specific code matters for both user experience and search engine behavior. A redirect checker displays the exact status code at each hop, allowing you to verify that the correct type of redirect is in place.
| Status Code | Type | Meaning | Use Case |
|---|---|---|---|
| 301 | Permanent Redirect | The page has permanently moved. Search engines transfer ranking signals to the new URL. | Use for permanent URL changes, domain migrations, HTTPS upgrades. |
| 302 | Temporary Redirect | The page has temporarily moved. Browsers may cache; search engines may not follow or may treat it as permanent. | Use for brief maintenance; avoid for permanent moves to preserve SEO signals. |
| 303 | See Other | Redirect after a form submission. Changes POST request to GET. | Use after form processing to prevent re-submission. |
| 307 | Temporary Redirect | Like 302, but keeps the original request method (POST stays POST). HTTP/1.1 compliant. | Use for temporary redirects when request method must be preserved. |
| 308 | Permanent Redirect | Like 301, but keeps the original request method. Newer standard. | Use for permanent redirects when POST/PUT requests must stay POST/PUT. |
| 4xx | Client Error | The redirect destination does not exist or is forbidden (404 Not Found, 403 Forbidden). | Indicates broken redirect; destination URL must be fixed or removed. |
| 5xx | Server Error | The server encountered an error during redirect (500 Internal Server Error, 503 Service Unavailable). | Indicates temporary server issue; the redirect may work when server recovers. |
For SEO purposes, 301 redirects are preferred for permanent moves because they pass link equity (PageRank) to the new URL. A 302 redirect may be treated as temporary, and search engines might not consolidate ranking signals. For permanent domain migrations or URL structure changes, use 301.
Redirect chains directly impact both search engine performance and user experience. When a search engine crawls a link that redirects multiple times, it consumes crawl budget following each hop. The engine must make multiple requests to reach the final page, which is inefficient. If the engine has limited time to crawl your site, redirect chains delay the discovery of new content.
From an SEO perspective, each redirect in a chain dilutes link equity. When page A links to page B which redirects to page C, the link signal passes to B first, then to C—but with some loss at each step. Google recommends keeping redirect chains to one hop or eliminating them entirely. A long chain may not pass full ranking signals to the final destination.
User-facing performance also suffers. Each redirect is an extra HTTP request, adding latency. On slow connections, a three-hop redirect chain can feel noticeable—the page loads slower. This impacts Core Web Vitals metrics, particularly Time to First Byte (TTFB) and Largest Contentful Paint (LCP). Performance-focused users expect fast loads, and redirect delays degrade experience.
Broken redirects create a worst-case scenario. If a redirect chain ends at a 404 error, the user and search engine never reach the intended page. The page may be delisted from search results. An affiliate link that breaks stops generating commission entirely. Always verify that redirect chains end at a valid, accessible page.
Using this redirect checker is straightforward. Simply enter the URL you want to check and the tool will trace its complete path, showing you every hop and status code.
The results are instant and require no login or account. Each check is independent, so you can test as many URLs as you need.
Redirect checkers often reveal problems that need fixing. Knowing what to look for and how to address each issue ensures your links work correctly and preserve SEO value.
| Problem | Cause | How to Fix |
|---|---|---|
| Redirect chain (A→B→C→D) | Multiple migrations or outdated redirects pointing to other redirects | Update the first redirect to point directly to the final destination (A→D). Remove intermediate redirects. |
| Wrong status code (302 instead of 301) | Site uses temporary redirect for permanent move, or 307/308 for wrong reason | For permanent moves, use 301. For temporary situations only, use 302/307. Check your server config or CMS settings. |
| Broken redirect (ends at 404) | Destination URL was deleted or moved again, and redirect was not updated | Update redirect to point to the correct current URL, or remove redirect and restore the page. |
| Redirect loop (A→B→A) | Redirect points back to itself or creates a cycle | Check the destination URL carefully for typos or logical errors. Break the loop by pointing to a different URL. |
| Mixed HTTP/HTTPS or www/non-www | Inconsistent handling of protocol or subdomain during redirects | Standardize first: choose http or https, choose www or non-www, then redirect all variations to that standard. |
After fixing redirects, re-run the redirect checker to verify the chain is now correct. On most servers, redirect changes take effect immediately, though DNS and browser caches may take a few minutes to clear.
A redirect checker traces the complete path a URL takes and shows every hop, status code, and final destination. It is used to verify that site migrations are set up correctly, identify broken links in redirect chains, check affiliate links and shortened URLs, audit performance by finding unnecessary redirect chains, and ensure proper HTTP status codes (301 vs 302) are used for SEO.
Paste the URL into a redirect checker and run it. The tool will display the full chain. A working redirect shows a series of hops with 3xx status codes, ending at a final URL with a 200 status code (success). If the chain ends with a 4xx or 5xx error, the redirect is broken.
Yes, this redirect checker is free and requires no sign-up or login. You can check as many URLs as you need at no cost.
Use a redirect checker to see the complete redirect chain for any URL. Enter the URL and the tool will display every hop, status code, and destination. This works for any URL—your own site's links, competitor links, affiliate links, or shortened URLs. The results are instant and show the exact path the browser takes.
A 301 redirect is permanent and tells search engines to transfer ranking signals to the new URL. A 302 redirect is temporary and may not consolidate SEO value. For permanent URL changes, use 301. For brief redirects (maintenance, testing), use 302. Using 301 for permanent moves preserves your site's ranking power.
Yes. Redirect chains dilute link equity at each hop and consume crawl budget. Google recommends keeping redirect hops to a minimum or eliminating them entirely. A long redirect chain may not pass full ranking signals to the final page, and it slows performance—both factors hurt SEO. Consolidate chains: instead of A→B→C, point A directly to C.
Yes. Each redirect is an extra HTTP request, adding latency. A three-hop redirect chain requires three round-trips instead of one, measurably slowing page load time. This impacts Core Web Vitals metrics like TTFB and LCP. Removing unnecessary redirect chains improves performance and user experience.