Supported
Not possible
These platforms render pages on infrastructure you cannot run code on, and expose no request log. There is no workaround, and any vendor claiming otherwise with a JavaScript snippet is measuring browsers, not crawlers.
If you are on one of these and AI visibility matters to you, AI Visibility measures whether assistants actually cite you - which is the outcome crawl data is a proxy for anyway.
What no platform can measure
Not a gap in our coverage. These produce no request to your server at all, so nothing on any platform can see them.- Google AI Overviews and AI Mode. Answered from the Search index. Your origin is never contacted.
- Anything a model learned during training. A crawler read the page once, possibly years ago. Every later answer drawing on it is invisible.
- Assistants answering from a third-party index. If a surface reuses Bing’s index, the fetch was Bing’s, not the assistant’s.
Caching
This bites hardest on WordPress, where WP Rocket, LiteSpeed, W3 Total Cache and most managed hosts serve stored HTML without booting WordPress. The plugin ships a coverage check under SnowSEO → AI Crawlers that fires two identical requests at your site and reports how many actually reached WordPress, so you get a real number rather than a guess. Markdown responses are excluded from the cache automatically, so.md fetches - which is where most assistant traffic goes once you have Markdown twins - are counted in full.
A CDN cache in front of your origin (Cloudflare, Fastly, a host edge) has the same effect on any platform. Only a worker running at that edge can see those requests.