Re-evaluating Your Web Presence: by Steven Brightbill, Assistant Editor

Contending With Broken Links

Avoid trouble spots that give your Web site an unattended appearance.

To me, encountering a broken link on a Web site ranks high on my list of Internet annoyance factors.

I can overlook other shortcomings such as marginal design and site organization, which are elements that tend to be more subjective in nature. But broken links strike at the very core of what a Web site is all about — functional access to information. A broken link is a dead-end, a barrier, a cyberspace void begging to be occupied.

Furthermore, broken links are usually fairly easy to correct once found. If a broken link persists for several days or weeks — or even months! — it generally means that the site owner isn't paying attention to his/her own Web site and is thus unaware of the problem. Observant and helpful site visitors would do well to send a courteous e-mail pointing out the broken link. Conscientious site owners should appreciate the notice and take corrective action.

Identifying broken links

Web site visitors don't need to hunt for broken links — they become immediately apparent when found. Broken links can occur within the pages of a particular Web site or when following a link to an external Web site.

Within the pages of a particular Web site, the two most common broken link messages are "page not found" or "404 error." These messages may also be encountered when attempting to link to a specific page within an external Web site. Of course, if the server on which the external Web site resides happens to be "down," an "unable to locate server" message will be displayed. That's usually a temporary situation, however, and doesn't mean the link is broken.

Reasons for broken links

Each individual Web page in every Web site is uniquely identified and stored. When a Web site is built, everything that goes into that site goes into the Web site's directory. Think of the directory as a series of pages within a series of file folders within a filing cabinet. In "real" filing cabinets, pages are sometimes renamed, file folder labels might be changed, and folders are moved from one drawer to another. In the process of maintaining a file cabinet, sometimes pages become misplaced, cross-references and indexes fail to get updated, and lo and behold, you can't find the information you're looking for when you try to access it.

In similar terms, that's what causes broken links. Files get renamed, moved, or deleted, and while the information may still be there, it becomes unlocatable and unavailable, thus prompting a "page not found" or "404 error" message.

Even relatively small and seemingly simple Web sites may contain scores or hundreds of uniquely identified files. When Web sites are maintained, updated, and modified, files might be renamed or moved. Obviously, the potential for broken links is greatly magnified in very large and complex sites, and it sometimes seems amazing that more broken links aren't encountered.

Typically, Web authoring programs such as FrontPage, Dreamweaver, and others include features that assist in tracking changes to files, alert users, and provide opportunity to update changes and links. The function and duties of good Webmasters should not be taken lightly. It's their job to accurately oversee or make updates and changes to a Web site, a task that involves the management of hundreds or thousands of pieces of uniquely identified information.

Preventing and fixing broken links

Considering the complexity of Web sites, even smaller ones, the best prevention of broken links (and other potential Web site problems) is limited technical access, routine maintenance, vigilant monitoring, and immediate corrective action. Some monitoring and detection tasks can be automated,* while others, such as actual fixes, require human intervention. If your Web strategy does not provide for these activities, you are inviting trouble.

*Web site diagnostic services that detect Web site errors, such as broken links, faulty HTML coding, and slow-loading graphics.

Doctor HTML
 www2.imagiware.com/RxHTML

NetMechanic
  www.netmechanic.com

OptiView
  www.optiview.com

Web Site Garage
  websitegarage.netscape.com

Sounding Line
March 2002

Interview: ChoicePoint

Editorial

Vendor: Marsh-Berry

Workflow Solutions

Get Rid of Pop-Ups

Vendor: PS4Plus

Contending With Broken Links

Industry Insight: Lessons from "Independent" Insurance Web Sites

Resources

Strategy: Don't Make Me Think (10 Tips)