What Is HTTP Status Code 404?

Ready to start learning? Individual Plans →Team Plans →

When a browser shows http 404, the server is usually up. The problem is simpler and more frustrating: the resource at that exact URL is missing, renamed, moved, or never published in the first place. For site owners, that means broken links, lost traffic, and avoidable SEO damage. For users, it means a dead end.

Quick Answer

HTTP status code 404 is the standard “Not Found” response, meaning the server is reachable but cannot locate the requested resource at that URL. It can affect pages, images, PDFs, JavaScript files, CSS files, and API endpoints. The right fix is usually to restore the asset, add a 301 redirect, or improve the custom 404 page when no replacement exists.

Quick Procedure

  1. Verify the exact URL in a clean browser session.
  2. Check whether the content moved, was renamed, or was deleted.
  3. Restore the missing file or page if it still matters.
  4. Set a 301 redirect when a close replacement exists.
  5. Update internal links, campaign URLs, and bookmarks.
  6. Review Search Console and server logs for repeat 404s.
  7. Improve the custom 404 page so users can recover quickly.
Status MeaningNot Found as of November 2026
Primary UseResource missing at the requested URL as of November 2026
Common CausesBroken links, moved content, deleted files, typoed URLs as of November 2026
Typical FixesRestore content, add 301 redirect, update links as of November 2026
SEO ImpactCan waste crawl budget and weaken link equity as of November 2026
Best PracticeUse a real 404 status with a helpful custom page as of November 2026

What HTTP Status Code 404 Means

HTTP status code 404 is the standard web response for “Not Found.” It tells the client that the server understood the request, but the specific resource at that address is unavailable. That distinction matters because a 404 is not the same thing as a server outage or a broken network connection.

In practical terms, the server is reachable and working. The issue is the resource mapping: the URL points to something that no longer exists, has moved, or was typed incorrectly. This is why the query http 404 error often appears alongside misunderstandings like “the server is down,” when the server is actually fine.

A 404 can apply to more than a webpage. You may see it for an HTML page, an image, a PDF, a stylesheet, a JavaScript file, or even an API endpoint. The same status code can also show up in device integrations, such as http 404 arlo or http 404 arlo google home issues when a device or service requests a URL that is no longer available.

The official definition comes from the Internet Engineering Task Force’s HTTP semantics work, which describes 404 as a client error indicating that the origin server did not find a current representation for the target resource. You can review that behavior in the IETF RFC for HTTP semantics and the broader HTTP status code model in the IETF RFC 9110.

A 404 is a location problem, not automatically a system failure.

  • 200 OK means the resource was found and returned successfully.
  • 301 Moved Permanently means the resource now lives at a new URL.
  • 404 Not Found means the requested resource cannot be located at the current address.

Why HTTP 404 Errors Happen

Most 404s come from simple URL mismatches. A link may point to a page that was renamed, deleted, or never published. A typo in the path, filename, or folder can produce the same result. In search results, this often appears as 404 code or cod 404, depending on how the query was entered.

Broken internal links are one of the most common causes. If a content team changes a slug from /services/cloud-security to /solutions/cloud-security and forgets the redirect, every old link becomes a dead end. The same happens when old campaign URLs continue to circulate in email archives, partner websites, PDFs, social posts, and bookmarks.

Deployment and content migration issues also create 404s. During a CMS migration, a page may be published in the new system but not mapped correctly in the routing layer. A file may be present in staging but missing from production after deployment. This is why teams need a clear release process and redirect map before content moves.

API consumers trigger 404s too. If a developer requests a deprecated endpoint, mistypes the route, or calls an old version of an API after a platform change, the response is often a clean 404. That is normal behavior for a missing resource, but it becomes a support problem when the API contract is not documented or versioned properly.

  • Broken internal links from menus, footers, and related-content blocks.
  • External links pointing to content that was removed or moved.
  • Typos in URLs, filenames, and folder paths.
  • Deployment mistakes that omit files from production.
  • CMS changes that alter slugs without redirect rules.
  • API requests for deprecated or mistyped endpoints.

For context, Google Search Central explains that 404 responses are expected when content is gone, but persistent or widespread 404s can harm crawl efficiency and user experience. See Google Search Central on 404 and soft 404 handling.

