Safe Official docs Search Engines

Baiduspider

Operated by Baidu

Quick Facts

User-Agent:
Baiduspider
Category:
Search Engines
Operator:
Baidu
Safety:
Safe
Blocking Impact:
Critical - Blocking removes you from search results
SEO Impact Score:
10/10
Official docs:
help.baidu.com

Confirmed by the operator

Baidu names Baiduspider on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Baiduspider?

Baiduspider is the official web crawler for Baidu, China's leading search engine. It is essential for having your website indexed and visible to users in China.

Baiduspider is the official web crawler for Baidu, China's leading search engine. It is essential for having your website indexed and visible to users in China.
Baiduspider is a production-grade search engine crawler operated by Baidu. It uses a distributed crawl infrastructure that respects crawl-delay directives, follows RFC 9309 (robots.txt) spec, and processes Sitemaps to prioritise fresh content. The user-agent string Baiduspider must be whitelisted if your site uses rate-limiting or WAF rules. Blocking impact is Critical - Blocking removes you from search results.

What happens if you block Baiduspider?

⛔ Critical Impact - Blocking Baiduspider will stop Baidu from crawling and indexing your pages. Within days or weeks you may see pages drop out of Baidu's search index entirely, resulting in a significant loss of organic search traffic. This is the most severe possible SEO consequence. Only do this intentionally, for example if you are migrating to a different search engine or decommissioning a domain. If you accidentally blocked Baiduspider, remove the rule immediately and request re-indexing via Baidu's webmaster tools.
Never block - it will remove your site from major search results.

How to block Baiduspider with robots.txt

<code>User-agent: Baiduspider</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: Baiduspider Disallow: /
Allow all (robots.txt)
User-agent: Baiduspider Allow: /
Block private only (robots.txt)
User-agent: Baiduspider Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Baiduspider if ($http_user_agent ~* "Baiduspider") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Baiduspider SetEnvIfNoCase User-Agent "Baiduspider" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Baiduspider safe to allow?

Yes, Baiduspider is a safe and legitimate crawler. It is operated by Baidu, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string Baiduspider is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).
Verify by reverse-DNS lookup: legitimate Baiduspider requests resolve to baidu's domain.

What does Baiduspider do?

Understanding Baiduspider's purpose helps you decide whether to allow or block it.

  • Crawls and indexes web pages for search results
  • Discovers new and updated content on your website
  • Analyzes page structure, content, and links for ranking
  • Renders JavaScript to understand dynamic content
  • Checks for mobile-friendliness and page speed

Baiduspider in context

Baiduspider is a search engine crawler operated by Baidu. In plain terms, it builds a search or answer index. Our database files it under search engines and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 62 of the 63 search engines in our database share this tier.

Its safety rating is safe and its blocking impact is critical. So Baiduspider is both well behaved and costly to lose: the strongest case for allowing it. How we rate safety and impact.

How site owners treat Baiduspider

Our robots.txt study of the Tranco top 10,000 did not track Baiduspider as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Baiduspider's operator does not clearly document how it treats robots.txt. Write the Baiduspider rule anyway, then confirm in your logs that its requests stop.

Baidu crawlers and close alternatives

Baiduspider is one of 10 Baidu crawlers in our database. A User-agent: Baiduspider group controls Baiduspider only; the other Baidu tokens below need their own lines.

  • Baiduspider: this crawler (Tier 3)
  • baidu: baidu, builds a search or answer index (Tier 3)
  • Baiduspider-ads: Baidu Business Search, checks pages for an SEO, uptime or analytics service (Tier 3)
  • Baiduspider-cpro: Baidu Union, checks pages for an SEO, uptime or analytics service (Tier 3)
  • Baiduspider-favo: Baidu Bookmark, builds a search or answer index (Tier 3)
  • Baiduspider-image: Baidu Image Search, builds a search or answer index (Tier 3)
  • Baiduspider-news: Baidu News Search, builds a search or answer index (Tier 3)
  • Baiduspider-video: Baidu Video Search, builds a search or answer index (Tier 3)
  • ERNIEBot: ERNIE (Baidu), collects pages to train AI models (Tier 2)

To give Baiduspider the same answer as its siblings, stack User-agent: Baiduspider with their lines above one set of rules; to treat Baiduspider differently, give it its own group.

Other search engines that do the same job (builds a search or answer index) include Amzn-SearchBot from Amazon, Applebot from Apple, bingbot from Microsoft, BingPreview from Microsoft, BingVideoPreview from Microsoft, DuckDuckBot from DuckDuckGo. Deciding about Baiduspider is usually a decision about the whole group, so check how your file treats these too.

