Baiduspider
Baiduspider is a search-engine crawler operated by Baidu. Its job is to find, fetch, and index web pages so they can be returned in organic search results.
Traffic is regular and bounded by your robots.txt. Allowing it is generally how your site stays discoverable through the corresponding search engine, blocking it almost always reduces visibility there.
For most sites, search-engine crawlers are still the largest source of bot traffic and the largest source of human visitors that follow.
See Baiduspider on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
Published IP ranges
Crawl frequency
Continuous
Honors robots.txt
Yes
Honors Crawl-delay
Yes
Baidu runs 11 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Search Engine
6- BaiduspiderYou are here
- Baiduspider-render
- Baidu ADS Server Proxy
- Baiduspider-favo
- Baiduspider-mobile
- BaiduMobaider
Link Unfurler
2Security Scanner
1Share of AI bot traffic
4.0%
↓ 17% vs 12 mo ago
% of top sites blocking it
4.0%
↑ 18% vs 12 mo ago
Top page categories crawled
Search Engines as a category, share of all bot traffic
66%
↓ 6% vs 12 mo ago
Sum of every search engine we have public stats on. Compare to Baiduspider's individual trend above to see if it's pulling ahead of its category or falling behind.
Crawl-to-click ratio
52 : 1
For every 1,000 fetches, this agent sends ~19 human visits back. Cloudflare crawl-to-click data
Snapshot updated
2026-04
Connect Agent Analytics for daily, per-site numbers.
Should I let Baiduspider through?
In most cases, yes. Blocking traditional search crawlers reduces organic-search visibility. Allowing is the default for almost all sites. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Baiduspider affect my Google rankings?
Only on Baidu Baiduspider feeds. Each search engine runs its own crawler, so blocking Baiduspider only removes you from that one index. Your visibility on Google, Bing, or anything else is untouched.
How do I confirm a request is really from Baiduspider?
Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be Baiduspider", not "the traffic is genuinely Baiduspider". If you need stronger guarantees, look for a reverse-DNS check or wait for Baidu to publish IP ranges.
What happens to my traffic if I block Baiduspider?
Your pages drop out of Baidu's index, which means losing the organic share you get from that engine. Not catastrophic if Baidu is a minor player, much more painful if it's a meaningful source of your traffic. Check your analytics for Baidu's actual referral share before deciding.
How is Baiduspider different from Baidu's other bots?
Baidu splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Baidu family above to see which ones actually matter for your site.
What's the cleanest way to control Baiduspider?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.