Library Research Guides Catalogue Sources: 71 Calculation Tools in 35,640 Outbound Links

A survey run on August 18, 2026 across 368 English-language university library installations on the LibGuides platform extracted 35,640 outbound links from 2,193 research guides covering calculation-heavy subjects. Of those links, 71 pointed to a calculator, converter, or spreadsheet tool. Five of the 71 were dead, and all five were assignment planners, not calculators. That puts a concrete number on an assumption that circulates without evidence: that academic library guides are a productive place to find where computational tools are cited and recommended.

What the survey set out to measure

Library research guides hold a specific position in the web graph. Subject specialists maintain them, institutions update them on their own schedules, and they are linked from university domains that carry substantial authority. They are often proposed as a place to discover tools, on the reasoning that a subject librarian curating a page on structural engineering or clinical nutrition would naturally include the calculators practitioners use.

The survey tested that reasoning directly, with two questions. First, at what rate do these guides link to calculation tools as opposed to information sources? Second, among the links they do carry, what proportion have decayed, and what kind of resource fails most often?

Seven subject areas were selected because each has an established body of routine computation: statistics, construction, HVAC, finance, logistics, nutrition, and electrical work. A guide entered the sample if its title or subject classification placed it in one of those areas.

The funnel

Most of the information is in the drop between rows. The 35,640 raw links collapse to 10,747 unique URLs, a deduplication ratio of 3.3 to 1, so the average distinct resource appears in slightly more than three places. Those 10,747 URLs resolve to 3,600 domains, so the average domain is cited three times across the corpus.

The final row is the finding. Tool links make up 0.199 percent of extracted links, about two in every thousand. Spread across 2,193 guides, that is one tool link for every 31 guides, in subjects defined by their computational content.

Method

Guides were enumerated from each installation's sitemap.xml. No search engine was used at any stage. The choice was deliberate, and it shapes what the numbers mean: search indexes reflect crawl priority and popularity, while a sitemap reflects what the institution itself publishes. Enumerating by sitemap produces a census of a platform instead of a sample of what ranks well.

Links were extracted from guide bodies, with navigation chrome and platform boilerplate excluded. A link counted as a tool link when its anchor text or URL path contained a tool indicator: calculator, converter, spreadsheet, and their common variants. This is a lexical test. It is conservative in one direction and permissive in another, a point the limitations section takes up.

Status testing used HEAD requests, falling back to GET where the server returned a method-not-allowed response or otherwise failed to implement HEAD. Only 404 and 410 were counted as dead. Status codes 403, 406, and 429 were treated as robot blocking and excluded from the dead count, since they describe how the crawler was received and say nothing about whether the resource exists.

Every candidate failure was then rechecked with a browser user-agent string. That second pass discarded 24 false positives. The clearest example is app.dimensions.ai, which returns 404 to an automated client and 202 to a browser. Without the recheck, the reported decay rate would have been inflated by roughly a third of its candidate volume.

Separately, 67 domains had no DNS record at all. Those are unambiguous failures and need no HTTP negotiation to confirm.

Finding one: the corpus catalogs sources

These guides are mostly bibliographic. Outbound links go overwhelmingly to databases, journal platforms, publisher sites, government statistical agencies, standards bodies, and professional associations. A guide on HVAC points to ASHRAE and to engineering databases. A guide on nutrition points to federal dietary data and to indexed literature. The librarian's job on these pages is to route a reader to authoritative material, and the pages do that job consistently.

Calculation tools fall outside that job. A load calculator, a unit converter or an amortization spreadsheet is an instrument of practice, not a source to be cited, and the guides reflect the distinction. The 71 tool links in 35,640 are that professional boundary, expressed as a number.

What this changes is where you look. Any project trying to map where calculation tools are recommended on the web should treat LibGuides installations as low-yield and go to other page types: course pages, professional association resource lists, trade publication roundups, and vendor documentation. If you were planning outreach to librarians to get a tool listed, this is the number to weigh before you write the first email.

Finding two: broken links point inward

Among the guides with at least one dead link, 172 in total, half of the broken links pointed to infrastructure belonging to the institution that published the guide: proxy servers, catalog endpoints, internal request forms, and authentication paths. The recurring example is proxy.lib.unc.edu, an EZproxy-style prefix that becomes invalid when access configuration changes.

This flips the usual framing of link rot. The standard worry is that the external web moves under a curated page. The measurement here shows the institution's own systems move at a comparable rate, and a guide can break without any outside publisher doing anything. Proxy migrations, catalog replacements and form retirements all break links that sit inside the library's own control.

That's the good news for whoever does the repair. Internal breakage can be fixed by the organization that caused it, usually in bulk, since a proxy prefix change affects every link built from that prefix.

Finding three: template links inflate naive counts

A single dead URL can appear many times across a campus because guides are cloned. The OWASP page at owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF) is dead because the project migrated off MediaWiki, and it appeared in six guides at one institution. Counted per link instance, that's six failures. Counted per unique URL, it's one failure that needs one correction.

Any decay statistic that skips deduplication overstates both the problem and the work. The 3.3 to 1 ratio between extracted links and unique URLs in this corpus gives the rough scale of that overstatement. Plan repairs around unique targets, since one edit to a shared template or one find-and-replace fixes the whole cluster.

Practical implications for guide maintenance

If you maintain research guides, the data points to a few concrete changes.

Dead links in research guides are ordinary. Treat them as a maintenance category with a scheduled cadence, not as an incident.

Start audits with your own infrastructure. Half of the broken links in affected guides pointed to the library's own systems, so a review of proxy prefixes, catalog URL patterns and internal form endpoints will clear a large share of failures before any external checking begins.

A link checker that resolves only the root domain will miss the most common form of external decay. The case to remember is energy.gov, which returns 200 at the home page and 404 at /energysaver/. A checker testing domain reachability reports the link as healthy while the cited section is gone. You need full-path testing, browser user-agent verification to suppress the false positives that cost this survey 24 candidate failures, and a rule that treats 403, 406 and 429 as inconclusive instead of dead.

Limitations

The sample is English-language only. Of 469 institutions in the public directory, 368 were analyzed, and the 101 excluded installations may distribute tool links differently. Practices in other language communities are unmeasured here.

The LibGuides resultCountEstimate field saturates, which is why sitemap enumeration was used instead of the platform's own search interface. Where a search count would have been convenient, it caps instead of reporting, and no total derived from it can be trusted at scale. The sitemap route avoids this but inherits whatever omissions exist in each institution's sitemap generation.

Tool classification is lexical. A calculator linked with anchor text that names the publisher instead of the function will be missed, so 71 is a lower bound on the true count. That direction of error doesn't threaten the conclusion, since the observed rate would have to be understated by more than an order of magnitude to change the interpretation.

The survey covers LibGuides installations only. University pages built on other platforms, departmental sites, course management systems and personal faculty pages are outside its scope, and nothing measured here describes them.

Finally, the survey is a single snapshot taken on August 18, 2026. It measures state, not rate of change, and no longitudinal claim about decay speed can be drawn from it.