410 Gone

410 vs 404 — the practical difference

	404 (Not Found)	410 (Gone)
Meaning	Server doesn’t know what’s at this URL	Server knows; the resource was deleted intentionally
Crawler behavior	Returns periodically to check if the URL came back	Drops the URL from index faster
Use case	Default “we don’t have that” response	”We deliberately deleted this, don’t return”

For URLs you’ve deliberately removed (deprecated products, retired blog posts, expired campaigns), 410 signals intent more clearly than 404 and accelerates index removal.

When to use 410

Legitimate use cases:

• Discontinued products — when you’re certain the product line is gone forever
• Retired blog posts / pages — content you’ve decided to remove without replacement
• Account deletion — user-facing pages for deleted accounts
• Spam / abuse cleanup — UGC pages that you’ve taken down
• Acquired-then-shuttered brand content — pages from an acquired company you’re explicitly retiring

When NOT to use 410

• Temporary 404s — pages that might come back later or are broken
• Pages with relevant replacement content — use 301 redirect to the replacement instead
• Pages with significant inbound links — 301 to a replacement preserves the link equity; 410 throws it away

The rule: if there’s a good redirect target, 301 there. If the content is permanently gone with no replacement, 410 it.

How to ship 410 responses

Server config varies by stack:

• Apache (.htaccess): Redirect 410 /old-page.html
• Nginx: return 410; in a location block
• Cloudflare Workers: return new Response(null, { status: 410 })
• Next.js / Astro: custom 410 handler in middleware or edge function
• WordPress: plugin like Redirection supports 410 status

The custom 410 page should match your 404 page in design but communicate intent (“This page was removed. We don’t expect it to return.”)

SEO impact

A page returning 410:

• Drops out of Google’s index within days-to-weeks (faster than 404)
• Inbound links lose their effect on your site
• Internal links to the 410 page should be removed

For sites cleaning up large legacy content, batch-410-ing dead pages accelerates the deindex without ongoing crawl-budget waste.

Resocial perspective

For most engagements, 301 redirects are the right answer; 410 is the right answer for the narrow case of “permanently delete with no replacement.” We use 410 deliberately in cleanups where there’s no legitimate redirect target — typically 5-15% of legacy URLs on a large migration. The rest get 301s to relevant replacements.