Redirect Types & Concepts
What is a URL redirect?
A URL redirect is a technique that automatically sends visitors and search engines from one web address to another. When someone requests a URL that has a redirect in place, the server responds with an HTTP status code and a Location header pointing to the destination. The browser follows the location automatically and loads the destination page. The visitor rarely notices anything happened.
Redirects are one of the most fundamental tools in web infrastructure. They are how websites handle moved content, enforce secure connections, consolidate domains, manage rebranding, and preserve search rankings through structural changes. Every website of any size uses redirects, and using them correctly is the difference between smooth transitions that preserve traffic and rankings, and broken experiences that lose both.
How a URL redirect works
The mechanics of a redirect are straightforward. A visitor or web crawler requests a URL. The server checks whether that URL has a redirect rule in place. If it does, the server responds with a 3xx status code and a Location header containing the destination URL. The browser reads the Location header and immediately makes a new request to the destination. The destination server responds, ideally with a 200 OK, and the browser renders the page.
The entire process typically takes milliseconds. For a visitor navigating a site, a single redirect hop is imperceptible. Multiple hops in a redirect chain add measurable latency. A circular loop creates ERR_TOO_MANY_REDIRECTS and makes the page completely inaccessible.
Types of URL redirects
Not all redirects are the same. The HTTP status code used in a redirect communicates the nature of the move to browsers and search engines, and choosing the right code has real consequences for SEO and application behaviour.
301 Moved Permanently: the most widely used redirect. Signals a permanent move, transfers SEO equity and link juice to the destination, and is cached by browsers. Use for any URL change that is intended to be permanent.
302 Found: signals a temporary move. The original URL stays indexed by search engines and SEO equity does not transfer. Not cached by browsers. Use for maintenance pages, A/B tests, and seasonal campaigns.
303 See Other: explicitly switches the follow-up request to GET regardless of the original method. Used primarily in Post/Redirect/Get patterns after form submissions and login flows.
307 Temporary Redirect: temporary redirect that strictly preserves the original HTTP request method. Use in API and application contexts where POST, PUT, or DELETE requests need to be temporarily redirected without losing their method.
308 Permanent Redirect: permanent redirect that strictly preserves the original request method. Use for permanently moving API endpoints and webhook receivers where method preservation matters. Beyond HTTP-level redirects, there are also client-side redirect methods that operate differently.
Meta refresh redirect: a redirect implemented via an HTML meta tag in the page head rather than a server response. Slower than server-side redirects, less reliable for SEO, and generally considered a poor practice for anything other than very specific use cases.
JavaScript redirect: a redirect implemented by JavaScript code that runs in the browser after the page loads. Even slower than meta refresh since it requires the JavaScript to execute first. Search engines can follow JavaScript redirects but they are less reliable and less efficient than server-side redirects for SEO purposes.
For all standard redirect use cases (domain migrations, HTTP to HTTPS, URL restructuring, domain parking) server-side redirects using the appropriate HTTP status code are always the correct choice.
URL redirects and SEO
Redirects and SEO are inseparable. Every significant structural change to a website involves redirects, and how those redirects are configured determines whether the SEO value built up over months or years is preserved or lost.
Link juice and SEO equity: backlinks pointing to a URL represent accumulated authority and ranking power. When a URL moves, a 301 redirect transfers that authority to the new URL. Without a redirect, the authority is lost entirely, incoming links point to a 404 error and pass nothing.
Canonical URL signals: permanent redirects send a strong signal to search engines about which URL is the canonical version of content. When multiple URLs could serve the same content (HTTP and HTTPS, www and non-www, trailing slash and no trailing slash) redirects enforce the canonical version and prevent duplicate content.
Crawl budget: search engines allocate a finite crawling budget to each site. Redirect chains, loops, and broken redirects waste that budget on URLs that do not deliver indexable content. Clean, direct redirects that resolve immediately to 200 OK responses preserve crawl budget for live content.
Index updates: when a URL moves permanently and a 301 is in place, search engines update their index over time to replace the old URL with the new one. The speed of this update depends on crawl frequency — high-traffic pages on well-established sites update faster than low-traffic pages on newer sites.
Common use cases for URL redirects
Redirects serve a wide range of purposes across different website management scenarios.
Domain migration: moving an entire site from one domain to another requires 301 redirects from every URL on the old domain to its equivalent on the new one. A complete domain migration redirect setup preserves SEO equity, ensures visitors are not stranded on the old domain, and tells search engines to update their index.
HTTP to HTTPS: redirecting all HTTP traffic to HTTPS is one of the most universal redirect use cases. Every page on the HTTP version of a site should have a permanent redirect to its HTTPS equivalent, ensuring all visitors and crawlers are served over a secure connection.
WWW to non-WWW: choosing one canonical version of a domain and redirecting the other prevents duplicate content, consolidates SEO equity, and ensures a consistent URL structure. Both versions should never serve content simultaneously without a redirect between them.
Domain parking: pointing parked or unused domains to a primary domain with a global redirect ensures any traffic or backlinks pointing to those domains are forwarded correctly rather than landing on a dead end.
Domain rebranding: when a company renames or rebrands and moves to a new domain, permanent redirects from the old domain preserve the SEO value built up under the old brand and ensure existing links and bookmarks continue working.
Company mergers: merging two companies online means consolidating their web presences. Redirects from the acquired company’s domain to the acquiring company’s site preserve link equity from both sites and ensure a seamless experience for visitors of either brand.
URL restructuring: changing URL slugs, removing dates from blog post URLs, reorganising site architecture, or any other change to URL patterns requires permanent redirects from old URL formats to new ones to prevent 404 errors and preserve rankings.
Apex to WWW: redirecting the apex domain to the www version or vice versa as part of enforcing a consistent canonical domain structure.
Redirect best practices
Getting redirects right requires more than just choosing the correct status code. Several principles apply across all redirect use cases.
Always redirect to the final destination: never chain redirects. A 301 pointing to another URL that redirects again creates a redirect chain that adds latency and dilutes SEO equity. Always point redirects directly to the final URL that returns a 200 OK.
Match the redirect type to the intent: permanent redirects for permanent moves, temporary redirects for temporary situations. Using a 302 for a permanent move is one of the most common and costly redirect mistakes.
Cover all URL variants: a complete redirect setup handles HTTP and HTTPS, www and non-www, trailing slash and no trailing slash, and any other variants that could serve the same content. Missing a variant means some traffic and link equity leaks through unredirected.
Verify destinations return 200: always confirm that redirect destinations are live and returning a 200 OK before deploying redirects. A redirect pointing to a 404 or 500 is worse than no redirect at all.
Audit redirects regularly: redirect configurations accumulate over time. Rules set up for specific situations can interact with newer rules in unexpected ways. Regular audits catch redirect chains, loops, and outdated rules before they cause problems.
Update internal links: redirects preserve external link equity but internal links should always point directly to the correct current URL. Relying on redirects for internal navigation adds unnecessary hops and slows down crawling.
Redirect chains and loops
Two of the most important redirect problems to understand and avoid are redirect chains and redirect loops.
A redirect chain occurs when URL A redirects to URL B which redirects to URL C before finally resolving to a 200 OK. Each hop adds latency and dilutes SEO equity. The fix is to update all redirects in the chain to point directly to the final destination.
A redirect loop occurs when redirect rules create a circular path with no exit, URL A redirects to URL B which redirects back to URL A. The browser follows the loop until it hits its redirect limit and shows ERR_TOO_MANY_REDIRECTS. The URL becomes completely inaccessible. Loops are most commonly caused by conflicting www and non-www rules or HTTP to HTTPS configurations at multiple infrastructure layers.
Bulk redirects
For large-scale redirect needs (domain migrations, major site restructures, CSV import of hundreds or thousands of rules) managing redirects individually is impractical. Bulk redirect tools and import features allow redirect rules to be defined in spreadsheets or CSV files and deployed all at once.
Bulk redirects require careful validation before deployment. Each rule should be checked for correct source and destination URLs, appropriate redirect type, and the absence of chains or loops. A single misconfigured rule in a bulk import can create widespread issues across a site.