Understanding URL Redirects

What Is a URL Redirect?

A URL redirect is an instruction from a web server to send a visitor (or search engine crawler) from one URL to another. When your browser requests a page and the server responds with a 3xx status code, it means 'the content is at a different URL — go there instead.' The browser (or crawler) then automatically makes a second request to the new URL. Redirects have different types depending on their HTTP status code: 301 (Moved Permanently) and 308 (Permanent Redirect) tell search engines the move is permanent and to transfer ranking signals; 302 (Found) and 307 (Temporary Redirect) indicate the move is temporary and ranking signals should stay with the original URL. A redirect chain occurs when the destination URL of one redirect is itself another redirect — creating a sequence of hops before reaching the final page. For example: old-domain.com → new-domain.com/old-slug → new-domain.com/new-slug → final page. Each hop adds latency and may dilute SEO equity. This tool traces the complete redirect chain for any URL, showing you every hop, its HTTP status code, the time taken, and the final destination — exactly as a search engine crawler would see it.

HTTP Reference

HTTP Redirect Status Codes Explained

301Moved Permanently

The resource has permanently moved to a new URL. Search engines update their index to the new URL and transfer ranking signals. Use for permanent URL changes, domain migrations, and HTTPS upgrades.

SEO: Transfers ~99% of link equity. Preferred for all permanent redirects.

302Found (Temporary)

The resource is temporarily at a different URL. Search engines keep the original URL in their index and do not transfer ranking signals. Browsers may or may not cache.

SEO: Does not transfer link equity. Use only for truly temporary redirects.

303See Other

Used after a POST/PUT/DELETE request to redirect to a GET page (typically a confirmation page). Not a standard content redirect. Rarely encountered in SEO contexts.

SEO: Treated like 302 by search engines. Uncommon in typical SEO scenarios.

307Temporary Redirect

Identical to 302 but explicitly preserves the HTTP method (POST stays POST through the redirect). The HTTP/1.1 successor to 302 for temporary redirects.

SEO: Does not transfer link equity. Treated as temporary by crawlers.

308Permanent Redirect

Identical to 301 but explicitly preserves the HTTP method. The HTTP/1.1 successor to 301 for permanent redirects. Increasingly common in modern web frameworks.

SEO: Transfers link equity like 301. Preferred in HTTP/2 and HTTP/3 contexts.

200OK (Final Destination)

The final URL in the chain — the server returned the actual content here. This is the URL search engines will index and the page users land on.

SEO: The canonical destination. Ensure this is the URL you intend to rank.

404Not Found

The redirect chain ends in a missing page. This wastes crawl budget, loses all link equity, and delivers a bad user experience. Must be fixed immediately.

SEO: Loses all link equity. Crawl budget wasted. High priority to fix.

410Gone

The page has been permanently removed and will not return. More explicit than 404 — tells search engines to remove the URL from their index faster.

SEO: Signals permanent removal. Faster de-indexing than 404.

Benefits

Why Check Your URL Redirects?

Redirect issues silently damage SEO, user experience, and site performance

Protect SEO Equity

Every redirect hop may dilute PageRank passing. A chain of 3+ redirects is far less efficient than a direct 301. Verify your redirect chains are as short as possible.

Reduce Page Load Time

Each redirect adds a round-trip HTTP request. On slow connections, a 3-hop chain can add 300–600ms to load time before the final page even starts downloading.

Verify HTTPS Migration

After migrating to HTTPS, confirm that http:// URLs redirect correctly to https:// in a single hop — not through intermediate steps or back to HTTP.

Catch Redirect Loops

Circular redirects (A→B→A) cause 'Too many redirects' errors that block all users. Detect loops before they affect real visitors or get indexed by Google.

Audit Site Migrations

After migrating domains or restructuring URLs, verify every old URL redirects to the correct new destination — not to a 404, a homepage, or a wrong page.

Trace Affiliate & Short Links

Affiliate links and URL shorteners often chain through multiple tracking systems. See exactly where a link ultimately lands before using or sharing it.

Debug Developer Issues

When a page returns unexpected content or a framework redirect fires unexpectedly, tracing the full chain helps identify where the wrong redirect is being issued.

Verify Tracking Parameters

Check that UTM parameters and tracking codes survive the redirect chain intact — or confirm they're stripped at the correct point before reaching analytics.

Quick Start

How to Use the Redirect Checker

Enter a URL, click Check, see the complete redirect chain in seconds

1

Enter the URL

Type or paste any URL into the input field. You can use http:// or https://, include paths, query strings, or fragment identifiers. Short links and affiliate URLs work too.

