Index WP MySQL For Speed vs MW LLMS Index

How do I use this plugin? After you install and activate this plugin, visit the Index MySQL Tool under the Tools menu. From there you can press the Add Keys Now button. If you have large tables, use it with WP-CLI instead to avoid timeouts. See the WP-CLI section to learn more. What does it do for my site? This plugin works to make your MySQL database work more efficiently by adding high-performance keys to the tables you choose. On request it monitors your site’s use of your MySQL database to detect which database operations are slowest. It is most useful for large sites: sites with many users, posts, pages, and / or products. You can use it to restore WordPress’s default keys if need be. What is this all about? Where does WordPress store all that stuff that makes your site great? Where are your pages, posts, products, media, users, custom fields, metadata, and all your valuable content? All that data is in the MySQL relational database management system. (Many hosting providers and servers use the MariaDB fork of the MySQL software; it works exactly the same way as MySQL itself.) As your site grows, your MySQL tables grow. Giant tables can make your page loads slow down, frustrate your users, and even hurt your search-engine rankings. And, bulk imports can take absurd amounts of time. What can you do about this? You can install and use a database cleaner plugin to get rid of old unwanted data and reorganize your tables. That makes them smaller, and therefore faster. That is a good and necessary task. That is not the task of this plugin. You can, if your hosting provider supports it, install and use a Persistent Object Cache plugin to reduce traffic to your database. That is not the task of this plugin either. This plugin adds database keys (also called indexes) to your MySQL tables to make it easier for WordPress to find the information it needs. All relational database management systems store your information in long-lived tables. For example, WordPress stores your posts and other content in a table called wp_posts, and custom post fields in another table called wp_postmeta. A successful site can have thousands of posts and hundreds of thousands of custom post fields. MySQL has two jobs: Keep all that data organized. Find the data it needs quickly. To do its second job, MySQL uses database keys. Each table has one or more keys. For example, wp_posts has a key to let it quickly find posts when you know the author. Without its post_author key MySQL would have to scan every one of your posts looking for matches to the author you want. Our users know what that looks like: slow. With the key, MySQL can jump right to the matching posts. In a new WordPress site with a couple of users and a dozen posts, the keys don’t matter very much. As the site grows the keys start to matter, a lot. Database management systems are designed to have their keys updated, adjusted, and tweaked as their tables grow. They’re designed to allow the keys to evolve without changing the content of the underlying tables. In organizations with large databases adding, dropping, or altering keys doesn’t change the underlying data. It is a routine maintenance task in many data centers. If changing keys caused databases to lose data, the MySQL and MariaDB developers would hear howling not just from you and me, but from many heavyweight users. (You should still back up your WordPress instance of course.) Better keys allow WordPress’s code to run faster without any code changes. Experience with large sites shows that many MySQL slowdowns can be improved by better keys. Code is poetry, data is treasure, and database keys are grease that makes code and data work together smoothly. Which tables does the plugin add keys to? This plugin adds and updates keys in these WordPress and WooCommerce tables. wp_comments wp_commentmeta wp_posts wp_postmeta wp_termmeta wp_users wp_usermeta wp_options wp_wc_orders_meta wp_woocommerce_order_itemmeta wp_automatewoo_log_meta You only need run this plugin once to get its benefits. How can I monitor my database’s operation? On the Index MySQL page (from your Tools menu on your dashboard), you will find the “Monitor Database Operations” tab. Use it to request monitoring for a number of minutes you choose. You can monitor either the site (your user-visible pages) or the dashboard, or both. all pageviews, or a random sample. (Random samples are useful on very busy sites to reduce monitoring overhead.) Once you have gathered monitoring information, you can view the captured queries, and sort them by how long they take. Or you can save the monitor information to a file and show it to somebody who knows about database operations. Or you can upload the monitor to the plugin’s servers so the authors can look at it. It’s a good idea to monitor for a five-minute interval at a time of day when your site is busy. Once you’ve completed a monitor, you can examine it to determine which database operations are slowing you down the most. Please consider uploading your saved monitors to the plugin’s servers. It’s how we learn from your experience to keep improving. Push the Upload button on the monitor’s tab. WP-CLI command line operation This plugin supports WP-CLI. When your tables are large this is the best way to add the high-performance keys: it doesn’t time out. Give the command wp help index-mysql for details. A few examples: wp index-mysql status shows the current status of high-performance keys. wp index-mysql enable --all adds the high-performance keys to all tables that don’t have them. wp index-mysql enable wp_postmeta adds the high-performance keys to the postmeta table. wp index-mysql disable --all removes the high-performance keys from all tables that have them, restoring WordPress’s default keys. wp index-mysql enable --all --dryrun writes out the SQL statements necessary to add the high-performance keys to all tables, but does not run them. wp index-mysql enable --all --dryrun | wp db query writes out the SQL statements and pipes them to wp db to run them. Note: avoid saving the –dryrun output statements to run later. The plugin generates them to match the current state of your tables. Why use this plugin? Three reasons (maybe four): to save carbon footprint. to save carbon footprint. to save carbon footprint. to save people time. Seriously, the microwatt hours of electricity saved by faster web site technologies add up fast, especially at WordPress’s global scale. How can I learn more about making my WordPress site more efficient? We offer several plugins to help with your site’s database efficiency. You can read about them here. Credits Michael Uno for Admin Page Framework. Marco Cesarato for LiteSQLParser. Allan Jardine for Datatables.net. Leho Kraav and Sebastian Sommer for suggesting the WooCommerce tables. Japreet Sethi for advice, and for testing on his large installation. Rick James for everything. Jetbrains for their IDE tools, especially PhpStorm. It’s hard to imagine trying to navigate an epic code base without their tools.

