A missing page is often treated as a design afterthought. For a local business, it may be the first page someone sees after tapping an old social post, saved estimate link, or search result. The owner needs to decide whether that URL is genuinely gone or whether a buyer should reach a new version. This guide is an acceptance test for that decision. The navigation guide covers working menu routes, while the launch checklist covers the rest of the site.
Demand for this exact question remains an unmeasured hypothesis after the finalized September 3 to September 30 Search Console review. The five-row record and example are editorial tools, not a Zendory customer test or evidence of a conversion lift. Use them on the actual website with the owner and builder.
Decide whether the page is missing or moved
Before designing the error message, inspect the old URL and the content it represented. If a service page moved to a clear successor with substantially the same buyer task, map the old address to that successor and verify the redirect. If the service no longer exists and there is no relevant replacement, a real 404 page is more honest than sending every visitor to the homepage. A former booking URL should not quietly become a different service's checkout. The owner approves the replacement relationship because a technically valid redirect can still mislead a buyer.
Google Search Central's crawling-error guidance distinguishes a missing page from content that moved. It recommends a 301 redirect when a clear replacement exists and an HTTP 404 response for a custom missing-page view. It also describes the soft 404 problem when a page looks missing but responds as if content exists. That is an implementation claim about status codes, not a guarantee that Google will index a particular page.
Use a five-row 404 acceptance record
Give the builder a short record for each representative missing URL: the requested address, expected state, tested response, recovery action, and owner approval. The table below separates the visible page from the server response. Mark a row failed when the route is wrong even if the page looks polished. Record the test date because a later website migration can break a previously correct redirect.
| Row | Accept when | Hold or repair when |
|---|---|---|
| HTTP state | A genuinely missing URL returns 404; a clear replacement uses a verified redirect | The page says missing but returns 200, or every old URL jumps to the homepage |
| Explanation | The copy plainly says the requested page could not be found without blaming the visitor | A branded joke or graphic hides the actual problem |
| Recovery | Current service, contact, and homepage routes are few, descriptive, and working | Links lead to retired offers, stale phones, or another 404 |
| Access | Phone layout, keyboard focus, link names, and readable text let a visitor choose a route | Controls clip, lose focus, or rely only on an image for the explanation |
| Ownership | The business can identify who reviews old links and approves replacements after changes | No one owns redirects, internal links, or the missing-page copy after launch |
Do not turn the 404 page into a sitemap of every article and offer. A visitor arriving from a retired service needs a clear route to current work or a monitored contact path. A visitor who mistyped an address may want the homepage or main menu. The owner should choose destinations using actual buyer tasks, then verify each link from a phone. Google's guidance suggests familiar site navigation and useful links; it does not mandate a specific number or visual template.
Test a real miss from the browser and server
Ask the provider for a URL that has never existed, such as a random path under the site's domain. Open it in a private browser window and note the visible headline, links, focus order, and mobile wrapping. Then inspect the network response or use a header request to confirm the server sent 404. A screenshot alone cannot prove the status code. Repeat with one formerly valid page that has a known replacement, and confirm its redirect reaches that exact current destination rather than an unrelated generic page.
Follow each prominent recovery link. The footer acceptance record is useful here because a shared phone link may be stale even when the 404 content is new. Check 320 and 390 pixel widths with a long old URL or service name, enlarged text, Tab and Enter navigation, and a keyboard-visible focus state. If the site has a search box on the error page, use a real business query and test its empty and error states; an unmaintained search field can create another dead end. The site-search acceptance guide tests whether that feature helps real buyers and who will maintain its results.
Rehearse a retired-service link
Imagine a fictional appliance-repair business that stopped offering microwave repairs. A three-year-old social post still links to the former microwave page. The business now repairs refrigerators and washers, but neither is an honest substitute for a microwave appointment. These details are invented solely for the test, not a Zendory customer case. A builder proposes redirecting the old URL to the current refrigerator booking page because it keeps visitors inside the site. The owner rejects that mapping: a buyer could believe microwave service remains available.
The owner instead approves a missing-page response with a plain explanation, a link to the current service list, and a monitored contact route for questions about an existing appointment. The provider verifies HTTP 404, checks that no new internal menu or footer link points to the retired page, and updates the old social link where the business controls it. If an old paid customer still has an open job, the business handles that promise directly. The 404 page helps new visitors recover; it does not resolve individual service obligations.
Keep the failure route in the website handoff
Request a small redirect map and a named owner for future service, location, and URL changes. The map should record old URL, replacement or 404 decision, reason, approver, and the date someone followed the route. The provider implements the technical response and demonstrates it. The business approves whether a replacement really serves the same buyer intent. Review old links in navigation, articles, profile listings, booking pages, and campaigns after a site restructure.
A 404 page is a recovery tool, not a substitute for fixing broken internal links. Track actual missing-page requests and repair important inbound or internal routes when evidence supports it. Keep 404 counts, qualified inquiries, booked work, and paid conversions separate; a lower error count alone does not prove customers found the right offer. If comparing providers, ask whether 404 status, redirects, internal links, and post-launch ownership are included. Zendory's website-build packages give a starting point for that scope discussion.