Caching and Accurate AI Activity Logs
A full-page cache or CDN can serve a response before WordPress runs. That matters for both current content and completeness of local crawler logs.
What the plugin can detect
The analytics screen recognizes WP Rocket, LiteSpeed Cache, W3 Total Cache and WP Super Cache and offers setup guidance. Detection does not prove that a cache exclusion is active or that an upstream CDN passes every request to WordPress.
Verify one URL
- Record a public page response and a Markdown response.
- Inspect cache headers and the host/CDN configuration.
- Make a controlled request that reaches WordPress and compare its appearance in local logs.
- Compare ordinary cached responses and confirm current content without disabling caching globally.
Set exclusions deliberately
Follow the guidance for your actual cache and provider. Excluding all bots from caching can increase origin load, and trusting a User-Agent alone is not identity verification. Prefer the smallest change that fixes the observed collection or format problem.
If traffic still looks wrong
Check server/WAF logs where available, tracker scripts for referrals, response ownership and retention. A missing PHP log event may simply mean that the edge answered the request. Crawler logs and referrals provide different evidence.
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.