404 Error | Uplithic Learn

Quick definition

A 404 error is an HTTP response indicating that the server did not find the requested resource. A visitor may see a “page not found” message, but the important technical element is the response status, not the wording or design of the page.

A 404 does not necessarily mean the entire website is broken. It may concern one mistyped address, a removed page, an outdated link, or an incorrectly generated URL. The right action depends on whether that resource should exist and whether customers are being directed to it.

What a 404 actually tells you

The response describes the requested resource at that address. It does not, by itself, explain why the resource is missing or whether the absence is intentional.

A missing page can arise from several different situations:

The address was typed incorrectly.
A page was deleted without a replacement.
The resource moved but no suitable redirect was configured.
A link contains an incorrect path or parameter.
A routing or publishing problem makes a valid page unavailable.
An automated crawler requested a URL that never existed.

These cases should not receive the same treatment. Restoring a valuable accidentally unpublished page is different from ignoring a meaningless scanner request.

Begin by establishing the intended state of the URL. A 404 is evidence to investigate, not a diagnosis of the underlying business or technical problem.

Why it matters to marketers

A visitor arriving at a missing page may have responded to an advertisement, clicked an email, followed a recommendation, or tried to return to useful information. The failure interrupts the promise made by that link.

Potential consequences include:

Wasted paid traffic when a campaign points to a missing destination.
Lost inquiries when a service page becomes unavailable.
Reduced confidence when important navigation leads to dead ends.
Frustration when a customer cannot access documentation or support.
Incomplete measurement when the missing page does not load expected analytics.

Impact depends on context. A rarely requested obsolete address may have little business significance, while a broken checkout-related link can be urgent.

Prioritize customer tasks and commercial importance rather than treating every 404 request as equally serious.

Common causes

Understanding the source of the problem helps prevent recurrence.

Content changes: editors remove or rename pages without reviewing incoming links.
Website migrations: the new structure omits old paths or redirect mappings.
Campaign errors: advertisements and emails contain incorrect destination URLs.
Application defects: routing generates invalid links or fails to handle expected addresses.
Case or character differences: the requested path differs from the actual route in a meaningful way.
Expired assets: a download, image, or document is removed while links remain active.
External mistakes: another website links to an incorrect address.

Do not assume the website owner caused every missing request. Automated tools and arbitrary external links can generate large volumes of invalid URLs.

The useful question is whether the missing address represents a real resource or customer journey the business intends to support.

Hard 404 and soft 404

A conventional, or “hard,” 404 returns the actual not-found HTTP status. A soft 404 is a situation in which a page appears to represent missing or inadequate content but returns a different response, often a successful 200 status.

For example, a page may say “this product does not exist” while technically reporting that the request succeeded. Search systems can interpret such mismatches differently from the site's intended behavior.

The visible message tells the person what happened.
The HTTP status tells clients how the request was handled.
The page content helps determine whether a meaningful resource is present.

A useful error page should not return success merely because its navigation and design load correctly. Conversely, a legitimate page should not be treated as missing simply because it has little text; inspect the actual purpose and rendered content.

404 compared with 410 and redirects

Choose the response according to the resource's intended state.

Use 404 when the requested resource is not found and a more specific permanent-removal statement is not appropriate.
Use 410 when the resource has intentionally been removed and is expected to remain unavailable.
Use a permanent redirect when the resource has a suitable lasting replacement.
Use temporary routing when the alternative location is genuinely temporary.
Use an appropriate server-error response when the problem is a temporary service failure rather than a missing resource.

These are distinctions in meaning, not a ranking contest between status codes.

A product temporarily out of stock may still deserve a normal page with accurate availability information. Deleting the page or redirecting it is not automatically the right response to a stock change.

Search implications

A genuine missing resource should not be represented as an available content page. Search systems generally stop using missing URLs over time, but the exact timing is not controlled by a marketer's preference.

