If you sell handmade or custom goods online, a visitor who hits an error page is often someone who was close to placing an order or submitting a personalization request. What they see in that moment can determine whether they try again or move on to a different shop. Most website platforms generate default error messages that were written for developers, not for a customer trying to order an engraved gift or a custom-printed mug.
The most common problem with default error messages is that they either display a bare status code like 404 or 500, or they use vague phrasing that gives the visitor no idea what to do next. A more useful approach is to write a short sentence that says what happened in everyday language and then offers one clear action. For example, telling someone the page they were looking for may have moved and providing a link back to your product catalog is more helpful than a blank page or a technical description. You do not need to be clever or humorous; clarity matters more than tone when someone is confused.
Error messages also behave differently on small screens. A message that reads fine on a desktop monitor may get cut off, pushed below the fold, or rendered in a font size that is hard to read on a phone. You can check this yourself by loading your site on a mobile device and deliberately triggering common errors, such as visiting a mistyped URL or letting a form session time out. If the message is not immediately visible and understandable without scrolling, adjust the layout or shorten the text.
For sites that collect custom details like names, dates, or design choices, an error during form submission carries extra risk because the customer may have spent several minutes entering personalization information. If your platform does not preserve that input after an error, the message should say so plainly and let the visitor know they will need to re-enter their details. If the input is saved, say that too. Either way, the customer should not have to guess whether their work was lost.
A straightforward way to test whether your error messages are working is to ask someone unfamiliar with your site to trigger one and then describe what they would do next. If they cannot tell you a concrete next step, the message is not doing its job. This kind of check takes only a few minutes and can be repeated whenever you update your site or add new pages.