Operator
Slack
Slack runs 6 bots across 2 agent types. Each one is a separate user-agent so you can allow or block them independently.
Slack Image Proxy is operated by Slack. Single-page fetch triggered by a user action, link previews, social unfurlers, RSS readers. Volume tracks shares and clicks rather than crawl schedules.
Slack-AI-Bot is operated by Slack. Fetches a page in real time when an LLM is mid-answer to a user question. Traffic spikes correlate with question volume rather than crawl schedules, so it shows up unpredictably.
Slack-ImgProxy is operated by Slack. Single-page fetch triggered by a user action, link previews, social unfurlers, RSS readers. Volume tracks shares and clicks rather than crawl schedules.
Slackbot is operated by Slack. Single-page fetch triggered by a user action, link previews, social unfurlers, RSS readers. Volume tracks shares and clicks rather than crawl schedules.
Slackbot-LinkExpanding is operated by Slack. Single-page fetch triggered by a user action, link previews, social unfurlers, RSS readers. Volume tracks shares and clicks rather than crawl schedules.
SlackbotLinkExpanding is operated by Slack. Single-page fetch triggered by a user action, link previews, social unfurlers, RSS readers. Volume tracks shares and clicks rather than crawl schedules.
Live data · via Cloudflare Radar
See how Slack's bots show up in real internet traffic
Cloudflare Radar publishes a continuously-updating view of AI bot activity across the websites Cloudflare protects. You can see which user-agents drive the most requests, how that share shifts week to week, and which industries each bot crawls hardest. The data refreshes on Cloudflare's side, so the link below is always current.
Open Cloudflare Radar AI InsightsWhat you'll find there
- ·User-agent share for every tracked AI bot, including Slack's
- ·Robots.txt and crawl-purpose breakdowns per operator
- ·Industry and content-type targets for each crawler
- ·Time-series trends going back several months