Scans now use far less server CPU. They take longer to finish, because external links are checked one at a time.<\/p>","1.1.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.0","1.1.1"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[905,14279,40482,14280,732],"plugin_category":[52],"plugin_contributors":[280914],"plugin_business_model":[],"class_list":["post-380081","plugin","type-plugin","status-publish","hentry","plugin_tags-905","plugin_tags-broken-links","plugin_tags-dead-links","plugin_tags-link-checker","plugin_tags-maintenance","plugin_category-performance","plugin_contributors-techpot","plugin_committers-techpot"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/blockbadurls-broken-link-checker.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
BlockBadURLS Broken Link Checker finds broken links - on your own site and pointing out to others - and lists them grouped by post so you can fix or remove them in one click.<\/p>\n\n
BlockBadURLS Broken Link Checker is built to stay out of the way: a scheduled, throttled scan that never runs continuously, so it never competes with your site's own traffic for server resources, even on shared hosting.<\/p>\n\n
Under Tools \u2192 BlockBadURLS Broken Link Checker \u2192 Settings<\/strong>:<\/p>\n\n A connection failure, 404, 410, or a 5xx server error. Responses like 401, 403, and 429 are treated as alive, since many sites block automated checkers - flagging those would bury real breakage in false positives.<\/p>\n\n A 404 or 410 is reported at once. A connection failure or 5xx error can be a temporary outage, so it is only reported after failing two checks in a row.<\/p>\n\n Links the plugin is not allowed to request - because of This plugin connects to the external sites your own posts and pages link to, in order to check whether those links are still working. This is the plugin's core function and cannot be turned off, since checking external links is what it does.<\/p>\n\n For each link found in your published content, during a scan, BlockBadURLS Broken Link Checker makes a HEAD request (falling back to a GET request only if HEAD fails or is rejected) to that URL, to read its HTTP response status. No data about your site or its visitors is sent - only a standard HTTP request identifying itself as BlockBadURLS Broken Link Checker, the same as a browser visiting the link would send.<\/p>\n\n Which external sites are contacted depends entirely on which external links exist in your own content - there is no fixed list.<\/p>\n\n\n 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.<\/p><\/dd>\n Yes. Links to your own posts, pages, and uploaded files are checked for free, with no outbound HTTP request - see \"What it does\" above.<\/p><\/dd>\n Only the Yes. Pause scan<\/strong> stops it and keeps the results so far; Resume scan<\/strong> carries on from the same post, without re-checking what is already done. Start over<\/strong> 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n Which post types are scanned is a setting (default: all public ones); the \n
What counts as broken<\/h4>\n\n
WP_HTTP_BLOCK_EXTERNAL<\/code> \/ WP_ACCESSIBLE_HOSTS<\/code>, a private network address, or an unusual port - are skipped rather than reported.<\/p>\n\nExternal services<\/h3>\n\n
\n
\/wp-content\/plugins\/blockbadurls-broken-link-checker<\/code>, or install directly from the Plugins screen in your dashboard.<\/li>\n\n
Will this slow down my site?<\/h3><\/dt>\n
Does it check internal links too?<\/h3><\/dt>\n
What happens when I click Unlink?<\/h3><\/dt>\n
<a><\/code> 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.<\/p><\/dd>\nCan I stop a scan part-way?<\/h3><\/dt>\n
Why does it say my site could not reach itself?<\/h3><\/dt>\n
Can I control which post types are scanned?<\/h3><\/dt>\n
blockbadurls_post_types<\/code> filter can still override it from code.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.1<\/h4>\n\n
\n
blockbadurls_concurrency<\/code> and blockbadurls_per_host<\/code> filters, which no longer apply.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n