cPanel® Blog

Error Pages, A Hidden Branding Opportunity

Let’s face it, links break, servers go down, pages go MIA and somehow all your web visitors manage to land on the dreaded error page. Eek! While there’s no full-proof way to ensure you will never have to serve up an error page, with cPanel you can, at the very least, make it a page that is enjoyable to look at.

In cPanel & WHM 56, users can create custom Error Pages for loads of different HTTP status codes. Whether it’s a bad request, or a missing page, bandwidth limitations or gateway timeouts, cPanel users can navigate to the Advanced settings of their cPanel account and select Error Pages to begin customizing away.

Why use custom error pages?
Think of customized error pages as an opportunity to make the best out of a bad situation. Sure, your site visitor or user isn’t getting the content they desire, but until the issue can be remedied, you can use that moment as an opportunity to promote a new product, share additional services, or just to let them know that the site should be back up and running soon.

Get started!
Head over to your Advanced feature section and begin exporting the variety of error pages available to customize. Find out more about custom error pages in our documentation and let us know your thoughts by leaving a comment below!

Client Request Errors
400 – Bad Request
401 – Authorization Required
403 – Forbidden
404 – Not Found
405 – Method Not Allowed
406 – Not Acceptable (encoding)
407 – Proxy Authentication Required
408 – Request Timed Out
409 – Conflicting Request
410 – Gone
411 – Content-Length Required
412 – Precondition Failed
413 – Request Entity Too Long
414 – Request-URL Too Long
415 – Unsupported Media Type

Server Errors
500 – Internal Server Error
501 – Not Implemented
502 – Bad Gateway
503 – Service Unavailable
504 – Gateway Timeout
505 – HTTP Version Not Supported

JR

JR Miller is a Copywriter and Social Media Marketer. A trained wordsmith and a prolific idea guy, he spends his time developing the voice, tone, and messaging for cPanel.

  • Lewis

    All I will add is that all website administrators should also include contact details as well as a way to report the broken page if you’re not so “hands on” with the error log. That way, if a customer was trying to answer a question, they could, for example, call you, and both report the 404 and get an answer rather than quitting the tab and losing that person altogether.