A website link audit helps you find broken destinations, verify redirects, and keep important journeys working after content changes or migrations. This repeatable checklist explains what to scan, which status codes and patterns to record, how to prioritize fixes, and when to run the process again.
Overview
Links change for ordinary reasons: a page is renamed, a product is removed, a domain structure is reorganized, or an external site changes its URL. A link that worked when an article was published can later return an error, redirect to an unrelated page, or pass through several unnecessary steps.
A website link audit is a controlled review of those destinations. It should cover internal links, external links, navigation, redirects, downloadable files, images or embedded resources where relevant, and important links in campaign or conversion journeys. A broken link checker and redirect checker workflow can help organize the technical process, but the most useful results come from combining automated scanning with human review.
The goal is not to remove every redirect or treat every non-200 response as a failure. The goal is to confirm that each important link reaches an appropriate destination, does so efficiently, and supports the task the visitor expected to complete.
What to track
1. Link inventory and location
Record the source page, the linked URL, the link type, and its location on the page. Useful location labels include main navigation, footer, body copy, call to action, related content, form confirmation, and downloadable asset. The same destination may deserve different priority depending on where it appears.
For internal links, identify the page's canonical or preferred URL where your site uses one. For external links, record the destination host separately so you can group recurring failures by domain. Include links generated through templates or components, not only links entered in individual articles.
2. HTTP status and redirect behavior
Capture the response status returned by each URL and, when possible, the complete redirect path. A successful final response does not necessarily mean the link is well maintained. A redirect may be intentional, but a long chain can indicate that older redirects were never consolidated. A redirect loop prevents the destination from loading at all.
For every redirected URL, check:
- Whether the first redirect points to the intended destination.
- How many redirect steps occur before the final response.
- Whether the chain contains a loop or repeatedly alternates between URLs.
- Whether the final page is relevant to the original link text and context.
- Whether protocol, host, or trailing-slash variations create avoidable extra steps.
A redirect checker or URL redirect test is useful here, especially after a domain change. Do not assume that every redirect should be removed: redirects can be part of a deliberate migration or URL management plan. Record the reason and owner instead.
3. Broken and questionable destinations
Separate hard failures from review cases. Hard failures include links that cannot be resolved, return a not-found response, or consistently fail to connect. Review cases include a page that loads but has changed topic, a link to a temporary campaign page, an unexpected authentication screen, or an external site that blocks automated requests.
Also track soft errors. A server may return a technically successful response while displaying an error page. A link may resolve to a generic homepage after a product or article was removed. These cases require someone to compare the destination with the promise made by the source page.
4. Business and SEO context
Record whether the affected link supports a primary conversion, a key navigation path, a high-value page, or a low-priority reference. Track internal-link changes that affect the route to important pages, and note whether a page has many incoming links from your own site. This context makes the audit actionable rather than turning it into an unranked list of URLs.
Keep a small change log with the original URL, issue, decision, replacement URL if any, date, and responsible owner. For trackable campaign links, document the intended destination before changing the URL. Guidance on UTM parameter governance can help prevent a link repair from introducing inconsistent campaign parameters.
Cadence and checkpoints
Use a layered schedule rather than waiting for a large annual audit.
- After a migration: scan the complete site or every affected URL set before launch, immediately after launch, and again after redirects have been deployed. Test priority journeys manually.
- Monthly: review monitored URLs, newly reported failures, important navigation, forms, downloads, and recently published or updated pages.
- Quarterly: run a broader internal and external link audit, review redirect chains, and inspect recurring failures by host, template, or content area.
- After major releases: check shared components, routing changes, authentication flows, product links, and any pages affected by a CMS or application deployment.
- During content updates: verify old references while editing a page, particularly links to time-sensitive events, product versions, documentation, and downloadable files.
At each checkpoint, preserve the scan date and tool settings. A recurring audit is easier to interpret when the scope is comparable. If a crawler cannot access part of the site, document the limitation and test that area through an appropriate authenticated or manual process instead of treating it as complete.
How to interpret changes
Look for patterns before fixing rows one at a time. A sudden increase in failures after a migration may point to a routing or redirect rule rather than dozens of unrelated editorial mistakes. Many broken links from the same template suggest a shared component issue. Repeated external failures from one host may reflect a change on that site, an access restriction, or an outdated collection of references.
Prioritize issues using four questions:
- Does the link block a key task, such as signing up, purchasing, downloading, or contacting the organization?
- Is the source page important, heavily linked, or frequently visited?
- Is the issue site-wide, repeated, or likely to affect many URLs?
- Can the problem be corrected by updating the source link, consolidating a redirect, restoring a destination, or removing an obsolete reference?
Fix high-impact internal issues first. Replace an outdated URL with the correct destination when the content has moved. If the destination is permanently gone and no suitable replacement exists, remove or rewrite the reference rather than sending visitors to an irrelevant page. For external links, consider whether a current, trustworthy alternative supports the original context; if not, rewrite the sentence so it does not promise a resource that no longer exists.
Review redirects separately from broken links. A single intentional redirect may be acceptable, while a chain across several old URLs is a maintenance signal. When changing redirect rules, test both the original URL and the final destination, including common variations such as HTTP versus HTTPS, uppercase characters where relevant, and trailing slashes.
When to revisit
Run the next audit on a monthly or quarterly schedule based on how often the site changes, and add event-driven checks for migrations, redesigns, domain changes, CMS updates, and large content releases. Revisit sooner when monitoring shows a new cluster of failures or when analytics indicate that visitors are abandoning a journey connected to a recently changed link.
Use this practical closeout checklist after every audit:
- Export the scan results and record the date, scope, and exclusions.
- Group issues by source template, status, destination host, and business priority.
- Manually verify the most important links and every unusual status or redirect path.
- Assign owners and due dates for repairs, then record the selected fix.
- Rescan repaired URLs and confirm the final destination is relevant.
- Review unresolved items at the next checkpoint instead of allowing them to disappear from the queue.
For teams managing shortened, campaign, or QR-based URLs, include those links in the same inventory. A destination can be technically available while its tracking or routing configuration is wrong. Related guidance on link analytics metrics can help distinguish a working URL from a working user journey. Consistent audits turn broken-link repair from a one-time cleanup into a manageable part of website maintenance.