Use 404 Not Found when a URL has no available page and you are not specifying whether it will return. Use 410 Gone when you know the resource has been deliberately removed and the change is likely to be permanent. That is a difference in HTTP meaning, not a shortcut for faster Google indexing changes. Before choosing either response, check whether the content moved to a suitable new URL.
- 404 is not necessarily temporary. It says the server cannot provide the requested resource without declaring how long it will remain unavailable.
- 410 expresses likely permanence. Google Search handles 404 and 410 alike for indexing purposes; neither guarantees faster removal or ends future crawling forever.
- Choose by what happened to the URL. Redirect genuinely moved content, return 404 or 410 when there is no replacement, and verify the HTTP response rather than relying on what the error page looks like.

404 vs 410: The HTTP Difference
Both responses belong to the HTTP 4xx class, but the HTTP specification makes a useful distinction. A 404 says the server has no current representation of the requested resource, without establishing whether that absence is temporary or permanent. A 410 says the resource is no longer available and that the condition is likely to be permanent.
| Question | 404 Not Found | 410 Gone |
|---|---|---|
| What does it communicate? | The requested resource is unavailable. | The resource has gone and is unlikely to return. |
| Does it establish permanence? | No. | It indicates likely permanence. |
| Can it describe a deleted URL? | Yes, even when the deletion is permanent. | Yes, when the publisher knows the resource is being retired. |
| Does Google promise faster removal? | No. | No. |
A misspelt address or a deleted article with no successor may quite reasonably return 404. A campaign landing page that has been deliberately retired may return 410. Neither code prevents the publisher from serving content at that URL again later.
Both 404 and 410 are also heuristically cacheable under RFC 9110 unless other cache controls apply. That concerns HTTP caching, not a guaranteed difference in Google’s deindexing speed. For the wider distinction between fetching a URL and including it in search results, see MOCOBIN’s crawling and indexing guide.

What Google Actually Does With 404 and 410 Pages
Google’s HTTP status code documentation says that its crawlers treat 4xx responses the same way, apart from 429 Too Many Requests. For Google Search, a URL returning 404 or 410 is not indexed as an available page. If it was indexed previously, its listing is removed over time; crawling of that URL gradually becomes less frequent.
There is no published rule that a 410 is removed sooner than a 404. Nor does either response order Googlebot never to visit the address again. The stronger meaning of 410 is useful for communicating a publisher’s intent, but it is not an indexing-speed control.
A normal 404 is not, on its own, a penalty against the rest of the site. Broken internal links still deserve attention because they send readers to dead ends. But a deleted page that correctly returns 404 does not need an elaborate SEO repair simply because it appears in a Search Console report.
Be more cautious with a soft 404: the page looks missing or empty while the server may return 200 OK. Google can identify such pages and exclude them from Search. On large websites, Google says soft 404 pages may continue to be crawled unnecessarily. Ordinary 404 and 410 responses are not equivalent to this problem.
Google’s crawl budget guidance is primarily aimed at large or rapidly changing sites. It recommends proper 404 or 410 responses for removed URLs, but that does not mean a handful of expected 404s will reduce a smaller site’s search visibility.

