VisiBeacon – llms.txt, AI Crawler Tracking and AI Search Visibility

Өзгөртүүлөр

1.9.7

• Fixed: the free plugin shipped a native uninstall.php alongside the bundled licensing SDK. WordPress runs that file instead of the uninstall hook the SDK registers, so the SDK’s own uninstall flow never ran when the plugin was deleted. The data cleanup is now wired through the SDK’s uninstall hook, exactly like the Pro editions. No behavior change for your data: cleanup still runs on delete and still removes data only when “Remove ALL VisiBeacon data when the plugin is deleted” is enabled on the Data & Backup tab.

1.9.6

• New: “Generate a new key” button on the IndexNow tab. IndexNow caches its verification verdict per domain and key, so a domain that failed verification while the key file was unreachable can keep answering HTTP 403 for weeks even after the file works. A fresh key carries no cached verdict – every domain is verified anew on the next push.
• Fixed: on multilingual sites the llms.txt conflict notice could reappear even after VisiBeacon was correctly serving the file, wrongly naming an installed SEO plugin as the source. The check compared the live file (served in the site’s primary language) against the admin language’s version – it now recognizes VisiBeacon’s own output in any language.
• Improved: when the serving source of /llms.txt cannot be identified from its content, the notice no longer names a plugin whose llms.txt feature is verifiably switched off.

1.9.5

• Fixed: on multilingual sites, the Key pages and Excluded content pickers mixed every language’s items together (wp-admin does not filter queries by language, and WPML’s “All languages” admin mode never does). The pickers now list only the edited language’s items; items of untranslatable post types stay listed in every language, matching how the multilingual plugin serves them.
• Fixed: the published counts next to Content sections (and the max-items overflow warning) counted every language’s items on multilingual sites. They now count the edited language’s items.

1.9.4

• New: per-language llms.txt switch on multilingual sites – “Serve llms.txt for this language” on the llms.txt tab, set per language. Uncheck it for languages that are defined on the site but not really in use: that language’s llms.txt (and llms-full.txt) returns 404 and its link leaves the Dashboard list, while every other language keeps serving. Existing sites are unaffected – every language stays enabled until you switch it off.
• New: “select all” checkbox on every content-type group in the Key pages and Excluded content pickers – one click selects or clears a whole type (Posts, Pages, Products…), with a dash state when only some items are picked.
• New: FAQ status table on the FAQ tab – every published item with its FAQ count and a direct edit link, so you can see at a glance which pages still need questions. (Pro installs keep their richer table with generation buttons.)
• Improved: the FAQ tab now says clearly where editing happens – each item’s questions live on the item itself, edited from the VisiBeacon box in its editor sidebar, and the tab’s Edit links take you straight there.
• Improved: ticking a content type under “Content sections” now reveals that type’s items in the Key pages and Excluded content pickers immediately – no more saving first just to see them. Picks made for a type you later untick are also no longer silently dropped on the next save.
• Improved: FAQ placement (append after content vs schema only) is now set per language on multilingual sites, like the FAQ heading. A language without its own choice follows the primary language, so existing sites behave exactly as before.

1.9.3

• New: “Free vs Pro” tab – a plain comparison of what the free plugin includes (everything listed stays fully functional) and what the separate Pro plugin adds. Nothing in the free plugin is locked or disabled; the tab is purely informative and disappears when Pro is installed.
• Improved: when an IndexNow push fails for some domains on a multi-domain site, only the failed domains’ URLs are kept for the automatic retry – the domains that went through count as pushed and are not re-sent. The verification error message now also explains that IndexNow re-checks key files periodically, so a 403 can persist for a while after the key file becomes reachable and then clears on its own.

Earlier releases are documented in changelog.txt, bundled with the plugin.