You run a link checker, it comes back green, and you move on. The myth here is subtle: a clean report means "no broken links among the links I found", not "no broken links". The gap between those two is where users still hit dead ends.
Here are seven blind spots, why checkers miss them, and how to close each one.
1. Links that only exist after JavaScript runs
Most crawlers, including many CI link checkers, parse the raw HTML. If your nav, footer or "related articles" block is rendered client-side, those links don't exist in the HTML they read.
Test it: compare link counts in raw vs rendered HTML.
// count-links.mjs import { chromium } from " playwright " ; const url = process . argv [ 2 ]; const raw = await ( await fetch ( url )). text (); const rawCount = ( raw . match ( /<a \s[^ > ] *href=/gi ) || []). length ; const b = await chromium . launch (); const p = await b . newPage (); await p . goto ( url , { waitUntil : " networkidle " }); const rendered = await p . $ $eval ( " a[href] " , as => as .…