422 Unprocessable Content
4xx client error
The request is syntactically valid but logically invalid, such as missing required fields or broken cross-field rules, so semantic processing could not proceed.
Common causes
- A required field is absent or fails validation.
- Cross-field rules are inconsistent.
- A referenced record does not exist.
How to fix it
- Return a per-field error map so the client can correct input.
- Validate before touching persistence so partial writes do not occur.
- Keep the message user-facing and specific rather than generic.
What it means for redirects and SEO
The page loads but data validation fails, common on search and filter endpoints that crawlers hit with odd parameters. Empty-result filters should return 200 with a no-results page. Reserve 422 for genuinely invalid input.