| 开发者 | plugupp |
|---|---|
| 更新时间 | 2026年7月13日 22:52 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Upgrade to Premium for a Learning Engine that tunes itself to your site, scheduled scans and email reports, change detection, soft-error and Safe Browsing checks, rule-based exclusions and CSV export. See plans and pricingWhat you get on the free plan
Most checkers read links out of your database. This plugin renders each page the way a visitor's browser would and checks the links and images that actually ship - including ones added by your theme, menus, widgets, footers and page builder, which database-only checkers never see. It runs entirely on your own server, with no external crawler and no per-link quota.
No. It audits only your known WordPress content and the links and images those pages output. It never follows links to discover new URLs like a crawler.
No. Scanning is local. To check whether an external link or image works, the plugin requests that URL directly from your server - but only URLs that already appear on your pages, and only to read their response. Google Safe Browsing checks are a Premium, opt-in feature that requires your own Google API key; without one, nothing is sent to Google.
No. It is fully functional with no limits: it scans all your content - posts, pages, custom post types and WooCommerce products, and optionally unpublished content - and checks every link, image and resource. The premium version is a separate plugin, delivered from plugupp.com, that adds the Learning Engine, scheduled scans and email reports, change detection, soft-error and Safe Browsing checks, rule-based exclusions and CSV export. See the full plan comparison
Password-protected pages are never scanned - there is no way to render them without the password. Private, draft, scheduled and pending content is skipped by default, but you can include it by enabling Unpublished content in Settings; it is rendered privately for the scan only and never shown to visitors. Make a page public (or remove its password) and it is picked up on the next scan.
Some hosts (for example sites behind Cloudflare) challenge automated requests. The plugin tells these apart from genuine failures and marks them "blocked, not broken" so you are not chasing false positives.