Bug: No 404 Not Found page #88

New Issue

Closed

opened 2026-05-17 21:15:12 -05:00 by null · 0 comments

null commented

2026-05-17 21:15:12 -05:00

Owner

Problem

The router has no catch-all/404 route. If a user navigates to a non-existent path (e.g. /foo), they see a blank white page with no navigation back.

Fix

Add a wildcard route to src/router.jsx that renders a 404 component with links back to Home, Services, etc. Include proper Helmet meta tags.

Files

src/router.jsx - add path: * route
src/pages/NotFound.jsx - new file

Severity

Medium - users hitting dead links see a broken experience with no way to recover

## Problem The router has no catch-all/404 route. If a user navigates to a non-existent path (e.g. /foo), they see a blank white page with no navigation back. ## Fix Add a wildcard route to src/router.jsx that renders a 404 component with links back to Home, Services, etc. Include proper Helmet meta tags. ## Files - src/router.jsx - add path: * route - src/pages/NotFound.jsx - new file ## Severity Medium - users hitting dead links see a broken experience with no way to recover