Title: Text encoding trouble
Last modified: June 8, 2026

---

# Text encoding trouble

 *  Resolved [kassilukraine](https://wordpress.org/support/users/kassilukraine/)
 * (@kassilukraine)
 * [3 days, 1 hour ago](https://wordpress.org/support/topic/text-encoding-trouble/)
 * After updating the plugin to 8.4.1, everything worked relatively correctly. Now,
   after the update, something has happened with the file encoding. I also checked
   the Include post excerpts / meta descriptions box, but the information wasn’t
   added. Is this data generated by the AIOSEO plugin, or do you not support it?
 *     ```wp-block-code
       [Кейс: Повний редизайн сайту клініки пластичної хірургії]Кейс: Полный редизайн сайта клиники пластической хирургии]
       ```
   

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/)
 * (@ryhowa)
 * [2 days, 20 hours 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.
 *  Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/)
 * (@ryhowa)
 * [2 days, 20 hours 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.
 *  Thread Starter [kassilukraine](https://wordpress.org/support/users/kassilukraine/)
 * (@kassilukraine)
 * [2 days, 13 hours ago](https://wordpress.org/support/topic/text-encoding-trouble/#post-18932715)
 *  Hi [@ryhowa](https://wordpress.org/support/users/ryhowa/)
 * I downloaded the latest version that you updated to 8.4.3 but got an error when
   activating “The plugin could not be activated because it caused a critical error.”
   By the way, this update did not appear in the automatic plugin updates.
 *  Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/)
 * (@ryhowa)
 * [2 days, 12 hours 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.
 *  Thread Starter [kassilukraine](https://wordpress.org/support/users/kassilukraine/)
 * (@kassilukraine)
 * [2 days, 2 hours ago](https://wordpress.org/support/topic/text-encoding-trouble/#post-18932977)
 * Good morning [@ryhowa](https://wordpress.org/support/users/ryhowa/)!
 * After completely removing the plugin and reinstalling it, everything worked, 
   the coding was correct, and the meta data was correctly pulled up with AIOSEO
   pro 4.9.7.2.
 * Thank you for such a quick response.
 *  Plugin Author [Ryan Howard](https://wordpress.org/support/users/ryhowa/)
 * (@ryhowa)
 * [1 day, 22 hours ago](https://wordpress.org/support/topic/text-encoding-trouble/#post-18933246)
 * Glad to hear it! And thank you for following up.

Viewing 6 replies - 1 through 6 (of 6 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ftext-encoding-trouble%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/website-llms-txt/assets/icon-256x256.png?rev=3322182)
 * [Website LLMs.txt](https://wordpress.org/plugins/website-llms-txt/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/website-llms-txt/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/website-llms-txt/)
 * [Active Topics](https://wordpress.org/support/plugin/website-llms-txt/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/website-llms-txt/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/website-llms-txt/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [Ryan Howard](https://wordpress.org/support/users/ryhowa/)
 * Last activity: [1 day, 22 hours ago](https://wordpress.org/support/topic/text-encoding-trouble/#post-18933246)
 * Status: resolved