Slackbot

Operator

Slack

Type

Crawler

Official page

api.slack.com

Follows robots.txt

No, according to Slack.

In Vireo

Excluded, reported under Link previews

What it does

Slack's general-purpose fetcher for any HTTP request its link-expanding and image-proxy agents don't cover, such as integration API calls and outgoing webhooks.

This is our default, does everything, kitchen sink robot. Anytime we need to make an HTTP request that is not covered by the above, we use this robot.

Slack

User agent

Requests from Slackbot carry a user agent like this:

Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots)

Device Detector identifies it with this pattern (a case-insensitive regular expression):

Slackbot|Slack-ImgProxy

Anyone can put any name in a user agent. Where the operator publishes IP ranges, checking the request's address against them is the way to confirm a visit is genuine.

Worth knowing

Slack ignores robots.txt for all its agents. Link previews come from Slackbot-LinkExpanding. To be blocked from Slack embeds you have to contact Slack.

If you would still like your site blocked from slack.com embeds, or would like changes to how your embeds are displayed, please contact us.

Slack

How Vireo counts Slackbot

Vireo keeps requests from Slackbot out of your pageviews and visitors and counts them on its bot report under Link previews, so you can see how much it left out rather than wonder why your server logs show more traffic.

Checked by running Vireo Analytics' own bot filter over Slackbot's user agents.

Sources

• Slack: crawler documentation (checked October 2026)
• Matomo Device Detector, bots.yml (LGPL-3.0)