Error 410: Gone
Does a deleted page really return 410, or 404, or even 200? Check right here what your server answers.
Checks the status code, every redirect, the variants with and without www and over http and https, the SSL certificate and the response time.
Free, no sign-up - no data about you is stored.
Result
Technical finding without guarantee. The check runs once from a server in Germany. If your website is only unreachable from certain networks or countries, the result may differ.
What does Error 410 mean?
A 410 Gone means this page existed, was removed on purpose and won't come back. It's a deliberate statement by the site owner, not a technical fault. A 404, by contrast, only says "not found" and leaves open whether the page ever existed or will return.
For visitors both usually look the same. The difference is aimed at search engines and other software: a 410 is the clearer signal to stop requesting a URL.
Common causes.
Content deleted on purpose
Outdated posts, discontinued products or expired offers without a fitting successor.
Cleaning up after a hack
Attackers often create thousands of spam pages. After the clean-up, those URLs should disappear from Google as fast as possible.
Legal reasons
Content has to be removed, for example after a legal notice or at the request of an affected person.
Unintended 410
An overly broad rule in a plugin or in
.htaccessalso catches pages that should have stayed.
With WordPress and hosting.
WordPress itself returns 404 for deleted pages, not 410. You can set a 410 with redirect plugins like Redirection or with the redirect features of SEO plugins that offer "content deleted (410)" as a type. At server level it also works via .htaccess or the nginx config, which makes sense for many similar URLs.
After a hack with spam pages, 410 is the tool of choice. The URLs usually follow a pattern, such as a particular folder or parameter, so they can be marked as gone in one go. Fix the cause first, otherwise the malware simply creates new pages.
How to fix it.
Decide: 410, 404 or 301
If there's a fitting successor, a 301 is better. If the page is gone for good, 410 fits. If you're unsure, 404 is never wrong.
Set 410 for deleted content
In your redirect or SEO plugin, create a rule of type 410 for each URL, or one pattern-based rule for many similar URLs.
Check the result
Run a few of the URLs through the checker above. They should return 410 directly, without going through a redirect.
Remove links
Delete internal links to the removed pages and take them out of the sitemap. Otherwise you'll keep sending visitors and Google there.
Find unintended 410s
If a page that should stay returns 410, look in the plugin and in
.htaccessfor rules that match it and narrow them down.
Impact on Google.
Google removes pages returning 404 and 410 from its index. According to Google the difference is small in practice, but a 410 can speed up removal a little because it clearly says the page is not coming back. After a hack with lots of spam pages, that is a noticeable advantage.
410s don't count against the rest of your site. The URLs still take a while to disappear from Search Console completely, because Google rechecks them for some time.
Help from a developer
I can take care of it.
The check shows where things go wrong. I am happy to fix it, once or on an ongoing basis.
Good to know
Questions about Error 410?
The most common questions, answered briefly.
Questions about Error 410
Is 410 better than 404?
For pages removed on purpose, yes, because it is clearer. For Google the difference is small. What matters more is that deleted pages return a real error code at all, not 200.
How do I get spam pages out of Google after a hack?
Remove the cause first, then answer the spam URLs with 410 and use the removals tool in Search Console if needed. For an active hack, WordPress emergency support can help.
Can I undo a 410?
Yes. If you remove the rule and the page returns 200 again, Google will pick it up on the next crawl. That can take a while, since Google visits the URL less often.
All status codes at a glance.
2xx: Success
- 200OKAll good: the server understood the request and delivers the page.
- 201CreatedThe request succeeded and created something new, for example a record via an API.
- 204No ContentSuccessful, but the response has no body. Typical for APIs and background requests, not for regular pages.
3xx: Redirects
- 301Moved PermanentlyPermanent redirect: the page now lives at a new address. Search engines switch to the new URL.Causes and fixes →
- 302FoundTemporary redirect: the page is currently available at another address, the original URL stays valid.Causes and fixes →
- 303See OtherRedirect to another page that is fetched with GET, typically after submitting a form.
- 304Not ModifiedThe page has not changed since the last visit, so the browser uses its cached copy. Not an error.
- 307Temporary RedirectTemporary redirect like 302, but the request method (such as POST) is guaranteed to stay the same.
- 308Permanent RedirectPermanent redirect like 301, but the request method (such as POST) is guaranteed to stay the same.
4xx: Client errors
- 400Bad RequestThe server can't process the request because it is malformed, for example due to oversized cookies or a broken URL.Causes and fixes →
- 401UnauthorizedThis page requires you to log in, for example via server-side password protection. No valid credentials, no access.Causes and fixes →
- 403ForbiddenThe server understood the request but refuses access, for example because of file permissions, a firewall or a block.Causes and fixes →
- 404Not FoundThere is no page at this address. It was deleted, moved, or the URL is misspelled.Causes and fixes →
- 405Method Not AllowedThe address exists but doesn't accept this kind of request, such as a POST where only GET is allowed.
- 408Request TimeoutThe server waited too long for the complete request and closed the connection, often on a slow connection.
- 410GoneThe page was removed deliberately and permanently and won't come back. A clearer signal than 404.
- 429Too Many RequestsToo many requests in a short time: a rate limit or bot protection is temporarily slowing down access.Causes and fixes →
- 451Unavailable For Legal ReasonsThe page is blocked for legal reasons, for example by an official order or a country block.
5xx: Server errors
- 500Internal Server ErrorGeneric server error: something went wrong while building the page. With WordPress it is usually a plugin, theme or PHP issue.Causes and fixes →
- 501Not ImplementedThe server doesn't know or support the request method. Rare on regular websites.
- 502Bad GatewayA server in front (proxy, nginx, CDN) didn't get a usable response from the actual server, often because PHP crashed.Causes and fixes →
- 503Service UnavailableThe server is temporarily unavailable due to maintenance or overload. Try again later.Causes and fixes →
- 504Gateway TimeoutA server in front waited too long for the actual server to respond and gave up.Causes and fixes →
- 520Web Server Returned an Unknown ErrorCloudflare error: the server behind Cloudflare sent an empty, invalid or unexpected response.
- 521Web Server Is DownCloudflare error: the server behind Cloudflare refuses the connection, so it is down or blocking Cloudflare.
- 522Connection Timed OutCloudflare error: Cloudflare couldn't establish a connection to the server behind it in time.
- 523Origin Is UnreachableCloudflare error: the server behind it can't be reached, often because of a wrong IP address in the DNS records at Cloudflare.
- 524A Timeout OccurredCloudflare error: the connection to the server works, but it didn't respond in time (100 seconds by default).
- 525SSL Handshake FailedCloudflare error: the encrypted connection between Cloudflare and the server behind it could not be established.
- 526Invalid SSL CertificateCloudflare error: the SSL certificate on the server behind Cloudflare is invalid or expired (with SSL mode "Full (strict)").
No status code: connection errors
- ×Server not found (DNS)There is no server for this domain: it has expired, is misconfigured, or the record with the IP address is missing.Causes and fixes →
- ×Connection refusedThe server is known but doesn't accept connections. The web server isn't running or a firewall is blocking.
- ×TimeoutThe server didn't answer in time. It is overloaded, stuck, or not reachable at all.
- ×Certificate error (SSL)The SSL certificate has expired, doesn't cover this domain, or the certificate chain is incomplete. Browsers show a warning.Causes and fixes →

