How the link checker works

The link checker provides you with a report of broken links in your:

  • Database assets
  • Link assets
  • Books from the Catalog assets

If you want the link checker to exclude checking certain links or domains (like your library catalog or any proxied links), add those links / domains to the Exclusions list! We recommend adding domains for any sites that require a login, as the Link Checker does not have any way to log into the site to verify that the link is valid, so it will always be listed as "broken" in your report (a.k.a., a false positive).

What the link checker report shows you:

  1. Use the Actions column to dismiss a link or add it to the exclusions list.
  2. Use the Title column to filter/search for links by their title.
    • This is the title of the asset.
  3. Use the Type column to filter the report by type (Link, Book, or Database).
  4. The URL column will show the URL that was flagged as being broken by the link checker.
  5. The Owner column will display the owner of the asset.
  6. The Mapping Count column will show you how many times the asset is being used on guides.
  7. The Asset column will allow you to edit the asset.

Link checker report overview


How often does the link checker run?

The link checker runs every 30 minutes, on the hour and half past the hour.


Who can use the link checker?

Any regular or admin user can access the link checker report. Although regular users can see every link listed in the report, they can only modify links for the assets they own. Admin users, however, can modify every link because they have the ability to edit any asset in your system.


Why is the link checker reporting links that aren't really broken?

False positives can occur with the link checker for a few reasons. Unfortunately, all of these things are out of our control. :/

  • When the Link Checker pinged that URL, that server really was down.
  • When the Link Checker pinged that URL, that server was so busy serving other requests that ours timed out.
  • The company / organization who owns that server set it up to refuse any connections from spiders, crawlers, etc., to save bandwidth / resources.
  • The company / organization who owns that server incorrectly set up their server response codes, meaning the code returned was inaccurate.

It can also return false positives if it's checking links that require a password before the page loads. Since the Link Checker cannot log into that site to verify the page, it returns the link as "bad". Or the server it's checking might refuse the connection altogether, as noted in the bullet points above. Please add domains that require logins to the Exclusions list. 

Related Articles