`Baiduspider-ads`

Baidu's English FAQ lists Baiduspider-ads as business search. It says pages this crawler fetches are not built into the index. The crawler works on the agreement set with customers and will not work on the records set by robots.txt. The page says to contact a customer service representative. The Chinese FAQ calls the product 商务搜索 and says it does not obey the robots protocol. This check does not apply that agreement and still reports the RFC 9309 decision. The page says blocking Baiduspider blocks all crawling from Baidu. This check matches the whole token and does not treat Baiduspider as a prefix.

robots.txt token: Baiduspider-ads
Operator: Baidu
Kind: ads_check
robots.txt: does_not_follow. The vendor says this crawler does not follow robots.txt rules.
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. The FAQ does not publish an IP list for this token. The verification section is about Baiduspider hostnames ending in .baidu.com or .baidu.jp. Botcard does not copy the example addresses.
Source: FAQs of Baiduspider. Retrieved 2026-10-18.

JSON

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

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Baiduspider-ads 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-ads\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["baiduspider-ads"]}}}'

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