Field notes about error-page design, web archaeology, and why getting lost should be better.
- · By The Curator
A missing page is a tiny, accidental self-portrait of a website. That makes it worth saving.
Read field note →
- · By The Curator
Make the error clear, make the recovery obvious, and spend the remaining space on one good surprise.
Read field note →
- · By Steve Bullis
A soft 404 looks missing to a person but returns a successful status to machines. Here is how to find and fix the contradiction.
Read field note →
- · By Steve Bullis
Use the response that tells the truth about the old URL. This field guide separates missing, gone, and moved pages.
Read field note →
- · By Steve Bullis
A custom 404 page should recover visitors without pretending the missing URL is indexable content. Check these ten things before launch.
Read field note →
- · By Steve Bullis
Error pages can be strange, funny, and branded while remaining clear to keyboard, screen-reader, low-vision, and motion-sensitive visitors.
Read field note →
- · By Steve Bullis
Mobile error pages need thumb-sized exits, resilient type, economical art, and less patience for clever obstacles.
Read field note →
- · By Steve Bullis
Sold-out, retired, and mistyped product URLs need different recovery paths. Build an error page that helps without faking relevance.
Read field note →
- · By Steve Bullis
Track enough context to repair real journeys, then group, filter, and prioritize instead of treating every nonsense URL as an emergency.
Read field note →
- · By Steve Bullis
The strongest error-page copy tells the truth first, commits to one premise, and leaves room for an obvious exit.
Read field note →
- · By Steve Bullis
Test the response, routing, recovery links, accessibility, phone layout, resilience, analytics, and a handful of genuinely impossible URLs.
Read field note →
- · By Steve Bullis
A collection of error-page concepts built around one strong premise, from web archaeology to tiny recovery tools.
Read field note →