How Do You Diagnose a 404 Error?

The fastest diagnosis starts with the URL itself. Open the address in a clean browser session, preferably in an incognito window, and retype it carefully. This rules out auto-corrected paths, copied whitespace, and cached browser behavior. If the URL works in one context but not another, the problem may be client-side rather than site-side.

Next, check whether the resource still exists under a different name or location. Content is often moved from one slug to another during redesigns, category changes, or repository reorganizations. A page that used to live at one path may now exist in a new directory or under a new filename. If so, the correct fix is usually a redirect, not a replacement page.

Then verify whether the resource was intentionally removed. If the page was merged into a broader article, archived, or retired because it no longer serves a purpose, leaving it as a 404 may be correct. The key question is whether users have a meaningful replacement. If they do, redirect them. If they do not, keep the 404 and make the recovery path better.

Note

Search Console, analytics, and server logs usually tell a clearer story than a single browser test. One URL might be a typo, but repeated hits from search bots, partners, or campaign traffic point to a broader problem.

Use Google Search Console to inspect indexing and crawl issues, and review your web server logs for repeated requests to the same dead URL. On Apache, look at access logs; on Nginx, inspect the access log for 404 status entries. If the same URL appears many times, that is a maintenance issue, not a one-off misspelling.

Also watch for redirect chains. A request that starts as a valid URL can fail if it passes through a bad redirect sequence and lands on a missing destination. A user sees a 404, but the real issue is in routing or configuration. This is why diagnosis should include both the original URL and the final destination URL.

How to Fix a 404 on Your Site

The right fix depends on whether the missing resource still matters. If the page or file has business value, restore it. If the content moved permanently, redirect it. If it was removed for good and has no relevant replacement, keep the 404 but improve the page experience. That simple decision tree prevents the most common mistakes.

  1. Restore the content if it still belongs on the site.

    If a page, PDF, image, or script file was deleted by accident, put it back exactly where the site expects it. This is the best option when the resource still has traffic, backlinks, or operational value. A missing downloadable spec sheet or support document is often better restored than redirected.

  2. Set a 301 redirect for permanent moves.

    A 301 redirect tells browsers and search engines that the content now lives at a new URL. This is the correct fix for renamed pages, folder changes, product page updates, and content consolidations. Point the old URL to the closest relevant destination, not just the homepage.

  3. Update internal links across the site.

    Menus, footers, breadcrumbs, related articles, and in-content links should point to the new location. Internal link cleanup matters because crawlers and users both follow those paths. If a popular page still links to a dead URL, the problem will keep resurfacing even after a redirect exists.

  4. Repair missing assets and downloads.

    If an image, stylesheet, JavaScript file, or PDF returns 404, check the build pipeline, file path, and deployment package. Missing assets can break a page visually or functionally even when the HTML page itself loads. In a front-end framework, one missing bundle file can make an entire interface appear broken.

  5. Redirect high-value backlinks carefully.

    If external websites link to the dead URL, preserve that value with a relevant redirect. A strong backlink should not vanish because a URL changed. Review linking pages in analytics, Search Console, and backlink tools, then map those old URLs to the best live equivalents.

For redirect best practices, review official guidance from Google Search Central on redirects. For HTTP behavior and status-code semantics, the IETF RFC remains the technical reference point.

How Does HTTP 404 Affect SEO?

HTTP 404 affects SEO when dead URLs become common, repeated, or unmanaged. A few intentional 404s are normal. A large volume of unhandled 404s can waste crawl budget, dilute link equity, and create a poor signal about site maintenance. Search engines do not punish a site for having any 404s; they react to patterns that suggest low quality or sloppy structure.

Crawl budget matters more on large websites. If search bots repeatedly request dead URLs, they spend less time on pages that matter. That is a problem for news sites, ecommerce catalogs, knowledge bases, and any site with many URL changes. Google’s documentation explains that persistent errors can consume crawl resources that would otherwise go to useful pages.

Broken backlinks create another SEO loss. If a high-authority page on another site points to a dead URL and there is no redirect, the link equity is stranded. A relevant 301 redirect can recover much of that value. A random redirect to the homepage usually does not help users or search engines because it does not match intent.

