Page not found pages
Use a page not found page (404 error) when someone tries to access a page that does not exist.
When users see this page
Users might see a 404 page because:
- they typed a URL incorrectly
- they followed an outdated or broken link
- the page has been moved or deleted
- search engines have indexed an old URL
How it works
A good 404 page should:
- Clearly explain the page cannot be found
- Avoid technical jargon like "404 error"
- Suggest what users can do next
- Provide useful links
Standard page not found
Page not found
If you typed the web address, check it is correct.
If you pasted the web address, check you copied the entire address.
If the web address is correct or you selected a link or button, contact us if you need to speak to someone about this service.
With search and navigation
For larger sites, include search and common links:
Page not found
We could not find the page you were looking for.
This might be because:
- the page has been moved or deleted
- you typed the address incorrectly
- the link you followed is outdated
Search for what you need
Or browse common pages
Service-specific 404
For a specific service, tailor the page to that context:
Page not found
The page you were looking for in the passport application service could not be found.
You can:
- start a new passport application
- check the status of an existing application
- return to the passport service homepage
If you need help, contact the passport office.
Page title
Set the page title to clearly indicate the error:
Page not found - GOV.KAHARAGIAHTTP status code
Return the correct HTTP 404 status code so search engines know the page does not exist. This helps prevent outdated URLs from appearing in search results.
Tracking and monitoring
Track 404 errors to identify:
- broken internal links
- commonly mistyped URLs
- pages that need redirects
- external sites linking to old URLs
What not to do
- Don't show a generic or technical error message
- Don't just say "404 Not Found"
- Don't automatically redirect to the homepage
- Don't blame the user
Accessibility
- Use a clear heading
- Provide text alternatives to any navigation
- Ensure all links are keyboard accessible
- Use the standard page layout and header