410 Gone

TL;DR — A 410 Gone status code is how you tell search engines “this page used to be here, we deleted it on purpose, and it isn’t coming back.” It’s like a 404 (Not Found), but with intent: a 404 just says “nothing here,” while a 410 says “gone, permanently, by design.” Both eventually get the page dropped from Google — Google documents the two as equivalent for Search.

What a 410 means

When a browser or a search engine asks your server for a page, the server answers with a status code. 200 means “here it is.” 404 means “I can’t find anything at that URL.” 410 means “there was something here, and it’s gone — permanently.”

The difference between 404 and 410 is one of certainty. A 404 is ambiguous: maybe the page was deleted, maybe someone mistyped the URL, maybe there’s a bug and it’ll be back tomorrow. A 410 removes that ambiguity — you’re explicitly telling the world the page was removed on purpose and won’t return.

Why it matters for SEO

If you delete a page and it returns a 404 or a 410, Google will eventually drop it from search results. That’s the important part: both codes get the job done. The Google’s published guidance treats the two codes the same for Search and promises no special removal timetable for 410. Evidence for this claim Google treats 404, 410, and other 4xx responses except 429 the same for Search, does not use their content, and removes previously indexed URLs over time. Scope: Google Search handling of 4xx responses; no exact removal timetable is promised. Confidence: high · Verified: 2026-07-17 Google: HTTP status codes and Search Google: How HTTP status codes affect Google's crawlers

A few things beginners get wrong:

• It’s not instant. Google has to re-crawl the URL to notice the new status. Until it does, the page can still show in results (sometimes with a cached snippet). A 410 speeds up the decision, not the crawl schedule.
• Don’t block the URL. If you delete a page and block it in robots.txt, Google can’t crawl it to see the 410 — so it can’t process the removal. Let it be crawled.
• If you have a good replacement, redirect instead. When the content moved or has a natural equivalent, a 301 redirect is usually the better choice — 410 kills the page and any demand for it, which is exactly what you don’t want if there’s somewhere useful to send people.

The simple rule

Use a 410 when you’re certain a page is gone forever and you want to say so clearly — retired products, deleted sections, spam cleanup. Use a 404 when you’re not sure, when the page might come back, or when it’s just not worth the engineering effort to special-case it. For most single-page deletions, a plain 404 is completely fine.

Want the data behind “how much faster,” what John Mueller actually said, and how to do this at scale during a migration? Switch to the Advanced tab.

TL;DR — 410 and 404 both remove a URL from Google’s index over time; the real question is speed of the removal decision and crawl-budget efficiency, not whether removal happens. Google’s reference docs treat 404/410 as one 4xx bucket. The “410 is faster” claim is a field-tested, rep-acknowledged nuance — small, not dramatic. The honest number: Google confirms a 410 removal a little faster and re-crawls 410s less often. The oft-repeated “3x faster, 4 vs 12 days” figure is unverified folklore — don’t repeat it. 410 earns its keep at scale (mass deletions, migrations with no equivalent URL, spam/hacked cleanup), and the bigger mistake is a soft 404, which wastes crawl budget indefinitely.

What 410 actually is

410 Gone is a client-error status in the 4xx family. Semantically it’s the “stronger 404”: the resource existed, it was intentionally and permanently removed, and no forwarding address is offered. A 404 makes no claim about intent or permanence — it’s just “not found right now.”

RFC 9110 §15.5.11, the actual HTTP standard, is specific about what “gone” means: the condition is likely permanent — and if you genuinely don’t know whether it’s permanent, the spec’s own guidance is to use 404 instead. Its stated purpose is to help maintenance by telling clients (and crawlers) the link should be removed. Two nuances the spec adds that most write-ups skip: it does not require every permanently-gone resource to use 410, and it does not require the 410 status to stay in place forever — both are left to the origin’s discretion. It also notes a 410 response is heuristically cacheable by default, so an intermediate cache or CDN can keep serving that response until it expires unless you set explicit cache-control headers.

For SEO the distinction lives entirely in intent signaling. Both codes tell a crawler the page shouldn’t be served. The 410 adds “…and don’t expect it back,” which is the bit search engines can act on.

Does Google de-index 410s faster than 404s?

Short answer: yes, but modestly. Here’s the honest version, separated into the three things people conflate.

