How to Audit Website Broken Links

Audit links as a reader would encounter them. Sample the home page, navigation, article pages, forms, downloads, translated pages, and older URLs rather than checking only a single route. Record the status, destination, redirect chain, link text, and whether the final page matches the promise. A redirect may work technically while sending people to an unrelated page. Check downloadable files for access, current dates, and safe names. Review external links again before publishing content that depends on them. Fix the source reference, then test the surrounding paragraph and navigation so a repair does not create a new dead end.

Define what to check

A link audit is more than finding a page that returns an error. Decide whether you are checking internal pages, external sources, images, scripts, downloads, feeds, redirects, and links inside documents. Include important templates and pages that are not linked from the home page. Keep a dated record so a later audit can distinguish a new failure from an old one.

Start with a representative set of pages and expand according to risk. Check the main navigation, search results, articles, help pages, forms, product pages, and older content. Broken links in a critical support instruction deserve faster action than a link in an archived opinion piece, but both should have an owner.

Inspect more than status codes

A page can return a successful status and still be wrong. Follow redirects, inspect the final title and language, and check whether the destination answers the linked sentence. A link may lead to a login page, a regional error, an unrelated replacement, or a page with changed terms. Do not replace every failed external link with a generic home page.

Test downloads in a browser and with the intended device. Confirm filenames, file type, permissions, and whether the content is current. Check that PDFs and images have usable alternatives when they contain important information. Verify anchors, deep links, email links, phone links, and links that open in a new context.

Fix causes, not symptoms

When an internal URL changes, update the source content and add a redirect when established references should continue to work. Remove or replace external sources that no longer exist, but preserve the claim only when another trustworthy source supports it. If links break after every publication, improve the build, validation, or content process rather than accepting repeated repairs.

Review link text and surrounding context during the fix. A technically working link can still be vague, inaccessible, or misleading. Check mobile wrapping, focus order, contrast, and language. Avoid changing a link destination without checking privacy, authentication, and regional availability.

• Keep private URLs out of public reports.
• Use a safe rate when checking external sites.
• Record the source and reason for replacements.
• Test critical paths after deployment, not only before it.

Monitor after publishing

Set up periodic checks for important links and review reports from users and search tools. Do not treat every temporary network error as a permanent broken link. Confirm repeated failures and use the destination owner's official status information. When retiring content, search for inbound links, update navigation, and provide a useful replacement or explanation.

A link audit protects the path between a reader's question and the information that answers it. Accurate destinations, maintained redirects, accessible text, and clear ownership keep a website trustworthy as its content changes.

Include links in translated and regional versions. A destination that works in one country may not work in another, and a translated page may still point to an old-language explanation. Review canonical links, alternate-language references, feeds, and sitemap entries after a large move. Technical maintenance is complete only when the paths readers and crawlers use both lead to the intended content.