406 Not Acceptable
4xx client error
The resource exists but no representation matches the content types, languages, or encodings listed in the request Accept headers, so negotiation fails.
Common causes
- The client Accept header lists only types the server cannot produce.
- A language variant is missing for the requested Accept-Language.
- A required encoding is not available on the server.
How to fix it
- Provide a default HTML representation when negotiation fails.
- Offer the missing language or encoding variant.
- Inspect the Accept headers from the failing client and align the response.
What it means for redirects and SEO
Content negotiation failure means no representation matches the Accept header, which some bots send narrowly. The URL may be skipped entirely. Adding a default HTML representation fixes crawling.