Thanks everybody. I didn't expect this massive amount of reactions.
I've tried to update the github repo gathering the info you all provided me (mainly references, websites and books).
I don't know if it works for your or not. But, to me, it makes lot of sense to gather as much info as possible so that when I have doubts on doing something, I can query first what info says and maybe the decision-making process is better.
Of course we can. But maybe it's not bad to have extra resources, books, opinions, techniques and methodologies you might want to look at to reflect on whether your common sense makes actual sense or not? I think it's healthy to be open to listen other opinions and evaluate your owns.
How certain startups CMS based content could go checking broken-links?
1. They implement their own checker - fair enough, if they want to do it.
2. They use a micro API for it and forget about investing the time on it, if it works well for them.
As a developer, I find this an useful API to validate links of my CMS generated websites within my CI system. This way, using sync requests to my sites, I can easily await the results and fail the jenkins job or promote the deployment.