Broken link check
Crawl the site for links that lead nowhere, and see them ranked by where they sit — a dead link in the main navigation is not the same problem as one in a 2019 blog post.
The free run checks the URL you enter. A full crawl runs on a monitored site.
What this crawl actually checks
A list of four hundred dead links is not a task anyone starts. This crawl follows internal and outbound links, records where each broken one lives, and orders them by consequence — navigation and checkout first, archive pages last — so the list has a top rather than just a length.
- Internal links
Including redirect chains that still resolve but should not.
- Outbound links
Domains that expired, moved, or now serve something else entirely.
- Assets
Images, scripts and stylesheets that 404 without breaking the page visibly.
- Where it sits
Navigation, product page or archive — the same 404 is not the same problem.
What a result looks like
Of 412 checked across 240 pages.
Every path a customer walks resolves.
Two point at a supplier who changed domain.
Each broken link is reported with the pages that contain it, its status code and whether it is yours or someone else. Where one dead target appears on forty pages, that is one fix, and it is counted as one.
A crawl tells you about today. Monitoring tells you at 04:00.
Links rot without you touching anything — a supplier rebrands, a document is moved, a category is renamed and three hundred links follow it into the void. Crawling on a schedule turns that into a short list of new breakages each week instead of an annual clean-up nobody schedules.
Common questions
- Is this the same engine as the paid monitoring?
- Yes — the same checks, run the same way. The difference is that monitoring repeats them on a schedule and keeps the history, which is what turns a number into a trend and a trend into an alert.
- Does testing my site slow it down or change anything?
- No. Everything is read from the outside, the way a visitor arrives — no agent, no script on your pages, nothing written. Our requests identify themselves so you can recognise them in your own logs.
- Will the crawl overload my server?
- No. Crawls are rate-limited and identify themselves in the user agent, and you set the ceiling. If several of your sites share one origin server, we notice and spread the load across them rather than testing them all at once.
Related tests
A free test is a snapshot. Monitoring is the product.