No response: what it means and how to fix it

What we look for

Raptor requested these pages and got nothing back, not even a status code (the three-digit reply a server sends with every page).

Why it matters

A page whose server does not answer cannot be opened by visitors or read by search engines.

How to fix

Open each address in a browser to see whether it loads now. If it still fails, ask your host whether the server is up, and check that the domain's DNS records (the settings that point a domain at its server) are correct.

What it cannot know

One crawl cannot tell a lasting fault from a brief outage or a single timeout.

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_no_response
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_no_response"
The HTML report: This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=response_codes.internal_no_response
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_no_response" }