LinkSolva - Broken Link Checker is a local WordPress tool for administrators who need to know what is genuinely broken before changing content.
It discovers URLs in public posts, pages, public custom post types, approved comments, custom navigation menus, featured images, and optionally scalar custom-field or page-builder data. It stores each unique URL separately from the places where it appears, so the same destination is verified once while all source locations remain available.
The plugin classifies results instead of treating every failed request as a dead link:
- Healthy — a successful response was received.
- Redirect — the destination works but reaches another URL.
- Broken — HTTP 404 or 410 provides strong evidence that the destination no longer exists.
- Blocked — the destination rejected automated verification, such as HTTP 401 or 403.
- Rate Limited — the destination returned HTTP 429 and should be checked later.
- Temporary Error — the destination returned a 5xx response.
- SSL Error, DNS Error, Timeout, or Unverified — the scanner could not establish enough evidence to call the URL broken.
Every result includes request history, redirect chain, response time, confidence, explanation, and source locations.
Local by design
- No cloud account.
- No link credits or usage limits imposed by a third party.
- No telemetry, advertising, or developer tracking.
- No URLs or site content are sent to a developer service.
- HTTP requests are made from your WordPress server to the destinations found in your content.
Safe repairs
Supported post content, approved comment content, and custom menu URLs can be replaced, unlinked, or marked nofollow. Builder metadata is read-only in this release. Each repair stores the complete before and after source, the user, time, operation, and checksums. Undo is blocked when the source changed after the repair.
Resource controls
Scanning runs in small resumable worker requests. Each discovered source batch is verified before the next source batch is read, and repeated occurrences do not re-queue a settled URL. Only one worker request processes the scan at a time. HTTP request timeouts are capped to the worker's remaining time budget, and URLs left unchecked stay queued for the next request. Network failures are recorded without repeating the same request immediately, so the worker can move on and retry later. The scanner also uses per-resource deduplication, redirect limits, response-size limits, and safe retry scheduling. Manual scanning remains available when WordPress cron is delayed.
Privacy
This plugin does not create a remote account or transmit data to the developer. The server running WordPress may make requests to external URLs found in your content. The request destination, response status, timing, and limited diagnostic categories are stored in your WordPress database.