What is an HTTP Redirect?
An HTTP redirect is a server response that tells a browser to load a different URL. The server responds with a 3xx status code and a Location header pointing to the new URL.
Redirect Status Codes
- 301 Moved Permanently — page has permanently moved. Browsers update their cache. Search engines transfer link equity to the new URL.
- 302 Found — temporary redirect. Original URL is preserved in search engine indexes.
- 307 Temporary Redirect — like 302 but explicitly preserves the HTTP method (GET stays GET, POST stays POST).
- 308 Permanent Redirect — like 301 but preserves the HTTP method.
- 303 See Other — used after a POST to redirect to a GET, preventing form resubmission on back button.
SEO Implications
A 301 redirect passes most link equity ("PageRank") from the old URL to the new one. A 302 does not — search engines keep the old URL indexed. Always use 301 when permanently moving content.
Redirect Chains
A redirect chain is A → B → C. Each hop adds latency and may reduce link equity transfer. Flatten chains by making A redirect directly to C.
Trace the full redirect chain for any URL: Open Redirect Checker →
Frequently Asked Questions
What is ERR_TOO_MANY_REDIRECTS?
This browser error means the page is in a redirect loop — A redirects to B which redirects back to A. Fix by checking the redirect rules in your server config or CDN settings.
Does a 301 redirect lose any link equity?
Google has said 301s pass "full" link equity in practice, though historically there was some loss. Minimising redirect chains is still best practice.