# Baiduspider-news

Baidu's FAQ lists Baiduspider-news as the News search user-agent. It says different user-agents can have different rules, and the user-agent it names as not supporting the rules is Baiduspider-video, not this token. Baiduspider-cpro and Baiduspider-ads are the tokens that do not follow robots.txt records. The page says blocking Baiduspider blocks all crawling from Baidu. This check matches the whole token and does not treat Baiduspider as a prefix.

- Operator: Baidu
- Kind: search
- robots.txt: obeys. The vendor says this crawler obeys robots.txt on automatic crawls.
- HTTP user-agent: The English FAQ names this robots.txt token and does not publish a full HTTP user-agent string.
- IP list: none on the cited page
- Source: https://help.baidu.com/question?prod_id=99&class=0&id=3001 (retrieved 2026-10-18)

## JSON

`curl -s https://whosthatbot.com/v1/crawlers/baiduspider-news`

## Check this token

tools/call with name check_robots is the same check at https://whosthatbot.com/mcp. Send `Content-Type: application/json` and `Accept: application/json, text/event-stream`. The pasted file disallows Baiduspider-news on `/docs` and allows `*`. The call does not fetch a host.

```
curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Baiduspider-news\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["baiduspider-news"]}}}'
```

That call returns fetched_target false. This row is disallow via group Baiduspider-news, rule Disallow: /.

Each card paraphrases the linked vendor page and was checked on source.retrieved. This is not legal advice. robots.txt is a request from the site owner. Botcard does not fetch third-party sites and does not suggest ways around a disallow rule.