1. What Google’s documentation actually says. Google’s reference docs don’t carve out special 410 timing. Its crawler documentation states the grouping directly: “All 4xx errors, except 429, are treated the same: Google crawlers inform the next processing system that the content doesn’t exist.” Evidence for this claim Google treats 404, 410, and other 4xx responses except 429 the same for Search, does not use their content, and removes previously indexed URLs over time. Scope: Google Search handling of 4xx responses; no exact removal timetable is promised. Confidence: high · Verified: 2026-07-17 Google: HTTP status codes and Search Google: How HTTP status codes affect Google's crawlers Its Search docs describe the same mechanics in different words: “Google doesn’t use the content from URLs that return 4xx status codes… URLs that are already indexed and return a 4xx status code are removed from the index.” The removal mechanics are described for 404s and apply the same way — “the indexing pipeline removes the URL from the index if it was previously indexed… The crawling frequency gradually decreases.” At the documentation level, 404 and 410 are functionally identical — 429 is the one 4xx code that gets different treatment (it’s a “try again later,” not a removal signal).

2. What John Mueller has said. Google’s own spokesperson has been on both sides of this, which is itself instructive. Early on he called the difference negligible. Later, after double-checking internally, he corrected himself: “it appears I was wrong there — we do treat 410s slightly differently than 404s,” and Google “will sometimes want to confirm a 404 before removing a URL from the index, and we tend to do that faster with a 410.” So there is a difference — a slightly faster index-removal decision — it’s just small. Critically, switching to 410 does not stop Google from occasionally re-checking the URL, especially if it still has inbound links.

3. What independent testing shows. The best real data I’ve seen is Reboot Online’s controlled experiment: 119 test URLs over 3+ months. Their finding was about crawl frequency, not raw days-to-deindex — “404’s are, on average, crawled 49.6% more often than 410’s.” In other words, Googlebot spends noticeably less budget re-checking 410s. That’s the crawl-budget argument in concrete form. (Note the caveat: they measured re-crawl frequency because the GSC API couldn’t cleanly measure “still indexed vs. removed.”)

My own framing in HTTP Status Codes: A Complete List has been consistent with all of this: “404s and 410s have a similar treatment. Both drop pages from the index, but 410s are slightly faster. In practical applications, they’re roughly the same.” Believe the “slightly” and disbelieve the “3x.”

The myth to drop

You’ll see “410 de-indexes 3x faster — 4 days vs. 12 days” repeated across a lot of blogs. I’ve never been able to trace that figure to an original, methodology-documented study — it looks like a mutated re-telling of the Reboot number. Don’t cite it. The defensible claim is “a little faster and re-crawled a little less,” full stop.

When to use 410 vs. 404 vs. a redirect

This is a three-way decision, not two.

• Use 410 when you’re certain the content is gone forever and you want to actively signal that: bulk deletions, retired product lines, spam/hacked-content cleanup, site consolidations where a set of URLs has no replacement. 410 is you taking a position.
• Use 404 when you’re uncertain, the page might return, or it’s simply not worth the engineering cost to special-case the response. For low-volume, one-off deletions, 404 is fine — the SEO difference won’t be worth a custom implementation.
• Use a 301 redirect when an equivalent page exists. Don’t 410 something that has a natural replacement — redirect it, pass the signals, and keep the demand. 410 throws that away by design.

One more thing worth being explicit about: none of this — 410, 404, or a redirect — is a lever on backlink equity or topical authority by itself. Whether inbound links keep sending value depends on where they point after you act (a redirect can pass signals to the new target; a 410 doesn’t have anywhere to pass them), not on some automatic property of the status code. Treat backlink and authority consequences as evidence-dependent — check what’s actually linking in and where it goes — rather than assuming a status-code choice guarantees an authority outcome either way.

The soft-404 trap (the mistake that actually costs you)

Picking the “wrong” 4xx code is a rounding error next to serving a soft 404 — a page that returns 200 OK with “not found” messaging in the body. Google keeps crawling soft 404s because, as far as the status code is concerned, they’re live pages. They “will continue to be crawled, and waste your budget.” If you’re deleting content, the goal is a real 404/410, not a friendly “oops, that’s gone” page that still answers 200.

410 during migrations and mass deletions

This is where the choice stops being academic. On a re-platform or a large content prune, you’re deciding the fate of thousands of URLs at once.

