410 Status Code: Meaning and How to Fix It

The HTTP 410 status code means the requested resource is no longer available, and the server expects that removal to be permanent. Visitors should check the address and look for a replacement, while website owners should confirm that the response is intentional.

What Does the 410 Status Code Mean?

The 410 status code is an HTTP response sent by a web server to a browser, app, or other client. It says that the requested page, file, or API resource used to exist or was deliberately removed and is not expected to return.

A visitor may see an error page instead of the requested content. An app using an API may display a message, fail to load information, or record status 410 in an error log. The exact screen varies, but the meaning of the 410 HTTP status code remains the same: the server considers the resource permanently unavailable.

A 410 response does not necessarily mean that the entire website is unavailable. Other pages and features may continue to work normally. The response applies to the specific address or resource requested.

What Is the Difference Between a 410 and 404 Status Code?

A 404 status code means that the server cannot find the requested resource. A status code 410 more specifically means that the resource is gone and that its removal is expected to be permanent.

• 404 Not Found: The resource is unavailable, but the server does not confirm whether it previously existed or whether it may return.
• 410 Gone: The server indicates that the resource was removed and is not expected to become available again.

Visitors usually take similar first steps for either response: check the address and search the main site. For website owners, the distinction matters because a 410 should reflect a deliberate decision or a known permanent condition. If the server cannot determine what happened to a missing resource, a 404 response may be more accurate.

Why Do You See an HTTP 410 Error?

An HTTP 410 status code can appear for several reasons. Some are intentional content decisions, while others result from configuration mistakes.

• Deleted pages: A website owner permanently removed an article, account page, document, or other resource.
• Retired API endpoints: An older API route was discontinued after a service changed its interface or ended support for that version.
• Expired resources: A temporary download, invitation, shared item, or time-limited record reached the end of its intended availability.
• Removed products or events: A site intentionally retired a page and chose not to provide a replacement.
• Incorrect server rules: A web server, proxy, security layer, or content delivery configuration mistakenly assigns status 410 to an address.
• CMS settings: A content management system, deletion feature, plugin, or routing rule marks content as permanently gone.

If many unrelated pages suddenly return the same response, the cause may be a broad rule or configuration problem rather than deliberate removal of every page.

What Can Website Visitors Do About a 410 Status Code?

A visitor normally cannot repair a status code 410 because the response comes from the website’s server. These checks can help determine whether the content moved or the address is wrong.

1. Review the full address for typing errors, missing characters, extra punctuation, or text copied into the address by mistake.
2. Remove only an unnecessary fragment at the end if it clearly looks incorrect, then try the corrected address.
3. Return to the website’s main page and use its menus, search box, help area, or document index to look for the same information.
4. Check whether the page title or resource name appears elsewhere on the site under a new category.
5. Refresh once in case an intermediate network service produced a temporary problem, but do not expect repeated refreshing to restore content that was intentionally removed.
6. Contact the website owner through the verified contact options on the company’s official website if the missing resource is important or if a working page repeatedly produces the error.

Do not enter account details into an unfamiliar page that claims to replace the missing resource. Start from the organization’s verified main site when looking for sign-in or support options.

How Can Website Owners Fix a 410 Response?

Website owners should first decide whether the resource is supposed to be gone. The correct fix depends on whether the 410 response is accidental, whether the original content should return, and whether a useful replacement exists.

1. Request the exact address and confirm the response with a browser’s developer tools, a server log, or an HTTP inspection tool.
2. Check web server rules, application routes, proxy settings, firewall rules, and content delivery settings for directives that produce a 410 response.
3. Review CMS trash, deletion, expiration, visibility, and plugin settings. Restore or republish the resource if it was removed accidentally.
4. Inspect recent deployments and configuration changes, especially when several valid addresses began returning status code 410 at the same time.
5. Check redirects. Remove a mistaken rule, or add a redirect when the old resource has a clear and relevant replacement.
6. Update internal menus, articles, sitemaps, API clients, and other references that still request the removed address.
7. Test the final response from outside an administrator session and verify both the old address and any replacement destination.

For a retired API endpoint, website owners should also check version routing and client documentation. Restoring the old endpoint, returning an appropriate error, or directing clients to a supported replacement depends on the service’s compatibility policy.

When Should a 410 Response Be Intentional?

An HTTP status code 410 is appropriate when the publisher knows that a resource has been permanently removed and does not intend to restore it. Examples include revoked shared resources, deleted records that must no longer be accessible, discontinued API routes, and obsolete pages with no suitable replacement.

A different response may be better in other situations.

• Use a redirect when the old address has a clear replacement that serves the same purpose.
• Use a temporary redirect when the move is temporary and the original address is expected to work again.
• Use a 404 response when the resource cannot be found but its history or future availability is unknown.
• Restore the normal successful response when the resource should still exist and the 410 came from a mistake.

Before intentionally returning an HTTP 410 status code, remove or update internal references to the resource. A purposeful 410 clearly communicates permanent removal, but it should not be used as a general response for every broken address.