HTTP status code
Not Found
The server could not find the requested resource.
The best-known status code. The server reached a decision and the answer is that nothing lives at this path. Importantly, 404 says nothing about whether the resource ever existed or might exist later — the server is deliberately not telling you.
Confirm whether the path exists on disk or in the router. If a page moved, return a 301 to the new location rather than a 404 — for anything with inbound links or search traffic, a redirect preserves value that a 404 discards. Case sensitivity catches people constantly when developing on macOS and deploying to Linux.
A 404 on a URL that used to work is a deploy problem, not a traffic problem, and it will not show up in an uptime check that only looks at your homepage. Monitor the specific URLs that matter.
Monitor for 404 responses freeA 404 on a page nobody links to is harmless and completely normal. A 404 on a page with inbound links or existing rankings wastes that value — redirect it. What actually causes damage is returning 404 for pages that should exist, or returning 200 for pages that do not.
A page that returns HTTP 200 while displaying "not found" content. Search engines treat this as a bug because the status line and the page contradict each other. Return a real 404 status for missing pages.
Pingura checks your endpoints from five regions and alerts on the status code, not just reachability.
Get Started Free