disabling "disable checking" in Day CQ Link Checker T...

[skadobe9]

We disabled the "disable checking" checkbox to login publisher servers in 6.5.9, is it a good practice?

added /libs/granite/core/content in blacklist paths.

Please let us know your thoughts

[Ravi_Pampana]

Hi,

Disabling link checker is fine in case you are referring to external links and don't want them to display as broken in live pages.

The feature will be useful if all the links will point to internal urls.

Refer: https://experienceleague.adobe.com/docs/experience-manager-64/administering/operations/external-link... for more details

[arunpatidar]

Hi,

It is always recommned to disable link checker in publish instances, otherwise it cause performance issues.

On Author, if you think it is good to have , keep it enable otherwise disable it in Author too. There is no harm in disabling.

[Shubham_borole · Accepted solution]

Hi @skadobe9 ,

In my understanding it is better to have the checking (and rewriting just to be safe) disabled in publishers since this can cause performance concerns.
For author instances, this can be kept on if there is some value to the authors in terms of catching incorrect urls. One of the challenges I faced for author instance and getting accurate broken links was discussed here - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/find-and-fix-broken-links-...  We ended up disabling it in author as well (time being).

Please also refer https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/external-link... for steps to disable link checker. There is no obvious indication of a best practice but based on project situation the Link Checker can be utilized. Plus suggestions from community members..

Thanks

[Dipti_Chauhan]

Hi @skadobe9 

  This is anyways good practice to disable it on Publish as it can impact site performance. You can still keep it for authors just to see all broken links.

Thanks

Dipti