About this plugin
AKSA AI Monitor records requests from supported AI crawler User-Agent strings and recognized AI referral hosts. txt, sitemap, API, administration, feed, HEAD, and common static-asset requests.
AKSA AI Monitor includes:
- AI requests, estimated AI sessions, content reads, and AI referrals for 24 hours or 7, 30, 60, 90, and 180 days.
- All-time request and content-read totals stored as compact daily aggregates.
- Top five content pages with WordPress titles, source agents, reads, and last activity.
- Topic trends derived from WordPress categories, tags, and titles.
- Recent activity with content and infrastructure events clearly separated.
- Open, Balanced, Protected, and Custom crawler-policy modes.
- Optional HTTP 403 enforcement. Without enforcement, blocking choices add advisory rules to WordPress virtual robots.txt.
- Optional public or administrator-only AI Signal corner widget.
- Activity status based only on content reads: active within 7 days, recent within 30 days, or no recent activity.
- Privacy-friendly local storage. Raw IP addresses are not stored.
- Configurable detailed-data retention, permanent reset controls, and CSV exports for periods up to 365 days.
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.
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.
Privacy
The plugin stores detected request metadata locally: time, event type, provider, agent label, purpose category, request path without query parameters, referrer host when supplied, response status, privacy-safe crawler fingerprint, shortened crawler User-Agent, request classification, WordPress content ID, identity label, and policy action. Human AI-referral events do not store a browser fingerprint or User-Agent.
Raw IP addresses are not stored. No telemetry or activity data are transmitted to the plugin author. Site owners remain responsible for assessing their own legal obligations and updating privacy notices where required.