Yes, the most common scenario to use LinkClick is when the file is in a secured folder.  However, some modules also re-purposed this feature to create links that could be tracked, such as the Links module.  It does both.  If the link doesn't need to use LinkClick anymore, I'd suggest just recreating the link using the respective tool(s) in the module you're using.  (Or get the link from the file/asset manager page.)  

This problem could concern more than 150 html modules in this website.

I made tests and it seems that, in DNN7, the HTML module coud create this type of links when the user create a link to one of the website pages. It's not need to enable the logs feature.

I tried to debug the process (with Visual Studio) and my conclusion is that my DNN doesn't notice that the targeted URL contains the LinkClick keyword.
I looked at https://www.dnnsoftware.c...e/posts/threadpage/2 and https://dnncommunity.org/forums/aft/3877. I also checked if the web[dot]config could be the cause but with no success. The LinkClickHandler seems to be ok.

Do you have any pointers on what I'm missing?

Thanks

Check the web(dot)config file in the root of the website.  You should find a line of code that looks similar to the example below.  

<add name="LinkClickHandler" path="LinkClick.aspx" verb="*" type="DotNetNuke.Services.FileSystem.FileServerHandler, DotNetNuke" preCondition="integratedMode" />

Also, here's a short video that shows you how to use the Config Manager.  

https://www.youtube.com/w...2yzhTZk&index=15

I think I've found the cause: those links have been created with the old html module which allowed to enable navigation statistics.
Then those contents may have been moved to another page and it didn't affect the linkclicks. Finaly users have deleted the source page.

I tried to make the same experience with the link module and it seems that the links take into account the current page.

With DNN 9.13, the advanced URL rewriter checks if the targeted tabid exists (line 2380 more or less). If the page doesn't exist anymore, DNN will show the 404 page instead of send the targeted file.

I don't know if it's a bug.
If yes, is it a html module bug or a DNN bug? I think DNN doesn't need to check if the targeted tabid exists in case of a linkclick URL.
Maybe there are some use case which could explain this check.

That's a great question... Is it a bug?  I think so.  It sounds like someone made an update without thinking of the tracking use case using LinkClick, but that's purely a guess. 😊