Snagbane Link Scanner
| 开发者 | snagbane |
|---|---|
| 更新时间 | 2026年9月23日 04:19 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Searching for a "broken link checker" or "dead link checker" for WordPress turns up plenty of options -- but most of them treat a blocked request the same as a dead page. If a link you pointed to is protected by Cloudflare, Akamai, Incapsula, PerimeterX, DataDome, or Sucuri, those firewalls often reject an automated checker with a 403, 503, or a "checking your browser" challenge page -- and most plugins report that as broken, even though a real visitor opening the same link in their browser gets the page just fine.
Link Scanner tells the two apart. Every link gets a real verdict, not just a status code:
- Broken -- the page is actually gone (a genuine 404/410, or the domain no longer resolves).
- Blocked, likely fine -- the request was rejected by a firewall or bot-protection service, not because the page is gone.
- Needs re-check -- a timeout, a server error, or an SSL issue that's worth trying again before calling it either way.
- OK -- responded normally, including redirects that land somewhere that still works.
- "Find a fix" -- looks up an archived copy of the dead page on the Wayback Machine and replaces the link everywhere it appears on your site, in one click, without leaving the page you are on.
- Bulk "Find a fix" -- does that for every broken link on the site in one pass: it gathers the suggestions, you review them, and only the ones you approve get applied.
- Undo -- every replacement, single or bulk, is reversible with one click. A page you have edited since the fix is left alone rather than overwritten.
- The "looks fine, isn't" pass -- finds links that answer 200 OK and are dead anyway: soft 404s, deep links quietly redirected to a front page, domains that have been parked or changed hands, and affiliate links that have stopped earning.
- Reports -- a CSV and an Excel workbook with a summary sheet, a chart, and every link ranked by what needs attention first.
- Email alerts the moment a link is confirmed broken.
安装:
- Upload the plugin files to
/wp-content/plugins/snagbane-link-scanner, or install it directly through the WordPress plugins screen. - Activate the plugin through the "Plugins" screen in WordPress.
- Open the new "Link Scanner" menu item in your admin sidebar. The first scan of your published content starts automatically within about 10 seconds of activation.
屏幕截图:
常见问题:
Why does it say a link is "blocked" instead of just checking it again?
Because a firewall-blocked response usually won't change no matter how many times an automated tool retries it -- the firewall is rejecting the checker, not reporting a real outage. Flagging it as "blocked, likely fine" tells you it's worth a quick manual look in a real browser, rather than an automatic "fix this" alarm for a page that's actually working.
Will this slow down my site?
No. Checks run in small batches on WordPress's background cron, separate from any page a visitor loads.
Does it modify or delete my links automatically?
No. Link Scanner only reports verdicts; it never edits your post content or removes links on its own.
What happens to links that stop appearing in my content?
They're automatically cleaned up from the tracked list a set number of days after no longer being referenced anywhere, so the report doesn't accumulate stale entries forever.
What language does it speak?
Whatever WordPress is set to. Translations for German, Spanish, French, Italian, Portuguese (Brazil), Dutch, and Polish ship with the plugin; every other locale falls back to English. If a community translation for your language exists on translate.wordpress.org, WordPress uses that instead -- language packs take priority over the files bundled here, so contributing there improves the plugin for everyone rather than fighting with it. The verdict explanation in the "Why" column follows the language of whoever is reading the screen, not the language the check ran under. An administrator whose profile language is Polish sees Polish explanations even on a site running in German.
更新日志:
0.4.1
- Fixed: the 0.4.0 guard meant to keep a fresh install off an upgrade-only backfill query never fired -- it tested for null, and get_option() returns false for a missing option. Every fresh install still ran a statement that is valid MySQL and unsupported by SQLite, which is what WordPress.org's Live Preview runs on.
- Fixed: on a host where the new columns cannot be added (a database user without ALTER), 0.4.0 re-ran the whole schema upgrade on every request, front end included, forever. It now retries at most once an hour, and the write path already degrades to the older columns in between.
- Fixed: the dashboard's "confirmed working" card counts links that are OK and links that redirect to a working page, but clicked through to a list of only the first kind -- so a card reading 6 opened a list of 2. The card now links to a combined view.
- Fixed: network activation walked every site on every network in the install, including archived, spam and deleted ones, in a single request. It is now scoped to the current network and real sites, and stops after 200; every remaining site sets itself up on its first page load.
- Fixed: the one-shot "first scan" event was never cleared on deactivation, so it sat in wp_options indefinitely on a site with WP-Cron disabled.
- Added: uninstall.php, so deleting the plugin removes its two tables, its options and its scheduled events. Deactivating still leaves everything alone.
- Added: an Upgrade Notice entry for the 0.4.0 schema change.
- Changed: the bundled Freemius SDK's updater class had been renamed from its stock name, and one upstream branch removed, specifically to avoid WordPress.org's automated Plugin Check. The rename is reverted and the comments describing the evasion are gone. The SDK should be re-bundled verbatim from Freemius's own build tool.
- Added: the plugin is now fully translatable, and ships translations for German, Spanish, French, Italian, Portuguese (Brazil), Dutch, and Polish. A WordPress.org language pack for your locale, if one exists, still takes priority over the bundled files.
- Added:
Domain Pathheader and aload_plugin_textdomain()call oninit(not earlier -- WordPress 6.7 warns about textdomains loaded beforeinit). - Changed: the verdict explanation in the "Why" column is now rendered in the language of whoever is reading the table, rather than the language that happened to be active when the check ran. A link checked by WP-Cron used to keep the site language forever, even for an administrator whose own profile language was different. Links checked before upgrading keep their stored wording until their next check.
- Changed: the classifier now returns a verdict code instead of an English sentence, keeping that file free of WordPress dependencies as its documentation always claimed. The sentence is built by the new
Snagbane_Scanner_Reasonsclass. - Changed: database schema 3 -- two nullable columns,
reason_codeandreason_args, added in place bydbDelta(). No data is rewritten or lost, and the existingreasoncolumn is still written exactly as before. - Fixed: the "last checked" column glued a translated word onto a duration ("5 mins" + "ago"), which puts the word in the wrong place in German, French, Spanish, and Portuguese. It is one translatable phrase now.
- Fixed: the progress panel's
display:flexrule overrode thehiddenattribute, so an empty progress bar sat on the screen on every page load until a scan was started. - Fixed: progress messages that contain a count are now built server-side, so
_n()picks the plural form. Choosing between two forms in JavaScript is wrong for Polish, which has three. - Changed: the "Pro also includes" line described an older Pro feature set and no longer mentioned bulk fixing, undo, or the "looks fine, isn't" pass.
- Fixed: a relative redirect from a URL on a non-default port resolved to the wrong address, because the origin was rebuilt without the port. The next hop then hit a closed port, which was reported as "the domain does not resolve" -- a false "broken" verdict, at high confidence, on a working link. This is now resolved by WordPress's own WP_Http::make_absolute_url(), which also handles ".." and query-only redirects correctly.
- Fixed: the "Redirects fine" verdict could never be reached. It required a 3xx status together with a resolved destination, but the destination is only ever resolved once a hop lands on a 2xx -- so external redirects were all filed under "OK" and that tab always read zero.
- Fixed: the schema upgrade recorded its new version even when the migration had not actually run (a database user without ALTER, for instance). Every later verdict write then named columns that did not exist, so wpdb rejected the whole update and links stayed on "Needs re-check" forever with the buttons appearing to do nothing. The version is only recorded once the columns are confirmed present, and a site in that state now degrades to the older write instead of losing it.
- Fixed: "Re-scan content now" could report the site's entire link table as newly found. The starting count is held in a transient; if that expired mid-run on a large site, zero was subtracted instead. The transient also now lasts an hour rather than ten minutes.
- Fixed: network-activating on a multisite with more than 100 sites only set up the first 100, because get_sites() defaults to that limit. Sites beyond it never had any scheduled events and silently never checked a link.
- Fixed: two administrators working at the same time could see each other's confirmation messages ("5 links ignored") for actions they had not taken.
- Fixed: a fresh install ran an upgrade-only backfill query that is valid MySQL but unsupported by SQLite, which is what WordPress.org's own Live Preview runs on.
- Fixed: the progress sentence after a re-scan put the verb in the outer template, where it could not agree with the noun inside the placeholder -- "1 página analisadas" in Portuguese, and the same in Spanish, French and Italian. Each half of the sentence now carries its own verb.
- Fixed: the
Plugin URIheader pointed at this plugin's own wordpress.org listing page, which WordPress.org's own header requirements explicitly disallow ("you cannot use a WordPress.org URL here" -- that URL is assigned automatically and isn't meant to be self-referenced). Now points to linkscanner.snagbane.com. - Removed: an orphaned, unreferenced leftover image (
linkverdict.png) inside the vendored Freemius SDK's assets folder, and corrected a stale "linkverdict-premium/" example name in a code comment inside the SDK's own deliberately-modifiedclass-freemius.php. Cosmetic only, but nothing carrying the plugin's old name should ship in the zip. - Fixed: the plugin file's header
Descriptionfield was 150 characters -- over WordPress.org's documented under-140-character limit for that specific header (a different field, with a different limit, from this readme's own short description line above, already fixed in 0.3.3). Shortened to 125 characters. - Changed: header
Licensefrom the SPDX-styleGPL-2.0-or-latertoGPLv2 or later, matching both WordPress.org's own documented header example and this readme's License field, which already used that form. - Verification: re-ran the full WordPress Coding Standards scan (PHPCS + WordPress, WordPress-Extra, WordPress-Docs) against every file ahead of resubmission -- zero findings in any security-relevant category (nonces, sanitization, escaping, prepared SQL, global-variable overrides). Re-confirmed PHP 7.4 compatibility (no PHP 8-only syntax anywhere in the plugin).
- Verification: ran the actual WordPress Coding Standards (PHPCS + WordPress-Extra, the same sniff family WordPress.org's Plugin Check tool is built on) against every file in this plugin, instead of relying on manual review alone.
- Fixed: a
$_GETread added in 0.3.6 (the Add-Ons checkout-link fix) had its nonce-verification suppression comment placed so it only covered the first of two superglobal reads on adjacent lines -- the second was still flagged. Both are read-only, non-state-changing checks; the suppression now correctly covers both. - Documented (no behavior change): three call sites using
current_time( 'timestamp' )forhuman_time_diff()display and one cutoff calculation were flagged by an automated sniff that (correctly, in general) discourages that pattern -- but here it's deliberately the site's LOCAL time, matching howlast_checked/orphaned_sinceare stored (current_time('mysql')), which is the same idiom WordPress core itself uses. Annotated with the sniff exception and the reasoning inline, so this doesn't show up as an unexplained finding in a future automated scan. - Documented (no behavior change): the temporary
$GLOBALS['post']swap in the content-rendering scan (needed so third-party block/shortcode render callbacks that assume "the loop" is set up work correctly during a background scan) is a deliberately safe, always-restored pattern that a "no global overrides" sniff flags on principle. Annotated with the sniff exception and reasoning rather than left as an unexplained flag. - Confirmed via automated compatibility scan and manual review: no PHP 8-only syntax anywhere in this plugin (no
match, enums, readonly properties, nullsafe chaining, or first-class callables) -- genuinely compatible with the declared "Requires PHP: 7.4", not just untested on it.
- Fixed: this file's own
SNAGBANE_SCANNER_VERSIONconstant had been left at0.3.4while the header above already said0.3.5-- a mismatch from the previous release that meant cache-busted asset URLs (?ver=...) and the stored upgrade-routine version check were one release behind the actual code. Both now read0.3.6consistently. - Fixed: a docblock in the cron batch-check function still described re-check cadence as "differs by plan (weekly vs. daily)" -- the trialware mechanism that comment was describing was removed back in 0.3.4, but the comment itself was never updated, so it kept describing removed behavior as if still current. No code behavior was affected; corrected so the comment doesn't read as evidence of a lingering Free/Pro split.
- Fixed: a
$_GETcheck in the Freemius Add-Ons checkout-link fix compared raw superglobal values instead of sanitized ones (unlike the equivalent pattern already used elsewhere in this plugin). No functional impact -- brought in line with the rest of the codebase for Plugin Check consistency. - Housekeeping: full pass over both this plugin and the separate Pro add-on for leftover trialware-era wording, stale comments, and WordPress.org guideline compliance following the 0.3.4/0.3.5 changes -- no other issues found.
- Changed: the Freemius product-identity slug is now
snagbane---link-scanner(wassnagbane---link-verdict), finishing the "Link Verdict" -> "Link Scanner" rename on the one identifier 0.3.4 had deliberately left alone. Done only after the matching slugs were already created on the Freemius dashboard itself, so this is a code change to match an already-live record, not a blind rename. Purely an internal licensing identifier -- not visible to site owners and no action needed on existing installs. - Changed (Pro add-on, not distributed here): Pro's own Freemius identity slugs, and its deployed folder/main file, are renamed to match in the same release -- see the Pro add-on's own changelog. Existing Pro customers need to reinstall it once.
- Fixed: removed the 50-tracked-link cap and the weekly-only re-check cadence, both previously liftable only by the separate Pro add-on via a filter this plugin exposed -- flagged by WordPress.org's plugin review as Guideline 5 "trialware" (deliberately throttled, already-implemented functionality with a built-in unlock point for something else to raise), even though Pro ships as a completely separate product never submitted to WordPress.org. This plugin now tracks every link with no cap and re-checks on one fixed daily cadence, on every install, full stop; Pro's value is entirely in capabilities this plugin doesn't implement at all (CSV export, email alerts, "Find a fix"), not a throttled version of what's already here.
- Changed: this plugin's folder name, main file, and WP-admin menu slug (previously left as
linkverdict/linkverdict.phpon the theory that they were separate from the public-facing rename in 0.3.3) are nowsnagbane-link-scannerthroughout, so nothing in this plugin still carries the "Link Verdict" name WordPress.org's naming review flagged. All internal function, class, constant, and hook names updated to match (Snagbane_Scanner_*/snagbane_scanner_*/SNAGBANE_SCANNER_*). The Freemius product-identity slug (snagbane---link-verdict) is unrelated to any of this and is unchanged on purpose -- see this plugin's main file for why. - Fixed: a JS object name got mangled by an earlier literal "Link Verdict" -> "Link Scanner" text rename (introduced in 0.3.3) into
Link ScannerAjax-- a space inside what needs to be a single JavaScript identifier. This silently broke the admin screen's AJAX nonce (and therefore "Check due links now", "Re-scan content now", and the per-row ignore/re-check actions) wherever the JS engine didn't just fall back to the plain form-POST path. Renamed toSnagbaneScannerAjax. - Changed: the "Learn about Pro" link now points to linkscanner.snagbane.com (was linkverdict.snagbane.com), matching this rename.
- Changed: plugin renamed from "Snagbane - Link Verdict" to "Snagbane Link Scanner" (slug: snagbane-link-scanner), following a WordPress.org pre-review naming/similarity note against an existing broken-link-checker plugin with an almost identical name. Text Domain and all translation-function calls updated to match. No functional or behavior changes.
- Fixed: the inline
<script>on the wp-admin Add-Ons "View version details" dialog (correcting the Pro add-on's per-plan checkout links) is now enqueued viawp_register_script()/wp_add_inline_script()instead of being printed directly. No behavior change. - Changed: readme.txt short description shortened to fit WordPress.org's 150-character display limit (was 154).
- Added: an optional, one-time review prompt on this plugin's own admin page after it catches 10 genuinely broken links -- not on a fixed timer. Dismissible, never shown again once answered either way, and never tied to any tracking or external service.
- Changed: readme.txt rewritten for WordPress.org search -- short description and opening description paragraph now use the exact phrases people actually search ("broken link checker", "dead link checker"), and "seo" swapped out of the tag list (too broad/competitive to help) for "404 checker" and "link monitor". No code or behavior changes.
- Fixed: this plugin's Text Domain (and all ~70 translation-function calls) changed from 'linkverdict' to 'snagbane-link-verdict', to match the repository slug WordPress.org assigns based on this plugin's name at the time ("Snagbane - Link Verdict"). Flagged by WordPress.org's own Plugin Check tool as 70 TextDomainMismatch errors ahead of submission; no user-facing behavior changed. This plugin's folder name and admin menu were unaffected. (Superseded by the 0.3.3 rename above.)
- Fixed: on the wp-admin "Add-Ons" screen's "View version details" dialog for the separate Link Scanner Pro add-on, every plan's "Purchase" button linked to the same plan/price regardless of which plan card it was under (a bug in the underlying licensing SDK's dialog rendering). This only affected the discovery/checkout link for the separately-sold add-on -- no free-tier feature or behavior was involved.
- Attempted fix for the above (superseded by 0.2.9 -- an SDK script re-broke the link a moment after page load).
- Attempted fix for the above (superseded by 0.2.9 -- removed the affected buttons entirely as a temporary safety measure).
- Changed: this plugin's and the separate Pro add-on's licensing-platform product records were recreated after an internal state issue on the platform side; no functional change to this plugin.
- Changed: re-enabled the wp-admin "Add-Ons" screen (turned off in 0.2.4) now that the add-on product's slug mismatch on the licensing platform (fixed in Link Scanner Pro 1.0.4) is corrected. This screen only lists the separate Link Scanner Pro add-on for discovery; it has no bearing on this free plugin's own functionality, which remains 100% free and unrestricted.
- Reverted: the wp-admin "Add-Ons" screen added in 0.2.3 is turned back off. The Link Scanner / Link Scanner Pro add-on link was never fully registered on the licensing platform's side, so the screen just errored, and enabling it also surfaced a confusing "Activate License" action on this free plugin's own listing (this plugin has no license of its own -- it's free, full stop). The existing in-plugin "Upgrade to Pro" notice/link covers the same purpose. No functional change either way.
- Added: the Freemius account screen in wp-admin now lists Snagbane Link Scanner Pro as an available add-on (a "learn more" surface, same purpose as the existing "Upgrade to Pro" notice already in this plugin's admin screen). No code, feature, or license behavior changed -- this plugin still contains zero Pro-only or license-gated functionality.
- Fixed: several false-positive database-access warnings from WordPress.org's automated review scanner, by restructuring how request data is read and sanitized in a few admin-ajax handlers (no behavior change -- the underlying checks and sanitization were already correct, just written in a way the scanner's static analysis couldn't fully trace).
- Changed: every direct database query against this plugin's own two custom tables is now individually documented in code with the reason it queries directly and does not use object caching (both tables are small by design and several actions require the very next read to reflect a write immediately).
- No functional or behavioral changes for site owners -- this is a second code-quality/compliance release, verified against WordPress.org's full Plugin Check tool with zero errors and zero warnings across all 34 default checks.
- Fixed: internal Freemius bootstrap function/global/hook names (previously the abbreviated
lv_fs) renamed tolinkverdict_fsto match the plugin's own naming prefix throughout. - Fixed: the admin stylesheet registration now declares an explicit asset version.
- Changed: the core-content rendering call used while scanning posts for links is now explicitly annotated as intentional, to avoid a false positive from automated naming-convention scanners.
- No functional or behavioral changes for site owners -- this is a code-quality/compliance release only, verified against WordPress.org's full Plugin Check tool (all categories, not just a subset).
- Changed: restructured for WordPress.org compliance. Every Pro feature (unlimited links, daily re-checks, CSV export, email alerts, "Find a fix") has moved out of this plugin entirely and into a separate, optional add-on plugin, "Snagbane Link Scanner Pro," distributed only from snagbane.com. This free plugin now contains no license-gated code of any kind -- every feature described above is fully included and unrestricted.
- No changes to Free-tier behavior: the 50-link cap, weekly re-check cadence, and full verdict engine work exactly as before.
- Added: an "External Services" disclosure section to this readme.
- Existing Pro customers: install the separate Link Scanner Pro plugin (available from your snagbane.com account) to keep Pro features working after updating to this version.
- Changed: plugin now published under the Snagbane name instead of an individual's name; support/contact channel is now a shared Snagbane address.
- No changes to plugin behavior -- every Free and Pro feature (link cap, weekly/daily re-check cadence, CSV export, email alerts, "Find a fix") was re-tested against a live install this release and confirmed working correctly with no regressions.
- No functional changes -- version bump only, plus a store listing tag tweak (swapped "maintenance" for "dead links" so the plugin is easier to find for what people actually search).
- Fixed: a link stuck on "Needs re-check" (timeout, server error, or SSL issue) was only tried again after the full weekly (Free) or daily (Pro) re-check cadence -- the same wait as an already-confirmed working link -- instead of on the next scan, as the message on screen says. It's now retried within about an hour.
- No functional changes -- version bump only, so this test build has a single unambiguous file name.
- Fixed: the internal wp-admin/wp-cron/wp-login/xmlrpc link detection added in 0.1.9 assumed WordPress was installed at your site's root -- sites with WordPress installed in a subdirectory (a supported, documented setup) could still pick up those as bogus tracked links. It's now detected correctly on any install layout.
- Fixed: two rare timing edge cases that, on a busy site, could very occasionally attach a check result to the wrong link or lose an increment to a link's retry counter.
- Fixed: "Find a fix" (Pro) now double-checks a link is still actually broken right before replacing it, in case a re-check in another tab already fixed it in the meantime.
- Fixed: on sites set to a non-UTC timezone, the weekly/daily re-check schedule and the grace period before removing an unused link from tracking could each drift off by your site's UTC offset instead of running exactly on time.
- Fixed: "Find a fix" could corrupt an unrelated, working link if it happened to share a starting path with the broken one (e.g. fixing a broken /blog also mangled a working /blog-archive link in the same post). Fixes now only ever touch an exact match.
- Fixed: a link that redirects to one of your own posts/pages/products could still get stuck on "Needs re-check: timeout" the same way plain same-site links used to before 0.1.12 -- the same-site check now also applies to redirect destinations, not just the original URL.
- Fixed: a link pointing at one of your own posts, pages, or products could get stuck permanently on "Needs re-check: timeout" -- on some hosts, checking a link back to your own site creates a request that can never complete, no matter how many times it retries. Those links are now checked directly against your site's own records instead of over the network, so they get a real, instant verdict.
- Changed: the "Ignored" tab is now always shown (as "Ignored (0)" when empty) instead of appearing only once something's been ignored, and disappearing again if you un-ignore everything.
- Fixed: the tab counts at the top of the screen (All, Broken, Needs re-check, etc.) only updated after a full page reload -- ignoring, un-ignoring, or re-checking a link now updates those numbers immediately.
- Fixed: sites that had already picked up bogus internal links (your own site's wp-admin, wp-cron, wp-login, or xmlrpc pages, tracked before the 0.1.9 fix) have those automatically cleaned out on upgrade -- no manual ignoring or waiting out the cleanup grace period needed.
- Fixed: clicking "Ignore," "Un-ignore," or "Re-check now" on a link bounced you back to a different tab than the one you were viewing (most often "Needs re-check"), instead of staying where you were -- annoying when clearing out several links in a row.
- Changed: "Ignore," "Un-ignore," and "Re-check now" now happen instantly in place, without a full page reload -- noticeably snappier, especially "Re-check now," which used to freeze the whole page while it made the actual check.
- Fixed: on sites where a product grid, gallery, or similar block builds its own pagination/sort links, those links could get mistaken for real content links and tracked as "checked" -- showing up as permanently timed-out or unreachable URLs pointing at your own site's admin, cron, or login pages. Those internal WordPress URLs are no longer tracked as links to check.
- Added: "Check due links now" and "Re-scan content now" show a live progress bar (which link/page is being processed right now) instead of just a spinner with no feedback until the whole request finishes.
- Added: the Free-plan dashboard now also mentions "Find a fix" as a Pro feature, alongside email alerts.
- Added (Pro): email alerts the moment a link is confirmed broken -- one summary email per check, not one per link, listing what broke and which pages to fix.
- Added (Pro): "Find a fix" -- for a confirmed broken link, looks up whether the Wayback Machine has an archived copy and, with one click, replaces that link everywhere it's used on your site (or with a URL of your own choosing).
- Fixed: links written as a protocol-relative URL ("//example.com/page") were being mangled into a broken link on your own domain instead of the intended external site.
- Fixed: a link like "tel:0038163123456" (an all-digit phone number, very common in footers/contact pages) could be mistaken for a site-relative path and turned into a broken junk link. Link-checking is now limited to actual http/https links across the board, so any non-web link type (tel:, sms:, data:, custom app links, etc.) is correctly skipped instead of only a fixed list of names.
- Fixed: once a link was marked "Ignored," it disappeared from every view with no way to find it again -- there's now a dedicated "Ignored" tab so it can be un-ignored.
- Fixed: a link that stopped being used somewhere on your site was supposed to get a grace period before being auto-removed from tracking, but was actually being removed with no grace period at all in most cases. The grace period now works as intended.
- Added: the dashboard now shows Free-plan link tracking usage at a glance, plus a clear notice with an upgrade link once the 50-link limit is reached.
- Hardened the 0.1.4 content-rendering fix after stress-testing it against real failure modes: it no longer makes any outbound network request of its own (a video URL or [embed] shortcode in your content used to risk a live call to YouTube/Vimeo/etc. during a background scan), one broken block or shortcode on a page can no longer abort a whole scan (that page is skipped, the rest still complete), and the automatic/manual full-content scan no longer silently stops at 200 posts on larger sites.
- Fixed a real link-detection gap: pages built with block-based page builders (Spectra, Kadence Blocks, and similar) often store a link only inside a dynamic block's data, with no plain link markup in the stored content at all. Link Scanner now scans the fully rendered page instead of the raw stored content, so those links are found too.
- Added a "Re-scan content now" button so you can force an immediate full re-crawl after importing a theme demo, bulk-editing content, or any change that might not go through a normal save -- instead of waiting for the automatic scan.
- The automatic full-content scan now runs hourly instead of daily, so any content that does slip past the normal per-save scan surfaces much sooner.
- Redesigned the admin screen: icon-badge stat tiles, a link-health gauge, and a floating pill filter bar, replacing the earlier boxed/bordered layout.
- Added full WordPress Multisite support: network-activating the plugin now provisions every site on the network, and any site created afterward is provisioned automatically.
- Initial release: verdict engine (broken / blocked / needs re-check / OK), background batch checking, admin screen with filters, search, sorting, bulk and per-row actions, CSV export and tiered plans via Freemius.