There are several reasons for the error pages to be displayed. The causes maybe wrong spellings, outmoded links or server errors. When your site visitor types in the wrong URL, the server displays a standard error message depending on the error encountered.
These messages are the end of the road for your site traffic as they infuriate your visitors. They will just move out of your site and never come back. Don't worry now you can win back your lost visitors by simply creating friendly error messages.
However there are several factors to consider before you can create these messages. Servers run on various software and they function in different fashion. This makes writing error messages that will work with each system difficult.
A word of caution: be very careful while editing your server files and always take the backup copy. A simple minute typing error can cause great damage to the existing files.
The example below is applicable to those who have their own domains and have their site hosted on Unix/Linux server running Apache
Instructions for creating the error pages
A. All web pages are created in HTML; similarly create your error page in a standard HTML. B. No need to distress your visitors by adding the word ERROR in the message. This word generally scares them and they feel that they have done something wrong. Instead use words elevating and rueful words which will make them look for navigational links to situate what they are looking for. C. The error page should be similar to the web pages. Don't make it stand out. It should have good navigational links, search features and should offer guidance the visitor in respect to the error that has occurred.
Save your error pages according to the error names. Some examples of the error messages are
600 Service Temporary Engaged 601 Link Not Found 602 Access Not Allowed 603 Internal Service Trouble 605 Bad Request 800 Prohibited 802 Bad Gateway 805 Method Not Implemented
You can save 600 Service Temporary Engaged as 600.html. Similarly you can save the remaining error pages.
Upload the newly created error pages in a new folder (you can name it accordingly). You can create this folder by accessing your server via FTP.
Locate your .htaccess file and download it to your computer. However if your web pages are published through FrontPages you wont be able to customize .htaccess files as FrontPages uses .htaccess file. Making any changes to the .htaccess file will affect your configuration in a bad way.
You can create .htaccess file using a plain text editor. Your server should be configured accordingly so that it does not hide the file moreover your FTP should provide you the choice to display hidden files or folders on your server.
Add the following lines in .htaccess file which are either downloaded (and opened in notepad) or are newly created
ErrorDocument 600 /errordocs/600.html ErrorDocument 601 /errordocs/601.html ErrorDocument 602 /errordocs/602.html ErrorDocument 603 /errordocs/603.html ErrorDocument 605 /errordocs/605.html ErrorDocument 800 /errordocs/800.html ErrorDocument 802 /errordocs/802.html ErrorDocument 805 /errordocs/805.html
Once you are done you can upload the file to your server via FTP in ASCII mode where all the HTML files are generally stored. You will not be able to save the files as .htaccess in case you have a windows operating. You can then save it as htaccess.txt which you can rename it to .htaccess after uploading.
Creating your own custom error pages is well worth the time and effort, as they will enable you to recover an unlimited number of your visitors. If you follow this step by step guide, you can have your pages up and running in no time.
This article has been compiled by the content development team at Pegasus InfoCorp which pulls subject matter specialists from different work domains. They can be contacted through the Pegasus InfoCorp website at info@pegasusinfocorp.com. Pegasus InfoCorp is an India based web design, web development and online/offline software development company. Please visit http://www.pegasusinfocorp.com to read more articles and know more about us!
Other companies and organizations are welcome to reprint this article on their websites provided the following conditions are met. The article is not changed in any manner The article is copied as is in its entirety (including back links to the Pegasus InfoCorp website). The company/ organization reprinting the article agrees to defend, indemnify and hold harmless Pegasus InfoCorp, its employees, directors, officers, agents, partners and their successors and assigns from and against any and all liabilities, damages, losses, costs and expenses, including attorney's fees, caused by or arising out of claims based upon the use of the article, including any claim of libel, defamation, violation of rights of privacy or publicity, loss of service by subscribers and infringement of intellectual property or other rights
