204 No Content
2xx success
The request succeeded and there is no body to return, often used for delete operations and form submissions where the page should not change.
Common causes
- A DELETE or PATCH completed without a new representation to return.
- A form handler finished and the client already knows the new state.
- A beacon or telemetry call needs a success signal with no payload.
How to fix it
- Return 200 with a body instead if the client needs confirmation data.
- Keep the 204 free of a Content-Length or body that would confuse clients.
- Send a Location header when the client must learn where the result lives.
What it means for redirects and SEO
No body means no document to index, so a URL returning 204 effectively drops out of search. Form and action endpoints legitimately use it. A page accidentally returning 204 looks empty to users and crawlers.