We first recorded Baiduspider on March 17, 2026. Baidu documents it on help.baidu.com, and we recheck that page before each release.

Which rule Baiduspider actually follows

Baiduspider reads exactly one group in robots.txt, the most specific one that names Baiduspider, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Baiduspider
Disallow: /drafts/
  1. Find the group. Baiduspider looks for a group naming Baiduspider. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Baiduspider, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Baiduspider if the file also has a User-agent: Baiduspider group?

No. Once a group names it, Baiduspider reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Baiduspider remove your pages from AI answers?

Often, yes. Baiduspider is a search engine crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: baiduspider the same as User-agent: Baiduspider?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Baiduspider? Decide by situation

Recommended setting for Baiduspider by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. It is how this search engine finds your pages.
You license content and want to stop AI trainingBlocking it does not stop training, because Baiduspider is a search engine crawler. Block the operator's training crawler instead.
You run an online shopAllow it unless it is overloading your servers.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Baiduspider on your own site

  1. Open /robots.txt on your domain and search for Baiduspider. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Baiduspider follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Baiduspider even when robots.txt allows it, and that never shows in the file.
  4. Run our AI crawler access test to see how Baiduspider and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Baiduspider

The errors we see most often with Baiduspider in the files and firewalls we test:

  1. Blocking Baiduspider to save bandwidth and then wondering why pages drop out of that search engine. Use crawl-rate settings or caching first.
  2. Writing a User-agent: Baiduspider group to add one rule for Baiduspider and accidentally dropping every rule it used to follow under User-agent: *.
  3. Disallowing CSS and JavaScript folders, which can stop Baiduspider rendering your pages properly.

All three hide inside a file that looks correct, so check Baiduspider from outside after every change.

Spotting Baiduspider in your logs

robots.txt says what Baiduspider may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "Baiduspider" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "Baiduspider" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Baiduspider user-agent, so confirm the source before acting on a match:

  • Baiduspider: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Baiduspider request with caution.

Frequently Asked Questions

What is the official user-agent string for Baiduspider?
The official user-agent string for Baiduspider is: Baiduspider. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from Baiduspider by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.
Is Baiduspider safe?
Yes, Baiduspider is a safe and legitimate crawler. It is operated by Baidu, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string Baiduspider is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).
Will blocking Baiduspider hurt my SEO?
⛔ Critical Impact - Blocking Baiduspider will stop Baidu from crawling and indexing your pages. Within days or weeks you may see pages drop out of Baidu's search index entirely, resulting in a significant loss of organic search traffic. This is the most severe possible SEO consequence. Only do this intentionally, for example if you are migrating to a different search engine or decommissioning a domain. If you accidentally blocked Baiduspider, remove the rule immediately and request re-indexing via Baidu's webmaster tools.
How do I block Baiduspider in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: Baiduspider
Disallow: /

This instructs Baiduspider not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt.
Does Baiduspider respect robots.txt?
Yes - Baiduspider is a well-behaved bot operated by Baidu. It fetches and parses /robots.txt before crawling any page, following RFC 9309.
How do I verify if Baiduspider is crawling my site?
Search your web server access logs for the string Baiduspider (case-insensitive grep: grep -i "Baiduspider" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For Baiduspider specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).
What is the crawl frequency of Baiduspider?
Critical-impact search crawlers like Baiduspider typically crawl popular pages daily and less popular pages weekly. You can manage crawl rate via the crawl-delay directive or via the search console.
Can I block Baiduspider from specific pages only?
Yes. Instead of a global Disallow: / you can restrict Baiduspider to specific paths:
User-agent: Baiduspider
Disallow: /private/
Disallow: /staging/
Allow: /

This allows Baiduspider everywhere except the listed paths. Path matching in robots.txt uses prefix matching - Disallow: /private/ blocks /private/page.html but NOT /public/private/.
How do I check if Baiduspider is blocked by my robots.txt?
Use Google's robots.txt Tester in Search Console, or a third-party checker to simulate a Baiduspider request. You can also manually check by opening https://aicrawlercheck.com/robots.txt and scanning for Baiduspider entries. If a block exists, immediately test it against your most important URLs using the Google Search Console URL Inspection tool.
My site is blocked by Baiduspider in Search Console - what do I do?
1. Open yourdomain.com/robots.txt and look for any User-agent: Baiduspider or User-agent: * Disallow rules covering your key pages.
2. Remove or restrict the blocking rules.
3. Validate via Google Search Console → robots.txt Tester.
4. Request re-indexing using the URL Inspection tool.
5. Wait 1-2 weeks for re-crawl. Monitor Coverage report for recovery.
WhatsApp us