Skip to content
Raptor home
Menu

Page error (4xx)

response_codes.internal_client_error
Priority
Fix now
Severity
Critical

What we look for

These addresses answered with a 4xx status code (the code a server sends when a page is missing or gone, such as 404 Not Found). 401, 403 and 429 are listed separately.

Why it matters

Search engines drop error pages from their results, and every link that points at one leads visitors to a dead end.

How to fix

Bring each page back, or send its address to the closest live page with a 301 redirect (a permanent forwarding rule set on the server). Then update the internal links that still point at the old address.

Seen in a real crawl

From a crawl of Fernhollow Outdoor, a test site built for this site’s demo.

Fix now

1 page returns an error instead of its content

  • /products/storm-shellStatus 404
Paths on http://127.0.0.1:8006raptor 0.3.0, 17 Oct 2026

Open this finding in that crawl’s report

It also fired on Millbrook Hardware.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: response_codes.internal_client_error
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "response_codes.internal_client_error"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=response_codes.internal_client_error
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "response_codes.internal_client_error"
}