Site Check

Site Check allows OU Campus™ administrators (Level 9 and 10) to check all links, both internal and external. The resulting report provides a list of all broken links and all warnings, which can then be used to make global changes or individual changes as necessary. This tool works in conjunction with the individual link checking feature of Page Check.

Site Check tests links found on pages under management on the Staging Server. It tests that the links exist on the Production Server, external sites, or if Dependency Manager is used, if links pointing to pages on the Staging Server are valid.

Site Check is a tool that can be used to identify and correct invalid links on pages under OU Campus management before or after they are published. Site Check does not test the links on pages on the Production Server, but it is checking that links to pages on the Production Server are valid. It is not parsing pages on the Production Server.

As of Version 9.15.6 the Dependency Manager broken link tags provide more informative reporting of broken links and broken assets. Previously, when a dependency was lost; for example, when a linked-to page or a subscribed-to asset was deleted, only the term BrokenLink or BrokenAsset would be displayed within a set of asterisks. This is no longer the case. Instead the dependency tag, path, and file name are shown within the asterisks.

For example, this:



*** Broken f:1234 /training/about/filename.html***

Please note that this change does not retroactively correct existing pages with broken dependencies. It only appears on pages with broken dependencies as of the date of the release and going forward. Existing pages with broken links or deleted assets continue to display the BrokenLink or BrokenAsset term. This is because the details, such as the path and file name are already lost, and in some cases the terms are hard-coded into the page. Once all old occurrences of the BrokenLink or BrokenAsset term are resolved or removed, no new ones should appear.

This change is currently implemented with the following:

  • Page Preview
  • WYSIWYG Editor
  • Page-based Link Check
  • Publish-based Link Check
  • Site Check
  • Custom Reports

Source Editor reports broken links both above the Editor window and in-context. The Dependency tag is highlighted red as an indicator.


Next Page


Initial Site Check

To run the initial site check:

  1. Navigate to Admin > Site Check.

    Keep in mind that the initial run of the site check will appear only once per site, regardless of users.
    Admin Site Check
  2. Make initial selections.

    Follow Redirects: Checking this option will direct the system to follow all redirects to the final resulting page for the most accurate reporting.

    With Includes: Checking this option directs the system to check the links within any include files. If an include file of a page being checked can not be reached page check reports an error.

    Timeout: Select how long the system should attempt to check each link before timing out.
    Initial Site Check
  3. Click Check Site.

    This may take several minutes to complete. It is possible to continue with other work while this is running.

    If additional administrators attempt to run the check during this process, they will see the same Checking links... indicator screen.

    After the check has been completed, the results will appear below.
    Checking Links

Previous PageNext Page


Rechecking a Site

After the initial site check is run, it can be run again using the settings and instructions as indicated above. Additionally, individual pages can be selected using the checkbox that appears in front of the pages with broken links or warnings in order to run a check on those pages only, which can be very effective for checking pages that have been fixed.

The site check box will be populated with a legend after the initial site check has been run. This provides details as to what the icons seen in the reports below refer.

Rechecking Links

 Below the site check box will be the results, which can be viewed by page or as a list of all broken links, and a list of invalid pages can also be viewed.

Previous PageNext Page


Broken Links

Broken Links by Page

The Broken Links by Page report will show all pages on which there is one or more broken links or warnings. Once the links have been fixed, the report can be rerun. It is possible to check the box(es) in front of the page(s) to be rerun to select only the page(s) to rerun. Use the Check Pages button within the report to rerun by page.

The report includes:

  • Page Path: Shows the root relative path
  • Last Checked On: The date that the links were last checked
  • OK: Number of links that were tested as ok or valid
  • Broken: The number of broken links on the page
  • Unchecked: The number of links that were not checked
  • Warning: The number of links with warnings
  • Preview: A direct link to preview the page listed

Broken Links By Page

For more details, each page can be expanded by clicking on the arrow next to the page path to see the list of links on that page and their status. Pages can also be previewed using the Preview icon. There will not always be an icon in both the Staging and Production columns depending on the link, where it resides, and the result.

When expanded, the results will include: 

  • Link URL: Shows the root relative path and published file name
  • Staging: Indicates the result of the link check on the Staging Server
  • Production: Indicates the result of the link check on the Production Server
  • Status Code: Shows the HTTP response status code, if applicable

Page Report

A broken Link URL is reflected with the broken link dependency tag:

Dependency Tag Broken Link Sitewide Check

All Broken Links

It is also possible to simply get a list of all broken links. This report can be exported as a CSV file using the Export Report link.

This list includes:

  • Link URL: A broken Link URL is reflected with the broken link dependency tag
  • Page Path: Clicking on the page path will take the user to the page
  • Staging: Indicates the result of the link check on the Staging Server
  • Production: Indicates the result of the link check on the Production Server
  • Status Code: Shows the HTTP response status code, if applicable

There will not always be an icon in both the Staging and Production columns depending on the link, where it resides, and the result.

All Broken Links


Previous PageNext Page


Invalid Pages

The Invalid Pages report will provide a list of pages that could not be checked and the error code indicating why that page cannot be checked. These pages have a Preview option which will take the user to the page. However, if the pcf cannot be rendered, the issue causing the error must be fixed before the page can be checked.

Invalid Pages

About the Validator

The W3C Compliance Validator is a service that OmniUpdate offers to they clients which helps check the validity of Web documents.

Most Web documents are written using markup languages, such as HTML or XHTML. These languages are defined by technical specifications, which usually include a machine-readable formal grammar (and vocabulary). The act of checking a document against these constraints is called validation, and this is what the Markup Validator does.

Validating Web documents is an important step which can dramatically help improving and ensuring their quality. Validation is, however, neither a full quality check, nor is it strictly equivalent to checking for conformance to the specification.

This Validator can process documents written in most markup languages. Supported document types include the HTML (through HTML 4.01) and XHTML (1.0 and 1.1) family, MathML, SMIL and SVG (1.0 and 1.1, including the mobile profiles). The Markup Validator can also validate Web documents written with an SGML or XML DTD, provided they use a proper document type declaration.

This Validator is also an HTML validating system conforming to International Standard ISO/IEC 15445-HyperText Markup Language, and International Standard ISO 8879-Standard Generalized Markup Language (SGML), which basically means that in addition to W3C recommendations, it can validate according to these ISO standards.

Previous Page


Was this page helpful?

Additional Comments:

(Include your email address if you would like a reply)