303 See Other
3xx redirect
After processing a request, the server points the client to another URL to retrieve the result with a GET, used for post-then-redirect patterns.
Common causes
- A form handler finishes and sends the browser to a confirmation page.
- A POST creates a resource and the result lives at a readable URL.
- A legacy app converts a write into a GET-safe destination.
How to fix it
- Always use GET on the target and return the result document there.
- Return absolute Location URLs and keep them stable.
- Distinguish it from 302 so clients do not resend the POST body.
What it means for redirects and SEO
Redirects a POST to a GET result page, the correct pattern for form handling that avoids duplicate-submit warnings on refresh. It is not cached and carries no ranking signal. Chains mixing 303 with 301 confuse crawlers about the final canonical URL.
Trace a link that returns 303 →