Distinguish a mistyped link from removed content
Start with the requested address, where it was found and what the visitor wanted to reach. Did it come from your navigation, an old campaign or an external link? If the correct page exists but your link is wrong, fix the link. That is different from choosing a replacement for a discontinued offering.
Use concrete examples. An installation guide may have moved while retaining the same instructions. That provides a clear redirect candidate. A discontinued service without a replacement should not be represented as though the homepage supplies the same help. Compare content and user tasks, rather than shared keywords alone.
Choose around the content's actual continuation
Record whether a relevant replacement exists and ask the content owner to confirm the decision. Use a permanent redirect for a permanent move when appropriate. Where the address remains missing, its response should reflect that state.
Google distinguishes successful responses, redirection and missing content when processing HTTP results. An error message returned with a success status can become a soft 404. Review visible content and response together: attractive error-page design does not establish that the server responds correctly.
| Situation | First useful check |
|---|---|
| Incorrect internal link | Correct the link to its existing destination |
| The same content has moved | Verify the replacement and plan the redirect |
| Content removed without replacement | Provide helpful error content with the correct status |
| Operational failure on an existing page | Investigate the service rather than assuming removal |
Make the error page helpful
Explain that the page could not be found. Offer a few understandable routes, such as the service overview, guides or contact page. Choose links that actually exist in the visitor's language. A long directory of every address is not necessarily an easier recovery path.
Let the visitor choose the next step. Automatic forwarding can erase context before the person understands what happened. Avoid an empty search box if the website has no working search function. Reuse the brand's visual design while clearly identifying the missing-page situation.
Verify the response in the intended delivery environment
Open a safe address that does not exist and check both the HTTP status and visible content. Follow a planned redirect to its final destination, checking for a further error or an unnecessary chain. Include direct links and normalised address variants where your rules can affect the response.
A local static preview does not establish how a Worker or another production host handles unknown addresses. Review the intended configuration before an authorised release and perform a follow-up when publication is allowed. Do not list the 404 page as ordinary indexable content in the sitemap. Maintain a small decision log containing old address, action, owner and test result. It helps distinguish intentional removals from new regressions.