SEO issue Broken URLs can reduce discoverability, waste crawl effort, and weaken referral value as of November 2026
Best response Redirect only when a closely related replacement exists as of November 2026

User experience also matters. A visitor who lands on a dead page often leaves quickly, especially if the page gives no recovery path. That can increase bounce behavior and reduce conversions. A strong custom 404 page can soften the blow, but it does not replace the need to clean up bad URLs.

Google’s official guidance on soft 404s is especially important here. A page that looks useful but actually provides no real content can be treated as a soft 404, which means the site is sending the wrong signal. See Google’s soft 404 documentation for how search systems evaluate these pages.

When Should You Use a 404 Instead of a Redirect?

Use a 404 when the content genuinely no longer exists and there is no meaningful replacement. That is the cleanest and most honest response when the old page has no useful successor. In those cases, forcing users to an unrelated destination creates confusion and can reduce trust.

Redirects are appropriate when the user intent still makes sense. If a blog post moved to a new slug, the old URL should redirect. If a product page was consolidated into a newer version, the old page should redirect. If an expired offer is gone and there is no close alternative, a 404 is better than sending users to a page they did not request.

That difference matters for both SEO and usability. Irrelevant redirects can look like a soft suppression tactic to users, especially if every missing URL dumps them onto the homepage. Search engines also prefer redirect targets that preserve topical relevance. A good redirect answers the user’s likely intent.

  • Use a 404 for deleted low-value pages with no replacement.
  • Use a 404 for expired assets that should not be resurrected.
  • Use a 404 for unsupported API endpoints that are truly retired.
  • Use a 301 for renamed pages, moved assets, and content consolidations.

A custom 404 page can still be useful even when the response remains 404. The page can offer search, navigation, popular content, or support links without pretending the missing page still exists. That preserves honesty while improving recovery.

How Do You Create a Better Custom 404 Page?

A good custom 404 page does not hide the error. It helps the user recover from it. The best pages are clear, calm, and useful. They explain that the requested page could not be found, then offer a path forward instead of a dead-end message or technical jargon.

Include navigation elements that match real user needs. A home link is essential. A site search box is even better, especially for content-heavy sites. Add links to popular pages, main categories, or support resources. If the site serves documentation or products, include top-level documentation hubs or category landing pages.

Keep the tone human. A message like “We couldn’t find that page, but you can still find what you need here” works better than “Error 404 occurred.” That is especially true for non-technical audiences. For technical audiences, it is still better to speak plainly and focus on recovery, not code.

Warning

Do not build a custom 404 page that returns 200 OK. A page that looks like an error page but sends a success status can become a soft 404 and create SEO problems.

Also test the page for accessibility and mobile usability. The search field should be usable by keyboard. Links should be easy to tap on small screens. If possible, include a help contact or chatbot link for users who are clearly stuck. The goal is not just to acknowledge the error; it is to preserve trust and reduce abandonment.

In environments with frequent typo traffic, custom pages can also suggest likely destinations. If a user enters a product path with one character missing, the 404 page can recommend the closest matching page. That is especially useful on large catalog sites, documentation portals, and internal knowledge bases.

What Tools Help You Find 404s Faster?

The fastest way to find 404s is to combine search data, logs, and crawl checks. No single tool catches everything. Search Console shows what Googlebot sees. Server logs show what real visitors and crawlers actually request. Site crawlers find broken internal links before users do.

Google Search Console is the best starting point for search visibility problems. Check indexing reports, page indexing issues, and crawl statistics for repeated not found URLs. If one old URL continues to appear in reports, that usually means the issue has not been fully cleaned up.

Server logs are the most direct source of truth. They show the exact request path, user agent, timestamp, and response code. That makes them valuable for spotting patterns such as a broken marketing link that sends thousands of visitors to the same dead page. A log review can also reveal bots repeatedly hammering obsolete URLs.

  • Search Console for indexing and crawl visibility.
  • Server logs for exact request patterns and response codes.
  • Website crawlers for broken internal links and missing assets.
  • Analytics for traffic landing on dead URLs from campaigns or referrals.
  • Post-release audits after redesigns, CMS changes, and migrations.

Routine checks matter most after deployments and content changes. If a site migration went live on Friday and no one reviewed redirect coverage on Monday, a 404 problem can quietly spread for weeks. That is why IT and content teams should treat URL audits like any other release validation step.

