Learn what HTTP redirects are, the difference between 301 and 302 redirects, why they matter for SEO, and how to check any URL for redirect issues.

What Are HTTP Redirects? A Complete Guide to 301, 302, and Redirect Chains

Click a link and end up somewhere different than the address you typed or clicked. It happens constantly, often without you noticing at all — you land on a page, and it looks correct, but the URL in your address bar has quietly changed. This is the work of an HTTP redirect, a fundamental mechanism that keeps the web functional as websites restructure, rebrand, migrate, and grow over time.

This guide explains exactly what HTTP redirects are, the different types you'll encounter, why they matter enormously for SEO, and how to check whether a URL is redirecting properly — or causing problems.

What Is an HTTP Redirect?

An HTTP redirect is an instruction sent from a server telling a browser (or any client making a request) that the resource it's looking for is located at a different URL. Instead of returning the requested content directly, the server responds with a status code and a new address, and the browser automatically follows that new address to load the correct page.

This all happens within a fraction of a second, which is why most redirects feel completely seamless. You click a link, and the correct page loads — the intermediate redirect step is invisible unless you're specifically looking for it.

Redirects are identified by their HTTP status code, which falls in the 3xx range. The two most common and most important to understand are 301 and 302.

301 Redirect: Moved Permanently

A 301 status code tells the browser — and just as importantly, search engines — that a resource has been permanently moved to a new location. This is the redirect type to use when a page or an entire site has relocated for good and has no intention of returning to the original URL.

When 301s Are Used

• A website changes its domain name entirely
• A page's URL structure is updated as part of a site redesign
• HTTP is redirected to HTTPS after a site adds an SSL certificate
• Old, outdated pages are consolidated into a single updated page
• A "www" version of a domain is redirected to the non-www version (or vice versa) for consistency

Why 301s Matter for SEO

Search engines treat a 301 redirect as a strong signal to transfer the vast majority of the original page's ranking authority to the new URL. This means that when done correctly, a 301 redirect allows a site to move or restructure its pages without losing the SEO value it had built up over time. It's the closest thing to a "safe" way to change a URL without tanking your search rankings.

302 Redirect: Found (Temporary)

A 302 status code indicates a temporary redirect — the resource has moved for now, but it's expected to return to its original location eventually. Unlike a 301, a 302 tells search engines not to transfer ranking authority to the new URL, since the original is still considered the "real," permanent address.

When 302s Are Used

• A site is undergoing temporary maintenance and redirecting visitors to a status page
• A/B testing sends a portion of visitors to an alternate version of a page temporarily
• Geographic or device-based redirects send users to a region-specific or mobile version of a site, while the original URL remains the canonical version
• A promotional page is live for a limited time before reverting

The Common Mistake

One of the most frequent SEO errors is using a 302 redirect for what should actually be a permanent change. If a page has genuinely moved for good but is redirected with a 302 instead of a 301, search engines may continue treating the original URL as the "real" one indefinitely, splitting ranking signals between two URLs instead of properly consolidating them. This is a small technical detail that can have a real, lasting impact on search visibility.

Other Redirect Status Codes Worth Knowing

While 301 and 302 are by far the most common, a few other redirect codes exist for more specific situations:

• 303 See Other — Instructs the client to retrieve the redirected resource using a GET request, commonly used after form submissions to prevent duplicate submissions if the user refreshes the page.
• 307 Temporary Redirect — Functionally similar to a 302, but strictly preserves the original request method (important for redirects involving form data or API calls where the method must not change).
• 308 Permanent Redirect — The stricter version of a 301, also preserving the original request method rather than potentially changing it.

For most everyday website management, 301 and 302 cover the vast majority of real-world use cases, and the stricter 307/308 variants are typically only relevant in more technical, method-sensitive contexts like API design.

Redirect Chains and Redirect Loops

Not all redirect setups are clean. Two common problems can develop over time, especially on sites that have gone through multiple redesigns or migrations without careful cleanup.

Redirect Chains

A redirect chain happens when one URL redirects to a second URL, which then redirects to a third, and so on, before finally landing on the actual destination. For example: Page A redirects to Page B, which redirects to Page C. Each additional hop adds a small amount of load time and, more importantly, can dilute the SEO value passed along the chain. Search engines generally recommend keeping redirects to a single hop wherever possible — redirecting Page A directly to Page C, rather than routing through an unnecessary middle step.

Redirect Loops

A redirect loop occurs when a chain of redirects eventually points back to a URL earlier in the chain, creating an endless cycle that never resolves. Browsers typically detect this and display an error like "too many redirects" rather than looping forever. Redirect loops are almost always the result of a misconfiguration — often introduced accidentally during a site migration, a botched .htaccess rule, or conflicting redirect rules set up by different systems (a CMS plugin and a server configuration both trying to redirect the same URL, for instance).

Why Redirects Matter Beyond SEO

While SEO is often the primary reason website owners care about redirect configuration, there are other important reasons redirects matter:

User Experience

A broken or missing redirect after a site restructure means visitors clicking old links — from bookmarks, search results, or external sites — land on a 404 error page instead of the content they were looking for. Proper redirects preserve a smooth experience even as a site evolves.

Preserving Backlinks

Other websites linking to your old URLs represent real value, often built up over years. A proper 301 redirect ensures that value carries over to the new URL rather than being lost entirely when old links start pointing to dead pages.

Security and Migrations

Redirecting HTTP to HTTPS is a standard and important practice once a site has an SSL certificate installed, ensuring visitors are never left on an insecure connection even if they type or click an old HTTP link.

How to Check a URL for Redirects

Understanding whether a URL redirects — and where it ultimately lands — is useful for website owners auditing their own site, developers debugging navigation issues, and anyone wanting to verify where a link actually leads before trusting it.

A redirect checker tool lets you enter any URL and see its complete redirect path: every hop in the chain, the status code used at each step (301, 302, or otherwise), and the final destination URL. This makes it easy to spot problems like unnecessary redirect chains, incorrectly used 302s where a 301 should be, or loops that need fixing.

What to Look for When Auditing Redirects

• Chain length. Ideally, a redirect should resolve in a single hop. Multiple hops indicate cleanup is needed.
• Correct status codes. Permanent moves should use 301s; only genuinely temporary situations should use 302s.
• Final destination accuracy. Confirm the redirect actually lands on the intended, correct page — not an outdated or unrelated one.
• HTTPS consistency. Ensure HTTP versions of URLs properly redirect to HTTPS, rather than loading an insecure version or breaking entirely.

Final Thoughts

HTTP redirects are one of those pieces of web infrastructure that work best when you never have to think about them — but when they're set up incorrectly, the consequences show up as broken links, lost search rankings, and frustrated visitors landing on dead pages. Whether you're managing a website through a migration, cleaning up old URL structures, or simply curious about where a link actually leads, understanding how redirects work — and knowing when 301 versus 302 is the right choice — is a genuinely practical skill.

Want to check exactly how a URL redirects and confirm it's set up correctly? Run it through our free Redirect Checker tool and see the full redirect path instantly.