A visitor opens an old link and sees “Page not found”, but the server reports that the request succeeded. The screen and the technical response disagree. A well-designed missing-page screen needs both a useful customer journey and an appropriate HTTP status.
For a business website, this matters when pages are removed, addresses are mistyped or a new release changes routing. Test those journeys before assuming that a friendly error message means the implementation is complete.
Concept illustration of conflicting page and server signals, not a browser screenshot or an ITZ client installation.
Understand the two signals
Google’s HTTP status guidance explains that a successful 2xx response does not guarantee indexing. If the returned content looks like an error or empty page, Search Console can classify it as a soft 404. A 404 response instead signals that the requested resource was not found.
The practical lesson is to check the actual response, not just the words on the page. A developer should inspect the main document request and any redirects involved. Client-side applications and hosting rewrite rules can make an error screen look correct while the original request still returns success.
Classify the URL before choosing a remedy
Use three categories. A page that should exist needs its content or routing repaired. A page with a genuine replacement may need an appropriate redirect. A resource that does not exist and has no equivalent needs an honest missing-page response and useful navigation.
Do not send every unknown address to the homepage merely to avoid visible errors. It can leave the visitor unsure where the requested information went. The website redirect review guide covers replacement destinations; this guide focuses on the missing-resource case.
ITZ’s website development service can help review the routing and visitor journey together. Request a missing-page handling review with representative broken URLs and the hosting or application platform.
Make the error screen useful
State plainly that the requested page could not be found. Provide recognisable routes to the relevant service catalogue, site search where available and an enquiry option. Keep the normal branding and readable navigation so the visitor can recover without starting again in a search engine.
Avoid claiming that the user caused the problem. The link might be outdated, shared incorrectly or broken within the website itself. If the page is part of an application, distinguish a missing record from a temporary service failure and from information the user is not authorised to access.
Test both direct visits and in-site navigation
- Use a controlled, clearly nonexistent path on the preview deployment and inspect its HTTP response.
- Open the same path directly in a browser, then test a missing route reached through the application’s own navigation where applicable.
- Check that the error screen’s links work and the visitor can reach an appropriate service page or enquiry form.
- Verify a real existing page still returns its intended content and status.
- After deployment, repeat the representative checks against the production host rather than assuming preview routing is identical.
Also review removed URLs listed in the sitemap or linked from other pages. Fix those references at source where possible. A correct error handler does not make broken internal links acceptable.
Use search reports as evidence, not a promise
The page indexing investigation guide helps separate discovery, crawling and indexing questions. Record the URL, observed status, expected behaviour and repair decision. Search reports can take time to reflect a change; do not claim that correcting a status immediately restores visibility or rankings.
Add missing-route checks to the website launch checklist, particularly after changes to hosting rewrites or application routes. Keep intentional error behaviour in the handover so a future release does not undo it.
Review Your Missing-Page Handling
Bring ITZ a short list of affected URLs, their intended replacements where any exist and the current hosting setup. We can discuss response codes, routing and visitor recovery. Review Your Missing-Page Handling through the article-specific form below.
Primary documentation reviewed on 31 October 2026. Examples describe proposed checks, not client case studies.
