Run a monthly dead-link sweep across the sales enablement library
A repeatable sweep that finds broken links in seller-facing assets before a buyer or a rep hits them in a live deal.

Export every link sellers can reach
Begin with an export of the links that appear in seller-facing assets and the library pages that point to them. Include the file name, the page or slide where the link appears, and the exact URL. Do not rely on a search of the library home page, because many links live inside decks and PDFs. A complete list is the only way to know what the sweep actually covers.
Add the links that sellers paste into emails from a saved template. Those links bypass the library and can stay broken long after the source asset is fixed. Ask two sellers for their most-used templates and include them in the export. A sweep that checks only the library will miss the links that appear most often in front of buyers.
Record the access level needed to check each link. A public page can be tested by anyone, while a gated asset requires an account. If the checker cannot access a link, mark it as unverified rather than broken. The distinction prevents a permissions issue from being fixed as a content problem.
Classify the failures before fixing
Sort each failed link into one of four groups: moved, removed, access denied, and slow. A moved link needs a redirect or an updated destination. A removed page needs a replacement or a decision to retire the claim. Access denied usually means a permissions problem rather than a missing page. Slow links are not dead, but they still damage a live conversation.
Record the classification beside the URL so the fix can be assigned to the right owner. A moved marketing page belongs to the content owner, while an access-denied document belongs to whoever manages the folder. Do not send every failure to one person, because the fixes require different permissions. The classification turns a long list into a set of small, assignable tasks.
Fix the link or retire the asset
For each moved link, update the source asset and the saved template in the same pass. A fix that updates only the deck leaves the email template broken. For each removed page, decide whether the claim still matters, and if it does, replace the source with a current one. If the claim no longer matters, remove it from the asset rather than linking to something vague.
Do not replace a dead link with a generic home page unless the home page answers the same question. A buyer who clicks a proof-point link and lands on a product overview learns that the proof is missing. When no replacement exists, mark the claim as unsupported and route it to the owner for a decision. An honest removal is better than a link that quietly wastes the buyer's attention.
Set a deadline for each fix and assign it to a person who can change the source. A fix without an owner returns to the list next month. If the owner is outside the enablement team, send a short request with the exact file and link. Close the item only when the source and the saved template both work.
Check links inside documents, not just the library
Open the PDFs and decks that sellers download and test the links inside them. A library card can show a healthy preview while the file it points to contains three broken citations. Check the table of contents, the appendix, and any source note in the footer. Those are the places where links are added late and reviewed least.
If a document is exported regularly from a template, fix the template as well as the current file. Otherwise the next export will reintroduce the same broken link. Record the template name beside the fix so the next sweep can check it directly. The goal is to stop the failure at its source, not to repair the same file every month.
Record the sweep in the asset record
Add the sweep date, the number of links checked, and the number of failures to the asset record. Note which failures were fixed, which were deferred, and who owns each deferral. A record that says the sweep happened without naming the open items is only a status update. The next reviewer should be able to see what remains broken and why.
Keep the record with the asset rather than in a separate spreadsheet that nobody opens. When a seller reports a broken link, the record should show whether it was already known. That context prevents the team from treating every report as a new surprise. It also shows whether the same asset keeps failing and needs a structural fix.
Put the sweep on a monthly schedule
Choose a fixed day each month and assign one owner for the sweep. Put the date on the enablement calendar and send a short reminder to the asset owners two days before. A monthly cadence is frequent enough to catch most rot without turning the task into a permanent project. If the library changes quickly, move to a two-week cadence for the highest-use assets.
Review the trend after three sweeps and look for assets that fail repeatedly. A file that breaks every month may need a different hosting location or a simpler source. Change the process rather than adding another manual check. The sweep is successful when the number of failures falls and the fixes become routine.
Keep the sweep tooling simple enough that a new owner can run it. A checklist and a shared spreadsheet are often enough for a small library. Document the steps beside the calendar entry so the task does not depend on one person's memory. The best sweep is the one that still happens when the original owner is away.