Start with a visitor task
Choose a task such as finding a service and reaching its contact page. Follow the journey from the homepage on desktop and mobile. Record the source page, visible link text, destination and what actually happens when you open it. This produces a repair list tied to a visitor need rather than a target number of links.
Separate a broken destination from a weak connection
A link can open successfully yet lead to the wrong service or an irrelevant page. Put unreachable destinations in one group and misleading or missing connections in another. Before removing a link, ask whether its destination moved and whether a relevant replacement exists. A timeout is a reason to recheck, not immediate proof that a page is permanently gone.
Make the route readable
Google recommends real anchor elements with an href and descriptive link text. Use a short phrase that describes the destination in the surrounding sentence. Avoid repeating keywords mechanically or adding links only to reach a quota. A relevant guide can point to the service it explains; an unrelated article should not be forced into that route.
Use a compact repair record
Keep these fields for each task: source URL, destination URL, observed problem, proposed replacement, owner and verification date. For a missing connection, record the paragraph where a link would help and the proposed wording. This is a suggested work template, not a report of measured customer results. Ask the page owner to approve changes that alter the meaning of the text.
Check the published result
After editing, open the source page and follow the link again. Confirm that the destination is correct and accessible. A bounded website audit can identify issues within its inspected sample; it does not establish that every page on a site has been checked. Pages outside the sample need a separate review.
Keep traffic measurement separate
A repaired route is an implementation result. It is not proof of higher rankings, more clicks or additional sales. If Search Console is connected, review later performance with comparable periods and filters. Without that connection, record the verified technical fix and leave search-performance fields unavailable.