How Can Developers and Content Teams Prevent 404s?

Prevention starts with change control. Every URL change should include a redirect plan before the old content is moved or removed. That plan should identify the old URL, the new URL, the reason for the change, and the owner responsible for testing it. Without that mapping, small edits become ongoing support tickets.

Use consistent naming conventions for URLs, files, and folders. Predictable patterns reduce accidental breakage and make it easier to spot errors during code review or content review. If your team uses slug-based URLs, avoid changing slugs unless there is a strong reason. Stability is valuable because links live longer than redesigns.

Coordinate across teams. Content editors, developers, SEO specialists, and release managers should all know when a page moves. The person publishing the update may not know which external links still point to the old path, so ownership has to be shared. A redirect map and post-release test list should be standard deliverables.

  1. Document every URL change before it goes live.
  2. Map old URLs to new destinations with relevant redirects.
  3. Test pages, downloads, and templates after deployment.
  4. Review analytics and logs for dead-link traffic after release.
  5. Maintain redirect documentation so future teams can trace changes.

For teams that work with structured change management, this is a straightforward governance issue. Better mapping prevents more than 404s; it protects campaign performance, user confidence, and search visibility. The best time to fix a broken URL is before anyone notices it is broken.

What Mistakes Should You Avoid with 404 Errors?

One of the biggest mistakes is leaving valuable removed pages without redirects. If the page had traffic, backlinks, or strong search visibility, deleting it outright often wastes equity that could have been preserved. A relevant redirect is usually the right answer when the old page still has intent value.

Another common mistake is redirecting everything to the homepage. That is a poor substitute because it ignores user intent. A visitor looking for a specific white paper, product, or support article should not be dumped onto a generic landing page. Search engines also treat irrelevant redirects as weaker signals.

Teams also make the mistake of ignoring repeat 404s in logs. If one URL keeps appearing from the same source, it is usually not random. It could be a broken email link, an outdated partner reference, or a page that still attracts search traffic. Repeated misses deserve investigation.

  • Don’t delete valuable pages without a redirect plan.
  • Don’t send everything to the homepage as a shortcut.
  • Don’t ignore repeated 404 patterns from search engines or partners.
  • Don’t use a fake 404 page that returns 200 OK.
  • Don’t confuse 404 with permission errors, DNS failures, or outages.

It is also easy to misdiagnose other problems as 404s. A Permission issue can block access even when the resource exists. A server outage can make multiple errors appear at once. A DNS problem can make an entire domain unreachable. The 404 code is specific: the server reached the request and could not find the requested resource.

Key Takeaway

HTTP status code 404 means the requested resource is missing at that URL, not that the server is broken.

Broken links, moved content, deployment mistakes, and stale campaigns are the most common causes.

The best fix is to restore the resource, redirect it with a 301, or improve the custom 404 page when no replacement exists.

Unmanaged 404s waste crawl effort, lose link value, and create avoidable user frustration.

How to Verify It Worked

Verification should prove two things: the fix is technically correct, and the user experience is better. Start by loading the old URL in a browser and checking the response behavior. If you added a redirect, confirm that the browser lands on the intended destination. If you restored the resource, confirm that it loads cleanly and consistently.

Use a command-line check when possible. A simple curl -I https://example.com/old-page should show the final status behavior. For a redirect, you should see a 301 or 302 followed by the final destination. For a restored page, you should see 200 OK. If you still see 404, the change did not take effect or the target path is still wrong.

  1. Open the old URL directly and confirm the expected destination or restored content.
  2. Inspect the HTTP response with browser tools or curl.
  3. Check internal links to confirm they no longer point at the dead URL.
  4. Review Search Console for declining repeat 404 hits after the fix.
  5. Watch server logs for lingering requests from bots or stale campaigns.

Common failure signs include a redirect chain that ends in another 404, a custom error page that returns 200 OK, or a destination page that is only loosely related to the original query. If users still bounce immediately, the fix may be technically valid but practically useless. The best verification includes both status-code checks and user-intent checks.

For teams managing many URLs, it helps to keep a short validation checklist after every release. That checklist should include top landing pages, recently renamed URLs, key downloadable assets, and any route changes in the CMS or application layer. Prevention is faster than cleanup.

