# Slackbot-LinkExpanding

> Fetches a page to build the unfurl card when somebody pastes your link into Slack. One paste, one fetch.

| field | value |
|---|---|
| operator | Slack |
| category | Link preview fetchers |
| robots.txt token | `Slackbot-LinkExpanding` |
| user-agent contains | `Slackbot-LinkExpanding` |
| robots.txt | obeys robots.txt (documented) |
| verify by | no published verification method |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://api.slack.com/robots |
| last reviewed | 2026-09-14 |

## What blocking it costs you

Your links appear in Slack as bare URLs. Inside working teams that quietly costs you clicks, and nothing is gained.

## Full user-agent string

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

## Block it

```
User-agent: Slackbot-LinkExpanding
Disallow: /
```

## Allow it

```
User-agent: Slackbot-LinkExpanding
Allow: /
```

## Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

- **How do I prove a request really is Slackbot-LinkExpanding?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=slackbot-linkexpanding&s=client-dossiers'`  
  The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error.

JSON: https://www.pathwren.workers.dev/crawler/slackbot-linkexpanding.json · index: https://www.pathwren.workers.dev/llms.txt