How do I fix an HTTP 410 error?

Use 410 when the removal is intentional and permanent; keep 404 for 'never existed / unknown'. For API sunsets, pair the 410 with a body pointing at the replacement endpoint and a migration link. Do not 410 things that might return — that is what 404 (or a temporary 503) is for.

410 Gone

Like 404, but with a promise: the resource existed, was removed on purpose, and is never coming back. Clients and crawlers may treat this as authoritative — search engines drop 410 URLs faster than 404s.

What usually causes it

Deliberately retired content (expired listings, deleted accounts, sunset API versions)

How to debug and fix it

Use 410 when the removal is intentional and permanent; keep 404 for 'never existed / unknown'.
For API sunsets, pair the 410 with a body pointing at the replacement endpoint and a migration link.
Do not 410 things that might return — that is what 404 (or a temporary 503) is for.

Easily confused with

404Not Found
301Moved Permanently

Debugging an API? Build and inspect requests, check response headers, or read the full status-code debugging guide.