A removed page and a broken website are not the same thing. The useful question is whether the response matches the resource’s current purpose and gives people an appropriate route forward.
Use a permanent redirect when content has moved to a relevant successor, an appropriate missing-resource response when it is genuinely gone, and direct internal links to current destinations. Fix loops, failed redirects, misleading successful error pages, and broken routes to important content. Ordinary 404s are not a sitewide ranking penalty.
The short answer by case
| Case | Appropriate investigation or response |
|---|---|
| Page moved permanently | Redirect directly to the relevant new URL |
| Page temporarily elsewhere | Use a suitable temporary redirect |
| Content removed without successor | Return 404 or 410 as appropriate |
| Error page returns 200 | Correct the response and content state |
| Internal link points to deleted content | Update the link or destination decision |
| Redirect loop | Repair routing so the destination can be reached |
| Long redirect chain | Point sources directly to the intended destination where practical |
These choices depend on page purpose. Do not apply a global routing rule simply because a crawler reports many missing URLs.
Redirect types
Google’s redirect documentation distinguishes permanent redirects, such as 301 and 308, from temporary redirects, such as 302 and 307. Choose according to whether the move is intended to persist.
A redirect communicates a routing decision; it does not repair an irrelevant destination. Moving an old service page to a generic homepage can disappoint users and may not communicate useful equivalence.
For migrations, maintain a mapping from old URL to intended destination with a reason and validation result. Include important downloads and media where they have moved. Avoid relying on ad hoc rules nobody owns.
Chains and loops
A chain routes through multiple intermediate URLs. A loop prevents completion by returning to an earlier point. Record the full path before proposing a fix.
Where practical, update redirect rules and internal links to the final relevant destination. Test alternate hostnames and protocol normalization in scope so a clean content redirect does not conceal additional routing problems.
Do not delete historical redirects indiscriminately. Old links and bookmarks can still serve users. Consolidate thoughtfully and test representative paths before deployment.
404, 410, and soft 404
A 404 indicates that the requested resource was not found. A 410 indicates it is gone. Google’s HTTP status documentation explains how its crawlers process these responses and distinguishes them from successful responses.
A soft 404 occurs when content looks like an error or empty page even though the server does not provide the corresponding missing-resource signal. For example, a missing product route may return a 200 response containing only “product unavailable” and little useful content.
The fix is to align the response and page state. Sometimes a product is temporarily unavailable but the page remains useful with meaningful product information and alternatives. Sometimes the resource is permanently removed. Make that business decision explicitly rather than forcing every case into one template rule.
Do ordinary 404s hurt the whole site?
A legitimate missing page is a normal part of the web. The concern is broken customer journeys, lost access to useful content, misleading responses, and unnecessary links to obsolete destinations—not an automatic penalty for having any 404s.
Prioritize important URLs and active internal links. A random historical request in a log is different from the primary navigation sending customers to a deleted booking page. Investigate consequence before spending time on every unknown URL.
The Page indexing report can surface missing-resource observations. Treat the report as evidence of discovered URLs and processing states, not a command to redirect everything.
Broken internal and external links
Internal links are under your control and help define current customer routes. Update those that point to removed or moved resources. Use descriptive anchors and direct destinations, consistent with Google’s link guidance.
External links can also matter for readers. If a cited source disappears, find a suitable replacement or revise the claim. Do not substitute a vaguely related page merely to eliminate a warning.
A broken inbound external link may justify restoring valuable content or adding a relevant redirect when an equivalent exists. If the original content is genuinely gone and no successor serves the need, an appropriate missing-resource response may remain correct.
Decision process for a removed page
Ask whether the content still serves a valid purpose. If yes, restore or improve it at the intended URL. If it has moved, redirect to the equivalent. If several pages have been usefully consolidated, map them to the genuine combined resource. If nothing appropriate remains, return 404 or 410 and remove obsolete internal links.
Then test the result. Verify status, destination, content relevance, canonical relationships, internal navigation, and sitemap treatment. Record the decision so future maintainers understand why the URL behaves as it does.
Constructed example: an old beginner guide is merged into a comprehensive current guide that covers the same task. A direct permanent redirect can help old visitors reach the successor. By contrast, redirecting an unrelated discontinued product to the company homepage does not establish equivalent content.
Implementation and monitoring
Group shared causes, such as a route handler returning 200 for every missing URL. Test both valid and invalid routes after the change. Ensure the fix does not make real pages return missing-resource responses.
Monitor important paths after release and keep rollback ownership clear. A corrected response can be verified immediately; search processing and visibility require separate observation. Do not promise that a redirect recovers a particular ranking.
For a wider move, use the migration guide. For the underlying pipeline, read what technical SEO is. If routing problems affect important journeys, request a redirect and status-code review.
Common questions
Do 301 redirects automatically lose ranking value?
Do not assume an automatic loss. Google’s migration guidance says permanent redirects do not cause a loss of PageRank, but relevance and the wider migration still matter.
Should every 404 redirect somewhere?
No. Use a relevant successor where one exists; otherwise a proper missing-resource response is appropriate.
Does a custom 404 page fix a soft 404?
Only if the response and content state are also correct. A visually attractive error page returning 200 can still communicate the wrong state.
Research checked October 25, 2026. Examples and planning frameworks are illustrative unless stated otherwise. Featured imagery is AI-generated editorial photography, not documentary evidence of clients or projects.
