Download Approaches To Link Checking

Briefing-07
Briefing-07
Approaches To
Link Checking
Approaches To
Link Checking
A QA Focus Document
A QA Focus Document
Why Bother?
Why Bother?
There are several reasons why it is important to ensure that links on Web sites work:
There are several reasons why it is important to ensure that links on Web sites work:
 Web sites are based on hyperlinking, and if hyperlinks fail to work, the Web site
can be regarded as not working correctly.
 Web sites are based on hyperlinking, and if hyperlinks fail to work, the Web site
can be regarded as not working correctly.
 Broken links can reflect badly on the body hosting the Web sites.
 Broken links can reflect badly on the body hosting the Web sites.
 Hyperlinks are increasingly being used to deliver the functionality of Web sites,
through links to JavaScript resources, style sheets files, metadata, etc. Broken links
to these resources will result in the Web site not functioning as desired.
 Hyperlinks are increasingly being used to deliver the functionality of Web sites,
through links to JavaScript resources, style sheets files, metadata, etc. Broken links
to these resources will result in the Web site not functioning as desired.
However there are resource implications in maintaining link integrity.
However there are resource implications in maintaining link integrity.
Approaches To Link Checking
Approaches To Link Checking
A number of approaches can be taken to checking broken links:
A number of approaches can be taken to checking broken links:
 Web site maintainer may run a link checking tool.
 Web site maintainer may run a link checking tool.
 A server-based link checking tool may send email notification of broken links.
 A server-based link checking tool may send email notification of broken links.
 A remote link checking service may send email notification of broken links.
 A remote link checking service may send email notification of broken links.
 Web server error log files may be analysed for requests for non-existent resources.
 Web server error log files may be analysed for requests for non-existent resources.
 Web server 404 error pages may provide a mechanism for users notifying the Web
site maintainer of broken links.
 Web server 404 error pages may provide a mechanism for users notifying the Web
site maintainer of broken links.
Note that these approaches are not exclusive: Web site maintainers may choose to make
use of several approaches.
Note that these approaches are not exclusive: Web site maintainers may choose to make
use of several approaches.
Policy Issues
Policy Issues
There is a need to implement a policy on link checking. The policy could be that links
will not be checked or fixed – this policy might be implemented for a project Web site
once the funding has finished. For a small-scale project Web site the policy may be to
check links when resources are added or updated or if broken links are brought to the
project’s attention, but not to check existing resources – this is likely to be an implicit
policy for some projects.
There is a need to implement a policy on link checking. The policy could be that links
will not be checked or fixed – this policy might be implemented for a project Web site
once the funding has finished. For a small-scale project Web site the policy may be to
check links when resources are added or updated or if broken links are brought to the
project’s attention, but not to check existing resources – this is likely to be an implicit
policy for some projects.
Produced by QA Focus – supporting JISC’s digital library programmes
Produced by QA Focus – supporting JISC’s digital library programmes
Oct 2005
Oct 2005
For a Web site one which has a high visibility or gives a high priority to the
effectiveness of the Web site, a pro-active link checking policy will be needed. Such a
policy is likely to document the frequency of link checking, and the procedures for
fixing broken links. As an example of approaches taken to link checking by a JISC
service, see the article about the SOSIG subject gateway [1].
For a Web site one which has a high visibility or gives a high priority to the
effectiveness of the Web site, a pro-active link checking policy will be needed. Such a
policy is likely to document the frequency of link checking, and the procedures for
fixing broken links. As an example of approaches taken to link checking by a JISC
service, see the article about the SOSIG subject gateway [1].
Tools
Tools
Experienced Web developers will be familiar with desktop link-checking tools, and
many lists of such tools are available [2] [3]. However desktop tools normally need to
be used manually. An alternative approach is to use server-based link-checking software
which send email notification of broken links.
Experienced Web developers will be familiar with desktop link-checking tools, and
many lists of such tools are available [2] [3]. However desktop tools normally need to
be used manually. An alternative approach is to use server-based link-checking
software which send email notification of broken links.
Externally-hosted link-checking tools may also be used. Tools such as LinkValet [4]
can be used interactively or in batch. Such tools may provide limited checking for free,
with a licence fee for more comprehensive checking.
Externally-hosted link-checking tools may also be used. Tools such as LinkValet [4]
can be used interactively or in batch. Such tools may provide limited checking for free,
with a licence fee for more comprehensive checking.
Another approach is to use a browser interface to tools, possibly using a Bookmarklet
[5] although UKOLN’s server-based ,tools approach [6] is more manageable.
Another approach is to use a browser interface to tools, possibly using a Bookmarklet
[5] although UKOLN’s server-based ,tools approach [6] is more manageable.
Other Issues
Other Issues
It is important to ensure that link checkers check for links other than <a href="..">
and <img src="">. There is a need to check external JavaScript, CSS, etc. files
(linked to by the <link> tag) and that checks are carried out on personalised interfaces
to resources.
It is important to ensure that link checkers check for links other than <a href="..">
and <img src="">. There is a need to check external JavaScript, CSS, etc. files
(linked to by the <link> tag) and that checks are carried out on personalised interfaces
to resources.
It should also be noted that erroneous link error reports may sometimes be produced
(e.g. due to misconfigured Web servers).
It should also be noted that erroneous link error reports may sometimes be produced
(e.g. due to misconfigured Web servers).
References
References
1 Approaches To 'Spring Cleaning' At SOSIG, QA Focus, UKOLN,
<http://www.ukoln.ac.uk/qa-focus/documents/case-studies/case-study-25/>
1 Approaches To 'Spring Cleaning' At SOSIG, QA Focus, UKOLN,
<http://www.ukoln.ac.uk/qa-focus/documents/case-studies/case-study-25/>
2 Link Management Software, Open Directory, <http://dmoz.org/Computers/
Software/Internet/Site_Management/Link_Management/>
2 Link Management Software, Open Directory, <http://dmoz.org/Computers/
Software/Internet/Site_Management/Link_Management/>
3 Link Management Software, Google Directory, <http://directory.google.com/Top/
Computers/Software/Internet/Site_Management/Link_Management/>
3 Link Management Software, Google Directory, <http://directory.google.com/Top/
Computers/Software/Internet/Site_Management/Link_Management/>
4 LinkValet, <http://www.htmlhelp.com/tools/valet/>
4 LinkValet, <http://www.htmlhelp.com/tools/valet/>
5 Bookmarklets <http:// www.bookmarklets.com/>
5 Bookmarklets <http:// www.bookmarklets.com/>
6 A URI Interface To Web Testing Tools, QA Focus, UKOLN,
<http://www.ukoln.ac.uk/qa-focus/documents/briefings/briefing-59/>
6 A URI Interface To Web Testing Tools, QA Focus, UKOLN,
<http://www.ukoln.ac.uk/qa-focus/documents/briefings/briefing-59/>
For further information on QA Focus see <http://www.ukoln.ac.uk/qa-focus/>
For further information on QA Focus see <http://www.ukoln.ac.uk/qa-focus/>