404 Not Found

What a 404 error is, how Google handles 404 pages (de-indexes them over time), the difference between a hard 404 and a soft 404, and best practices for 404 pages in SEO.

First published: Jun 27, 2026 · Last updated: Jul 17, 2026 · Advanced
demand #5 in HTTP Errors#5 in HTTP Status Codes#18 in Technical SEO#27 on the site

A 404 Not Found is the client-error status code a server returns when a URL doesn't exist — a deleted page, a broken link, a typo. 404s are normal and expected: Google doesn't use their content, and the fact that some URLs on your site return a 404 doesn't drag down your other, successful pages — so you don't need to scramble to fix every one. Google de-indexes 404'd URLs over time (re-checking them less and less often), not instantly, and it doesn't promise to ever fully stop trying. The real distinction that matters is hard 404 (correct — actually returns 404) vs. soft 404 (a success code on a page that's really gone), which wastes crawl resources. Only 301-redirect a 404 when the page truly moved to a relevant target — don't blanket-redirect everything to the homepage.

Evidence for this claim HTTP 404 means the origin server did not find a current representation for the target resource. Scope: HTTP semantics; it does not by itself explain why a URL is missing. Confidence: high · Verified: RFC 9110: 404 Not Found Evidence for this claim Google treats normal 404 responses as expected web behavior and recommends redirects only when there is a relevant replacement. Scope: Google Search handling; sitewide quality depends on more than the presence of 404 URLs. Confidence: high · Verified: Google Search Central: 404 errors

TL;DR — A 404 is a 4xx client-error status code for a URL the server can’t find — the spec (RFC 9110) defines it as “no current representation, or unwillingness to disclose one,” and it doesn’t itself say whether the absence is temporary or permanent. It is not useful indexable content, and the fact that some URLs 404 doesn’t drag down your site’s other, successful URLs. Removal from search can be gradual, not instant: Google removes a previously-indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. 404’d URL and re-crawls it at a decreasing frequency; the source language is that GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. “will probably” keep retrying for some period, not that it retries forever. The distinction that actually matters is hard 404 vs. soft 404A soft 404 is a URL that returns a success status code (usually 200 OK) even though the page is empty, missing, or shows a 'not found' message. It isn't a status code a server sends — it's a label search engines apply after comparing the response code against the rendered content, and they treat the page like a 404 for indexing.: returning 200 (or blanket-redirecting to the homepage) for gone content wastes crawl resources and misleads your analytics. 301-redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. only when a page genuinely moved to a relevant target; otherwise let it 404 (or 410) cleanly. Custom 404 pages are a UX/retention lever, not an indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. one.

What a 404 actually is

404 Not FoundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. is an HTTP client-error status code (4xx) the server returns when it can’t find the requested URL. The 4xx class means the request is the problem — the resource doesn’t exist at that address — as opposed to 5xx server errors, where the server itself is failing.

The HTTP spec itself (RFC 9110) defines 404 more narrowly than the day-to-day SEO conversation implies: the origin either has no current representation for the target resource, or is unwilling to disclose that one exists. The status code alone doesn’t say whether the absence is temporary or permanent — that judgment call is yours to make with a redirect, a 410, or just leaving the 404 in place. One practical quirk worth knowing: a 404 response is heuristically cacheable by default, so a browser or intermediate cache can keep serving a stale 404 for a URL that has since started working again, unless your server sends cache-controlCaching stores a copy of a page or resource — in a browser, a CDN edge node, or a search crawler's own cache — so it can be served again without regenerating or re-downloading it. It isn't a direct ranking factor, but it feeds page speed and crawl efficiency. headers that say otherwise.

They come from all the ordinary churn of a website: deleted pages, discontinued products, retired campaigns, broken or mistyped internal and external links, and URL changes that weren’t redirected. None of that is unusual, and none of it is inherently a problem to solve.

The fact that a URL 404s doesn’t hurt your other pages

Start here, because most of the anxiety around 404s is misplaced. Google’s own documentation is explicit: “Google doesn’t use the content from URLs that return 4xx status codes.” There’s nothing on a 404 page for Google to score. And Google’s own guidance is specific on the scope of the claim: the fact that some URLs on a site return 404 doesn’t affect the performance of that site’s other, successful URLs. That’s the sourced boundary — it isn’t a blanket promise that every 404-adjacent situation is harmless. A page Google can’t find that you wanted indexed, a good page that lost its inbound links, or a broken user path are separate problems the 404 status code alone doesn’t fix or cause.

Google’s people have said the same thing in plainer language for years. Gary Illyes: 404s “are not to be afraid of and you don’t need to scramble to fix them, at least not most of the time.” John Mueller has repeatedly called 404s “fine & expected.” Even sites with enormous numbers of 404/410 URLs don’t see a domain-wide penalty for them. The specific fear that 404s are a ranking or quality signal is a myth — though a 404’d page that used to earn you traffic or links is still worth a decision, covered below.

How Google removes a 404’d URL from the index

De-indexing is real, but it’s gradual and undramatic. Google’s docs describe the mechanic: “the indexing pipeline removes the URL from the index if it was previously indexed. Newly encountered 404 pages aren’t processed. The crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. frequency gradually decreases.”

Two consequences worth internalizing:

  • A previously-indexed URL that starts returning 404 gets dropped from the index, and a URL first discovered as a 404 is simply never processed.
  • GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. keeps retrying the URL, just less and less often. As Search Console Help puts it: “Googlebot will probably continue to try this URL for some period of time; there is no way to tell Googlebot to permanently forget a URL, although it will crawl it less and less often.” Note the bounded wording — “probably,” “for some period of time” — Google doesn’t promise this continues forever, just that there’s no button to force it to stop early. So seeing a known 404 keep appearing in your reports for a while is expected — it’s not a sign something is broken.

Can you speed it up? Not really. The Removals toolA Google Search Console feature for verified owners to manage how their URLs appear in Search. A Temporary Removal hides a URL for about six months — it does not delete the page from the index. in Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. hides a URL temporarily (about six months), which is useful for urgent cases, but it’s a temporary hide, not a permanent de-index. For genuine removal you return the right status code and let the gradual process run.

404 vs. 410 Gone

Both 404 (Not Found) and 410 (Gone) drop a page from the index, and the practical SEO difference is negligible. 410 is the marginally stronger, faster “this is intentionally gone” signal — but as Mueller has said, the difference in processing is so minimal it rarely justifies choosing one over the other for SEO. Use 410 if your CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. makes it easy and you want to signal permanent removal; otherwise a plain 404 is completely fine. (There’s a dedicated comparison of these two elsewhere in this cluster.)

Hard 404 vs. soft 404 — the distinction that matters

This is where real SEO problems live, not in the existence of 404s themselves.

  • Hard 404 — the server genuinely returns the 404 status code for missing content. This is correct. CrawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. read the code, understand the page is gone, and handle it cleanly.
  • Soft 404 — the server returns a success code (usually 200 OK) for a page whose content is really an error: an empty page, a “not found” message, or a redirect to the homepage. Google detects these algorithmically. Its docs: “If the content suggests an error for Google Search, an empty page or an error message, Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. will show a soft 404 error.”

Why soft 404s are worse than real ones is a crawl-efficiency problem. A crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. can’t tell from a 200 that the content is gone, so it keeps re-fetching those URLs. Illyes described exactly this: crawlers “use the status codes to interpret whether a fetch was successful, even if the contents of the page is basically just an error message. They might happily go back to the same page again and again wasting your resources, and if there are many such pages, exponentially more resources.” Google’s guidance is unambiguous: “We recommend returning a 404 response code for truly ‘not found’ pages.”

John Mueller frames the whole thing well on his personal site: “Using soft-404s instead of real 404s is a bad practice, and it makes things harder for our algorithms,” while “returning 404 — and having the URLs listed in the crawl errors in Webmaster Tools — is not a problem.” In other words: the honest 404 is the good outcome; the fake success code is the bug.

Where accidental soft 404s come from

  • Blanket-redirecting every 404 to the homepage. The homepage returns 200, so from the engine’s view a “missing” URL now resolves successfully to unrelated content — a soft-404 pattern (more on why this is bad below).
  • JavaScript / SPA “not found” states. Client-side routers can’t natively throw a server-level 404. A single-page app that renders a “Page not found” component while the server still returns 200 is a soft 404 — and it also corrupts your analytics, because the status code no longer matches reality, so GA4, GSC, and crawlers all record a “successful” hit on a dead page. The fixes: server-side route those URLs to a real 404 response, or (weaker) render the not-found state with noindex and accept the tracking tradeoffs.
  • CMS / template misconfigurations where a deleted item falls through to a generic template served with 200.

When to fix a 404 (and when to leave it)

The decision tree is short:

  • Let it 404 (or 410) if the page has no real value, no traffic, and no backlinks. This is the default and it’s correct — no action needed.
  • 301-redirect it only if the page genuinely moved, or if it has real backlinks/traffic worth preserving. A relevant redirect recovers link equity; Search Console Help agrees: “If your page has moved, use a 301 redirectA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. to the new location.” My own workflow at Ahrefs: use Site Explorer’s “Best by links” report, filter for 404-responding URLs, prioritize by referring domains, and redirect the valuable ones to the closest relevant live page.
  • Don’t blanket-redirect to the homepage. Martin Splitt is blunt about this: “If it moved somewhere else, use a redirect. If it’s gone, don’t redirect me to the homepage.” It creates a soft-404-like signal and, in his words, “it annoys me as a user.” A 404, he notes, is “a very clear signal this link is wrong and broken or this URL no longer exists.” Only redirect to a specific, genuinely relevant target.

Reduced to a quick matrix, this is the whole decision:

Page has real backlinks/traffic?Relevant live replacement exists?Action
NoNoLet it 404 (or 410). No action needed.
YesYes301-redirect to the specific relevant page.
YesNoConsider rebuilding the page or redirecting to the closest relevant category; don’t redirect to the homepage by default.
NoYes (broken internal linkAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. pointed at it)Fix the link that points at the 404, not the 404 itself.

Custom 404 pages: UX lever, not an indexing lever

A good custom 404 page doesn’t change how Google indexes the URL — the status code does that. What it changes is what happens to the human who hit the dead link. A helpful 404 page keeps them on your site instead of bouncing, which protects conversions and engagement. So there are two separate jobs:

  1. Status code correctness (the SEO/crawler side): the page must still return a real 404. A beautifully designed custom 404 page that returns 200 is a soft 404 — you’ve solved the UX problem and created a crawl problem.
  2. On-page helpfulness (the UX side): clear messaging that the page is gone, your main navigation and a search box, and links to popular or related content. Mueller’s advice: “Think about ways that you can make your 404 pages useful to users, so that they recognize that the page no longer exists, and so that they can find something else that’s appropriate.”

How to find and audit 404s

  • Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.Page indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason.. Surfaces both “Not found (404)” and “Soft 404” statuses, with example URLs.
  • Ahrefs Site Audit / Site Explorer. Site Audit flags 404s and broken internal links; Site Explorer (“Best by links”) lets you find 404’d URLs that still have backlinks so you can prioritize redirects by referring domains.
  • Ahrefs Web Analytics. For the traffic companion, filter Possible 404 pages to the AI SearchAI search uses large language models and retrieval-augmented generation (RAG) to synthesize an answer from multiple sources rather than returning a ranked list of links. Examples include Google AI Overviews, ChatGPT Search, and Perplexity. channel and sort by sessions. That surfaces candidate URLs receiving AI-referred clicks in the selected window; it does not prove the response is a 404 or that the URL was hallucinated. I document the validation steps in AI Hallucination MonitoringAI hallucination monitoring is the practice of systematically detecting, documenting, and fixing instances where AI search tools and chatbots fabricate or misrepresent facts about your brand — wrong pricing, invented quotes, made-up URLs, and the like..
  • Screaming Frog and server log analysis for a full crawl-level and real-traffic view of which 404s bots and users actually hit.

Bing, briefly

Bing’s public commentary here is much thinner than Google’s, so don’t assume exact parity, and treat the specifics below as less firmly sourced than the Google section above. Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. does offer a Content Removal tool for notifying Bing about a URL you want treated as gone, and a Crawl Information report that surfaces 404s and server errors — those tools are documented. What’s not independently verified in current primary sources is the specific claim that Bing runs a classifier to distinguish “temporarily down” from “genuinely deleted,” or that using Content Removal meaningfully speeds up de-indexing versus just returning a correct 404 and waiting. Treat Bing as secondary to the well-documented Google behavior above, and don’t repeat the classifier/speed claims as settled fact.

For the broader status-code picture, see my HTTP Status Codes & Their SEO Impact and 11 Types Of Redirects & Their SEO Impact.

TIP Confirm the missing URL returns a real 404

A friendly not-found template can still return 200 and become a soft 404. The response code and final destination must match the visible state.

Run the URL through my HTTP Status Checker to distinguish a real 404 from a redirect, server error, or success-coded error page. HTTP Status Checker Free

  1. Test the exact missing URL without browser cache.
  2. Confirm the final response is 404 and not a 200 template, redirect loop, or irrelevant homepage redirect.
  3. If a true replacement exists, add one relevant permanent redirect and retest the chain.

Try it live

This is a real endpoint on this site — not a simulation. Hit it from the button, open it in a new tab, or curl -i it from your terminal, and the server answers with the actual status code this article is about.

Open in new tab ↗

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.