AI Bot Analytics: Read Local Crawler Activity
Bot Analytics logs requests whose User-Agent matches a known AI-related pattern when they reach WordPress. Use it to inspect activity and collection gaps.
Read the dashboard
- Open citelayer® → Bot Analytics and choose a period.
- Compare the trend with top matched bot names and categories.
- Open Crawler Logs to inspect the paths behind a spike.
- Keep the human AI Referrals tab separate from automated requests.
What a match establishes
A match identifies a claimed User-Agent pattern, not a cryptographically verified provider. Some patterns are categorized as possible AI. Google-Extended is a robots control token, not a separate HTTP request User-Agent; its absence from logs says nothing about Gemini usage.
Repeated crawler requests are not human visitors or citations. Read the log fields before reporting results.
Collection and retention
Logs live in the site’s database. IP logging is optional and off by default; records normally expire after 90 days. Full-page caches and CDNs can answer requests before the WordPress logging hook runs. See cache setup.
Use the data to decide a next check
Inspect whether important paths return useful content and whether sudden changes match cache/WAF/deployment changes. Compare recognized referral visits separately. A quiet bot graph alone is not a reason to add unsupported schema or pad an article.
Next step
Continue with the quick start checklist, or check the common questions. For a reproducible problem, send the plugin versions, affected URL, expected result and actual response through Support. Do not include passwords, license keys or customer details.
Reviewed 6 October 2026 against citelayer® Free 1.13.5, WooCommerce add-on 1.2.19 and EDD add-on 1.2.1. Features depend on the active components and settings on your site.