A useful missing-page response tells the truth, preserves the appropriate status, and offers a few durable recovery routes. The deployed host must be tested because a local template cannot prove production routing behavior.
Finish with
Outcome
A tested missing-page response with the observed HTTP status, direct copy, durable recovery links, and an owner for recurring broken paths.
What you need
- A deployed test or preview address where requesting an invented path is safe.
- Browser developer tools or a command such as curl -I for inspecting the response status.
- Knowledge of durable site destinations and any equivalent replacement for a removed page.
- Access to hosting or application routing when the status does not match the visible page.
The observable problem
Some systems display a friendly “not found” message while returning a success status. Others redirect every unknown path to the homepage. Both hide the missing state from technical tools and can disorient a reader who expected specific content.
Separate layers in the record. The observed fact is “GET /invented-review-path returns 200 and shows the homepage.” The interpretation is “the host may be using a catch-all rewrite.” The recommendation is “inspect route rules and retest an unknown path.” Do not claim the server configuration from the page appearance alone.
Invented for instruction
Fictional worked example
Fictional worked example: Harbor Notes is an invented archive. Before revision, /old-map/ silently opens the homepage with status 200. The visitor sees no explanation and may think the map exists somewhere on that page.
After revision, an unknown path returns status 404 and shows: “Page not found. The address may be old or mistyped.” It offers “Browse the archive index” and “Go to the homepage.” For the specific old map, the editors find a genuine replacement and configure a permanent redirect only after confirming that the replacement contains the same map and context.
The worksheet records both browser copy and technical response. The recovery links are selected because the archive index and homepage are maintained destinations, not because every navigation item belongs on an error page.
Procedure
Request an unmistakably invented path
Use a path that is highly unlikely to collide with real content and contains no personal information. Record the full address, date, visible message, and whether the browser address changes. Test on the deployed environment whose behavior matters.
Inspect the response status
Open the network panel, reload the path, and inspect the document response, or run curl -I followed by the test URL. Record the status and redirect chain. A command-line HEAD response can differ from GET on some systems, so confirm with a normal browser request when results conflict.
Write direct recovery copy
State that the page was not found without blaming the visitor. Offer a small number of descriptive links to durable indexes or the homepage. Do not disguise the error with jokes, a search field that does not work, or a list of unrelated popular content.
Choose behavior for known old routes
Review recurring missing paths. Redirect only when an equivalent replacement exists. Keep a missing response for unknown addresses. Consider a distinct removed response only after technical and editorial review determines that the distinction is useful and supported by the platform.
Retest and assign follow-up
Test a second invented path, a known redirected path, recovery links, keyboard focus, narrow width, and behavior without client-side JavaScript where relevant. Assign an owner to repair important internal links and review route patterns without collecting unnecessary personal detail.
Reusable worksheet
| Requested path | Visible result | Status and redirects | Equivalent replacement | Recovery routes | Owner and action |
|---|---|---|---|---|---|
| /invented-review-path/ | Page not found with direct explanation | 404, no redirect | None | Archive index; homepage | Web maintainer; keep test in release review |
| /old-map/ | Replacement map opens | Permanent redirect to /maps/harbor-1920/ | Confirmed same map and context | Not applicable after redirect | Archive owner; recheck if replacement changes |
Decision rules
- If a genuinely equivalent replacement exists, use an intentional permanent redirect and verify the complete destination.
- If the resource is absent or the URL is unknown, return a missing-page status with useful recovery choices.
- If a resource was deliberately removed and the distinction matters, consider a removed response only after technical review.
- If the failure is temporary, do not disguise it as a missing page; diagnose and communicate the temporary condition.
- If logs contain request paths or network data, limit access and retention according to verified operational and privacy decisions.
Limitations and escalation
- A template file does not prove status behavior. Content delivery networks, application fallbacks, static-host rules, and deployment configuration can change the response.
- This guide does not prescribe a logging system or determine privacy obligations. Missing paths can contain sensitive fragments, so monitoring requires separate review.
- One test cannot find all broken internal and inbound links, localized routes, method-specific responses, or temporary infrastructure failures. Repeat the check after deployment changes, and use a broader link inventory when many routes have moved or an old campaign generated substantial inbound traffic.
Review list
Check the work
- At least two invented paths were tested on the deployed environment.
- The visible message and actual response status were recorded separately.
- Recovery links are descriptive, durable, keyboard reachable, and working.
- Redirects are limited to verified equivalent replacements.
- Important recurring paths have an owner and privacy-aware follow-up.
Review again when
- A hosting or routing migration
- A framework fallback changes
- A major section is retired
- Missing-path patterns increase
- Recovery destinations move or disappear