• Migrations: Google’s migration guidance is explicit that content you’re not carrying over should return a real 404 or 410 on the new site. The mental model: redirect what has an equivalent, 410 what’s deliberately retired with no equivalent, and don’t sweat leaving genuinely uncertain URLs as 404s. Keep any redirects in place for a long time (Google suggests at least a year) — but a URL with nothing to redirect to is a 410 candidate, not a forced redirect to a vaguely-related page.
• Mass deletions (ecommerce delistings, content pruning, consolidations): this is the strongest case for 410. When you kill 50,000 discontinued SKUs or a whole subsection, the crawl-budget savings from 410’s lower re-crawl frequency compound. A quick judgment call for retail: a product that’s genuinely discontinued forever is a 410; a product that’s temporarily out of stock but returning is not — keep that live (a stockout is not a deletion).
• Implementation at scale: do it with rules, not one page at a time. Match URL patterns in your server config, CDN/edge worker, or CMS — an Nginx location block, an Apache RewriteRule … [R=410], or a bulk plugin — so the whole retired set answers 410 without hand-editing pages.

See the Playbooks tab for a step-by-step mass-deletion runbook.

How Bing handles it (and how to speed it up)

Bing’s mechanism is the same in spirit: delete the page so it returns 404 or 410, keep the URL crawlable (not blocked in robots.txt) so Bingbot can observe the status, and Bing removes it after a re-crawl confirms the removal. Bing’s practical accelerant is IndexNow — ping it on deletion so Bing learns to revisit the URL sooner, and keep your sitemap current. For urgent takedowns (leaked/compliance cases), Bing’s Block URLs tool hides a URL for ~90 days as a stopgap while the permanent 410 propagates.

A caveat on that last paragraph: Bing’s help pages render via JavaScript, which has blocked a clean automated re-verification of the exact current wording. Treat the mechanism above as Bing’s documented practice rather than a freshly-confirmed quote — check Bing Webmaster Tools’ live help page before treating specifics like the ~90-day Block URLs window as final.

How to verify a 410 is working

• Check the raw status. curl -I https://example.com/gone-page/ should show HTTP/… 410. Browser DevTools → Network tab shows the same. Don’t trust the visible page — trust the header.
• URL Inspection (GSC). Confirms how Google last crawled it and what status it saw.
• Coverage / Page Indexing report. Watch for the removed URLs moving out of the indexed set over the following crawls.

Remember the expectation-setting from my remove URLs guide: a page is “removed from the index shortly after the page is re-crawled. Until it is removed, the page may still show in search results.” A 410 doesn’t beat the re-crawl — it just wins the decision once the re-crawl happens.

Related reading in this cluster: the general 404 Not Found status, the head-to-head 404 vs. 410 comparison, and the soft 404 pitfall above.

AI summary

A condensed take on the Advanced version:

• 410 Gone = intentional, permanent removal. Unlike a 404 (“not found,” no reason given), a 410 explicitly signals the page was deleted on purpose and won’t return.
• Both de-index the page eventually. Google puts 404 and 410 in the same 4xx bucket; indexed URLs returning 4xx get removed and crawled less over time.
• 410 is faster — modestly. Mueller confirmed Google treats 410s “slightly differently” and removes them “faster.” Reboot Online’s 119-URL test found 404s are crawled ~49.6% more often than 410s (a crawl-frequency proxy, not days-to-deindex).
• Don’t repeat the “3x faster / 4 vs 12 days” stat — it’s untraceable folklore.
• It’s not instant and doesn’t stop re-crawling; Google still occasionally re-checks 410s, especially URLs with inbound links.
• Decision rule: 410 = certain-and-permanent (bulk deletions, migrations with no equivalent, spam cleanup); 404 = uncertain/low-effort; 301 = an equivalent page exists.
• Soft 404 is the worse mistake: a 200-status “not found” page wastes crawl budget forever.
• At scale, implement 410 with server/CDN/CMS rules; use IndexNow to speed up Bing; keep URLs crawlable so bots can see the status.

Official documentation

Primary-source documentation from the search engines.

Protocol

• RFC 9110 §15.5.11 — 410 Gone — the HTTP standard’s definition: likely-permanent unavailability, the maintenance/link-removal purpose, owner discretion on scope and duration, and heuristic cacheability.

Google

