Skip to main content
A full-page cache can answer a request without PHP running, and then the plugin never sees the visit. Crawlers often read cached pages, so without help your crawler counts would look low.

​
WordPress page caches: handled

With Let AI and search crawlers bypass the page cache turned on (the default), the plugin writes a small block to the top of your .htaccess:
For AI and search crawler user agents only, the rule routes the request past the page cache to WordPress so it is logged. Visitors still get cached pages. When a crawler request reaches PHP, the plugin also tells the cache not to store that response. Works with FlyingPress, WP Rocket, LiteSpeed Cache, WP Super Cache and LiteSpeed’s server cache. The rules are written only while logging is on and are removed when you turn logging or the bypass setting off, deactivate the plugin or uninstall it.

​
Check it

On Settings → RankRaft AI → Status, click Check cache bypass. The plugin requests your homepage as a test crawler and confirms the request reached WordPress. The .htaccess rules row shows one of:

​
Caches in front of your server: use Cloudflare

Caches that sit in front of WordPress, such as Cloudflare, another CDN or a managed host’s Nginx cache, answer requests before they reach your server. Nothing inside WordPress can see those requests. If your site is on Cloudflare, add the Cloudflare integration as well. It sees every request, cached or not. You can keep the plugin running alongside it.
If you are upgrading from a pre-release build named “RankRaft Agent Analytics”, deactivate it before installing RankRaft AI Analytics. Deactivation removes its .htaccess block. Installing over the top leaves an orphaned block behind.