Error Reference › HTTP
HTTP
404 Not Found
The server is up, but there's nothing at the URL you requested.
What it looks like
Not Found
The requested URL /pricing was not found on this server.
What does "404 Not Found" mean?
Returned when the server is up but has nothing at that path. Search engines drop 404 pages from their index over time, and every link pointing at one is wasted, so broken internal links are worth fixing even when visitors rarely hit them.
What causes "404 Not Found"?
- The path is misspelled or the page/route moved or was deleted.
- A relative link resolved to the wrong place.
- An SPA/framework router has no matching route.
- The file wasn't deployed.
How do I confirm the cause?
- Compare the requested path with the real one character by character — case, trailing slashes and file extensions all matter on most servers.
- For an SPA, check whether the 404 comes from the server (a deep link refreshed) or from the client-side router.
- Check the file was deployed: list the directory on the server rather than trusting your local copy.
How do I fix "404 Not Found"?
- Double-check the exact URL/path for typos.
- Confirm the route exists in your router/config.
- Verify the file was uploaded/deployed.
- Add a redirect if the page permanently moved.
How do I stop it happening again?
- When a page moves, add a 301 redirect from the old URL instead of deleting it.
- Run a link checker regularly to catch broken internal links before visitors do.