Trace the redirect chain of any URL. See every hop, status code, and the final destination.
Enter a URL and click "Check" to trace its redirect chain.
A redirect chain is a sequence of URL redirects that a browser follows before reaching the final destination. When you click a link, the server may respond with a redirect (3xx status code) that sends you to a different URL — which itself may redirect to another URL, and so on.
For example:
http://example.com
→ 301 → https://example.com
→ 301 → https://www.example.com
→ 302 → https://www.example.com/landing-page
→ 200 (final destination)That's a 3-hop redirect chain. Each hop adds latency (50–200ms per redirect), and long chains can cause:
Affiliate links often pass through multiple redirects: your tracking platform → affiliate network → advertiser's landing page. If any hop is slow or broken, you lose conversions. Use this tool to:
Redirect chains directly impact SEO performance:
When you check a URL, this tool shows every step in the chain:
| Column | What It Means |
|---|---|
| Step | The hop number (1, 2, 3...) |
| URL | The URL at this step |
| Status Code | The HTTP response code (see reference below) |
| Redirect Type | Permanent (301/308) or Temporary (302/307) |
| Response Time | How long this hop took in milliseconds |
Not all redirects are equal. Choosing the right type matters:
| Type | Code | Use Case | Caching | SEO Impact |
|---|---|---|---|---|
| Permanent | 301 | Domain migration, URL restructuring | Browser caches permanently | Transfers link equity to new URL |
| Temporary | 302 | Affiliate tracking, geo-targeting, A/B tests | Not cached — every click hits the server | No link equity transfer |
| Permanent Strict | 308 | Same as 301 but preserves HTTP method | Browser caches permanently | Same as 301 |
| Temporary Strict | 307 | Same as 302 but preserves HTTP method | Not cached | Same as 302 |
| Meta Refresh | N/A | HTML-based redirect (slow, not recommended) | Not cached | Poor — search engines may not follow |
| JavaScript | N/A | Client-side redirect (requires JS execution) | Not cached | Worst — many bots can't follow |
For affiliate smart links, 302 is almost always correct. It ensures every click passes through your tracking server, destinations can be changed instantly, and A/B test assignments are fresh on every click. GeoRedir uses 302 redirects for all smart links. Learn more in our glossary: A/B Testing.
Symptom: Browser shows "ERR_TOO_MANY_REDIRECTS" or this tool shows the same URLs repeating.
Cause: URL A redirects to URL B, which redirects back to URL A.
Fix: Check your redirect rules for circular references. In GeoRedir, ensure your destination URLs don't point back to your smart link URL.
Symptom: Chain ends with a 404 (Not Found) status.
Cause: The final destination page has been removed or the URL is wrong.
Fix: Update the destination URL in your redirect rule. In GeoRedir, edit the smart link and correct the destination.
Symptom: Extra redirect from HTTP to HTTPS at the start of the chain.
Cause: The link uses http:// but the destination server forces HTTPS.
Fix: Always use https:// in your destination URLs to avoid the unnecessary extra hop.
Symptom: Total chain time exceeds 500ms.
Cause: Too many hops, slow servers in the chain, or geographic distance.
Fix: Reduce the number of hops. Use an edge-based redirect platform like GeoRedir (sub-200ms from 300+ locations) instead of server-based redirects.
OK
The request succeeded. This is the final destination — no more redirects.
No Content
The server processed the request but returned no content. Common for tracking pixels and API calls.
Moved Permanently
The URL has permanently moved. Search engines transfer SEO value to the new URL.
Found (Temporary Redirect)
The URL has temporarily moved. GeoRedir uses 302 redirects for smart links (best for affiliate tracking).
See Other
The server redirects to a different URL using GET. Often used after form submissions.
Not Modified
The resource hasn't changed since the last request. The browser uses its cached version.
Temporary Redirect (Strict)
Like 302 but guarantees the request method stays the same. Used by HSTS and modern redirect systems.
Permanent Redirect (Strict)
Like 301 but guarantees the request method stays the same. The permanent counterpart of 307.
Bad Request
The server couldn't understand the request. Usually caused by malformed URLs or missing parameters.
Unauthorized
Authentication is required. The request lacks valid credentials.
Forbidden
The server understood the request but refuses to authorize it. Access is permanently denied.
Not Found
The requested page doesn't exist. Check the URL for typos or broken links.
Gone
The resource has been permanently removed. Unlike 404, the server confirms it existed before and won't return.
Too Many Requests
Rate limit exceeded. The client has sent too many requests in a given timeframe.
Unavailable For Legal Reasons
The resource is blocked due to legal demands (censorship, DMCA, GDPR). Common in geo-restricted content.
Internal Server Error
Something went wrong on the server. A generic error when no more specific message is available.
Bad Gateway
The server received an invalid response from an upstream server. Often a temporary infrastructure issue.
Service Unavailable
The server is temporarily unable to handle requests. Usually due to maintenance or overload.
Gateway Timeout
The upstream server didn't respond in time. The request may work if retried later.
GeoRedir delivers sub-200ms redirects from 300+ global edge locations. Perfect for affiliate links, geo-targeting, and A/B testing.
Free plan included • No credit card required • Upgrade anytime