Not Found and Resource Errors
You'll learn how to design helpful 404 and missing resource messages that guide users back to working paths instead of leaving them stranded.
Why This Matters
When a user requests a page or resource that doesn't exist—whether they followed a broken link, typed a wrong URL, or tried to access deleted content—they encounter a "Not Found" error (typically HTTP 404). A generic "404 - Page Not Found" leaves users frustrated and confused. Your error message should be a helpful guide, not a dead end.
Anatomy of a Good Not Found Message
Clear explanation: Tell users exactly what happened: "We couldn't find that page" is better than cryptic codes.
Provide context: If possible, explain why it might be missing ("This post may have been deleted" or "That user doesn't exist").
Offer next steps: Don't just report the problem—show solutions:
- A link back to the home page
- A search bar to find what they need
- Links to popular sections or categories
- A "Go back" button
Keep the tone friendly: A conversational, empathetic tone ("Oops, we can't find that!") reduces user frustration compared to technical jargon.
Example Pattern
"Page Not Found"
We couldn't find the page you're looking for. It may have been moved or deleted.
Here's what you can do:
• Return to Home
• Search our site
• Browse popular articles
Think of it like a helpful store employee: instead of saying "We don't have that" and walking away, they suggest alternatives and help you find what you need.
Key Takeaway: A good 404 message acknowledges the error, explains it simply, and actively helps users find their way to working content—turning a frustrating moment into a recovery opportunity.