Choose and Implement the Right Response
The first question is whether the old URL still has a useful destination. A redirect, 404 and 410 solve different problems. They are not interchangeable methods of removing a page from search results.
| Situation | Usually appropriate | Reason |
|---|---|---|
| Content moved permanently to a genuinely equivalent page | 301 or 308 redirect | Send visitors and crawlers to the new location. |
| Content is temporarily available at another URL | 302 or 307 redirect | Indicate that the move is not intended to be permanent. |
| Page was removed and there is no suitable replacement | 404 | A clear missing-page response is sufficient. |
| Page was deliberately retired and is unlikely to return | 410, if desired | Communicates the intended permanence; 404 is still acceptable to Google. |
| Address was never valid or contains a typing mistake | 404 | No existing resource is available at that address. |
| Content is temporarily unavailable because the server is undergoing maintenance | 503, where appropriate | Signal a service problem rather than falsely declaring the page removed. |
For permanent moves, the destination should satisfy substantially the same reader need. Redirecting a deleted product, article or campaign to an unrelated homepage is not a substitute for finding a real replacement. MOCOBIN’s 301 and 302 redirect guide covers the separate question of implementing URL moves.
Apache example: return 410 for an intentionally removed path
On Apache with mod_rewrite enabled, a rule in an appropriate .htaccess context can return 410 for one retired URL:
RewriteEngine On
RewriteRule ^old-page/?$ - [G]
The [G] flag means Gone and returns HTTP 410. The exact rule depends on the site’s routing and configuration. Check rule order, CMS behaviour and any CDN or caching layer before deploying it. Apache’s mod_rewrite flag reference explains the behaviour.
Most content management systems can return 404 automatically when a page is removed. You do not need to force a 410 for every deleted post. If a product or article is merely unavailable for a short period and its page still serves a useful purpose, consider keeping that valid page live rather than marking it missing.

Test the Status Code, Not Just the Error Page
A custom error page may look helpful while the server incorrectly returns 200 OK. The browser’s Network panel shows the response status for the requested URL. You can also test a GET request from the command line:
curl -sS -o /dev/null -w "%{http_code}" https://example.com/old-page
The result should be 404 or 410 for a truly missing URL. A redirect should show the intended 3xx response first and lead to a working destination. Check the final destination separately rather than assuming a redirect is correct because the old address loads something.
For Google-specific checks, use Search Console’s URL Inspection tool to compare Google’s recorded information with an available live test. Reports and inspection data may not reflect the newest server change immediately. Browser and command-line tests tell you what the server is returning now; Search Console answers a different question about Google’s view of that URL.
Four mistakes worth checking
- Returning 200 on a missing page: This can create a soft 404. Keep helpful navigation on the error page, but return the appropriate HTTP status.
- Redirecting every old URL to the homepage: The destination may not meet the user’s original need, and Google may treat irrelevant redirects as soft 404s.
- Blocking a deleted URL in robots.txt instead of returning a missing-page code: Google may not be able to crawl the URL to observe its 404 or 410 response.
- Confusing a server outage with a deletion: HTTP 429 and 5xx responses have different implications for crawling. Investigate availability problems rather than converting them into permanent missing-page signals.
An error page can still provide a search field, navigation and a link to relevant content. Those elements assist visitors; they do not replace the HTTP status in the response header.

Which Missing URLs Should You Investigate?
Start with URLs that visitors or your own site still rely on. A broken link in primary navigation, a recently deleted article with relevant incoming links, or a current sitemap entry that points to 404 is a stronger reason to act than an old address requested once by a crawler.
If the page should exist, restore it or correct the link. If it has genuinely moved, point the old URL to the closest relevant successor. If it was deliberately removed without a replacement, keep the correct 404 or 410 and remove stale internal references. MOCOBIN’s guide to finding and fixing 404 errors covers that investigation in more detail.
When the concern is crawler capacity rather than a broken visitor journey, look at the site’s scale, server availability and actual crawling evidence first. The crawl budget guide explains when that becomes an operational priority.
The useful end state is modest: the server tells the truth about the URL, visitors can find their way to relevant content, and internal links no longer point at unintentional dead ends. Changing an appropriate 404 into 410 solely to accelerate Google removal does not offer a documented advantage.
- IANA HTTP Status Code Registry (RFC 9110)
- MDN Web Docs: HTTP Response Status Codes
- RFC 9110: HTTP 404 Not Found
- RFC 9110: HTTP 410 Gone
- Google: How HTTP Status Codes Affect Crawlers
- Google Search Central: Troubleshoot Crawling Errors
- Google: Optimise Your Crawl Budget
- Google Search Central: Redirects and Google Search
- Apache HTTP Server: RewriteRule Flags











