Keep audit history
Compare completed crawls instead of relying on one-off reports.
Detect newly introduced broken links and separate them from older unresolved findings.
This page focuses on broken link monitoring in crawl context. The crawler records the fetched URL, response status, discovery source when available, metadata, redirect outcome, and history signals that explain why a finding appears.
Use the check to review recurring crawls, audit history, and change detection. The goal is not just to report a problem, but to show the URL-level evidence needed to decide whether the issue is intentional, accidental, fixed, or still unresolved.
Compare completed crawls instead of relying on one-off reports.
See whether findings are new, resolved, or still persistent after changes.
Use monitoring to focus attention on meaningful site changes and breakages.
Small technical issues become expensive when they remain invisible. For broken link monitoring, a repeatable crawl helps distinguish a one-time anomaly from a persistent problem caused by templates, redirects, routes, metadata, or content changes.
Start with the concrete evidence: affected URL, source page, HTTP status, metadata value, redirect target, or comparison row. After the fix is made, run another crawl with comparable settings to confirm the finding is resolved.
It checks recurring crawls, audit history, and change detection and presents the result as summary counts plus URL-level evidence. That makes the audit useful for deciding what to fix and for verifying the result in a later crawl.
No. The URL is transferred to the crawler seed field so you can review scope, limits, redirects, and sitemap policy before starting.
Yes. Registered users can create scheduled audits and review whether findings are new, resolved, or still unresolved across completed crawls.
No. The same findings are useful for site maintenance, release validation, migration checks, and general quality assurance.
Create a free account to keep private crawl history and schedule recurring checks for monitored sites.