If a specific page on a website doesn't load for some reason or if a link is broken, the visitor shall see an error page with some generic message. The page will have nothing in common with the rest of the website, which may make the visitor leave your Internet site. A possible solution in cases like this is a feature offered by some website hosting companies - the option to set your own custom-made error pages that shall have the same design and style as your site and that could contain any text or images that you would like dependent upon the particular error. There are 4 popular errors which can take place and they involve the following so-called HTTP status codes - 400, when your browser sends a bad request to the web server and it cannot be processed; 401, if you are supposed to log in to see some webpage, but you have not done so yet; 403, if you don't have a permission to view a certain page; and 404, in case a link which you have clicked leads to a file which does not exist. In any of these scenarios, visitors will be able to see your personalized content as opposed to a generic error page.
Custom Error Pages in Hosting
If you buy a hosting from us, you shall be able to set personalized error pages for your Internet sites fast and easy, since this function is part of all of our solutions. Once you've created the files and uploaded them to your hosting account, you can go to the Hosted Domains section of your Hepsia CP and click on the Edit button for the specific domain or subdomain. In the pop-up that will appear, you shall see drop-down menus for all 4 types of errors and for each one of them you could pick an Apache default page, a generic page from our system or a tailor-made page. Should you select the 3rd option, you should just input the URL to the file which you have uploaded then save the change. Another way to set personalized error pages is to create an .htaccess file inside the domain or subdomain folder and to include several lines of code in it. If you don't have preceding experience or if you're simply not sure how to do this, you may just copy/paste the code from our Knowledge Base article on that subject.