💡 Include the full URL including the protocol (https://). If you're unsure, try both the http:// and https:// versions to compare.

2

Click Check Redirects

Click the Check button. The server follows each redirect hop one at a time, recording the URL, status code, and response time at every step.

💡 The check is performed server-side — there are no CORS or cross-origin limitations, so it works on any publicly accessible URL.

3

Read the Chain

The redirect chain appears as a visual flow — each hop shows the URL, status code badge, redirect type (permanent/temporary), and response time.

💡 Hover over or click a URL in the chain to copy it individually. The final destination is highlighted in green.

4

Act on the Results

Use the results to shorten long chains, fix incorrect redirect types, verify HTTPS upgrades, or identify loops. Copy the chain summary for reports.

💡 For SEO: chains longer than 2 hops should be collapsed to a single direct redirect from old URL to final destination.

How Redirect Following Works Server-Side

Server makes HEAD requests first (faster), falls back to GET if needed
Follows Location header in 301, 302, 303, 307, 308 responses
Detects circular loops by tracking all visited URLs in the chain
Maximum 10 hops to prevent runaway chains from hanging the request
Records wall-clock response time for each individual hop
Sends a realistic User-Agent string (Googlebot-like) for accurate results
Resolves relative redirect URLs against the current hop's base URL
Returns all hops including the final 200 (or error) response

Features

Why Use Our Redirect Checker?

Server-side checking, loop detection, and full chain visualization in one free tool

Full Chain Visualization

See every redirect hop laid out as a visual chain — from the URL you entered to the final destination, with arrows between each step.

Status Code Badges

Each hop displays a colour-coded HTTP status badge: green for 200/final, blue for 301/308 permanent, amber for 302/307 temporary, red for errors.

Per-Hop Response Time

See the response time for each hop in the chain, so you can identify slow redirect steps that add latency to the user's page load.

Redirect Loop Detection

Automatically detects circular redirect loops (URL A → URL B → URL A) and stops tracing with a clear warning before hitting the browser limit.

HTTP → HTTPS Detection

Flags when a redirect upgrades from HTTP to HTTPS (or downgrades), making it easy to verify your SSL redirect is in place and working correctly.

Copy Full Chain

Copy the entire redirect chain as a formatted text summary — useful for including in SEO audit reports, bug reports, or developer tickets.

Instant Server-Side Check

Redirect checking is performed server-side so cross-origin restrictions never apply. Gets the true redirect chain exactly as search engine crawlers see it.

Any URL, Any Protocol

Works with HTTP and HTTPS URLs, shortened links (bit.ly, t.co), affiliate links, tracking URLs, and any publicly accessible endpoint.

Examples

Common Redirect Chain Scenarios

Clean single-hop HTTPS upgrade

✓ Good

301 http://example.com200 https://example.com

Ideal: one permanent redirect, direct to final HTTPS URL.

Problematic 3-hop migration chain

⚠ Fix Recommended

301 http://old.com301 https://old.com301 https://new.com/old-slug200 https://new.com/new-slug

Fix: collapse to a single 301 from http://old.com directly to https://new.com/new-slug.

Redirect loop detected

✗ Must Fix

302 https://example.com/a302 https://example.com/bLOOP https://example.com/a

Circular loop — users and crawlers will see 'Too many redirects'. Fix the redirect rules immediately.

Redirect ending in 404

✗ Must Fix

301 https://old.com/page404 https://new.com/wrong-slug

Link equity lost. The destination page doesn't exist — update the redirect target.

Use Cases

Redirect Checking for Every Scenario

From site migrations to affiliate link tracing — check redirects in any context

Site Migration

Domain & URL Migration Audit

After migrating domains or restructuring URLs, verify every redirected URL resolves correctly to its intended destination with the right status code.

Check 500 old URLs after domain migration → confirm each 301s to correct new URL

HTTPS

SSL / HTTPS Redirect Verification

Confirm that http:// URLs redirect to https:// in a single hop. Catch double redirects (http→http→https or http→https→http) that waste equity.

http://example.com → 301 → https://example.com (1 hop, correct)

SEO Audit

Redirect Chain Length Audit

Identify redirect chains longer than 2 hops. Each extra hop dilutes link equity and adds latency. Collapse chains to single direct redirects where possible.

Discover old.com → mid.com → new.com → final.com (3 hops) → collapse to single 301

Link Tracing

Affiliate & Short Link Tracing

Trace exactly where affiliate links, URL shorteners (bit.ly, t.co, ow.ly), and tracking links ultimately land before trusting or sharing them.

bit.ly/xyz → tracking.network.com → affiliate.com/landing → shop.com/product

Bug Detection

Redirect Loop Investigation

When users see 'This page isn't working — too many redirects', use this tool to identify exactly which URLs create the circular loop.

example.com/page-a → example.com/page-b → example.com/page-a (loop detected)

Performance

Redirect Latency Profiling

Identify slow individual hops in a redirect chain. A single slow CDN or tracking redirect can add 200–400ms to TTFB before the page starts loading.

Total chain: 450ms — hop 2 took 320ms → investigate slow tracking server

Development

Framework Redirect Debugging

Verify that Next.js redirects, Express middleware, Nginx rules, or .htaccess configurations issue the correct status code and destination URL.

Test /old-route → confirm 301 to /new-route not a 302 or infinite loop

Analytics

UTM Parameter Preservation

Verify that UTM parameters and tracking codes are preserved (or intentionally stripped) as a URL passes through redirect hops.

example.com/?utm_source=email → check final URL still contains UTM params

Complete Guide

The Complete Guide to URL Redirects and SEO

How Search Engines Crawl and Follow Redirects

When Googlebot crawls a URL and receives a 3xx response, it follows the Location header to the new URL and makes a fresh request — exactly like a browser does. However, there are important differences in how Google handles this versus a human visitor. Google processes redirect chains during the crawl, and very long chains (5+ hops) may cause Googlebot to defer crawling or stop following after a certain number of hops. Google's crawl budget — the number of URLs it will crawl on your site in a given period — is consumed by each hop in a redirect chain. A site with 10,000 pages that all have 3-hop redirect chains is effectively using 3× its crawl budget on redirects rather than new content.

The SEO Impact of Different Redirect Types

The choice between 301, 302, 307, and 308 has direct SEO implications. For permanent changes (domain migrations, URL restructuring, HTTPS upgrades), 301 or 308 is required — these signal to Google that the move is permanent and trigger index updates and link equity transfer. Using 302 or 307 for permanent changes is a common mistake that leaves the original URL in Google's index and prevents link equity from flowing to the new URL. Google has become better at detecting the 'intent' of redirects even when the wrong code is used, but relying on this is risky. Always use the correct status code: 301/308 for permanent, 302/307 for temporary.

Redirect Chains After Site Migrations: What Actually Goes Wrong

Site migrations are the most common source of problematic redirect chains. A typical migration generates chains through layered decisions: first, all old URLs get 301s to new URLs (1 hop). Then, the new site restructures some URLs, adding another 301 layer (2 hops). Then, HTTP-to-HTTPS redirects are added at the server level before the application redirects (3 hops). The result: a URL that was accessible in one request now requires three. The solution is to audit redirect chains immediately after migration using a crawler, then collapse any multi-hop chains by pointing the original URL directly to the final destination.

Redirect Loops: Causes, Detection, and Fixes

Redirect loops are among the most disruptive technical SEO issues because they completely block access to a page — both for users and crawlers. The most common cause is a conflict between two redirect rules: a server-level redirect (in .htaccess or nginx config) and an application-level redirect (in WordPress, Shopify, or another CMS) that contradict each other. For example, a server rule might redirect all HTTP to HTTPS, while the CMS has a setting that redirects HTTPS back to HTTP for some reason, creating a loop. Another common cause is a redirect that was added for a new URL but forgot to exclude the destination from the same redirect rule. This tool detects loops by tracking visited URLs and stopping with a clear warning when a loop is identified.

Advanced Redirect Strategies: Internationalization, A/B Testing, and Geo-Redirects

Beyond simple URL changes, redirects are used for sophisticated scenarios. Geo-redirects send users to country-specific domains (example.com → example.de for German users) — these should use 302 or 307 (temporary) since the redirect target varies by visitor, not 301 which would cache the wrong destination. A/B testing redirects should always use 302 to prevent the test variant URL from being indexed and ranking instead of the original. For hreflang implementations across multiple language domains, redirects combined with proper hreflang annotation help search engines serve the correct language version. Cookie-based redirects (returning user vs. new user) must not use 301 as the redirect target changes per session. Understanding which redirect type is appropriate for each scenario is essential for maintaining SEO performance across complex site architectures.

FAQ

Frequently Asked Questions

Everything you need to know about redirect checking and HTTP status codes

A redirect chain occurs when URL A redirects to URL B, which redirects to URL C, and so on — requiring multiple HTTP round-trips before the browser reaches the final page. Each additional hop in the chain has two negative effects: it adds latency (each hop is a separate HTTP request with its own DNS lookup, TCP connection, and response time), and it may reduce the link equity (PageRank) passed to the final destination. Google's John Mueller has confirmed that very long chains can cause crawl issues and that collapsing chains to a single direct redirect is best practice. As a rule of thumb, any chain longer than 2 hops should be consolidated.

More Tools

Related SEO & Developer Tools

More free tools for technical SEO and URL analysis

HTTP Status CheckerFree

Check the HTTP status code of any URL — 200, 301, 302, 404, 500 and more.

Meta Tag CheckerFree

Check any live URL's meta tags, Open Graph data, and Twitter Card tags.

SERP PreviewFree

Preview how your title and meta description appear in Google search results.

UTM BuilderFree

Build UTM-tagged campaign URLs for Google Analytics tracking.

Sitemap GeneratorFree

Generate an XML sitemap for your website to improve search engine crawling.

Robots.txt GeneratorFree

Create a valid robots.txt file to control how search engines crawl your site.

Check Your Redirects Now

Free, instant, and accurate. See the full redirect chain for any URL — exactly as Google's crawler sees it.

Check a URL Browse All Tools

Redirect Checker — Trace Any URL Chain