AI assistants like ChatGPT, Perplexity, Gemini and Claude are becoming a real traffic source, and a real audience for your content. Unlike single-purpose llms.txt generators, SanityAI Visibility Toolkit covers the full AI channel in one lightweight plugin: measurement (referral attribution across six analytics stacks and a real crawler activity log), control (per-bot robots.txt management, including physical files), and visibility (multilingual llms.txt):<\/p>\n\n
1. llms.txt generation<\/strong><\/p>\n\n Automatically serves a machine-readable guide to your site at 2. AI crawler control<\/strong><\/p>\n\n Decide, bot by bot, which AI crawlers may access your site, with a plain-language explanation of what each block actually costs you. The plugin distinguishes:<\/p>\n\n Rules are added to WordPress's robots.txt. Nothing is blocked by default.<\/p>\n\n 3. AI referral attribution<\/strong><\/p>\n\n Detects visitors arriving from ChatGPT, Perplexity, Gemini, Claude, Copilot, Grok, DeepSeek, Meta AI, Mistral and more, using both the referrer and utm_source\/ref parameters (AI platforms increasingly strip referrers, so UTM detection matters). Fires an Register 4. AI crawler activity log<\/strong><\/p>\n\n See which AI crawlers actually visit your site: a 30-day count of real GPTBot, ClaudeBot, PerplexityBot (and more) visits, shown on your dashboard and settings screen. Identification is by user agent, so treat numbers as directional.<\/p>\n\n Plays well with your stack<\/strong><\/p>\n\n The plugin detects your environment and tells you the truth about it instead of showing settings that silently do nothing:<\/p>\n\n\/llms.txt<\/code>, following the llms.txt convention. AI assistants can use it to understand your site structure and cite your best content. Choose which content types to include, how many items, whether to append descriptions, and which posts to exclude. Multilingual sites are fully supported: with WPML or Polylang active, every language gets its own sections. Cached and regenerated when content changes.<\/p>\n\n\n
ai_referral<\/code> event with an ai_source<\/code> parameter into your existing GA4 (gtag) or Google Tag Manager (dataLayer) setup, once per session.<\/p>\n\nai_source<\/code> as a GA4 custom dimension and you can segment any report by AI platform, build AI-traffic audiences, and see whether AI-referred visitors convert differently.<\/p>\n\n\n
wp avt status<\/code>, wp avt regenerate<\/code>), and a REST endpoint (\/wp-json\/sanivt\/v1\/sources<\/code>) for headless front ends.<\/li>\n<\/ul>\n\n