Map live, moved, removed, empty and temporarily unavailable URLs to honest HTTP responses — a friendly 200 error page can be read as a soft 404.
Next step
Use the free audit or a strategy call to map these frameworks to your current website, market, and revenue goals.
Start free auditRelated services
Related sample
Direct answer
Return the HTTP status that truthfully represents the resource state. Use success for a usable resource, a redirect when another URL is the intended destination, not-found/gone for permanent removal without a replacement, and retryable server errors for genuine temporary failures. Do not return a friendly error page with 200; Google may treat error-like successful responses as soft 404s.
Key takeaways
| State | Response decision | Guardrail |
|---|---|---|
| Valid resource | 200-class | Body must contain the intended resource |
| Permanent move with close replacement | Permanent redirect | Avoid irrelevant mass redirect/homepage |
| Temporary move | Temporary redirect | Reassess expiry and canonical intent |
| Permanently removed, no replacement | 404 or 410 | Keep useful navigation; no deceptive 200 |
| Temporary outage/overload | Appropriate 5xx, often 503 | Retry/monitor; do not convert to permanent removal |
| Legal/access restriction | Applicable status and policy | Qualified legal/security review |
Returning a friendly error page with a 200 status can be treated by Google as a soft 404.
Test chains, loops, query variants, trailing slash/case, edge versus origin, mobile and bot-equivalent requests. Google documents how common status classes affect crawling and processing; HTTP semantics are defined by the standard, while search behavior is consumer-specific.
HTTP status semantics are defined by RFC 9110, while how a search engine treats a given status is consumer-specific documented behavior.
Discontinued products are redirected to a category regardless of relevance. Users cannot find the promised item and the destination does not replace its task. Apply a product-specific lifecycle matrix rather than a blanket redirect.
Taskcover's Technical SEO service audits status codes, redirect chains, and soft-404 risk across a site.
Yes. If the page effectively communicates that content is missing but returns 200, Google may treat it as a soft 404, which can affect how the URL is processed.
410 signals a deliberate, permanent removal, while 404 simply signals the resource is not found. Both are valid for permanently removed content with no replacement; 410 is a more explicit signal of intent.
Not automatically. A blanket redirect can fail the user if the destination does not replace the original task. Evaluate relevance per URL using a lifecycle decision matrix.
Taskcover can audit your URL state matrix and remove soft-404 and redirect-chain risk before it affects crawling.
Google Search Central · Accessed: July 13, 2026
IETF · Accessed: July 13, 2026
Build canonical-only XML sitemaps by template, keep lastmod values truthful, segment for diagnosability, and monitor processing so exceptions stay accountable.
A prioritized technical SEO audit checklist for crawlability, indexation, architecture, canonicalization, rendering, Core Web Vitals, schema, international setup, and migrations.
Choose crawl, index and snippet controls correctly — robots.txt cannot reliably keep a known URL out of search, and a crawler that cannot fetch a page may never see its noindex.
Use the free audit or a strategy call to map these frameworks to your current website, market, and revenue goals.
Taskcover uses necessary storage for security and forms. You can choose whether we use preferences, analytics, and marketing measurement.
