# DuckAssistBot

DuckAssistBot fetches a page live when a DuckDuckGo's AI-assisted answers user's question needs it, for example when the user pastes a link or the assistant decides to read a source. A visit from it is a strong signal that your page is being used in a real answer.

## Should you allow DuckAssistBot?

**Allow it.** DuckAssistBot acts for a person who is asking about your page right now. Blocking it means the assistant answers without your page, often citing someone else instead.

## robots.txt

To allow DuckAssistBot everywhere:

```text
User-agent: DuckAssistBot
Allow: /
```

To block it:

```text
User-agent: DuckAssistBot
Disallow: /
```

Bots follow the most specific `User-agent` group that matches them. If you have a `User-agent: DuckAssistBot` group, the rules under `User-agent: *` no longer apply to it. Matching on the token is case-insensitive.

## Identifying DuckAssistBot

DuckAssistBot identifies itself with `DuckAssistBot` in its `User-Agent` header. It **does not run JavaScript**: it reads the raw HTML only. Content your site adds with JavaScript is invisible to it.

DuckDuckGo doesn't publish a machine-readable IP range list for DuckAssistBot that we verify against, so treat the user agent alone as unverified. `bots_report` marks these hits as unverifiable rather than genuine.

## Check your site

```bash
llmentions audit example.com            # is DuckAssistBot allowed by robots.txt, and what does it see?
llmentions bots /var/log/nginx/access.log   # did DuckAssistBot really visit, and is it genuine?
```

Or identify any user agent over REST (free): `GET https://api.llmentions.com/v1/bots/lookup?ua=DuckAssistBot`.

---
https://llmentions.com/bots/duckassistbot/
