What Is a 404 Page?
A 404 page is the page a website shows when a visitor requests a URL that does not exist, named after the HTTP 404 'Not Found' status code the server returns. It appears after mistyped addresses, outdated links, or deleted pages. A good custom 404 page acknowledges the error, keeps the site's branding, and offers helpful next steps, like search or navigation, so a dead end becomes a recovery point instead of a lost visitor.
- Status code
- HTTP 404 means the server found nothing at that URL (HTTP spec, RFC 9110)
- Correct behavior
- A true 404 returns a 404 status, not a 200 'OK' (soft 404 is a common error) (Google Search Central)
- Not indexed
- Search engines drop 404 URLs from the index over time (Google Search Central)
- Best practice
- Custom branded page with navigation, search, and a link home (UX convention)
What is a 404 page? #
A 404 page is what a website displays when someone asks for a page that is not there. Every time a browser requests a URL, the server replies with a status code; 404 is the code for 'Not Found,' meaning the address is valid syntactically but nothing lives at it. This happens for ordinary reasons: a visitor mistypes a URL, clicks a link that points to a page that was moved or deleted, or follows an outdated bookmark. Left to defaults, the server shows a bare, technical 'Not Found' message that looks broken and confusing. A custom 404 page replaces that with a branded, friendly screen that explains what happened and helps the visitor get back on track. Designing a helpful 404 is part of thorough /services/web-design and the safety net an agency builds into a site. It connects to how a site handles URLs and redirects, topics that also come up during /services/website-migrations and /services/website-redesign, where changing URLs can accidentally create the very dead links a good 404 page catches.
Why does a good 404 page matter? #
A 404 page matters because it turns a moment of failure into a chance to keep a visitor. Someone who hits a dead end is, by definition, already interested enough to have clicked or typed a URL; losing them there is a wasted lead. A default error screen tells them nothing and often makes them assume the whole site is broken, so they leave. A well-designed custom 404, by contrast, calmly says the page could not be found, keeps your logo and colors so the visitor knows they are still on your site, and offers clear ways forward: a link to the homepage, a search box, or links to popular pages and services. For a local business, that might mean guiding a lost visitor straight to the contact or booking page, recovering a call that would otherwise vanish. This recovery function ties directly into /services/conversion-optimization. A thoughtful 404 also signals professionalism; caring enough to design even the error page tells customers you sweat the details, which quietly reinforces trust across the whole site.
What makes a good 404 page? #
A strong 404 page does four things. First, it clearly and plainly tells the visitor the page was not found, without cryptic jargon, so there is no confusion about what happened. Second, it keeps the site's branding, header, logo, colors, and navigation, so the visitor knows they are still on your site and can move around normally. Third, it offers concrete next steps: a prominent link home, a search box, and links to your most important pages, such as services or contact, so the visitor is not stranded. Fourth, it keeps the tone helpful and on-brand, sometimes with a touch of light personality, though clarity always beats cleverness. What it should avoid is a bare technical message, a dead end with no navigation, or anything that makes the site feel broken. Getting these elements right is part of the polish delivered in /services/ui-ux-design and /services/web-design. For businesses in trades like /web-design-for-plumbers, a 404 that funnels a lost visitor toward an emergency phone number can directly rescue an urgent lead that would otherwise slip away.
How does a 404 differ from a soft 404? #
A crucial technical distinction separates a real 404 from a 'soft 404.' A proper 404 page returns the HTTP 404 status code, telling browsers and search engines that the page genuinely does not exist. A soft 404 is a page that shows a 'not found' message to humans but mistakenly returns a 200 'OK' status code, telling machines the page exists and is fine. Soft 404s confuse search engines, which may keep the empty or error page in their index, waste crawl budget, and dilute a site's quality signals, problems Google Search Central specifically warns against. This is a common misconfiguration on DIY and poorly built sites, and it is exactly the kind of issue an /tools/website-grader or a technical audit surfaces. The fix is to ensure the server returns a true 404 status for missing pages while still displaying your friendly custom design. Handling status codes correctly is a routine but important part of professional /services/web-design and any /services/website-migrations project, where mismanaged URLs can otherwise scatter soft 404s across a site.
<?php
// Ensure the server sends the real 404 status,
// not a 200 'OK', before showing the custom page.
http_response_code(404);
?>
<h1>Page Not Found</h1>
<p>Sorry, we couldn't find that page.
<a href="/">Return home</a> or use search.</p>Do 404 pages affect SEO? #
404 pages themselves are a normal, healthy part of the web and do not harm SEO when handled correctly, in fact, returning a proper 404 for a page that truly no longer exists is exactly what search engines want. Over time, Google drops legitimately missing URLs from its index, which is correct behavior. Problems arise not from 404s but from mismanagement: large numbers of internal links pointing to 404s waste crawl budget and frustrate users, and soft 404s that return 200 confuse indexing. The SEO-smart approach is to monitor which URLs are returning 404s, using tools and search console data, and decide case by case: if a page moved, set up a redirect to the new location so link value transfers; if it is genuinely gone with no replacement, let it 404 cleanly. This maintenance overlaps with the link-hygiene work behind /services/local-seo and is exactly what a /tools/broken-link-checker helps automate. A well-managed site keeps its 404s meaningful and rare, using redirects where appropriate and a helpful custom 404 page to catch the rest.
404 versus redirects: when to use each #
When a page disappears, you have two main options, and choosing correctly matters. If the content moved to a new URL, or a close equivalent exists, the right move is a 301 redirect that sends both visitors and search engines automatically to the new page, preserving the link value the old URL earned. If the content is truly gone with no replacement, letting the URL return a clean 404 (or a 410 'Gone') is appropriate, and your custom 404 page then catches any visitors who land there. The mistake to avoid is redirecting every missing page to the homepage, which frustrates users who expected specific content and can be treated by search engines as a soft 404. This decision-making is central to /services/website-migrations and /services/website-redesign, where whole sets of URLs may change at once and careless handling can spawn hundreds of broken links overnight. A disciplined redirect map plus a strong custom 404 page ensures that visitors and search engines are guided sensibly rather than dumped at dead ends, protecting both user experience and the SEO equity built up over years.
How do you find and fix broken links? #
Because 404s often stem from broken links, keeping them in check means regularly finding and fixing those links. Broken links come from internal references to pages that were renamed or deleted, from external sites linking to old URLs, and from typos. The practical workflow is to crawl your site periodically with a /tools/broken-link-checker, review the list of 404-generating URLs, and act on each: repair or update internal links that point to the wrong place, set up 301 redirects for pages that moved, and confirm that genuinely removed pages return a clean 404. Search Console's coverage reports also flag URLs Google is finding as not found, which is valuable because they reveal what real users and crawlers are hitting. This upkeep is part of ongoing site health, the kind of routine maintenance bundled into /services/care-plans, and it is especially important after a /services/website-redesign or migration when URL structures change. Staying on top of broken links keeps visitors from hitting dead ends, preserves SEO value through proper redirects, and ensures your custom 404 page remains a rare backstop rather than a page people see constantly.
How a 404 page fits site quality #
A custom 404 page is a small but telling indicator of overall site quality. Sites built with care handle the unhappy paths, errors, dead ends, missing pages, as thoughtfully as the happy ones, while rushed or DIY sites leave visitors staring at raw server errors. Along with correct status codes, sensible redirects, and monitored broken links, a good 404 page is part of the technical and experiential polish that separates a professional build from an amateur one. It also connects to broader site management: the same discipline that produces a helpful 404 page keeps URLs stable through redesigns and migrations, maintains clean internal linking, and monitors for problems over time, all of which support both user experience and search performance. For local businesses relying on their site to capture leads, that reliability matters; a visitor who hits a dead end and finds a clear path back is a lead saved. Treating the 404 page as a real design deliverable, not an afterthought, is the mark of the thorough /services/web-design and /services/care-plans approach that keeps a business site working even when something goes wrong.
FAQ
What does a 404 error actually mean?
It means the server received a valid request but found no page at that URL, so it returns the HTTP 404 'Not Found' status code. This commonly happens after a mistyped address, an outdated link, or a deleted page. The 404 itself is normal web behavior; the goal is to catch it with a helpful custom page rather than a bare error.
Should I redirect all 404 pages to my homepage?
No. Redirecting every missing page to the homepage frustrates visitors who expected specific content and can be treated as a soft 404 by search engines. Instead, 301-redirect pages that genuinely moved to their new location, and let truly gone pages return a clean 404 that your custom 404 page catches with helpful navigation.
What is a soft 404 and why is it bad?
A soft 404 is a page that shows a 'not found' message to humans but incorrectly returns a 200 'OK' status to machines. It confuses search engines, which may keep empty pages indexed and waste crawl budget. The fix is ensuring missing pages return a true 404 status while still showing your friendly custom design.
Do 404 pages hurt my search rankings?
Not when handled correctly. Returning a proper 404 for a page that truly no longer exists is exactly what search engines expect, and they drop those URLs over time. Problems come from soft 404s, many internal links pointing to dead pages, or failing to redirect content that moved, not from legitimate 404s themselves.
What should a good custom 404 page include?
It should clearly say the page was not found, keep your branding and navigation so visitors know they are still on your site, and offer next steps: a link home, a search box, and links to key pages like services or contact. A helpful tone and a path forward turn a dead end into a recovery point.
How do I find broken links causing 404s on my site?
Crawl your site periodically with a broken link checker and review Google Search Console's coverage reports, which flag URLs found as not found. Then act on each: fix internal links pointing to the wrong place, set up redirects for moved pages, and confirm truly removed pages return a clean 404. This upkeep keeps dead ends rare.
Was this helpful?