MW LLMS Index is a WordPress plugin that automatically generates AI-friendly index files for your website. It creates llms.txt (plain text) and llms.json (structured JSON) files inside wp-content/uploads/mw-llm-index/, making it easy for AI systems to discover and understand your content. Key Features: Automatic Index Generation: Automatically generates llms.txt and llms.json files with all your published posts and pages SEO Plugin Integration: Seamlessly integrates with popular SEO plugins (Rank Math, Yoast SEO, All in One SEO) to use meta descriptions Flexible Scheduling: Choose from daily, weekly, or manual regeneration schedules using WP Cron AI Bot Logging: Optional logging of AI bot visits (GPTBot, ClaudeBot, PerplexityBot) to track when AI systems access your site REST API Access: Access your index data programmatically via WordPress REST API Auto-Generation: Automatically creates files on activation if they don’t exist Clean Uninstall: Removes all generated files and settings when uninstalled Technical Features: ✔ WP Cron Integration: Uses WordPress built-in cron system for scheduled updates ✔ Editor Compatibility: Works seamlessly with both Gutenberg and Classic Editor ✔ Zero Frontend Assets: No JavaScript or CSS files loaded on the frontend – lightweight and fast ✔ WordPress Standards: Follows WordPress coding standards and best practices ✔ Multisite Compatible: Works on single-site and multisite installations What is llms.txt? The llms.txt file is a standardized format for providing AI systems with a structured index of your website’s content. It helps AI models like ChatGPT, Claude, and Perplexity understand what content is available on your site and how to access it. How It Works: The plugin scans all published posts and pages on your WordPress site Extracts titles, URLs, and descriptions (from SEO plugins when available) Generates two files: llms.txt – Human-readable plain text format llms.json – Machine-readable JSON format for programmatic access Files are automatically updated based on your chosen schedule Use Cases: Help AI systems discover and index your content Improve AI model understanding of your website structure Provide structured content metadata for AI training Track when AI bots visit your site Export your content index for external use Useful Links: Documentation Report Issues GitHub Repository External Services This plugin does NOT connect to any external services or APIs. All data is: * Generated locally on your WordPress server * Stored in your uploads directory * Accessible only through your own domain * Not transmitted to third parties The plugin is completely self-contained and operates entirely within your WordPress installation. Support For support, feature requests, or bug reports, please visit: * GitHub Issues * WordPress.org Support Forum Credits Developed by Mohamed Khalil Wazery Website: https://wazery.net Privacy This plugin: * Does not collect any user data * Does not send data to external servers * Only generates files locally on your WordPress installation * Optionally logs AI bot visits locally (can be disabled) * Does not use cookies * Does not track users The generated llms.txt and llms.json files are publicly accessible (located in wp-content/uploads/mw-llm-index/) and contain information about your published content, similar to what would be available in your sitemap. Security Notes Important Security Information: This plugin does not expose private data and only outputs publicly available content, similar to a sitemap. The generated files contain: * Only published posts and pages (same visibility as your public website) * Titles, URLs, and meta descriptions (already publicly accessible) * No private user information * No sensitive data or credentials The files are placed in wp-content/uploads/mw-llms-index/ and are publicly accessible, but they only contain information that is already available on your public website. If you have concerns about specific content being indexed, ensure those posts/pages are set to private or draft status.