Currently writes to aiVisibilityRequestLog happen only on successful 2xx responses to the package's three Markdown surfaces: - /llms.txt - /llms-full.txt - Per-page Markdown (either .md direct, or Accept: text/markdown content negotiation on the canonical URL) So it's only AI-crawler / Markdown-route traffic. NOT regular HTML page views. Standard /about/ browsing by humans doesn't touch the log. Other relevant bits: - Skipped on 304 / 404 / 500 (cache revalidation + miss paths don't double-count) - Async fire-and-forget — bounded channel drained in batches by a hosted service, doesn't block response time - 90-day retention by default; background job purges older rows - Kill switch via AiVisibility:RequestLog:Enabled = false - IRequestLog is a public extension point if you want to redirect writes to App Insights, Serilog, or a different sink