DevDome Link Monitor
| 开发者 | devdome |
|---|---|
| 更新时间 | 2026年9月2日 18:34 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Every 404 is logged automatically: normalized path (query string removed), hit counters, last referrer, last user agent, first/last seen.
- Bot/human split from the user-agent string. Each hit is matched against known crawler patterns, so obvious crawler noise is separated from everything else. A user agent can be forged, so "human" means "did not match a known crawler pattern" - it is not proof of a real visitor. A request with no user agent at all is always counted as a bot. The screen names the classifier it used.
- Humans-only view, per-path ignore, row delete, CSV export, and automatic purging (30/90/180 days, your choice) with a row cap. Ignored paths have their own bounds: they are kept for one year and capped in number, so they cannot grow without limit either.
- Redirect suggestions: each 404 path is fuzzy-matched against your published post and page slugs. If DevDome Redirect Manager is active you get a one-click "Create redirect" prefill; otherwise a copy-ready .htaccess rule.
- Chunked, resumable, pausable and cancelable. It runs in small background slices driven by your browser while the screen is open, or by WP-Cron.
- Conservative by design. A link is only marked broken after it fails twice in checks that are separated in time (15 seconds by default) - two failures inside the same processing burst are not treated as independent evidence, and a link that recovers starts from a clean slate. Timeouts, DNS failures, TLS errors and refused connections are never counted as broken; they are shown as "Unverified" with the reason. 401 (authentication required), 403 after a full GET, 429 (rate limited) and 999 (anti-bot) are shown as "Could not verify", never as broken.
- Redirect chains are followed manually (up to 5 hops, loop detection) and reported with the final URL and hop count.
- Fix problems from the review table: Re-check now, Edit URL (updates every post that contains that exact link), Unlink (keeps the anchor text), or Dismiss. Every content change requires WordPress' own permission to edit each affected post and is recorded in an audit trail.
- Low default budgets and per-host courtesy spacing: at most 2 links per host are processed per tick. Verifying one link can involve more than one request - HEAD is used first, a size-capped GET (128 KB) is sent when the server rejects or gates HEAD or before any HEAD failure is recorded (some servers mishandle HEAD while GET works), and redirects are followed up to 5 hops.
- Optional weekly/monthly scheduled rescan with an email summary of NEW broken links only (sent to the email of your connected DevDome account).
post_content) of published posts in public post types (attachments excluded) - <a href> and <img src>, including markup inside block comments.
Not scanned: widgets, menus, theme and customizer options, post meta and custom fields, srcset candidates, oEmbed/iframe targets, the bodies of reusable/synced patterns that are not inlined in the post, and drafts, private or scheduled content. This is not a whole-site crawler.
Link health at a glance
The Overview tab shows a link-health score, checked/healthy/broken/redirect counts, and the 404 monitor's human-vs-bot totals.
安装:
- Upload the plugin to
/wp-content/plugins/and activate it, or install it from the Plugins screen. - The 404 monitor starts working immediately - no setup needed.
- Open DevDome Tools → Link Monitor and click Scan Links to run your first broken-link scan.
常见问题:
Why does it report fewer broken links than my old link checker?
Because it refuses to guess. A link is only marked broken after failing twice in checks separated in time; timeouts, DNS failures and TLS errors are shown as "Unverified" rather than broken; and 401/403/429/999 responses are shown as "Could not verify". What is left is much more likely to be genuinely broken. It is a conservative policy, not a guarantee - a target that answers 200 with a "page not found" page still counts as OK.
Does it slow down my site?
404 logging adds one indexed lookup and one write, and only on requests that are already 404s. The scan runs in small chunks with low default budgets and at most two links per host per tick, but it does run on your server and does use PHP workers, so a scan is not free. Lower the batch sizes in Settings on small hosts.
How does the bot/human split work?
It matches the user-agent string against known crawler patterns. That is all it can do: user agents are trivially forged, so treat "human" as "not obviously a crawler". Requests with no user agent are counted as bots. The Settings tab names the classifier that produced the split.
Do scheduled scans work on a quiet site?
They use WP-Cron, which only fires when someone visits your site (or when a real cron job calls wp-cron.php). On a low-traffic site a scheduled scan can run late.
Can it fix links, not just find them?
Yes. From the review table you can edit a URL (updated in every post that contains it), unlink it while keeping the anchor text, re-check it, or dismiss it. You must have WordPress permission to edit every post the link appears in - if even one is out of reach, nothing is changed. Every change is written to WordPress in the normal way (so revisions apply) and recorded in an audit trail.
Does it support multisite?
Yes. Network activation provisions the sites it can reach in one request; any remaining site (and any site created later while the plugin is network-active) creates its own tables on its first load. Settings, the 404 log and scan results are per site.
更新日志:
- Shared DevDome library updated to core 1.6.3: the DevDome Dashboard now reads the current plugin catalog (names, descriptions, logos, links) from devdome.com once every 12 hours, and other DevDome plugins can be installed from WordPress.org in one click.
- First tab is now called Overview, in line with the other DevDome plugins. Old links to the Dashboard tab still open it.
- Scan history pruning now binds every id in its IN (...) lists through $wpdb->prepare().
- First WordPress.org release.
- Broken link scanner with a two-strike rule: a link is only called broken after two separate failures, and 401, 403, 429 and anti-bot answers are reported as blocked, never broken.
- Passive 404 monitor with human hits and bot hits kept apart, redirect suggestions on request, .htaccess rule copy and Redirect Manager hand-off, CSV export.
- Edit, unlink or dismiss a link from the list; every content change is verified against the saved post and needs edit rights on that post.
- Scans run in bounded chunks and finish on their own, with a closed browser and without visitors, and recover from an interrupted finish.
- Optional email summary of newly broken links, sent by DevDome to the connected account email, counts only.
- Outbound checks refuse private and reserved addresses and pin the resolved address to the connection; requires the cURL extension.