DevDome Link Monitor checks links and image URLs in saved published content, and logs incoming requests for missing pages. Review results and replace exact links from your WordPress dashboard, with no account required for scanning.
Free and GPL licensed, reviewed by the WordPress.org plugin team.
Check published content, review uncertain results separately and choose which links to fix. The always-on 404 log also shows missing URLs requested by visitors and crawlers.
Scan internal links, external links and image URLs in saved published content from public post types, excluding attachments. This is not a whole-site crawler: menus, widgets, custom fields and unpublished content are outside its scope.
Links need two failures separated in time before being marked broken. Connection failures and access restrictions stay separate from broken results. A missing page returning HTTP 200 still counts as OK.
Use Edit URL to replace an exact link across its source posts, or Unlink to keep its text. Changes require edit permission on every affected post, retain WordPress revisions and record an audit trail.
The always-on 404 log separates human and bot hits using user-agent patterns, which can be forged. Review redirect suggestions against existing slugs; applying them requires active DevDome Redirect Manager or copying the suggested .htaccess rule.
The Overview shows checked links, healthy links, broken links, redirects and human and bot 404 totals. Follow the health trend across the last 12 scans; the score covers scanned content, not your entire website.
Start, pause, resume or cancel scans running in small batches, and adjust timeout, batch sizes or excluded domains. Scanning uses your server resources; optional weekly or monthly schedules depend on WP-Cron and can run late.
The 404 log stores no IP addresses and nothing on a visitor device. Requested paths omit query strings; referrer storage can be reduced or disabled. Export results to CSV, ignore paths and automatically purge old active entries.
On WordPress 6.9 and newer, compatible AI agents can review results, control scans, edit links and manage settings through exposed WordPress Abilities. MCP access needs an adapter; the same permissions and per-post edit checks apply.
The 404 monitor starts as soon as you activate the plugin. Start a link scan when you are ready to check published content.
Install DevDome Link Monitor from WordPress.org and activate it. The 404 monitor starts immediately, with no setup needed.
Open DevDome > Link Monitor and click Scan Links. Scans run in small batches, driven by your browser while the screen is open or by WP-Cron.
Review broken links and uncertain results separately. Choose Edit URL, Unlink, Re-check now or Dismiss, then review incoming missing-page requests in the 404 log.
No. It checks anchor and image URLs in saved content from published public post types, excluding attachments. Menus, widgets, theme options, custom fields, srcset candidates, oEmbed and iframe targets, and reusable or synced patterns not inlined in posts are excluded. Drafts, private content and scheduled content are also excluded.
No. Scanning reads content and records results. Only choosing Edit URL or Unlink changes content, and you need edit permission on every affected post. Edit URL replaces exact link URLs, not arbitrary text or other database values. Changes retain WordPress revisions and an audit trail.
Timeouts, DNS failures, TLS errors and refused connections stay Unverified. Authentication, blocking and rate-limit responses stay Could not verify. Verification also requires PHP cURL and a connection that can be pinned to validated public addresses; unsupported proxy routing leaves URLs unverified. Try Re-check now or open the link yourself.
Scans use PHP workers on your server, with small batches and at most two links per host per tick. Lower batch sizes in Settings on smaller hosts. Scheduled scans use WP-Cron, so they can run late without visits or a real cron job calling wp-cron.php.
Scanning requires no account and has no page or link limits. Email summaries require a connected DevDome account and report newly broken links with counts only. DevDome sends the email; the plugin does not. Without a connected account, no email is sent.
Link checks go directly from your server to destination sites. DevDome receives no link URLs or visitor data. Connecting an account shares aggregate scan metrics and account and scan metadata. Connecting through the disclosed Tools dashboard also shares active DevDome plugin and platform versions. The catalog fetch sends only the bundled core version.
The log offers suggestions matched against existing post and page slugs. Use the one-click action when DevDome Redirect Manager is active, or copy the suggested .htaccess rule. You can also ignore paths, delete rows and export the log to CSV.
Yes. Settings, scan results and the 404 log are per site. Network activation provisions sites it can reach in one request. Remaining sites, and sites created later while the plugin is network-active, create their own tables on first load.
Installation, settings, data use and troubleshooting, before you install.
Install DevDome Link Monitor from WordPress.org (Plugins, Add New, search for DevDome Link Monitor) or upload the ZIP, then activate it.
No account is needed for link checking or 404 monitoring. Optional email summaries require a connected DevDome account and contain counts only.
Open DevDome, Link Monitor in the admin menu and click Scan Links to run your first scan. The 404 monitor starts immediately with no setup needed.
In Settings, adjust the check timeout, posts per batch and links per batch, and configure the user agent and excluded domains. Scans run in small, resumable batches driven by your browser while the screen is open or by WP-Cron.
You can enable weekly or monthly rescans and an optional email summary of newly broken links. Privacy settings let you disable user-agent storage and reduce referrers to their origin or turn referrer storage off.
Link scan results, including URLs and their HTTP status, stay in your own database. The 404 log stores requested paths without query strings, hit counts, the last referrer and, unless disabled, the last user agent. No IP addresses are stored and no cookie is set. Referrer query strings are never stored, and values that look like credentials or personal data are masked. Active log rows expire after 30, 90 or 180 days, and ignored rows after one year, with row caps on both.
During a manual or enabled scheduled scan, link checks go directly from your server to the linked sites. Each destination sees your server's IP address, the configured user agent and the URL, including any personal data or signed token in that URL. Neither a cookie nor an authentication header is sent with those checks. The DevDome Dashboard also fetches the plugin catalog from devdome.com at most once every 12 hours, and only after the site is connected to a DevDome account, sending only the bundled core version and no site or visitor data. Only public http or https destinations on ports 80 or 443 without credentials in the URL are checked; private-network destinations are skipped, and the same limits apply after each redirect.
Connecting an optional DevDome account sends your site address, generated site ID and secret site token to DevDome; later account checks send the site domain and token. Connected scans send account identifiers, the scan number, aggregate scan metrics, the email-summary setting and the plugin screen address for the account dashboard and optional counts-only email. No scanned URLs, anchor text, post titles, 404 paths, referrers, user agents or visitor IP addresses are sent to DevDome. Connecting through the DevDome Tools dashboard card that discloses this also shares active DevDome plugin slugs and versions, plus the bundled library, WordPress and PHP versions. The Connect card in Link Monitor Settings enables the same sharing. Earlier connections and connections through buttons without that disclosure do not send the plugin list; disconnecting stops it.
Updates come from WordPress.org like any other directory plugin and can be installed through the Plugins screen, bulk updates or automatic updates.
Deactivating keeps all data. Deleting the plugin immediately removes its own tables, settings, transients and scheduled events on every site of a network. The shared DevDome library settings, including the account connection and cached detection lists, are also removed when Link Monitor is the last DevDome plugin installed; they remain while other DevDome plugins are installed.
A working link appears as Unverified or Could not verify: the destination may block automated requests, require a login, rate-limit requests or time out. Use Re-check now or open the link yourself.
Links are missing from the scan: check where they are stored. The scanner checks anchor and image URLs in saved published post content; widgets, menus, custom fields and theme options are not scanned.
Scanning slows the site: lower the batch sizes in Settings on small hosts. Scans run on your server and use PHP workers, even though they run in small chunks with low default budgets.
A scheduled scan runs late: check whether WP-Cron is being triggered by site visits or a real cron job calling wp-cron.php. Scheduled scans can run late on low-traffic sites.
Still stuck? Ask on the WordPress.org support forum or use the DevDome contact form. For a security problem, use the Report a security issue tab instead.
Read from the WordPress.org release when this site was last synced. The two latest versions are shown here; the full history is on WordPress.org.
Please tell us before telling anyone else, and we will fix it and credit you if you want the credit. Use the contact form and say it is a security report, so it gets read first.
We are a small team, so we will not pretend to a 24/7 security desk or a guaranteed response time. We will read it, reply, and tell you honestly what we are doing about it.
Install DevDome Link Monitor from WordPress.org, activate it and click Scan Links. No account is required for scanning.
