Upaccn Content Link Health Check

Upaccn Content Link Health Check is a focused broken-link diagnostic tool for WordPress content. It scans published posts, pages, and other public post types locally, checks each discovered HTTP or HTTPS link in small batches, and shows exactly which WordPress content contains each URL.

The first release deliberately stops at diagnosis. It does not edit posts, create redirects, calculate an SEO score, connect to a cloud crawler, or require an account.

Its key difference is conservative status handling:

• Broken is reserved for hard not-found responses such as HTTP 404 and 410.
• Redirect highlights 3xx responses so you can decide whether to update the source URL.
• Retry is used for authentication failures, rate limits, server errors, DNS/TLS/network failures, and other evidence that may be temporary or caused by bot protection.
• OK means the URL responded successfully during the scan.

This reduces the common failure mode where one blocked or rate-limited request is presented as if a page definitely disappeared.

The plugin uses short browser-driven batches instead of one long PHP request. It deduplicates URLs, keeps a list of source posts for each URL, and lets administrators manually recheck individual results.

Version 0.1.0 scans anchor (href) links in stored WordPress content. It does not yet crawl rendered page-builder DOM output or validate image/script/style assets.

No telemetry is sent. The only external requests are the URL checks you explicitly start. Scan data is stored in small local diagnostic tables and removed when the plugin is uninstalled.

External services

Upaccn Content Link Health Check sends HTTP requests only when an administrator starts a scan or manually rechecks a URL. The destination URLs come from links already stored in published WordPress content.

For each discovered HTTP/HTTPS link, the plugin first sends a HEAD request. If the destination rejects HEAD with HTTP 403 or 405, the plugin may send a bounded GET request with a Range header to obtain enough response information for diagnostics. The request uses a User-Agent containing the plugin version and this site’s public home URL. As with ordinary server-to-server HTTP traffic, the destination can observe the originating server IP address.

The plugin does not send WordPress account credentials, cookies, post contents, customer data, or a central telemetry payload. Because destinations come from links in the site’s own published content, they may belong to many unrelated third-party websites; there is no single external service operator or universal terms/privacy URL for those destinations.