Link Checker for Microsoft Word: Find Broken Links FastBroken links in a Microsoft Word document are more than a minor annoyance — they undermine credibility, reduce usability, and can break workflows when collaborators or readers expect clickable references, embedded resources, or cross-references to work. This article explains why broken links happen, how to find them quickly, and practical ways to fix and prevent them in Microsoft Word documents of any size.
Why broken links matter
- Broken links harm reader trust and the professional appearance of documents.
- They interrupt navigation in long documents that use hyperlinks or cross-references.
- In business and academic contexts, broken links can lead to missed resources, lost sales, or failed citations.
- Accessibility and automated processing (e.g., document conversion to PDF or web) often rely on valid links.
Common causes of broken links in Word
- File moves or renames: Linked files stored on a local drive or network have paths that change.
- Broken web URLs: Target websites may change URLs, remove pages, or go offline.
- External resource access: Permissions, network access, or expired subscriptions can make resources unreachable.
- Improper copy-paste: Copying text with links from other sources sometimes yields malformed links.
- Cross-reference issues: After heavy editing or reflow, internal cross-references (bookmarks, headings) may point to removed or renamed anchors.
Types of links in Word
- Hyperlinks to web pages (http/https).
- Links to local or network files (file:// paths).
- Cross-references and bookmarks to headings, figures, tables, or bookmarks within the same document.
- Linked OLE objects or inserted files (e.g., Excel spreadsheets, images linked rather than embedded).
- Fields that generate links (e.g., INCLUDEPICTURE, HYPERLINK fields).
Manual ways to find broken links (quick checks)
- Hover and inspect: Hover over hyperlinks to see the target URL; test by Ctrl+Click.
- Use Find (Ctrl+F) for “http” or “.com” to locate web links quickly.
- Check the Links dialog for linked objects: go to File > Info > Related Documents > Edit Links to Files (available when linked objects exist).
- Update fields: select all (Ctrl+A) and press F9 to refresh fields; errors in fields sometimes reveal broken references.
- Inspect cross-references: Review the References tab > Cross-reference to find outdated refs.
These manual checks work for short documents but become impractical with many links or multiple files.
Automated approaches: built-in and third-party options
Built-in features
- Edit Links to Files dialog: shows linked objects (not web hyperlinks) and allows updating, changing source, or breaking the link.
- Check Accessibility: Review tab > Check Accessibility can surface some navigation issues but not all broken links.
- Macro-based checks: You can use VBA macros to iterate through hyperlinks, fields, and linked objects to validate targets programmatically.
Third-party tools and add-ins
- Dedicated link-checker add-ins for Word scan hyperlinks, cross-references, and linked files and produce a report of broken or redirected links.
- Document management systems and proofreading tools sometimes include link validation as part of their feature set.
- Online services: upload or sync documents to services that validate links, but consider privacy when sending documents to third parties.
A VBA macro to find dead hyperlinks and file links
Below is a sample VBA macro that checks web hyperlinks and linked files in the active document. It attempts an HTTP request for web links and checks file existence for local links. (Run in Word’s Developer > Visual Basic editor. Save a copy of your document before running macros.)
Sub CheckLinks() Dim hl As Hyperlink Dim fld As Field Dim linkCount As Long, badCount As Long Dim report As String Dim http As Object Set http = CreateObject("MSXML2.XMLHTTP") linkCount = 0 badCount = 0 report = "Link check report for: " & ActiveDocument.Name & vbCrLf & vbCrLf ' Check Hyperlinks collection For Each hl In ActiveDocument.Hyperlinks linkCount = linkCount + 1 On Error Resume Next Dim target As String target = hl.Address If Len(target) = 0 Then target = hl.SubAddress If InStr(1, LCase(target), "http") = 1 Then ' HTTP/HTTPS link: attempt HEAD request On Error GoTo SkipHTTP http.Open "HEAD", target, False http.setRequestHeader "User-Agent", "WordLinkChecker/1.0" http.send If http.Status >= 400 Then report = report & "Broken web link: " & target & " (Status " & http.Status & ")" & vbCrLf badCount = badCount + 1 End If SkipHTTP: On Error GoTo 0 Else ' Assume file path If Len(Dir(target)) = 0 Then report = report & "Missing file link: " & target & vbCrLf badCount = badCount + 1 End If End If Next hl ' Check linked OLE objects (Links collection) Dim ln As Object For Each ln In ActiveDocument.LinkSources linkCount = linkCount + 1 If Len(Dir(ln)) = 0 Then report = report & "Missing linked object: " & ln & vbCrLf badCount = badCount + 1 End If Next ln report = report & vbCrLf & "Scanned links: " & linkCount & " Broken: " & badCount MsgBox report, vbInformation, "Link Check Complete" End Sub Notes:
- The macro uses a HEAD request which some servers block; results may vary.
- Network latency may slow checks in large documents.
- For cross-references and bookmarks, additional code is needed to inspect fields like REF, PAGEREF, and INCLUDETEXT.
Handling cross-references, bookmarks, and fields
- Cross-references use fields such as REF and PAGEREF. Run a fields update (select all + F9) and look for error text (e.g., “REF error”).
- Use the Navigation Pane (View > Navigation Pane) to confirm headings are present and match references.
- For missing bookmarks, open Insert > Bookmark to see listed bookmarks; recreate or update references accordingly.
Best practices to prevent broken links
- Use relative paths for links to files shared within the same folder structure or repository; avoid absolute local paths when collaborating.
- Prefer embedding critical resources when file size and licensing permit.
- Centralize downloadable assets (host on a stable web server or document management system) and use stable permalinks.
- When distributing, consider converting Word documents to PDF with links preserved; test links post-conversion.
- Document link-creation standards for teams (naming, location, and update procedures).
- Regularly run automated link checks as part of release or publishing workflows.
Workflow examples
- Single-author report: Use the VBA macro above on final draft, fix any broken URLs, and embed critical assets before sharing.
- Team collaboration: Store linked files in a shared cloud folder (use service permalinks), use relative links, and add a CI step that runs a link-checker before publishing.
- Large documentation set: Use an automated script that extracts hyperlinks from many .docx files (they’re ZIP packages with XML) and validates them in bulk, producing a consolidated report.
When to use an external service or tool
- If documents are sensitive, prefer local tools or scripts rather than cloud upload.
- For enterprise-scale documentation (hundreds of documents), use automated pipelines that scan docx files in version control or content repositories.
- If you need advanced reports (redirects, response time, crawler-like checks), use dedicated link-checking software that supports scheduling and reporting.
Quick checklist before publishing
- Run an automated link scan (macro or tool).
- Manually test any critical external links in a browser.
- Update fields (Ctrl+A, F9) and check cross-references.
- Convert to PDF and re-validate links if distributing PDFs.
- Ensure linked files are in shared, stable locations or embedded.
Finding and fixing broken links in Microsoft Word is a mix of the right tools and consistent practices. For small documents, manual checks plus a short macro may be enough. For teams and large documentation sets, adopt relative linking, central hosting for assets, and automated checks in your publishing pipeline to keep links reliable and readers satisfied.
Leave a Reply