When a visitor hits a page that doesn’t exist, the default server error page is bleak and unhelpful — and it often sends them straight off your site. A custom error page turns that dead end into a helpful signpost that keeps people engaged. Here’s how to set one up.
Why bother with custom error pages
The generic “404 Not Found” page tells visitors nothing useful and looks broken. A custom page can apologise, explain what happened, and — most importantly — offer a way forward: a link home, a search box, links to popular pages. This keeps visitors on your site instead of losing them to a browser back button. It’s a small touch that improves the experience and can even recover a would-be lost visitor.
Creating a custom error page in cPanel
- In cPanel, open Error Pages under the Advanced section.
- Select the domain you’re setting the page for.
- Choose the error code — 404 (Not Found) is the most important and common one.
- An editor opens where you can write the page’s HTML content.
- Use the buttons provided to insert useful dynamic tags, then save.
What to put on a good 404 page
- A friendly, plain-language message: something went wrong, but here’s help.
- A prominent link back to your homepage.
- Links to your most popular or important pages.
- A search box, if your site has search, so visitors can find what they were after.
- Your branding, so the page still feels like part of your site rather than a system error.
Common error codes worth customising
Beyond 404, a few others are worth a custom page: 403 (Forbidden) for access-denied situations, 500 (Internal Server Error) for when something breaks server-side, and 401 (Authorization Required) for protected areas. The 404 is by far the most common, so start there.
If you use a CMS like WordPress
Note that WordPress and similar platforms have their own built-in 404 handling through your theme, which usually overrides the cPanel error page for URLs within the site. In that case, customise the 404 template in your theme instead. The cPanel error pages apply to requests the CMS never sees — genuinely missing files and folders. Both have their place.
Test it
After creating the page, visit a URL you know doesn’t exist (like yourdomain.com/this-page-is-not-real) and confirm your custom page appears and its links work. A quick check ensures visitors get the helpful version rather than the bare default.
It’s a small polish that makes your site feel more considered. If you’d like help designing a branded error page that matches your site, we’re happy to assist.