• How HTTP status codes, and network and DNS errors, affect Google Search — the 4xx table (including 410 (gone)) and how Google removes 4xx URLs from the index.
• How HTTP status codes affect Google’s crawlers — states the grouping directly: all 4xx codes except 429 are treated the same.
• Optimize your crawl budget — return 404/410 for permanently removed pages; eliminate soft 404s.
• Soft 404 errors — what a soft 404 is and why it’s worse than a real 404/410.
• Site moves with URL changes — return 404/410 for deleted/merged content not carried to the new site; redirect-duration guidance.

Bing / Microsoft

• How to permanently remove a URL or page from Bing or Copilot — delete to return 404/410, keep it crawlable, and use the Block URLs tool for urgent cases.
• IndexNow / indexnow.org — ping changed/removed URLs so Bing re-checks them sooner.

Quotes from the source

On-the-record statements from Google, its spokespeople, and independent testing. Each official link is a deep link that jumps to the quoted passage on the source page.

Google — how 4xx (including 410) is handled

• “All 4xx errors, except 429, are treated the same: Google crawlers inform the next processing system that the content doesn’t exist.” — Google’s crawler documentation. Jump to quote
• “Google doesn’t use the content from URLs that return 4xx status codes. If a URL was previously used but is now returning 4xx status code, Google systems will stop using the URL over time.” — Google Search Central docs. Jump to quote
• “the indexing pipeline removes the URL from the index if it was previously indexed. Newly encountered 404 pages aren’t processed. The crawling frequency gradually decreases.” Jump to quote

Google — crawl budget and permanent removal

• “Return a 404 or 410 status code for permanently removed pages. Google won’t forget a URL that it knows about, but a 404 status code is a strong signal not to crawl that URL again.” — Google Search Central docs. Jump to quote
• “Eliminate soft 404 errors. soft 404 pages will continue to be crawled, and waste your budget.” Jump to quote

John Mueller, Google (via secondary reporting)

• “It’s good to double-check these things, and it appears I was wrong there — we do treat 410s slightly differently than 404s.” Google “will sometimes want to confirm a 404 before removing a URL from the index, and we tend to do that faster with a 410 HTTP result code.” Relayed via Search Engine Roundtable’s coverage of Mueller’s follow-up; re-verify against the live source before treating as final. Read the coverage

Independent testing — Reboot Online

• “An analysis of the Google Search Console API data looking at our sample of 119 test web pages shows that 404’s are, on average, crawled 49.6% more often than 410’s.” Measures re-crawl frequency (their measurable proxy), not raw days-to-deindex. Read the experiment

Runbook: mass-410 a set of URLs (deletion or migration)

Use this when you’re retiring many URLs at once — a discontinued product range, a pruned content section, or content you’re deliberately not carrying to a new site. Work top to bottom.

1. Confirm these URLs are truly permanent-gone. 410 is a one-way door. Anything that might return (seasonal ranges, temporary stockouts) is not a 410 — keep it live. Anything with a real equivalent is a 301 redirect, not a 410. Only URLs with no future and no replacement belong on the 410 list.

2. Segment the URL set into a clean rule. You want a pattern, not a spreadsheet of 50,000 lines: a path prefix (/archive/, /discontinued/), a query signature, or a list you can express as a map. If it can’t be expressed as a rule, it’s usually too messy to be safe — re-check step 1.

3. Implement the 410 at the edge or server, in bulk.

   • Nginx: location /discontinued/ { return 410; }
   • Apache/.htaccess: RewriteRule ^discontinued/ - [R=410,L] (or Redirect gone /old-path).
   • CDN/edge worker: return a 410 response for matching paths — fastest to ship across a large set and cache-friendly.
   • CMS/plugin: many platforms (or a redirect/410 plugin) let you bulk-assign 410 to a URL list without touching each page.

4. Serve a real 410 body — not a soft 404. The response must carry the 410 status in the header. A friendly “this is gone” page is fine as long as the status is 410, not 200. Verify a sample: curl -I <url> must show HTTP/… 410.

5. Keep the URLs crawlable. Do not block them in robots.txt. If bots can’t crawl the URL, they can’t see the 410 and can’t process the removal. Remove any competing disallow rules for the set.

6. Prune internal links and sitemaps. Remove the retired URLs from your XML sitemap and internal navigation so you’re not actively pointing bots (and users) at dead pages. Lingering inbound links are the main reason Google keeps re-checking a 410.

7. Accelerate the re-crawl. For Bing, ping IndexNow with the removed URLs. For Google, there’s no bulk removal-speedup, but URL Inspection and an updated sitemap help it notice sooner. Expect this to take multiple crawls, not hours.

