404 Not Found
Quick summary
The page or resource you requested doesn't exist at that URL — the path is wrong, the file was removed, or the route isn't configured.
Why this happens
Typo in the URL path
The page or file was deleted or moved without a redirect
The route is not configured on the server or in the framework
Minimal example
fetch("/api/usrs") // typo: should be "users"fetch("/api/users")The URL path has a typo (usrs instead of users) — the server returns 404 because no route matches /api/usrs.
How to diagnose
Check the URL spelling in the browser address bar or the request
Verify the route exists in your routing configuration
Check server logs for the 404 and confirm the requested path
How to fix
Correct the URL to the right path
Add a redirect from the old URL to the new one
Create the missing page or configure the route
How to prevent
Set up redirects when moving or renaming pages
Test internal links regularly and use a sitemap checker
Related Resources
Related Practice
- HTTP Methods Quiz
Test your knowledge of HTTP methods.
- Predict the HTTP Status Code
Practice predicting HTTP status codes.
Related Tools
- HTTP Status Codes
Reference for all HTTP status codes including 404.
- URL Parser
Parse URLs to find path issues causing 404s.