The article promises a useful template. The reader clicks. The destination loads perfectly: a general homepage with no template in sight.

A technical link checker might see a successful response. The reader has reached a dead end anyway. That is why a useful link-repair session needs both a machine's inventory and a person's sense of what the page promised.

Try this on a small website you own or are authorized to maintain. Begin with a few important reader journeys: the latest article, the page that explains your service, and a page people use to find a resource. The aim is to repair a manageable set of routes, then decide what deserves a wider check.

Collect the destinations before changing them

Save a list containing the source page, the words used for the link, and its destination. A standard crawler can help. The W3C Link Checker documentation describes extracting links and anchors, checking destinations and fragments, and reporting redirects. Respect the tool's scope and the site's access controls.

Keep the first result as a starting record. Do not ask an AI to rewrite every link it dislikes. The same destination can be appropriate in one sentence and misleading in another, and a checker can report a temporary access problem as well as a permanently missing page.

For a first pass, choose ten links with a clear reader purpose. A source report, a download, a contact route, and the next story in a series are more useful test cases than ten identical footer links.

Separate four kinds of trouble

A missing destination is the obvious case. MDN's explanation of HTTP 404 says the server cannot find the requested resource. It does not establish whether the absence is temporary or permanent. Open the page and investigate rather than inventing a replacement from its old address.

A redirect is different. HTTP 301 indicates that the resource has moved permanently. Follow it to the final destination and check whether the meaning survived. A redirected research paper and a redirect to a publisher's homepage can share a technical status while offering very different experiences.

A missing fragment is a smaller trap: the page opens, but the promised heading or section is gone. Finally, a semantically wrong destination may load successfully while failing the sentence's promise. These cases need different repairs.

If a destination is private, blocked to the checking tool, or unavailable in the current environment, mark it unresolved. A failed check is evidence about that attempt, not proof that the resource no longer exists.

Let AI help with the comparison

Give the assistant the link inventory and the relevant source sentences. Ask it to group likely problems and explain the reader's expectation for each. It can spot repeated labels, summarize a destination page, or suggest clearer wording after a person finds the correct resource.

Do not ask it to manufacture replacement addresses from titles. Locate a candidate on the publisher's own site or another authoritative source, open it, and confirm the content. If the resource has disappeared, it may be more honest to revise the sentence than to substitute a vaguely related page.

For link wording, use the W3C guidance on descriptive link text. A reader should be able to understand the destination's purpose. “Download the workshop worksheet” tells someone more than a repeated “click here.” Be accurate about formats and access requirements where they affect the decision to follow the link.

Repair the sentence as well as the address

An article can outlive the offer it describes. If a free worksheet has become a paid course, updating the address alone preserves a false promise. Read the surrounding paragraph and decide whether the recommendation is still useful.

Make each change in the site's normal editing process. For an external reference, preserve enough source detail for a reader to identify the original work. For an internal resource, check whether another page also points to the old location before removing or renaming it.

Then return to the public page as a reader. Follow the changed link, inspect the final destination, and test the relevant anchor or download. A successful save in an editor does not tell you what the visitor can reach.

Keep one small recurring habit

After the repair session, choose a practical trigger for the next check: publishing a new resource, changing a site section, or revising an older article. A short list of high-value journeys can be easier to maintain than a huge report nobody acts on.

The AI's contribution is organization and candidate wording. The reader's experience supplies the test. When the link promises a template, the destination should deliver a template. That modest agreement between sentence and click is one of the simplest ways a publication earns trust.

Sources and limitations

  1. W3C, Link Checker documentation: checked October 15, 2026. Supports link, anchor, fragment, redirect, and recursive-checking capabilities; tool output does not establish semantic suitability.
  2. MDN, “404 Not Found”: checked October 15, 2026. Supports the meaning and limits of the HTTP status.
  3. MDN, “301 Moved Permanently”: checked October 15, 2026. Supports permanent-redirect behavior; the final content still requires inspection.
  4. W3C WAI, “Providing link text that describes the purpose of a link”: checked October 15, 2026. Supports descriptive link wording. This workshop does not establish full accessibility conformance.