404 Not Found
A 404 Not Found error means the server cannot find the resource at the requested URL. The server is reachable, but the specific page, file, or API endpoint does not exist or is no longer available. For end users, this usually means the link you followed is broken, the page was moved or deleted, or there is a typo in the URL.
Common causes
- The URL contains a typo or incorrect path segment
- The resource was moved or renamed without setting up a redirect
- The page or content was deleted but inbound links still reference the old URL
- Server-side routing is misconfigured and does not match the requested path
- The API endpoint version has changed and the old version was deprecated
How to fix it
- Double-check the URL for typos, incorrect casing, or missing path segments
- Set up 301 redirects from old URLs to their new locations to preserve links and SEO
- Audit your site for broken links using a crawler tool and fix or remove stale references
- Review server routing configuration to ensure all expected paths are correctly mapped
- Implement a custom 404 page with navigation links to help users find what they need
Detect 404 Not Found errors with Checkend
Checkend monitors your application and alerts you when 404 errors occur, with full request context:
- Full request details (URL, headers, params)
- Server-side stack trace and error context
- Automatic grouping of similar errors
- Instant notifications when error rates spike
Related HTTP errors
A 400 Bad Request error means the server cannot process the request because the client sent somethin...
A 403 Forbidden error means the server understood the request but refuses to authorize it. Unlike a ...
A 405 Method Not Allowed error means the HTTP method used in the request (GET, POST, PUT, DELETE, et...
Stop debugging HTTP errors in production
Get full error context and fix issues faster with self-hosted error tracking.