In one paragraph
A 404 page without navigation finding means the sampled not-found response did not contain enough same-host links for this check. Offer meaningful ways to recover, such as a relevant section, homepage, or usable search. Keep the correct error status instead of turning the page into a success response. Link quantity alone does not prove the recovery options match what the visitor needed.
Why it matters
People reach missing URLs through bookmarks, old links, typos, and retired content. A clear error explanation and appropriate next steps can help them continue, without blaming them or pretending the requested resource still exists.
A useful custom page can still return 404. Styling an error inside the site's layout does not require status 200, and changing the status merely to make the design visible can create a soft-error problem. A relevant moved resource may instead warrant a deliberate permanent redirect.
Recovery should reflect context. A retired product, unknown account route, and missing article may need different suggestions. Three unrelated footer links are not necessarily more helpful than a small set of well-chosen actions.
How WebAuditOS evaluates this finding
The supplied rule examines the first actual 404 encountered in the crawl rather than requesting its own missing URL for this assessment. It counts same-host anchor links, ignoring the documented www variation and excluding fragment-only or script destinations.
Three or more links passes; two or fewer warns informationally. No crawled 404, or an unavailable rendered client-side case, can leave it ungraded. It does not validate all section-specific error templates, link relevance, search quality, or recovery completion. The separate soft-404 probe has another scope.
How to fix it
- Open a safe nonexistent URL and inspect the actual status and displayed page. Check multiple application sections if different systems serve their own error templates.
- Explain that the requested page could not be found without exposing internal errors or repeating untrusted URL text unsafely. Keep the message understandable and proportionate.
- Offer relevant native links. A structural example is:
<main><h1>Page not found</h1><p>Try a relevant section or return to the homepage.</p><a href="/">Homepage</a><a href="/guides">Guides</a><a href="/contact">Contact</a></main>Use destinations that exist and help your audience. This example illustrates recovery, not a mandatory three-link design or a complete error template.
- Add search only if it works for the content and remains appropriately labelled and keyboard-operable. An empty search widget is not automatically a better recovery mechanism.
- Preserve the 404 status through application, hosting, and CDN layers. A successful asset response or a branded screenshot does not verify the document's HTTP status.
- For genuinely moved equivalents, map the old URL to the relevant replacement instead of sending all missing content to the homepage. Keep a useful real not-found path for unknown resources.
- Test focus, mobile layout, zoom, and the actual onward links while signed out. Check that authentication boundaries and error-page scripts do not prevent recovery.
- Rescan and review observed missing-entry journeys where appropriate. A site with no crawled 404 has not necessarily had its error-page usability tested by this rule.
What the fix can break
Reusing a normal layout can fail if it depends on the same service causing the error. Keep essential recovery robust enough to work in relevant failure conditions.
Do not return 200 merely to keep navigation available. Error status and useful page content can coexist.
A hard-coded link set can become stale after another migration. Maintain it like the rest of navigation rather than treating the error page as a one-time asset.
Questions
Does no grading mean the 404 template is good?
No. The crawl may simply never have encountered a 404 for this check to inspect.
Are three links a usability standard?
No. They are the supplied detector's threshold. Actual recovery depends on purpose and working destinations.
Can a custom design still return 404?
Yes. Keep the correct status while providing useful content.
Which related checks help?
Review soft 404s, navigation, and broken links.