Technical SEO Link Health Checklist: Find and Fix Broken Internal and External Links

Overview

A link is broken when a user or crawler follows it and cannot reach the intended resource. The most visible example is a 404 Not Found response, but link health problems can also involve server errors, redirect chains, incorrect URLs, blocked resources, expired domains, or pages that now contain unrelated content.

Not every 404 is an emergency. A retired page with no useful replacement may be intentionally removed. However, a broken link in a key product page, evergreen guide, navigation menu, or high-traffic referral path deserves prompt attention. The purpose of a website link audit is not to eliminate every unusual status code; it is to identify links that create a poor experience or weaken an important path through the site.

Use a crawler, analytics platform, server logs, browser checks, or a combination of these tools. The tool matters less than the workflow: crawl the site, verify the reported issue, assess its value, apply the right fix, and record the result. For a broader maintenance routine, compare this process with the technical SEO checklist for small business websites.

What to record in a link-audit spreadsheet

• Affected URL: the page containing the link.
• Link destination: the URL being referenced.
• Link type: internal, external, image, download, canonical, or other resource.
• Status code: the response observed during the audit.
• Issue severity: critical, high, medium, or low.
• Recommended action: replace, redirect, remove, update, or monitor.
• Owner and due date: the person responsible for the change.
• Verification date: when the repaired link was tested.

Checklist by scenario

1. Audit broken internal links

1. Start with important page groups. Crawl your home page, main navigation, category pages, service or product pages, top articles, contact paths, and pages that receive organic or referral traffic.
2. Export links returning errors. Pay attention to destinations returning 4xx or 5xx responses. A crawler may also flag timeouts, blocked requests, malformed URLs, or redirect chains.
3. Open the affected source page. Confirm that the link is visible to users and not merely a technical reference produced by a plugin or template.
4. Check the destination manually. A temporary server problem, login requirement, regional restriction, or crawler setting can produce a misleading result.
5. Look for the closest valid replacement. Search your site for an updated version, renamed article, current product, or equivalent resource before creating a new redirect.
6. Repair the source when possible. Updating the link directly is usually clearer than sending visitors through several redirects.

For internal links, a direct replacement is often preferable when the destination has changed permanently. It keeps the page current and makes future audits easier. Review surrounding copy as well: an updated destination may require a more accurate link label or a revised sentence.

2. Review redirects and status codes

Status codes provide evidence, not the entire decision. A page returning 200 can still be irrelevant, thin, inaccessible, or the wrong language or version. A redirected page can be perfectly acceptable when it leads to a closely related, functioning resource. Treat the user’s expected destination as the main standard.

3. Check external links and referral paths

External links can decay when another site changes its structure, removes a resource, changes its domain, or introduces a security or access restriction. Review external links in authoritative guides, comparison pages, partner pages, resource lists, and content that receives regular referral traffic.

1. Confirm that the destination domain is the intended one.
2. Check whether the page is relevant to the surrounding claim.
3. Look for redirects, unexpected downloads, login walls, or unrelated replacement content.
4. Replace the link with a current first-party or authoritative source when appropriate.
5. Remove the reference if it no longer adds value.

If an external link generated meaningful visits, review your analytics before removing it. When replacing a campaign or partner URL, preserve measurement conventions with a consistent UTM parameter and campaign URL process where tracking is appropriate.

4. Decide whether to redirect, replace, or remove

Use this simple decision path:

1. Is there a close, current equivalent? If yes, update the link directly or create a permanent redirect when old URLs still receive visits or external links.
2. Is the page temporarily unavailable? Retest and investigate before making a permanent change.
3. Does the old URL have valuable references or traffic? A relevant redirect may preserve a useful path, but do not redirect unrelated pages merely to avoid an error.
4. Is there no suitable replacement? Remove the link and revise the surrounding sentence so it remains complete.

A redirect should help a visitor reach what they expected. It should not be used as a blanket solution for every 404.

What to double-check

Internal-link context

Inspect links in reusable components such as headers, footers, sidebars, related-post modules, XML-generated menus, and call-to-action blocks. One bad template link can affect many pages. Also review pagination, breadcrumb links, language variants, faceted navigation, and downloadable files.

Canonical and indexed URLs

When a page is renamed, check more than the visible body copy. Review canonical references, structured navigation, XML sitemaps, hreflang references where used, and links from high-value pages. Remove retired URLs from systems that should no longer advertise them, while keeping a relevant redirect when the old address remains useful.

Anchor text and destination relevance

Do not replace a dead link with the first page that appears in search. The new destination should satisfy the original intent. Update the anchor text if the subject, title, product name, or action has changed. For a wider review of link labels and distribution, see the anchor text optimization guide.

Performance and accessibility

Test repaired links on mobile and desktop when the page is important. Confirm that buttons and linked images have clear purpose, downloads use understandable labels, and links do not depend on hover-only behavior. A technically valid link can still be difficult to use.

Common mistakes

• Fixing only the error report. A crawler identifies symptoms; it may not show which broken paths matter most. Combine crawl results with traffic, conversions, backlinks, and page importance.
• Redirecting every missing URL. An unrelated redirect can confuse visitors. Use one only when the replacement is genuinely relevant.
• Ignoring external links. External references can become inaccurate even when your own site is functioning correctly.
• Leaving redirect chains in place. Update prominent source links to the final destination after migrations or URL changes.
• Forgetting non-HTML assets. PDFs, images, scripts, feeds, and downloads can fail independently of ordinary pages.
• Changing a link without documenting it. Without an owner, date, and verification note, the same issue may return during the next content edit.
• Using a shortened URL without checking its destination. If you use shortened links in promotion, verify the destination and tracking parameters before publishing. The guide on shortening URLs without losing SEO or analytics tracking covers that workflow.

When to revisit

Run a focused link check after a redesign, migration, domain change, CMS update, navigation restructure, or large content cleanup. Also audit before seasonal planning cycles when important landing pages, campaigns, or referral partnerships are likely to change.

For an established site, a monthly review of high-value templates and a broader quarterly crawl is a practical starting point. Smaller sites may use a quarterly full audit with checks after every major publishing batch. Increase the frequency when the site publishes heavily, changes inventory often, or depends on many external resources.

At each review, follow this short routine:

1. Export new errors and compare them with the previous audit.
2. Prioritize links on pages with organic traffic, conversions, backlinks, or strong referral activity.
3. Verify each reported issue in a browser or a second tool.
4. Assign a repair, replacement, removal, or monitoring action.
5. Re-crawl after changes and record the verification date.
6. Review recurring failures to identify a template, migration, plugin, or publishing-process problem.

Keep the spreadsheet with your site-maintenance records, and revisit the workflow whenever your CMS, crawler, analytics setup, or URL structure changes. A consistent audit is more useful than a one-time cleanup: it keeps internal navigation dependable, protects valuable referral paths, and gives future editors a clear record of what was checked and why.