Understanding bot status codes

What status codes mean

Every bot request gets a 3-digit HTTP status code. You see these in the Status column of the Bot Activity table.

200 — Success

Page rendered fine. Most of your traffic should look like this.

301 / 302 — Redirects

Bot was sent to a different URL. 301 = permanent, 302 = temporary. Common for http→https or /old → /new. We don't cache redirects, so they don't count against your render quota.

404 — Page not found

The URL doesn't exist. Common causes: deleted page, broken external link, typo in a sitemap. Restore the page or set up a 301 if you see clusters of 404s.

5xx — Server or render errors

500/502/503/504 means rendering itself failed (origin down, timeout, JS crash). RenderBeam fails open — the user is still served by your origin via the worker. See Fail-open behavior.

Cache hits and codes

Cache hits return 200 with X-Cache-Status: HIT. They are free — they don't count toward your monthly render quota. Only MISS rows are billable. See Cache & billing.

What to do when you see errors

1. Filter Bot Activity by Errors.
2. Open the URL in a browser to confirm it works for humans.
3. If humans are fine but bots fail, run Test bot render to reproduce.
4. Frequent or clustered errors are worth investigating; one-off 404s/5xx from old links are normal internet noise.