If I only run lychee on the same single page, the numbers are closer:
> 76 Total (in 1s) 73 OK 0 Errors 2 Excluded
If I only run lychee on the same single page, the numbers are closer:
> 76 Total (in 1s) 73 OK 0 Errors 2 Excluded
So, if you add example.com, the crawl starts at / and all links found therein are added to the queue, and so on. For convenience www.example.com is also considered within crawl scope (and viceversa). Everything else is treated as an external link, so tested but not parsed.
Is it possible that your links are hosted on another subdomain than the one you have entered? I'll do a deeper dive into this issue tomorrow.
> I'll do a deeper dive into this issue tomorrow.
FWIW, I don't think I'd go as far as calling this an issue, I suspect both Bernard and Lychee are doing different, but reasonable things.
No need to spend much time on my account, and cheers on launching a useful project!
<a href="https://luke.hsiao.dev/blog/2023-workstation-build/">My 2023 Workstation Build</a>
I have never seen forward slashes encoded that way. These were simply not recognised. Added to the todo list.