The presence of some 404 responses does not establish that a site has a general search-quality problem. Websites naturally accumulate obsolete and invalid addresses.

Focus on actionable issues:

Important pages returning 404 unintentionally.
Internal navigation linking to missing resources.
Valuable moved content without suitable routing.
Missing assets that prevent valid pages from working properly.
Incorrect status handling that misrepresents unavailable content.

Avoid redirecting every missing URL solely to reduce the count in a report. A lower error count can conceal a worse customer experience if visitors are sent to irrelevant pages.

Finding and diagnosing missing pages

Use several information sources because each reveals a different part of the problem.

A site crawl can identify links from current pages to missing destinations.
Server or application logs can show requested URLs and response statuses.
Search reporting can identify missing URLs encountered by search crawlers.
Analytics may reveal visits to an error-page template where tracking is available.
Customer reports can identify failures that automated checks missed.
Campaign audits can test active advertising, email, and partner destinations.

For each important URL, determine how visitors reach it and what they expected to find.

An analytics report alone may undercount failures if the error response does not load tracking. A crawl alone may miss old external links. Combine evidence rather than assuming one tool gives a complete inventory.

Prioritizing the work

A practical triage process separates high-impact defects from harmless noise.

Consider:

Customer impact: does the missing resource block a purchase, inquiry, login, or support task?
Traffic quality: are real customers arriving, or mainly automated requests?
Source importance: does the URL appear in active campaigns or prominent navigation?
Content value: was the missing resource important, current, and intended to remain available?
Replacement availability: is there a genuinely suitable destination?
Recurrence: is a system repeatedly generating similar broken links?

A single broken campaign destination can deserve immediate attention even when its request count is modest. Thousands of requests for random nonexistent paths may require no content action.

Record the decision and reason. This prevents the same intentional removal from being repeatedly escalated as a new defect.

Choosing the correct fix

The fix should restore the intended relationship between the address and the customer task.

Restore the resource if it should still exist and was removed accidentally.
Correct links if the destination address is wrong.
Redirect to a relevant replacement if the resource moved permanently.
Leave an accurate missing response when no resource should exist.
Use a gone response when intentional permanent removal is the appropriate meaning.
Repair routing or publishing defects that cause valid pages to appear missing.

Do not substitute a redirect for understanding the cause. If a content-management system is generating malformed links, adding individual redirects may hide the symptom while allowing new errors to accumulate.

After fixing the source, test the complete journey that originally failed.

Designing a useful error page

A custom error page can help a visitor recover without pretending the requested content exists.

Useful elements include:

A clear statement that the requested page could not be found.
Familiar navigation so the visitor knows they are still on the same website.
A search option when site search is useful.
Links to relevant main sections or support.
A way to report a broken link where appropriate.
A design that remains readable and accessible on common devices.

Keep the page helpful rather than overly promotional. A visitor trying to find a support article may not appreciate an aggressive sales popup.

The error page should still return the correct not-found status. Visual polish and technical accuracy serve different purposes, and both matter.

Worked example: a renamed service page

Imagine a company renames its “Reverse Auction Platform” page during a website redesign. The new page is available, but an email campaign still links to the old address, which returns 404.

The response should address both immediate access and the underlying reference.

Confirm that the new page serves the same customer need.
Configure a suitable permanent redirect from the old address.
Update editable campaign and internal links to the new address.
Test campaign parameters and the inquiry form.
Review whether other renamed pages have the same problem.
Monitor the old address for continued customer traffic.

If the old service had instead been discontinued with no suitable replacement, the decision would differ. The important step is understanding the content relationship before choosing the technical response.

Ecommerce and content lifecycle decisions

Missing-page handling becomes more complex when products, events, jobs, or articles have natural lifecycles.

A product may be temporarily unavailable, permanently discontinued, or replaced by a newer version. An event may have ended but still have useful recordings or information.

