Linux 软件免费装
Banner图

AKSA AI Monitor - AI Crawler Analytics & Bot Control

开发者 mikiaksa
更新时间 2026年8月1日 07:10
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

robots.txt ai analytics ai crawler ai traffic bot control

下载

1.0.4 1.0.5

详情介绍:

AKSA AI Monitor records requests from supported AI crawler User-Agent strings and recognized AI referral hosts. It separates content reads from robots.txt, sitemap, API, administration, feed, HEAD, and common static-asset requests. AKSA AI Monitor includes: The plugin does not use an AI API and does not send activity data to the plugin author or an external analytics service. Report availability depends on the configured detailed-data retention period. New installations retain detailed activity for 180 days by default, and administrators can choose between 7 and 365 days. Measurement limits Crawler identity is currently detected from the request User-Agent header. User-Agent strings can be imitated, so the plugin labels identity as detected and unverified. A detected request is not proof that an AI provider cited, recommended, approved, endorsed, or rated the website or its content. AI sessions are estimates. Requests from the same detected agent and privacy-safe fingerprint within a 30-minute time bucket are grouped together. Confirmed AI referral visits require a recognized campaign parameter (including ChatGPT Search's utm_source=chatgpt.com) or browser referrer. Some AI services remove both signals, so referral totals can be lower than actual visits. Visits by logged-in WordPress users are excluded to avoid counting site-owner activity.

安装:

  1. Upload the plugin ZIP through Plugins > Add New > Upload Plugin, or install it from the WordPress.org directory after publication.
  2. Activate the plugin.
  3. Open AKSA AI in the WordPress administration menu.
  4. Keep Open mode while testing unless you intentionally want to publish crawler restrictions.
  5. Choose whether the corner signal is hidden, administrator-only, or public.

屏幕截图:

  • Topic trends and the most-read WordPress pages based on locally detected AI-agent requests.
  • Optional public AI Activity signal showing recent measured activity and clearly stating the limits of the measurement.

升级注意事项:

1.0.5 Improves cross-theme appearance, administration controls, branding, and timezone clarity without removing existing statistics. 1.0.4 Internal identifiers now use the unique AKSA AI Monitor prefix requested during WordPress.org review. 1.0.3 Renamed release with unrestricted report periods, selectable CSV exports, and WordPress.org review corrections. 1.0.0 First public release of AKSA AI Monitor.

常见问题:

Does this prove that ChatGPT or Claude recommends my website?

No. It records requests whose User-Agent matches a supported AI crawler or user agent. Access is not proof of a citation, recommendation, approval, endorsement, or quality assessment.

What is a content read?

A crawler GET request for a content page after robots.txt, sitemap, REST API, administration, feed, HEAD, and common static-asset requests are excluded.

What is an AI session?

An estimate grouping the same detected agent and privacy-safe visitor fingerprint within a 30-minute time bucket.

Does the plugin store IP addresses?

No raw IP address is stored. When available, the server address is immediately transformed into a site-specific HMAC hash used only for estimated sessions. CSV exports exclude this fingerprint.

Where are the data stored?

In tables inside the website's own WordPress database. Activity is not sent to the plugin author or an external analytics account.

What is the difference between robots.txt and HTTP 403?

robots.txt publishes an advisory request that compliant crawlers may follow. HTTP 403 enforcement actively refuses a matching request. The enforcement option is off by default.

Will deactivation remove my statistics?

No. Deactivation keeps settings and data. During uninstall, data are deleted only when the administrator previously enabled the explicit uninstall-deletion setting.

更新日志:

1.0.5 1.0.4 1.0.3 1.0.2 1.0.1 1.0.0