How to create a custom error page in cPanel
cPanel Error Pages let you show a clearer message when someone opens a URL that does not exist, does not have permission, or fails temporarily. This is useful after moving pages, changing links, or launching a new site on shared hosting.
The most common case is customizing the 404 error, but you can also review 403 and 500 if you need to guide visitors better. If your site uses a CMS such as Joomla or another application, confirm first whether the theme or plugin already handles those errors.
Before you start
- Have access to cPanel for the account where the domain is hosted.
- Decide which domain or subdomain will use the custom page.
- Prepare a short message with a link back to the home page or contact page.
- Avoid including internal paths, usernames, PHP versions, or technical server details.
Choose domain and error type
- Log in to cPanel and use the top search box to find Error Pages. If your panel is localized, the tool may appear as Páginas de error.
- Open the tool and select the domain or subdomain you want to modify.
- Choose 404 if you want to customize the page shown when a URL does not exist.
- Use 403 only if you want to explain blocked access, such as protected folders or restricted permissions.
- Use 500 carefully; if it appears often, it is better to fix the error cause first.
- Confirm that you are working on the correct domain before editing the content.
Write the page message
- Write a short text that explains the problem in simple language, for example:
We could not find this page, but you can go back home. - Add a link to the home page or a contact page so the visitor is not stuck.
- If cPanel shows buttons for inserting variables, use them only if you understand which data they will show visitors.
- Do not publish sensitive information such as file paths, account names, internal emails, or complete technical messages.
- Keep the design lightweight; if you need a very visual page, create your own HTML file and link it from your site or CMS.
Save and test
- Click Save or the equivalent button shown by your cPanel version.
- Open an incognito window to avoid browser cache.
- Visit a made-up URL under the domain, for example
https://yourdomain.com/page-that-does-not-exist. - Check that your custom message appears and that the internal links work.
When to use the CMS instead of cPanel
- If your CMS already loads for missing URLs, the theme usually controls the 404 page.
- If you use a cache plugin, clear the cache after changing the page.
- If the error appears only on CMS posts or pages, check permalinks before changing cPanel.
- If the browser shows a CMS page instead of the cPanel page, adjust the design from the CMS.
Verify result
- The made-up URL shows your custom message.
- The link back to the home page or contact page opens correctly.
- The page does not reveal internal paths or sensitive technical information.
- The real site error did not change; only the message visitors see improved.
Common errors
- The generic browser page still appears: clear cache, test in incognito, and confirm that you edited the correct domain.
- The CMS shows another 404 page: edit the theme template or settings because the CMS is responding before cPanel.
- The 500 error continues after customizing the page: check the error cause in files, plugins, or
.htaccess; the custom page does not fix the failure.
Recommended reading
Still need help?
If this guide didn’t solve your issue, our team can help you via ticket.