8. Monitor de-indexing. Track the set leaving the index via GSC’s Page Indexing report and Bing Webmaster Tools over the following weeks. If URLs linger, re-check for (a) accidental robots.txt blocking, (b) a 200 soft-404 slipping through, or (c) strong inbound links keeping the URL “interesting” to the crawler.

When not to run this playbook

• Single-page deletion: a plain 404 is fine; a custom 410 rule isn’t worth the effort.
• Temporary removal / stockout: keep the page live; don’t 410 something coming back.
• Content that moved: 301 to the new URL — 410 destroys the demand you want to keep.
• Urgent legal/leaked takedown: set the 410, but also use Bing’s Block URLs tool and Google’s Removals tool for immediate suppression while the status propagates.

Diagnosing an accidental 410

If a URL is returning 410 and shouldn’t be, work through these before assuming it’s a bug in application code — bulk rules fail in a handful of predictable ways:

• Origin, edge, and CMS rules. Check server config, CDN/edge-worker rules, and any CMS-level redirect or status plugin for a path pattern that matched more than you intended.
• The cache/CDN layer. A 410 is heuristically cacheable by default — a stale cached 410 can keep serving after you’ve fixed the underlying rule, until the cache entry expires or is purged.
• Internal links and sitemaps. Confirm the affected URL wasn’t swept into a bulk-410 rule by a path-prefix match that was broader than the intended retired set.
• Canonicals, hreflang, and feeds. A canonical target, an hreflang alternate, or a product/content feed entry pointing at the URL means the 410 breaks more than the one page — trace anything that references the URL, not just the URL itself.
• Rollback. Keep the pre-rollout rule/config on hand so you can revert a mistaken match immediately instead of re-diagnosing the whole rule from scratch.

Should this URL return 410?

Prompt: classify a deletion list

Classify each URL in this deletion spreadsheet as keep live, 301 redirect, 404, 410,
or needs human review. Use only the columns I provide: current status, replacement
candidate, permanence, traffic/backlink notes, internal links, and sitemap membership.
Explain each 410 decision, flag unsupported replacement mappings, and output a CSV
plus a validation sample. Do not invent destinations or assume a product is permanent.

[PASTE ROWS AND COLUMN DEFINITIONS]

Prompt: review a bulk 410 rule

Review this server, CDN, or application rule that returns 410 for retired URLs. Find
overbroad path matches, conflicts with redirects, robots.txt blocking, soft-404 200s,
and URLs that might return. Give a minimal safer rule and a pass/fail test matrix.
Preserve the configuration language I provide and do not invent provider syntax.

[PASTE RULE AND REPRESENTATIVE URLS]

Shell: verify a list of retired URLs

Run this in a macOS/Linux terminal with one absolute URL per line in gone-urls.txt.

while IFS= read -r url; do
  code=$(curl -sS -o /dev/null -w '%{http_code}' "$url")
  printf '%s,%s\n' "$code" "$url"
done < gone-urls.txt

Review anything other than 410 rather than automatically rewriting it; a redirect or live URL may be intentional.

PowerShell: verify the same list

Get-Content .\gone-urls.txt | ForEach-Object {
  $r = Invoke-WebRequest -Uri $_ -SkipHttpErrorCheck
  [PSCustomObject]@{ Status = $r.StatusCode; Url = $_ }
} | Export-Csv .\gone-results.csv -NoTypeInformation

DevTools Console: find links to a retired path

Run this in the browser Console after replacing the path prefix.

console.table([...document.links].filter(a => new URL(a.href).pathname.startsWith('/retired/')).map(a => ({text: a.textContent.trim(), href: a.href})));

Tools for implementing and checking 410s

• Bulk HTTP Status Code Checker: verify the whole retired set and catch accidental 200s, redirects, and inconsistent responses.
• Redirect Map Builder: separate URLs with real equivalents from URLs that should be removed before writing the 410 rules.
• SEO Migration Planner & Validator: review redirect mappings and deployed statuses during a migration where some URLs are retired.
• Link Analyzer: find internal links that still point to removed URLs so the site stops advertising dead destinations.
• Search Console URL Inspection and Page Indexing: confirm Google’s last observed response and monitor the set leaving the index after recrawl.

Validate a 410 rollout

Status and scope test

