An HTTP response indicating that a requested resource is permanently unavailable.
Webmasters checking search engine reports like Google Search Console's Coverage report
01What is 410 Gone and how does it work?
The 410 Gone status code is an HTTP response indicating a requested resource is permanently unavailable. Unlike a 404 Not Found, which implies temporary unavailability, 410 Gone signals that the page has been intentionally removed and will not return. Search engines interpret this as a directive to deindex the URL over time.
When a website permanently deletes a page, it should return a 410 Gone status code. This tells Google and other search engines that the page is no longer available and should be removed from search results.
02What to do about 410 Gone errors
If you encounter 410 Gone errors, first verify whether the removal was intentional. If so, update internal links to point to relevant existing pages. If unintentional, restore the page or redirect it using a 301 redirect. Use Google Search Console's Coverage report to identify affected URLs and submit updated sitemaps.
- Check Google Search Console for 410 errors in Coverage report
- Update internal links to point to active pages
- Implement 301 redirects for unintentional removals
- Remove outdated URLs from sitemaps
- Monitor crawl stats weekly to catch new errors
03How is 410 Gone measured or noticed?
Webmasters notice 410 Gone errors through Google Search Console's Coverage report, where URLs marked as 'Gone' appear with a 410 status code. Site crawlers like Screaming Frog or Ahrefs will also flag these errors during technical audits. Server logs may show 410 responses for specific URLs.
- Review Google Search Console Coverage report weekly
- Use Screaming Frog to crawl site and identify 410 responses
- Check server logs for 410 status codes
- Monitor crawl stats for sudden spikes in errors
- Verify robots.txt isn't blocking access to critical pages
04Common mistakes with 410 Gone
A frequent error is using 410 Gone for temporary page removals. This prematurely removes URLs from search results. Another mistake is failing to redirect or update links after deletion, leaving users and crawlers with dead ends. Some webmasters also forget to remove 410 URLs from sitemaps, prolonging their presence in search indexes.
- Avoid using 410 Gone for temporary maintenance pages
- Always redirect deleted pages to relevant content
- Remove 410 URLs from sitemaps promptly
- Test redirects before removing pages
- Avoid 410 Gone for pages with incoming backlinks
05Limits and common confusions
410 Gone should not be used for pages that might return in the future. It's often confused with 404 Not Found, but 404 implies temporary unavailability while 410 indicates permanent removal. It's also mistakenly applied to pages with 301 redirects, which already signal content relocation.
- Do not use 410 Gone for pages that may return
- Distinguish 410 Gone from 404 Not Found
- Avoid combining 410 Gone with active redirects
- Do not apply 410 Gone to pages with valuable backlinks
- Do not use 410 Gone for pages with seasonal content
06Worked example
Imagine an e-commerce site permanently removes a product page for a discontinued item. The webmaster updates internal links to the category page, implements a 301 redirect from the old product URL to the category, and removes the URL from the sitemap. Google Search Console shows the URL as 'Gone' in Coverage, but the redirect preserves traffic and SEO value.
After removing the discontinued product page, we implemented a 301 redirect to the category page and updated our sitemap. Google Search Console now shows the URL as 'Gone,' but our traffic to the category page increased by 15% within two weeks.
Frequently asked questions
How does 410 Gone differ from a 404 Not Found in terms of search engine behavior?
A 410 tells crawlers the resource is permanently gone and should be removed from the index faster than a 404, which may be treated as a temporary error. Google typically drops 410 URLs from the index within days, while 404s can linger for weeks.
When should I choose 410 Gone over a 301 redirect for a deleted page?
Use 410 when there is no relevant replacement page and the content is truly gone forever. A 301 passes link equity to a new URL; a 410 discards it, so only choose 410 if preserving equity is not a goal.
How do I actually return a 410 status code on Apache, Nginx, or a CMS like WordPress?
On Apache add Redirect 410 /old-url to .htaccess; on Nginx use return 410; in a location block. In WordPress, plugins like Redirection or a custom template_redirect hook can send the header before any output.
Does serving 410 actually speed up deindexing compared to letting the page 404?
Yes — Google's documentation states 410 is a stronger signal for permanent removal. In practice, URLs returning 410 tend to disappear from the index noticeably faster than equivalent 404s.
What breaks if I mistakenly serve 410 on a page that should have been 301 redirected?
You lose all accumulated link equity and rankings for that URL instantly. Traffic drops to zero, and any external backlinks stop passing value. Recovery requires reverting to 200 or 301 and waiting for re-crawling.
How long after serving 410 should I expect the URL to vanish from Google Search Console's index coverage report?
Typically a few days to two weeks, depending on crawl frequency. You will see the URL move from 'Indexed' to 'Removed' in the Coverage report, and the 'Gone' count will rise accordingly.
Asked out loud
spoken, not typedThe same term in the words somebody uses speaking to an assistant rather than typing into a box — written from the situation, which is why each one carries the situation it came from.
Send a 410 Gone header for each deleted URL; Google treats it as a permanent removal signal and deindexes faster than a 404.
410 kills the equity; 301 passes it to a new page. Choose 410 only if there is no relevant replacement and you accept the loss.
Switch those URLs to return 410 Gone; it's a clearer permanent-removal signal and Google removes them from the index faster than 404.