Title: Ryan Howard's Replies | WordPress.org --- # Ryan Howard [ ](https://wordpress.org/support/users/ryhowa/) * [Profile](https://wordpress.org/support/users/ryhowa/) * [Topics Started](https://wordpress.org/support/users/ryhowa/topics/) * [Replies Created](https://wordpress.org/support/users/ryhowa/replies/) * [Reviews Written](https://wordpress.org/support/users/ryhowa/reviews/) * [Topics Replied To](https://wordpress.org/support/users/ryhowa/replied-to/) * [Engagements](https://wordpress.org/support/users/ryhowa/engagements/) * [Favorites](https://wordpress.org/support/users/ryhowa/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 51 total) 1 [2](https://wordpress.org/support/users/ryhowa/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/ryhowa/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/ryhowa/replies/page/4/?output_format=md) [→](https://wordpress.org/support/users/ryhowa/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] WPML Hidden Languages Are Included in llms.txt](https://wordpress.org/support/topic/wpml-hidden-languages-are-included-in-llms-txt/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 week, 3 days ago](https://wordpress.org/support/topic/wpml-hidden-languages-are-included-in-llms-txt/#post-18934333) * Hi [@rskdev](https://wordpress.org/support/users/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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Text encoding trouble](https://wordpress.org/support/topic/text-encoding-trouble/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 week, 4 days ago](https://wordpress.org/support/topic/text-encoding-trouble/#post-18933246) * Glad to hear it! And thank you for following up. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Text encoding trouble](https://wordpress.org/support/topic/text-encoding-trouble/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 week, 4 days ago](https://wordpress.org/support/topic/text-encoding-trouble/#post-18932746) * Hi [@kassilukraine](https://wordpress.org/support/users/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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Text encoding trouble](https://wordpress.org/support/topic/text-encoding-trouble/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 week, 5 days ago](https://wordpress.org/support/topic/text-encoding-trouble/#post-18932247) * Hi [@kassilukraine](https://wordpress.org/support/users/kassilukraine/) My BOM removal in 8.4.1 was the cause. Turns out web servers need explicit UTF-8 charset header for non-ASCII. After updating, go to Settings → LLMs.txt → Generate Now to rebuild the file * AIOSEO meta description support now added in **8.4.3** and verified against AIOSEO** 4.9.7.2 Free** via a single test. Thanks for reporting both issues. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Text encoding trouble](https://wordpress.org/support/topic/text-encoding-trouble/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 week, 5 days ago](https://wordpress.org/support/topic/text-encoding-trouble/#post-18932229) * Hi [@kassilukraine](https://wordpress.org/support/users/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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Visibility Kit & Cloudflare](https://wordpress.org/support/topic/visibility-kit-cloudflare/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [2 weeks ago](https://wordpress.org/support/topic/visibility-kit-cloudflare/#post-18930562) * Hi [@heeroyui](https://wordpress.org/support/users/heeroyui/) We’re rolling out the Visibility Kit dashboard in phases to ensure it’s airtight. Hoping to have it widely available by mid summer. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Generated llms.txt fails Lighthouse/Semrush “missing H1” check due to —](https://wordpress.org/support/topic/generated-llms-txt-fails-lighthouse-semrush-missing-h1-check-due-to/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [2 weeks ago](https://wordpress.org/support/topic/generated-llms-txt-fails-lighthouse-semrush-missing-h1-check-due-to/#post-18930560) * Hi [@volskr](https://wordpress.org/support/users/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 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Why Limit Max Post & Words?](https://wordpress.org/support/topic/why-limit-max-post-words/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [2 weeks ago](https://wordpress.org/support/topic/why-limit-max-post-words/#post-18930557) * Hi [@beachholiday](https://wordpress.org/support/users/beachholiday/) Thanks for the kind words! The max-posts and words-per-summary settings are a relief valve for large sites, where llms.txt can become slow to generate, heavy to serve, or unwieldy for models to parse. There is a separate issue where some users included full content from pages/posts and reported pages from their sites being dropped from the index due to duplicate content. Side note: We tested serving full .md files for every page on a site with proper canonicals, but we didn’t record any noticeable lift in grounded search visibility. Google lighthouse recently added a llms.txt entry under “Agentic browsing audits” and we hope to see more detailed guidance there in the future. [https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt](https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] GDPR](https://wordpress.org/support/topic/gdpr-256/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [2 weeks ago](https://wordpress.org/support/topic/gdpr-256/#post-18930549) * Hi [@webministeren](https://wordpress.org/support/users/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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Showing FAQ page in llms.txt file](https://wordpress.org/support/topic/showing-faq-page-in-llms-txt-file/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [2 weeks ago](https://wordpress.org/support/topic/showing-faq-page-in-llms-txt-file/#post-18930547) * Hi [@olistic](https://wordpress.org/support/users/olistic/) That’s expected behavior. The section headings in llms.txt come from your post types. Your FAQ page is a regular WordPress Page, so it correctly lists under `## Pages`. The`## All FAQs` section is generated from an “FAQs” custom post type (registered by your theme or an FAQ/SEO plugin) and only contains entries of that post type. So a Page titled “FAQ” will always appear under Pages, not under All FAQs. If you want it under All FAQs, the content would need to be created as an FAQ custom- post-type item rather than a Page. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Fatal error with Rank Math when not fully configured (Call to setup() on null)](https://wordpress.org/support/topic/fatal-error-with-rank-math-when-not-fully-configured-call-to-setup-on-null/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 month, 2 weeks ago](https://wordpress.org/support/topic/fatal-error-with-rank-math-when-not-fully-configured-call-to-setup-on-null/#post-18899785) * [@aldricke](https://wordpress.org/support/users/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). * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Website LLMs.txt] Doesn’t track anything](https://wordpress.org/support/topic/doesnt-track-anything/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 month, 3 weeks ago](https://wordpress.org/support/topic/doesnt-track-anything/#post-18890382) * The old version tracked only hits to your llms.txt file as described in the documentation. Not all bot traffic. The new version is still not a “track every training bot” plugin, but it now tracks AI search related visits with a counter in the WP admin. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Slim SEO Integration](https://wordpress.org/support/topic/slim-seo-integration/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 month, 3 weeks ago](https://wordpress.org/support/topic/slim-seo-integration/#post-18890376) * New version live today. Please let me know if it works for you. * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[SearchOptimizer.ai – AI Search Optimizer] Tracking doesn’t work, audit is buggy](https://wordpress.org/support/topic/tracking-doesnt-work-audit-is-buggy/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [1 month, 3 weeks ago](https://wordpress.org/support/topic/tracking-doesnt-work-audit-is-buggy/#post-18890194) * Hi [therber2](https://wordpress.org/support/users/therber2/), This plugin is no longer supported. I’ll add a note to the main plugin page this week. AI tracking has been improved significantly and is moving to [https://wordpress.org/plugins/visibility-kit-seo/](https://wordpress.org/plugins/visibility-kit-seo/) with a new version launch coming next week. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Website LLMs.txt] Flushing permalinks & network activation](https://wordpress.org/support/topic/flushing-permalinks-network-activation/) * Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/) * (@ryhowa) * [2 months ago](https://wordpress.org/support/topic/flushing-permalinks-network-activation/#post-18882579) * Hi Teemu, This is fixed but we are making some other significant changes and they will all be released together sometime next week. Viewing 15 replies - 1 through 15 (of 51 total) 1 [2](https://wordpress.org/support/users/ryhowa/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/ryhowa/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/ryhowa/replies/page/4/?output_format=md) [→](https://wordpress.org/support/users/ryhowa/replies/page/2/?output_format=md)