This article refers to a process used on sites that have already been migrated to the New WMS.
If your site has not yet migrated, see the Index of documentation for the McGill Web Management System.
Target audience: Site Administrators, Site Managers
What this is: This article explains how to use the Broken links report in the New Web Management System (WMS) to identify, review, and fix links that are not working as expected.
The WMS includes a link checker that automatically scans your website content for broken links. It checks both published and unpublished content and produces a report showing which links are working and which need attention.
The link checker runs approximately every two to four weeks.
As a site administrator or site manager, your goal is to:
In this article:
You should prioritize links with a 4xx or 5xx status code (e.e., 404, 403, 500 etc.)
Use the Found here column to locate the content item that contains the broken link.
This column shows:
After fixing content, the link checker will re-scan links during its next scheduled run and update the report.
The URL column shows the exact web address the link checker tested.
The URL may point to:
If a link is broken, this is the URL you need to replace or correct.
How to use it: Confirm that the link in the URL column is spelled correctly and/or that the destination still exists.
This column reflects when the link checker scans your site’s content, which is every two to four weeks.
It shows the date and time when the link checker last tested the URL. The date and time will help you understand how up-to-date your information is.
This column shows the HTTP response code returned when the link checker tried to access the URL.
Most common status codes:
For full list of all status codes and their definition, you can visit Wikipedia's List of HTTP status codes.
How to use it: Review any links with status codes other than 200, and prioritize 404 and 500 errors.
This column gives a human-readable explanation of what went wrong.
Examples include:
How to use it: Use the message together with the status code to understand whether the issue is a broken destination, a permissions problem, or a temporary connection issue.