Custom 404 Page
Checks that the 404 page is branded with helpful navigation and search.
What this check measures
We request a non-existent URL. Valid 404 status + a branded page with search/nav = pass. Bare "404 Not Found" = fail.
Why it matters
A default 404 bounces ~90% of users. A branded one with search and nav retains most of them. UX + SEO both benefit.
How our audit detects it
Request random non-existent URL. Verify 404 status and count links/search inputs on the response page.
Typical findings
- error_outlineDefault framework 404 with zero branding.
- error_outline404 returns 200 status (soft-404).
- error_outlineNo search, no popular links on 404.
How to fix
Ship a 404 page matching your brand with: "Sorry, this page moved" message, 3-5 popular links, search input. Return 404 status code. In Next.js: `app/not-found.tsx`.
Copy-paste fix prompt for your stack
Lovable · Cursor · Bolt · v0 · Replit · Windsurf · Claude Code · Base44
Frequently asked questions
Should I redirect 404s to homepage?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.