| 开发者 | techpot |
|---|---|
| 更新时间 | 2026年10月14日 01:51 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
WP_HTTP_BLOCK_EXTERNAL / WP_ACCESSIBLE_HOSTS, a private network address, or an unusual port - are skipped rather than reported.
/wp-content/plugins/blockbadurls-broken-link-checker, or install directly from the Plugins screen in your dashboard.No. Scanning runs in small batches on a schedule, never as a continuous crawl, and links to your own posts/pages/uploads are checked without any HTTP request at all.
Yes. Links to your own posts, pages, and uploaded files are checked for free, with no outbound HTTP request - see "What it does" above.
Only the <a> tag is removed; the link's visible text stays in the post. Nothing else in the post is changed. A button block keeps its button and just loses the link, so the block stays valid in the editor.
Yes. Pause scan stops it and keeps the results so far; Resume scan carries on from the same post, without re-checking what is already done. Start over checks every post again from the beginning. A scan left paused for longer than your scan interval starts fresh, so the results are never badly out of date.
BlockBadURLS Broken Link Checker checks some links to your own site with a real request, and that request failed - often a firewall, security plugin, maintenance mode or a local development setup blocking the site from calling itself. Those links are skipped, not reported as broken. Links to your own posts, pages and uploads are still checked directly. WordPress's Site Health screen shows the same problem.
Which post types are scanned is a setting (default: all public ones); the blockbadurls_post_types filter can still override it from code.
blockbadurls_concurrency and blockbadurls_per_host filters, which no longer apply.