Conclusion

HTTP status code 404 means the server found the request but not the resource at that URL. That is why a 404 is a location problem, not automatically a server failure. Once you understand that difference, diagnosing and fixing the issue becomes much easier.

The practical response is straightforward: verify the URL, find out whether the resource was moved or removed, restore it when it still matters, and use a 301 redirect when there is a clear replacement. If the content is truly gone, keep the 404 and make the custom page useful enough to help people move forward.

From an SEO and operations standpoint, unmanaged 404s are avoidable waste. They can hurt crawl efficiency, drain link equity, and create a poor user experience. Well-handled 404s, on the other hand, are a normal part of site maintenance. ITU Online IT Training recommends treating them as a routine governance task, not background noise.

If you are seeing repeated http 404 errors, start with Search Console, server logs, and a redirect audit today. The fastest fixes are usually the simplest: restore what belongs, redirect what moved, and retire what no longer serves the site.

HTTP status code 404, HTTP 404, and Not Found are technical terms used in web standards and browser behavior.

[ FAQ ]

Frequently Asked Questions.

What does HTTP status code 404 mean?

HTTP status code 404 is a standard response code indicating that the server is reachable but the requested resource cannot be found at the given URL. Essentially, it tells the client that the page or file they are trying to access does not exist on the server.

This commonly occurs when a webpage has been deleted, moved without redirecting, or the URL has been typed incorrectly. Unlike server errors, a 404 error confirms the server itself is working fine, but the specific content is missing or unavailable.

How does a 404 error impact website SEO?

404 errors can negatively affect SEO by signaling to search engines that a site has broken or dead links. When search crawlers encounter many 404 pages, it can lower the overall ranking and user trust.

However, occasional 404s are normal and not inherently harmful if managed properly. Site owners should implement strategies such as:

  • Setting up 301 redirects from old URLs to relevant new pages
  • Creating custom 404 pages that guide users back to useful content
  • Regularly auditing the site for broken links

These actions help maintain a good user experience and preserve SEO value despite missing resources.

Why do I see a 404 error even when the server is up?

A 404 error means the server itself is operational and responding but cannot find the specific resource requested. This can happen for various reasons including:

  • The URL was mistyped or contains errors
  • The page or file has been deleted or moved without an updated redirect
  • The resource was never published or is temporarily unavailable

In all cases, the server confirms availability but signals the resource is missing at that location, leading to the 404 response.

What is the difference between a 404 and other HTTP error codes?

HTTP status codes indicate different server responses. A 404 error specifically means “Not Found,” which means the server is reachable but the resource is missing. Other common error codes include:

  • 403 Forbidden – access to the resource is denied
  • 500 Internal Server Error – server encountered an unexpected condition
  • 301 Moved Permanently – resource has permanently moved to a new URL

Each status code serves a unique purpose, and understanding these distinctions helps diagnose the nature of web issues accurately.

How can website owners fix and prevent 404 errors?

Website owners can reduce 404 errors by maintaining clean URLs and managing site structure carefully. Key strategies include:

  • Implementing 301 redirects from outdated or removed pages to relevant replacements
  • Regularly auditing the website to identify broken links using tools like Google Search Console or crawling software
  • Creating user-friendly custom 404 pages that provide navigation options or search functionality
  • Ensuring consistent URL naming conventions and avoiding frequent renaming without redirects

Proactive management of 404 errors improves user experience, helps preserve SEO rankings, and ensures visitors are guided effectively even when content changes.

Related Articles

Ready to start learning? Individual Plans →Team Plans →
Discover More, Learn More
What Is HTTP Compression? Discover how HTTP compression can drastically reduce data transfer sizes, boost your… What Is a Code Signing Certificate? Discover how a code signing certificate enhances software trust and security, ensuring… What is HTTP Pipeline? Discover how HTTP pipelining boosts web performance by reducing delays with multiple… What is Code Coverage? Discover how to measure, interpret, and improve code coverage to enhance your… What is HTTP Basic Authentication Discover how HTTP Basic Authentication works and when to replace it with… What is Cloud Infrastructure as Code (IaC)? Learn how Cloud Infrastructure as Code streamlines environment deployment, ensuring consistency and…
FREE COURSE OFFERS