Keep a useful page when customers still need specifications, support, or historical context.
Explain temporary unavailability when the resource remains relevant.
Redirect when a genuine replacement satisfies the original intent.
Remove content when it no longer serves a legitimate purpose and no replacement exists.
Review links and campaigns whenever lifecycle status changes.

Do not apply one deletion rule to every content type. A product manual may remain valuable long after sales end, while an expired promotion may need removal or substantial revision.

The marketing and content teams should agree on lifecycle rules before large volumes of pages accumulate.

Monitoring and preventing recurrence

Prevention should focus on the systems that create or distribute links.

Validate important destinations before launching campaigns.
Include URL checks in content publishing and migration workflows.
Review internal links after structural changes.
Maintain clear ownership of high-value downloads and landing pages.
Alert on unexpected failures in important customer journeys.
Keep intentional removals documented so monitoring remains meaningful.

Use thresholds that reflect business importance. A sudden 404 on a primary inquiry page can justify an alert immediately, while a steady stream of meaningless invalid paths may not.

Measure the reduction in broken customer journeys, not merely the reduction in every recorded 404. The latter can encourage unnecessary redirects and make reports look cleaner without improving the site.

Common mistakes and misconceptions

A 404 is not automatically a catastrophe, nor should it automatically be ignored.

Redirecting everything to the homepage often fails to satisfy the original intent.
Returning 200 for a missing-page message misrepresents the resource's state.
Deleting all discontinued-product pages can remove useful customer information.
Treating bot requests as customer demand can waste repair effort.
Fixing only external symptoms can leave broken link-generation logic untouched.
Assuming a designed error page means the HTTP status is correct skips an essential check.
Measuring only request volume can obscure the importance of affected journeys.

The appropriate response is evidence-based triage: establish what should exist, identify who is affected, and repair the actual mismatch.

Frequently asked questions

Do 404 errors automatically damage the whole website's SEO?

No. Missing URLs are a normal part of the web. The important distinction is whether useful, intended pages are missing or whether the requests concern obsolete or invalid addresses. Investigate broken internal links and valuable customer destinations, but do not assume every 404 request creates a site-wide ranking penalty.

Should I redirect all 404 pages to the homepage?

No. A redirect should lead to a relevant replacement. Sending unrelated missing pages to the homepage can confuse visitors and fail to preserve their original task. If no suitable content exists, an accurate missing response with helpful navigation is often more appropriate than an indiscriminate redirect.

Can a 404 page still contain navigation and useful links?

Yes. A custom page can explain the problem and help visitors continue through the site. It should remain clear that the requested resource was not found, and the server should return the correct status. Helpful design does not require presenting the error page as a successful content response.

What is the difference between a 404 and a soft 404?

A 404 is the actual not-found response. A soft 404 describes a mismatch in which the page appears missing or insufficient but does not return the expected missing status, often returning 200 instead. Check both the HTTP response and the rendered content rather than relying only on the page title.

Should an out-of-stock product page return 404?

Not necessarily. Temporary unavailability does not mean the product information has ceased to exist. A useful page can explain stock status, expected availability where known, and relevant alternatives. Permanent discontinuation requires a separate decision based on customer needs, support value, and whether a suitable replacement exists.

How do I know which 404s to fix first?

Prioritize important customer tasks, active campaigns, prominent internal links, and valuable intended content. Review how real users reach the missing address and what they need. A low-volume failure in a purchase journey can be more urgent than a high-volume stream of automated requests for random nonexistent paths.

Related terms

Soft 404: a mismatch between apparently missing content and the response used to deliver it.
301 redirect: a permanent route from an old address to a suitable replacement.
410 status code: an explicit indication that a resource is intentionally no longer available.
Broken link building: an outreach approach involving relevant replacements for broken external links.
Site migration: a change that can create missing URLs if mapping and validation are incomplete.
Log file analysis: examination of request records to understand access, errors, and crawler behavior.