SEO

Redirect Checker

Generate curl commands to check redirects, visualize redirect chains, and learn HTTP redirect status codes and best practices.

Quick Answer

A 301 redirect (permanent) passes 90-99% of link equity to the new URL and is best for domain migrations, HTTPS upgrades, and permanent URL changes. A 302 redirect (temporary) keeps the original URL indexed and should be used for A/B tests or maintenance pages. Redirect chains (A to B to C) add 50-200ms of latency per hop and can lose link equity — always redirect directly to the final destination.

Curl Command Generator

Enter a URL to generate terminal commands that check its redirect chain. Copy and paste into your terminal.

Redirect Chain Visualizer

Map out your redirect chain by entering each URL in the sequence. Select the status code between each hop.

1
2

HTTP Redirect Status Codes

301Moved Permanently

The resource has permanently moved to a new URL. Search engines transfer link equity (PageRank) to the new URL. Use this for permanent URL changes, domain migrations, and HTTPS upgrades.

SEO Impact: Best for SEO. Passes ~90-99% of link equity.

302Found (Temporary Redirect)

The resource is temporarily at a different URL. Search engines keep the original URL indexed. Use for A/B testing, temporary maintenance pages, or geolocation-based redirects.

SEO Impact: Not ideal for permanent moves. Search engines may not transfer link equity.

307Temporary Redirect

Similar to 302, but strictly preserves the HTTP method (POST stays POST). Use when you need to ensure the request method is not changed during the redirect.

SEO Impact: Same SEO implications as 302. Temporary by definition.

308Permanent Redirect

Similar to 301, but strictly preserves the HTTP method. Use for permanent redirects where method preservation matters (e.g., API endpoints).

SEO Impact: Same SEO implications as 301. Passes link equity permanently.

About This Tool

The Redirect Checker is a free SEO utility that helps you understand, debug, and visualize HTTP redirects. While browser-based tools cannot directly follow cross-origin redirects due to CORS security policies, this tool provides everything you need to diagnose redirect issues from your terminal and understand redirect behavior.

The curl command generator creates ready-to-use terminal commands for checking redirect chains. Simply paste your URL, copy the generated command, and run it in your terminal to see every hop in the redirect chain with its status code and destination. This is the same approach used by professional SEOs and web developers worldwide.

The redirect chain visualizer lets you map out known redirect paths step by step. Whether you are documenting a migration plan, troubleshooting a chain you discovered via curl, or presenting redirect architecture to a client, the visual flow diagram makes complex chains easy to understand at a glance.

The status code reference covers the four main HTTP redirect codes: 301 (Moved Permanently), 302 (Found/Temporary), 307 (Temporary Redirect), and 308 (Permanent Redirect). Each entry explains when to use it, how it affects SEO, and the key differences from similar codes. Understanding these codes is essential for anyone managing website migrations, URL changes, or domain consolidations.

Frequently Asked Questions

Why can't this tool follow redirects directly in the browser?
Browser-based tools are blocked by CORS (Cross-Origin Resource Sharing) policies. When JavaScript in a browser tries to fetch a URL from a different domain, the browser blocks the response unless that domain explicitly allows it. This is a security feature, not a limitation of this tool. The curl commands we generate bypass CORS because they run directly from your terminal.
What is a redirect chain and why is it bad for SEO?
A redirect chain occurs when URL A redirects to URL B, which redirects to URL C, and so on. Each hop in the chain adds latency (typically 50-200ms per redirect) and can lose a small amount of link equity. Google follows up to 10 redirects but recommends keeping chains as short as possible. Ideally, every redirect should point directly to the final destination.
When should I use a 301 vs 302 redirect?
Use a 301 (Moved Permanently) when the old URL will never be used again — domain migrations, URL structure changes, HTTP to HTTPS upgrades. Use a 302 (Found/Temporary) when the redirect is temporary — A/B tests, seasonal promotions, maintenance pages. The key difference is that 301s tell search engines to transfer ranking signals to the new URL, while 302s tell them to keep the original indexed.
How do redirect chains affect page speed?
Each redirect in a chain requires a full HTTP round-trip: DNS lookup, TCP connection, TLS handshake (for HTTPS), and the redirect response itself. This typically adds 50-200ms per hop. Google's Core Web Vitals measure page load from the user's first request, so redirect chains directly impact your LCP (Largest Contentful Paint) score. A 3-hop chain could add 300-600ms before any content loads.
How do I check redirects using curl?
Run 'curl -I -L [URL]' in your terminal. The -I flag shows only headers (not the full page body), and -L follows redirects. You'll see each hop in the chain with its status code and Location header. For verbose output including TLS details, add -v. This tool generates these commands for you automatically.

You might also like

Tax & Finance

Self-Employment Tax Estimator

Calculate your quarterly SE tax payments and deductions.

⏱ 2 minFinance

Compound Interest Calculator

See how your money grows with compound interest over time.

⏱ 1 minCareer

Freelance Rate Calculator

Find your ideal hourly, daily, and project rates.

⏱ 3 min