# Fix pages and APIs returning 404 not found

> Find which visitors land on "not found", which request failed, where they came from, and fix the link or the API that sends them there.

Section: Find and fix real problems · Page: https://tryrelia.com/docs/not-found-errors · Last checked against the product: 2026-11-01
Video walkthrough: https://youtu.be/ed4I6yqAPXc

A 404 means "not found": the page or the thing a request asked for doesn't exist. Your server isn't crashing, so it's easy to miss, but for the visitor the page is broken. Common causes are an old link to something you deleted or renamed, a typo in a URL your app builds, or a route that moved.

The example is Relia's demo shop: an old social media post links to a product that no longer exists, so visitors land on a product page whose request comes back 404.

## What you'll see

- **Home** says something needs you, for example *Users get errors from GET /api/products/:id on /products/:id*. **Users** shows **Needs you**.
- **APIs** usually stays normal: a 404 is the server answering correctly, not a server error.
- Relia raises it as **Needs you** once at least 3 different visitors hit it. With fewer it stays quiet or **Watch**, since one or two can be a typo or your own testing.

> **Note:** 401 and 403 answers (signed out, not allowed) are treated differently: they are usually a page asking for data before the user signs in, so Relia keeps them as information, not alerts.

## Find the cause

1. **Open the incident.** It says how many visitors opened the page and had the request fail, and each visit links to its session.
2. **Open a visit, then Network.** Find the request that came back `404`, for example `GET /api/products/1009`. That tells you exactly what was missing.
3. **Open Device & User.** The **referrer** shows where the visitor came from: a social post, a search engine, an email, another site, or a page of your own app.
4. **See how often it happens.** Go to **APIs**, then **Errors**, and choose the **4xx Client Errors** filter. It groups client errors such as 404 by API, with how many there were and when they were last seen.

> **Tip:** watch [Monitor API requests, errors, logs and latency in one place](https://youtu.be/W_SUfdKLns0) (2 min).

## Fix it

Decide which side is wrong:

| What you found | What to do |
|---|---|
| The link points to something that was deleted or renamed | Fix the link where it lives (the post, the email, your own page), or redirect the old address to something that exists. |
| Your app builds the wrong URL | Fix the code that builds it (a missing id, a wrong path). |
| The API route moved | Keep the old route answering, or redirect it, until old clients stop using it. |
| The item really is gone | Show a helpful "not found" page with links onward, instead of a blank or broken page. |

**Do this next** on the incident says to fix the API. Read it together with the referrer: when the API answers correctly and the item is simply gone, the fix is usually the link, not the API.

## Check the fix worked

Once the link or redirect is fixed, click **I fixed it** on the incident. Relia watches real visits. After 30 minutes with no new errors it says **Fix confirmed** and sends *Your fix worked*. If visitors hit it again, you get *Still happening after your fix*.

## Next

- [Fix JavaScript errors](https://tryrelia.com/docs/javascript-errors.md)
- [Teach Relia when an alert is wrong](https://tryrelia.com/docs/feedback.md): mark a 404 that is expected so it stops coming back.
- [Users and visitors](https://tryrelia.com/docs/users-and-visitors.md)

---
All Relia docs for AI assistants: https://tryrelia.com/llms.txt (index) · https://tryrelia.com/llms-full.txt (everything in one file)
