1.6 HTTPS / security / infrastructureLowIndustry consensus

No custom 404 page

A bare default error page is a dead end for users who land on a broken link. A custom 404 that returns the correct status but offers navigation keeps people on the site.

What it is

Default error page.

Why it matters

Minor UX loss; correct 404 status still matters more than styling.

How to fix it

Add a helpful 404 with navigation; keep the 404 status.

How to find it on your site

  1. Visit a URL that does not exist and see what is served.
  2. Confirm it returns a real 404 status, not a 200, with curl -I.
  3. Design a helpful 404 with search and links back into the site.
  4. Keep returning the 404 status so the page is not indexed.

Cross-reference to ranking and citation factors

A custom 404 is a user-experience and retention improvement rather than a direct ranking factor, as long as it still returns 404.

Impact

Low. Consensus.

Evidence

Return proper 404 status; a helpful page aids UX. Google Search Central, How HTTP status codes affect Google Search