-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the LinkChecker wiki!
Here is a sample output:
This project or the concept of it might be useful in several different situations. Here, I am going to state the usefulness of it from my experience.
If you are a website that focuses on its content (online newspaper/ digital information company), you often run into situation where you want to know if the links/content that has been recently pushed to QA /staging/ production are working as expected or not.
This problem could be caused by various components of a website that are brought together. Most prominent that I have experienced are server and content management system config. issues. Following are a few examples of that:
- One or more nodes from the server farm is not responding
- Older links are not being redirected to newer ones as expected.
- The response code of redirection is not as expected. A redirect could be 302 instead of 301, which is a concern from SEO standpoint although not for a Sysadmin.
- URLs timeout during connection (a ping) not returning a status code.
This is where link checker can be very useful, especially if it's on the CI, scheduled to run after every few minutes which can send emails if there are any failures.
I've experienced that color coding (Green, Blue, Red) helps you achieve faster feedback. Just to give an example, it's easier to spot red URLs in the humongous console log that might exist on the CI.