Check URL Redirects: Trace Redirect Chains

What Are URL Redirects?

A URL redirect tells the browser (or any HTTP client) that the requested resource has moved to a different URL. Instead of serving content at the original URL, the server responds with a redirect status code and a Location header pointing to the new URL. The browser then automatically follows the redirect and loads the new URL. This happens fast enough that users often do not notice — they click a link and arrive at the destination, unaware that the URL changed mid-flight.

Redirects serve many purposes. When a website moves to a new domain, redirects send visitors from old URLs to new ones. When a page is reorganized and its URL structure changes, redirects preserve bookmarks and incoming links. When a marketing campaign uses short URLs, redirects expand them to the full destination. When an HTTP site migrates to HTTPS, redirects ensure all traffic reaches the secure version.

The problem with redirects is that they can accumulate into chains — one redirect leads to another redirect, which leads to another, before finally arriving at the actual content. Each hop adds latency (typically 50-200ms per redirect), wastes bandwidth, and can cause issues with search engines, analytics, and browser compatibility. Redirect chains also increase the chance of loops (A redirects to B, B redirects back to A), which most browsers detect and display as an error after a limit (usually 20 redirects).

Redirect Types: 301, 302, 307, and 308

301 Moved Permanently: The resource has permanently moved to a new URL. Browsers cache this redirect — future requests for the old URL go directly to the new URL without contacting the server. Search engines transfer the SEO value (link equity, page rank) from the old URL to the new one. Use 301 for permanent URL changes: domain migrations, HTTPS upgrades, and permanent URL restructuring.

302 Found (Temporary Redirect): The resource is temporarily at a different URL. Browsers do not cache this redirect — they check the original URL each time. Search engines keep indexing the original URL. Use 302 for temporary situations: A/B testing, maintenance pages, geographic redirects, and seasonal content swaps. In practice, 302 is heavily overused — many redirects that should be 301 are accidentally implemented as 302, which dilutes SEO value.

307 Temporary Redirect: Similar to 302 but with a strict guarantee: the HTTP method is preserved. A POST request that receives a 307 will be resent as a POST to the new URL (with the same body). With 302, some browsers historically changed POST to GET during the redirect. Use 307 for API redirects and form submissions where method preservation matters.

308 Permanent Redirect: Similar to 301 but preserves the HTTP method, like 307 does for temporary redirects. A POST to a URL returning 308 will be resent as POST to the new URL. Use 308 for permanent API endpoint migrations where clients send non-GET requests.

Meta refresh and JavaScript redirects: These are not HTTP-level redirects but achieve the same effect. A <meta http-equiv="refresh"> tag or JavaScript window.location redirect happens after the page loads, adding delay and creating a visible flash. Search engines handle them inconsistently. Avoid them for SEO-critical redirects; use server-side HTTP redirects instead.

SEO Impact of Redirects

Search engines follow redirects to find canonical content, and the redirect type affects how they treat the old and new URLs:

Link equity transfer: A 301 redirect passes most of the old URL's ranking signals to the new URL. Google has confirmed that 301 redirects pass full PageRank (this was not always the case — older guidance suggested a 15% loss, but Google updated this in 2016). A 302 redirect signals that the old URL should retain its ranking, and the new URL does not inherit authority.

Redirect chains dilute equity: While Google follows up to 10 redirects in a chain, each additional hop reduces crawl efficiency. Long chains waste crawl budget — the number of pages Google will crawl on your site in a given time period. For large sites, excessive redirects mean Google spends its crawl budget following chains instead of indexing new content.

Redirect loops cause deindexing: If a redirect chain forms a loop, search engine crawlers cannot reach the content. The URLs involved may be dropped from the index entirely. Even temporary loops (caused by misconfigured rules during deployment) can take days to recover from as crawlers retry and eventually give up.

Mixed redirect types: A chain that mixes 301 and 302 redirects sends confusing signals to search engines. If the chain is A →301→ B →302→ C, the search engine may index B (because the 302 suggests C is temporary) rather than C (the actual destination). Consistent redirect types within a chain produce predictable search engine behavior.

Common Redirect Issues

HTTPS + www normalization chains: A common misconfiguration creates a 3-hop chain: http://example.com → http://www.example.com → https://www.example.com. Each step is individually correct (add www, then upgrade to HTTPS), but the chain adds unnecessary latency. The fix is to redirect directly to the final canonical URL in one hop: http://example.com → https://www.example.com.

Trailing slash inconsistency: Servers that sometimes redirect /page to /page/ (or vice versa) create unnecessary redirects and can cause infinite loops if combined with other rules. Pick a convention (trailing slash or no trailing slash) and apply it consistently.

Case sensitivity: Some servers redirect /About to /about, adding a hop. If this combines with other redirects, the chain grows. Enforce consistent URL casing at the source (generate links in the correct case) rather than relying on redirect rules.

Outdated redirect rules: Over years of site changes, redirect configurations accumulate rules that are no longer needed or that conflict with newer rules. Regular audits of your redirect rules (.htaccess, nginx config, CDN rules) prevent accumulation of legacy chains.

Check URL Redirects Online

Our Redirect Checker traces the complete redirect chain for any URL, showing every hop with its HTTP status code, response headers, and destination URL. It identifies redirect chains, detects loops, flags mixed redirect types, and measures the response time of each hop so you can see the total latency cost.

Use it to audit your own site's redirects, debug redirect issues reported by search console, or verify that a URL migration was implemented correctly with proper 301 redirects and no unnecessary chains.