| 开发者 | pierreferrolliet |
|---|---|
| 更新时间 | 2026年10月5日 14:33 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<a href>, <img src>, <img srcset>, and <source srcset> — all natively, using the WordPress HTTP API. No SaaS, no API key, no external dependency.
Features:
srcset and <picture> elementstidy-broken-link-scan folder to /wp-content/plugins/No. Scans run in the background via WP-Cron and are never triggered by front-end visitors.
Yes — <img src>, <img srcset>, and <source srcset> are all parsed and checked.
Once per day automatically (at 03:00 server time). You can also trigger a full scan manually or re-scan individual posts on save.
Posts are automatically re-scanned every time you publish or update them.
Some servers refuse automated requests, or answer a HEAD request differently from a real visit. Open the link, confirm it is fine, then use Ignore on that row: it stays out of your broken count without being deleted.
It is the share of checked links that are broken. Above 3% the grade drops sharply, because at that level readers and search engines hit dead ends regularly.
Yes, and a link that ends on a working page is not reported as broken. The Fix redirect action rewrites the link to its final destination so readers skip the extra hop.
Yes. Settings has a domain exclusion list, plus a URL exclusion list for one-off cases. Social networks that systematically block crawlers are skipped by default.
You edit the URL from the results table and the plugin rewrites it everywhere it appears in your content, so you do not have to open each post.
No. Every check is made from your own server with the WordPress HTTP API. The optional cloud scanner is a separate tool you visit yourself.
FILTER_VALIDATE_URL, which is ASCII-only, so those URLs were treated as relative and the site origin was prepended a second time.blsc_scannable_post_types filter to customise the list.wp_remote_*) for link and image checking, including the batch scanner. Redirects are now followed via the HTTP API while still reporting redirect chains and loops.blc export now writes CSV to STDOUT only (use shell redirection, e.g. wp blc export > report.csv); the arbitrary --file path option was removed.$wpdb queries, and translators comments for all i18n placeholders (Plugin Check compliance).<?=) with full <?php echo in the post meta box (WordPress.org coding-standards compliance).phpcs:ignore suppressions with explicit wp_kses(), esc_attr() and (int) casts in the dashboard view (WordPress.org coding-standards compliance).blsc_extra_links filter.load_plugin_textdomain() call (handled by WordPress.org translation system since WP 4.6).