If a particular page on a site does not load for some reason or if a link is broken, the site visitor will see an error page with some generic message. The page will have nothing in common with the rest of the site, which can make the visitor leave the site. A likely solution in such a case is a feature made available from some web hosting service providers - the ability to set your own custom error pages that will have the same design and style as your website and which can contain any text or images that you'd like depending on the specific error. There are four common errors that may take place and they involve the following so-called HTTP status codes - 400, when your Internet browser sends a bad request to the server and it can't be processed; 401, in case you are supposed to log in to see a page, but you haven't done this yet; 403, if you don't have a permission to see a certain page; and 404, if a link that you've clicked leads to a file that does not exist. In all of these scenarios, website visitors shall be able to see your personalized content rather than a generic error page.
Custom Error Pages in Shared Web Hosting
The personalized error pages feature is provided with each and every shared web hosting plan that we offer and you will be able to replace all generic pages with your own with no more than just a few clicks in your Hepsia website hosting Control Panel. You shall need to create the actual files and to upload them to your account, then to set them for a specific domain or subdomain from the Hosted Domains section of the Hepsia CP. You could do this for each and every web site hosted inside the account individually, so that every group of customized pages shall have the exact same design and style as the Internet site it's part of. If necessary, you could always revert back to a default page from our system or to the default Apache server page. One other way to set personalized error pages is to create an .htaccess file in the domain/subdomain root folder and to add a few lines in it. If you haven't done this before, you could simply copy the needed code from our Help article about this.