404 pages report to your users that a page they wanted is gone. But you can use them to tell you about problems and suggest solutions. But to use them, you need to read your error logs. I was working on a CGI today, and to test it I was watching the error log on the server. While I was watching a bunch of errors came through for another site on my server. In an update I had done last month had removed a page that people still access. I went in and added that page back - netting that site an additional 100 pageviews per day. Too bad I didn't see that sooner! By reviewing the error log regularly, you can solve problems your readers might not tell you about.
Explore Web Design / HTML
Must Reads
Most Popular
I agree that regularly checking error logs is important and that it can pay off. Also, having a fun 404 page with a link back to your site is a good way to turn a users bad experience into a fun surprise.
I personally include the 404 page and all other 4xx and 5xx errors in my PHP template system, they also get hooked to my stats page, and report the event, so I won’t need to look at the logs.
So, if you make a .htaccess error and a user bumps into a non-customized 403 or 500 (that one due to heavy scripts, or some programming error), it’s just as bad. The rest are just rare. I say they should be included too, just in case, one never knows.
A great reminder to may of us. I am planning to not only use .htacess to improve the 404, but also use our analytic tool, WebTrends to scan and analyze the 404’s. Thanks!