Ryan Howard

Hi @rskdev

Thanks for the clear report and the reproduction steps. The plugin now reads WPML’s hidden-languages setting and skips any post whose language is hidden, so those URLs no longer appear in llms.txt.

This will go out in the next release (8.4.4). After you update, please do a full rebuild so already-cached pages are re-evaluated.

Settings → LLMs.txt and use the Reset option (it clears the cache and regenerates from scratch). A plain “Generate Now” only adds new pages, so the Reset is what clears out the previously-included hidden-language URLs.

Hi @kassilukraine

8.4.3 is healthy on wp.org and the auto-update should be showing for you now.

A “critical error on activation” right after a manual zip upload is typically a partial or mixed install (some old files left behind, or the upload didn’t fully extract). Please try letting WordPress do the update from the Plugins screen to see if that sorts the issue.

I’ve verified the 8.4.3 package itself is complete and activates cleanly on PHP 7.2 through 8.4 with All in One SEO active. You can also try a clean reinstall:

1. Deactivate and delete the Website LLMs.txt plugin (your settings and generated file are kept in the database, so nothing is lost).
2. Reinstall it fresh from Plugins → Add New → search “Website LLMs.txt”
3. Activate.

If you still get the critical error after a clean reinstall, please send me the exact error so I can pinpoint it. You can find it in Tools → Site Health → Info, in the “critical error” email WordPress sends the admin, or by enabling debug logging (add define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); to wp-config.php, reproduce, then check wp-content/debug.log). The fatal’s file and line number will tell us exactly what’s happening on your setup.

Hi @kassilukraine

The web server must have been setting headers for .txt with no charset causing issues for non-ASCII-language sites. Shipping the fix now with BOM back and an explicit UTF-8 header.

After updating, go to: Settings → LLMs.txt → Generate

Meta descriptions are now supported for AIOSEO in version 8.4.3. I tested against AIOSEO 4.9.7.2 Free, but please let me know if any issues crop up on your end on Pro versions or otherwise.

Thanks for reporting both issues.

Hi @volskr

Excellent report, thank you.

8.4.1 released today removes the --- separators and I dropped the UTF-8 BOM 💥 so the first byte is now the # of the H1

Hi @webministeren

Thanks for the detailed note, and for supporting the plugin. I want to clarify the most important point: the Visibility Kit tracking is not enabled by default. On a fresh install the plugin sets no cookies and loads no third-party scripts. The vk.js script (and the _vk_* cookies) only load after an administrator enters an email address and clicks “Connect to Visibility Kit” in the settings. That connection step is what activated it on your site. You can switch it off completely at any time with “Disconnect from Visibility Kit,” which you found, and that removes the script and stops the cookies.

As of 8.4.1 we’ve added documentation listing every _vk_* cookie (_vk_vid, _vk_session_id, _vk_attr_first, _vk_landing, _vk_referrer) so you can declare them in your cookie policy, plus guidance to connect only after wiring the script into your CMP (Cookiebot, Complianz, etc.) so the cookies fire post-consent. We’re also reviewing the wording at the connect step to make the cookie/script behavior clearer before you opt in.

Appreciate you flagging it.

@aldricke

Thank you for the detailed report and patch.

Shipped your fix as 8.3.4. The $use_rankmath flag now also requires isset(rank_math()->variables) so the integration cleanly skips when Rank Math is active but not yet initialized (fresh install / setup wizard incomplete).

New version live today. Please let me know if it works for you.

Hi Teemu,

This is fixed but we are making some other significant changes and they will all be released together sometime next week.