Frequently Asked Questions
Do broken links hurt SEO?
Not as a direct penalty, but as a quality and crawlability problem. Crawlers waste budget on dead ends, internal 404s break the flow of link equity through your site, and a page full of dead outbound links reads as unmaintained to both users and search engines. Fixing them is one of the cheapest maintenance wins in SEO.
Why does this tool check whole pages instead of whole sites?
A single-page scan finishes in seconds and covers the pages that matter most: your homepage, service pages, and resource lists. Site-wide crawls take minutes to hours and are agency-tool territory. Scan your handful of key pages individually and you get most of the benefit with none of the wait.
Why is a link marked Blocked when it works in my browser?
The site's bot protection (Cloudflare and similar) is refusing automated requests while allowing real browsers. That is why Blocked is a separate yellow category and not counted as broken. Verify those links manually before changing anything.
Does the checker use GET or HEAD requests?
GET, the same method browsers use. HEAD is lighter, but a meaningful share of servers answer it incorrectly: they return 200 for pages that 404 on a real visit, or reject HEAD outright. The checker stops reading the response as soon as the status is known, so the accuracy of GET comes without downloading whole pages.
Can it check links that only appear after JavaScript runs?
Not yet. It reads the HTML the server sends. For most business sites that covers every link. If your site is a single-page app that renders links client-side, the scan may find few or no links; check your rendered HTML with your browser's developer tools instead.
Is the URL I submit stored?
We fetch, scan, and discard the page you submit without keeping a scan history. Link statuses are cached briefly (a few hours) so repeated scans of popular targets stay fast.