416 Range Not Satisfiable means that none of the ranges in the request's Range header overlap the current extent of the resource, or that the server rejected the set of ranges, for example because it contained too many small or overlapping ranges. For byte ranges, the server should send Content-Range: bytes */<length> so the client learns the actual size.
It typically happens when a download manager or media player resumes downloading a file that has since become shorter or been replaced. Clients usually recover by requesting the whole file again.
Example response
HTTP
HTTP/1.1 416 Range Not Satisfiable
Date: Fri, 06 Nov 2026 10:15:32 GMT
Content-Range: bytes */52428800
Content-Length: 0SEO and redirect checking
Crawlers request complete documents, so 416 has no SEO impact. It appears in a redirect check only when you add a Range header to the request.
Common causes and use cases
- A download resumes at an offset beyond the end of a file that has changed.
- A media player requests a byte range of a video that was re-encoded with a different size.
- A client sends malformed or excessive ranges, and the server rejects them.