ANDPLUS-LLMO

AI Visibility logs which known AI crawlers request your public pages. Filter by period, compare bots and paths, and download a UTF-8 CSV—all stored in your database on this site.

You also get llms.txt and an AI sitemap so crawlers can understand your site: public /llms.txt and /sitemap-ai.xml, plus standard head tags. Many sites already output structured data (such as schema.org), but AI crawlers may still miss context—llms.txt and sitemap help close that gap.

ANDPLUS-LLMO helps you:

• Monitor AI crawler activity inside WordPress (period filters, bot breakdown, top paths, recent visits, CSV export of the access log)
• Provide a public /llms.txt endpoint for AI visibility
• Add official <link rel=”llms”> and <link rel=”sitemap”> tags via wp_head
• Automatically generate /sitemap-ai.xml including your llms.txt

All of the above works in this plugin without payment. No physical llms files are created on disk, and visibility data stays in your database on this site. Apache: copy the mod_rewrite block from Setup → Redirect into your site root .htaccess (the plugin does not write to .htaccess). Nginx: configure as shown in Setup. WordPress robots.txt can include a comment for the llms.txt URL and a Sitemap: line for sitemap-ai.xml (disable or customize via filters ap_llmo_robots_append_llms_comment, ap_llmo_robots_append_sitemap_ai, ap_llmo_robots_txt_append). Home can show optional rule-based hints (no API).

Optional Pro add-on (separate download): Adds AI-assisted content workflows (BYOK with OpenAI), extended endpoints (llms.full.txt, .ai-context, docs/ai), weekly reports, and extended sitemap-ai.xml URLs. Licensing is handled only in the Pro add-on. In the free plugin, upgrade links use the filter ap_llmo_pro_upgrade_url; AI Visibility “recent visits” list length can be tuned with ap_llmo_visibility_recent_limit (default 100).

Filters: ap_llmo_llms_public_url, ap_llmo_sitemap_ai_public_url are available for custom environments without pretty URLs. AI Visibility retention and export can be tuned with ap_llmo_access_log_retention_days (default 90), ap_llmo_access_log_max_rows, ap_llmo_access_log_export_max_rows, and ap_llmo_access_log_csv_filename (default andplus-llmo-access-log-{period}-{date}.csv). Extensions can supply ap_llmo_visibility_trends_url_for_path (empty string, path) so the access log shows an extra link per path (ANDPLUS-LLMO Pro uses this for Visibility trends when licensed).

Support

• Directory plugin: Community support and documentation; individual replies are not guaranteed.
• Pro: Support as described when you purchase ANDPLUS-LLMO Pro (see vendor or product page linked from the add-on).

We do not support custom theme/plugin conflicts, server configuration, or general WordPress usage beyond this plugin.

Privacy

• AI Visibility: When a request is detected as a known AI crawler user-agent, the plugin may store a row with timestamp, request path, user agent, and derived bot name / service in a custom database table on this site. A separate daily summary table stores one row per calendar day (totals only, no per-request paths) for analytics; it follows the same retention policy unless changed via ap_llmo_visibility_daily_retention_days. Data stays on your server; it is not sent to the plugin author by this plugin. Timestamps follow your WordPress timezone (Settings → General). Rows are kept for a limited time (default 90 days, removed by WordPress’s scheduled tasks). The log also has a maximum row count (default 5000); when that limit is reached, the oldest rows are removed first, so on very busy sites you may see fewer days of history than the retention window. This cap applies to all users of this plugin—it is not a Pro-only restriction. Administrators can download a CSV of stored rows from the AI Visibility screen; the file stays local to your browser.
• No telemetry: This plugin does not load a licensing SDK and does not call the plugin author’s servers for licensing or analytics.