URLRedirection

URLRedirection, also known as URL forwarding or URL redirect, is a mechanism that makes a resource available at a different URL than the one originally requested. When a user agent requests the original URL, the server responds with a 3xx status code and a Location header that specifies the new URL. The client then automatically requests the new URL, completing the redirection.

Redirects are typically handled on the server, by web server software or application logic. Client-side redirects exist but are less common and can be slower or less reliable for search engines. Server-side redirects are preferred for long-term changes, migrations, and URL hygiene.

The most common HTTP redirects are 301, 302, 303, 307, and 308. A 301 Moved Permanently indicates a permanent change and should be used when the resource has moved permanently. A 302 Found (historically “Temporary Redirect”) and a 307 Temporary Redirect both signal a temporary move, with 307 preserving the original request method. A 303 See Other instructs the client to fetch the new URL using a GET method, often after a POST. A 308 Permanent Redirect is a permanent move that preserves the original request method. These codes influence how user agents and search engines treat the redirect and how link equity is passed.

Use cases include site migrations or domain changes, removing duplicate content, trailing-slash normalization, and load balancing or A/B testing. For search engines, a properly implemented 301 redirect generally transfers most link equity, while a 302/307 redirect may not. Configuration examples vary by server: Apache, Nginx, and IIS offer directives or modules to implement 301 or 302 redirects.