About Verflink

Verflink crawls a website from the outside, the way a visitor or a search engine would, follows every link it finds on every page it reaches, and reports the ones that no longer lead to a working page. It checks internal links between your own pages and outbound links to other sites, pays particular attention to affiliate links, and re-runs the whole scan every month once you have verified that you own the site. It needs no plugin, no account access, and no change to your theme, because it never touches anything but your public pages.

Zero false alarms

We double check every link before flagging it. A single timeout is never treated as broken, so what reaches your report is worth your time.

Safe scanning, zero risk to your site

The crawler honors robots.txt and keeps a polite per-domain pace. Checks run server-side through a sandboxed fetcher that blocks private and internal addresses.

The links that make you money get checked first

Affiliate links are surfaced ahead of the rest, and confirmed 404s are kept apart from uncertain timeouts, so your attention goes where the revenue is.

A link is only called broken when the failure has been confirmed on more than one request. Everything that fails once and then behaves, or that returns an ambiguous answer like a timeout, a rate limit, or a 403, is filed as uncertain and kept in its own group rather than mixed into the broken list. This matters more than it sounds: a checker that reports every hiccup as breakage trains you to ignore its reports, at which point it has stopped being useful. Affiliate links get a further distinction, because a clean final URL means a stripped tag on Amazon, where the tag travels in the URL, but is perfectly normal on networks like Awin and CJ, where tracking is carried in a cookie set along the redirect. Reporting those identically would be wrong in one direction or the other.

We do not store the pages we crawl. Checks run server-side through a sandboxed fetcher that resolves and validates every address before connecting and re-validates on each redirect hop, so a submitted URL cannot be used to reach private or internal infrastructure. We wrote up one of the bugs we hit building that guard, in some detail, because a security control that fails silently is worse than none: my SSRF guard blocked every IPv4 address on the internet. What we hold about a scan is described in the privacy policy.