404 Error

A 404 error is an HTTP status code returned by a web server when a requested page does not exist at the specified URL, signaling to both users and search engines that the content they’re looking for is unavailable at that address.

What 404 Error Means in Practice

When a user or search engine crawler requests a URL, the server responds with an HTTP status code that indicates the result of that request. A 200 status code means success. A 301 redirect means the content has permanently moved. A 404 status code means the server received the request, understood it, but couldn’t find any content at that URL. The page simply doesn’t exist.

404 errors occur for several common reasons. The page was deleted without a redirect in place. The URL was mistyped in a link, either internally or on an external site. The site’s URL structure changed during a migration or redesign, and not every old URL was mapped to a new destination. A product was removed from an ecommerce catalog. A location was closed and its page was taken down. In every case, the result is the same: a user or crawler arrives at a URL and finds nothing there.

The distinction between a hard 404 and a soft 404 is important for SEO. A hard 404 returns the correct 404 HTTP status code, which tells search engines clearly that the page doesn’t exist. Google processes this signal, removes the URL from its index, and moves on. A soft 404 is a page that displays a “not found” message to users but returns a 200 (success) status code in the HTTP response. This confuses search engines because the server says the page loaded successfully, but the content is a dead end. Google Search Console specifically flags soft 404s as an indexing issue because they waste crawl budget on pages that have no real content.

For multi-location businesses, 404 errors tend to appear in patterns. When a location closes, its pages need to be properly handled. When a healthcare organization acquires new practices and migrates their websites, hundreds of old URLs may become orphaned. When a franchise network rebrands and changes its URL structure, every old location page becomes a potential 404. The scale of the problem is proportional to the size of the site, and we’ve seen portfolios with thousands of unresolved 404 errors that accumulated over years of acquisitions, closures, and migrations.

Custom 404 pages play a role in damage control. When a user hits a 404, the default server error page provides no navigation, no branding, and no path forward. A custom 404 page maintains your site’s design, offers search functionality, links to popular pages, and gives the user a way to continue their visit. While a custom 404 page doesn’t fix the underlying URL issue, it reduces the chance that a 404 error turns into a permanent lost visitor.

Monitoring 404 errors is an ongoing maintenance task, not a one-time audit item. New 404 errors can appear at any time. External sites may link to URLs that no longer exist. Internal links may reference pages that were removed. CMS updates or URL slug changes can create 404s without anyone noticing. Google Search Console’s Pages report surfaces these errors systematically, and regular monitoring catches issues before they compound into significant traffic or crawl budget problems.

Why 404 Error Matters for Your Marketing

404 errors directly affect two things that matter for your marketing performance: user experience and search engine crawl efficiency. Every 404 error a user encounters is a broken promise. They clicked a link expecting content and got nothing. Depending on how they reached the URL, they may not try a second path to find what they were looking for. They may leave your site entirely. For pages that previously ranked and drove traffic, an unresolved 404 means that traffic goes to zero permanently.

Google’s documentation on HTTP status codes explains that while 404 errors don’t directly penalize a site’s overall rankings, excessive 404s waste crawl budget and can indicate broader site quality issues. When Googlebot encounters a 404, it records the error and may recrawl the URL later to see if it’s been resolved. Multiply that across hundreds of 404 URLs and you’re consuming crawl budget on pages that return nothing, reducing the budget available for your actual content. For large sites with tens of thousands of pages, this crawl budget impact becomes measurable.

The business case for fixing 404 errors is straightforward. If a page that was generating 500 organic visits per month returns a 404, you’ve lost those 500 visits and whatever conversions they produced. If 50 external sites linked to that page and it now returns a 404, you’ve lost the link equity from those backlinks. A single 301 redirect from the old URL to the most relevant replacement page recovers both the traffic and the link value. For organizations with large content libraries or frequent site changes, systematic 404 monitoring and resolution is one of the highest-ROI technical SEO activities.

How 404 Errors Work

At a technical level, a 404 error is generated when a web server receives a request for a URL path that doesn’t match any file, route, or resource in its configuration. The server responds with an HTTP 404 status code in the response header, and typically serves an error page as the response body. The browser renders that error page for the user, and the interaction ends there unless the user navigates elsewhere manually.

Finding 404 errors on your site starts with Google Search Console. The Pages report (under Indexing) shows URLs that returned 404 responses when Googlebot attempted to crawl them. This includes both hard 404s and soft 404s, reported separately so you can address each type appropriately. For a more comprehensive view, run a site crawl using tools like Screaming Frog or Sitebulb, which will check every internal link on your site and flag any that return 404 status codes. This catches internal linking issues that Search Console may not surface because they depend on Googlebot’s crawl patterns.

Resolving 404 errors requires a decision for each URL. If the content has moved to a new URL, implement a 301 redirect to the new location. If the content was consolidated into another page, redirect to that page. If the content was removed and there’s no relevant replacement, let the 404 stand. Not every 404 needs a redirect. Redirecting deleted pages to your homepage or to irrelevant pages creates a poor user experience and sends misleading signals to search engines. Google treats mass homepage redirects as soft 404s anyway. The key is to redirect when there’s a genuinely relevant destination and accept the 404 when there isn’t.

Common mistakes include ignoring soft 404s, which look fine to users but waste crawl budget because the server returns a 200 status code. Another frequent issue is creating redirect chains when fixing 404s. If URL A was redirected to URL B in a previous round of fixes, and URL B now returns a 404, redirecting URL B to URL C creates a chain. Update the original redirect so URL A points directly to URL C. For multi-location sites, a common pattern is failing to handle closed location pages. Rather than returning a 404 or redirecting to the homepage, the best practice for closed locations is to redirect to the nearest open location page or to a location finder page, preserving both user experience and whatever local search equity the closed location’s page had accumulated.

External Resources

• Google Search Central: HTTP status codes — Google’s official documentation on how Googlebot handles 404 errors, soft 404s, and other HTTP response codes
• Google Search Console Help: Page indexing report — How to use Search Console to find and diagnose 404 errors and soft 404 issues on your site
• Conductor: What Are 404 Errors? — A practitioner-level overview of 404 errors, their SEO impact, and best practices for resolution
• Ahrefs: How to Find and Fix 404 Errors — A step-by-step guide to auditing 404 errors using crawl tools and fixing them with redirects
• Search Engine Journal: 404 Errors and SEO — How 404 errors affect rankings, crawl budget, and user experience, with practical fix recommendations

Related Resources

• Site Structure and Links: Understanding the SEO Impact of Changes — How URL changes, redirects, and 404 errors affect site architecture and organic search performance
• The Technical SEO Audit Guide — How 404 errors are identified and prioritized during a technical SEO audit
• Enterprise SEO: What Makes It Different and How to Get It Right — Managing 404 errors at scale across large sites with thousands of pages and frequent structural changes
• The Ultimate SEO Checklist — 404 monitoring and resolution as part of a complete technical SEO maintenance routine

Related Glossary Terms

• 301 Redirect: A permanent URL forwarding instruction that sends users and search engines from one URL to another. 301 redirects are the primary tool for resolving 404 errors when a relevant replacement page exists.
• Crawl Budget: The number of pages a search engine will crawl on your site within a given timeframe. Excessive 404 errors and soft 404s waste crawl budget on URLs that return no indexable content.
• Google Search Console: Google’s free tool for monitoring search performance and site health. Search Console’s Pages report is the primary tool for identifying and tracking 404 errors on your site.
• Technical SEO: The practice of optimizing a website’s technical foundation for search engine crawling and indexing. 404 error management is a fundamental component of ongoing technical SEO maintenance.