HTTP 204 No Content and indexing
204 No Content means the request succeeded but the server intentionally returns no body. It is useful for actions where the client needs no new content, such as a save that updates nothing visible. For a crawler there is nothing to render or index, so a 204 on a URL meant to be a page is a problem.
What 204 means
204 No Content is a success status telling the client the request was handled and there is deliberately no message body to return. The client should not change its current view. It is common for background actions — a save, a heartbeat, an update that produces nothing to display.
The key point is that success and emptiness coexist: the request worked, but there is no document.
204 and indexing
A crawler exists to fetch and evaluate content. A 204 hands it a successful response with nothing inside, so there is nothing to render, parse, or index. That is exactly right for an action endpoint and exactly wrong for a URL you want in search results.
If an indexable page returns 204, treat it as a bug: the route should return the page HTML with a 200. Keep 204 for endpoints that are not meant to be content.
- 204 is success with an empty body
- Crawlers have nothing to index on a 204
- Use 200 with HTML for indexable pages, 204 for actions
Operator checklist
Confirm indexable URLs return 200 with real HTML, not 204. Keep 204 for action or background endpoints, and keep those endpoints out of internal links and sitemaps. Investigate any 204 a crawler receives on a path that should be a page.
How it appears in analytics and logs
A 204 means success with no body. A crawler receiving 204 has no content to evaluate, so the URL cannot be indexed on its own merits. A 204 on a page URL usually means a route is misconfigured or an action endpoint was crawled.
Diagnostic use case
Understand why a crawler indexes nothing for a 204, and confirm that indexable URLs return content (200) rather than an empty 204.
What WebmasterID can help detect
WebmasterID can surface where crawlers receive 204s, helping you catch page URLs returning empty success responses instead of indexable content.
Common mistakes
- Returning 204 on a URL you expect to be indexed.
- Linking action endpoints that answer 204 from crawlable pages.
- Assuming a 204 is an error — it is a success with no body.
Privacy and accuracy notes
Status codes carry no personal data. WebmasterID reports 204 patterns for crawler traffic without exposing individual visitors.
Related pages
- HTTP 200 OK: what it means for crawlers
200 OK means the request succeeded and the server returned the resource. For crawlers it is the green light to process and potentially index a page. The subtle trap is the soft 404 — an error or empty page served with a 200 status, which wastes crawl budget and pollutes the index.
- Soft 404 diagnosis and fixes
A soft 404 is a page that is effectively missing or empty but returns a 200 status, so it looks successful to crawlers while offering no real content. Search engines try to detect them, but you should not rely on that. Soft 404s waste crawl budget and can clutter the index with low-value URLs.
- Website observability
See the status-code mix crawlers receive across your URLs.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.