Test to run: check representative matches, near-misses, and exceptions with the Bulk HTTP Status Code Checker. Expected result: only approved retired URLs return 410. Failure interpretation: the rule is overbroad, underbroad, or shadowed. Monitoring window: immediate after every edge/origin deployment. Rollback trigger: any live or redirectable URL becomes 410.

Crawlability and body test

Test to run: fetch each sample normally and inspect robots.txt plus the raw status. Expected result: crawlers can request the URL, the response is 410, and any friendly body does not change it to 200. Failure interpretation: a robots rule hides the signal or the error template creates a soft 404. Monitoring window: immediate. Rollback trigger: the rollout blocks the retired path from crawling or serves 200.

Internal-signal cleanup test

Test to run: crawl internal links and inspect XML sitemaps for the retired set. Expected result: approved 410 URLs are absent from current navigation and sitemaps. Failure interpretation: the site still sends conflicting discovery signals. Monitoring window: after the next sitemap/build publication. Rollback trigger: cleanup removes links or sitemap entries for URLs outside the approved set.

Accidental-410 diagnosis test

Test to run: for any URL unexpectedly returning 410, check origin/edge/CMS rule scope, the cache/CDN layer, and any canonical, hreflang, or feed entry referencing the URL. Expected result: the match is intentional, and no canonical, hreflang, or feed target is affected. Failure interpretation: an overbroad rule, a stale cached 410, or a mis-scoped canonical/hreflang/feed entry is producing the wrong status. Monitoring window: as soon as an unexpected 410 is reported. Rollback trigger: revert to the last known-good rule/config and purge the cache for the affected path.

Test yourself: 410 Gone

Five quick questions on what a 410 means and when to use it. Pick an answer for each, then check.

Resources worth your time

My related writing

• HTTP Status Codes: A Complete List — my full status-code reference, including the 404-vs-410 “roughly the same in practice” framing.
• How to Remove URLs From Google Search (5 Methods) — where 404/410 fits among the removal options, and why removal lags the re-crawl.
• The Beginner’s Guide to Technical SEO — where status codes sit in the bigger technical picture.

My speaking

• How Search Works (SlideShare) — my walkthrough of crawling, indexing, and how status codes feed the pipeline. (Standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)

From around the industry

• RFC 9110 §15.5.11 — 410 Gone (IETF) — the HTTP standard’s actual definition of the status code.
• How HTTP status codes affect Google Search (Google Search Central) — the authoritative 4xx handling doc.
• How HTTP status codes affect Google’s crawlers (Google) — states the 4xx-except-429 grouping directly.
• Optimize your crawl budget (Google Search Central) — the clearest official pairing of 404/410 with a crawl-budget rationale.
• Site moves with URL changes (Google Search Central) — 404/410 for content not carried to a new site.
• 404 vs 410: The Technical SEO Experiment (Reboot Online) — the 119-URL, 3+ month controlled test; 404s crawled ~49.6% more often than 410s.
• Google’s John Mueller Clarifies 404 & 410 Confusion For SEO (Search Engine Journal) — coverage of Mueller’s early “no real difference” stance.
• Now 404 & 410 Response Codes Treated The Same By Google (Search Engine Roundtable) — Mueller’s follow-up admitting a small difference (ironically-titled; read the substance).
• How to permanently remove a URL from Bing or Copilot (Bing Webmaster Tools) — Bing’s 404/410 + IndexNow removal mechanism.

410 Gone

A 410 Gone status code tells search engines a page was intentionally and permanently removed, prompting slightly faster de-indexing than a standard 404.

Related: 404 Not Found, Soft 404, 301 redirect

410 Gone

HTTP 410 Gone is a 4xx client-error status code that tells a crawler or browser a resource used to exist at this URL and has been intentionally, permanently removed, with no replacement. It differs from a 404 (Not Found) mainly in intent: a 404 just says “nothing here” — which could be a typo, a bug, or a page that might come back — while a 410 says “this was here on purpose, we took it away on purpose, and it isn’t coming back.”

For search, both codes eventually drop the page from the index. Google groups 404 and 410 together in the same 4xx bucket, and the practical difference is small: a 410 signals permanence more strongly, so Google tends to confirm and remove it a touch faster and re-checks it a little less often. It’s a signal about this URL’s crawl and index treatment — not a ranking factor, and not a benefit to the rest of the site.

Related: 404 Not Found, Soft 404, 301 redirect

Changelog