All HTTP status codes

HTTP 302 Found

Redirection

The resource temporarily lives at another URL. Search engines keep the original URL indexed; browsers don't cache the redirect.

Defined in RFC 9110

Common causes

  • Login flows and post-action redirects
  • Temporary moves, A/B routing

How to fix it

  1. If the move is permanent, switch to 301/308 so SEO signals transfer

  2. If the request method must not change, use 307 instead

Related status codes

301 Moved Permanently

The resource has permanently moved to the URL in the Location header. Browsers cache it and search engines transfer ranking signals to the new URL.

303 See Other

Tells the client to fetch a different URL with GET — the standard way to redirect after a POST (Post/Redirect/Get pattern).

307 Temporary Redirect

Like 302, but the client must repeat the request to the new URL with the same method and body — a POST stays a POST.

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.