Information checked: 21 July 2026.
A custom 404 page should confirm that the requested page is unavailable while helping the visitor recover. It must still return an actual 404 HTTP status; a friendly design served with 200 OK creates a soft 404 and sends a misleading technical signal.
In brief: Return the correct status, explain plainly and offer a few useful recovery routes.
Include only useful recovery tools
- A clear statement that the page could not be found.
- A link to the home page and main categories.
- Site search when it works well.
- A contact or corrections route for an important missing page.
- The normal header and footer, provided they do not mask the error.
Avoid common mistakes
404 mistakes
- Automatic redirect to home
- Confuses users and may appear as a soft 404
- 200 status with error message
- Search engines cannot reliably treat it as missing
- Huge list of links
- Creates another navigation problem
- Blaming the visitor
- Reduces trust
- No monitoring
- Valuable broken internal and external links remain unknown
Use 404 data carefully
Review referrers, requested paths and frequency. Fix broken internal links immediately. Redirect a misspelling or moved URL only when a close equivalent exists; do not redirect every unknown path.
Final verification
Request a random nonexistent URL, confirm the HTTP 404 response, test recovery links and verify the event appears in the chosen monitoring or analytics process without storing sensitive URL data.
The most common weak point
A custom error design can accidentally return 200 OK because the CMS renders it like a normal page. It may also include a search form or navigation that fails for the same reason as the requested page. Without logging, recurring broken internal links remain invisible.
Evidence and records to preserve
- Approved 404 template
- HTTP-status test evidence
- Broken-link monitoring report
- High-value missing-URL decisions
- Owner for recovery links and search
Start with this
Request five random paths and five known deleted URLs using an HTTP checker. Confirm status, content, internal recovery links and monitoring for each.
Sources and date checked
This practical guidance was checked against the following primary sources. Date checked: 21 July 2026.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.